Recent public statements from Public Services and Procurement Canada regarding alleged overbilling on federal contracts, together with related guidance from the Treasury Board of Canada Secretariat on professional services and digital talent, point to something larger than a single enforcement matter.
They point to a broader question that every public-sector technology supplier, consultant, project leader, and business owner should be willing to ask:
How do we make complex work trustworthy?
That question matters because modern technology delivery is no longer simple. Public institutions rely on systems, platforms, data, vendors, contractors, subcontractors, cloud services, cyber controls, project teams, and reporting structures that often span multiple departments and organizations.
In that environment, trust cannot depend only on reputation, résumés, rate cards, or professional language.
Trust has to be visible.
It has to be documented.
It has to be managed.
And it has to withstand scrutiny.
That is why I believe integrity is not branding. It is infrastructure.
Procurement Integrity Is a Delivery Standard
When professional services are used well, they can help government access specialized expertise, temporary capacity, independent advice, technical implementation support, and outcome-focused delivery capability that may not be available internally at the exact moment it is needed.
But when professional services are poorly structured, poorly governed, or poorly monitored, complexity itself becomes a risk. Work can become difficult to verify. Accountability can become diluted. Subcontracting chains can become opaque. Invoices can become disconnected from actual delivery.
Departments can become dependent on external parties without enough knowledge transfer. And public servants can be left trying to manage highly technical work without the control environment needed to understand what is happening beneath the surface.
This is not only a procurement issue.
It is a delivery issue.
It is a governance issue.
It is a public trust issue.
The future of professional services in government should not be reduced to a simple argument of “contract more” or “contract less.” The more important question is whether the work is justified, properly scoped, visibly managed, security-aware, outcome-driven, and documented in a way that protects the public interest.
Internal capacity should be respected and developed. External suppliers should be used where they bring real expertise, accountable delivery, transparent controls, knowledge transfer, and measurable value. In that model, procurement integrity is not a barrier to good suppliers. It is what separates serious delivery partners from opaque pass-through arrangements.
The Manager as Business Owner
One of the most important ideas in the recent federal guidance on procuring professional services is the role of the manager as a business owner.
That language matters.
A manager is not simply requesting “a resource.” A manager is responsible for defining the outcome, explaining why contracting is the appropriate path, working with procurement specialists, verifying that work was performed, ensuring invoices reflect actual delivery, documenting key decisions, and managing the contract through its lifecycle.
That is a major responsibility.
Approving a contract is not just an administrative act. Approving an invoice is not just paperwork. Accepting a deliverable is not just a checkpoint.
Each of those actions is part of stewardship.
For technology and digital work, this responsibility becomes even more important. Many digital initiatives are complex, fast-moving, and difficult for non-specialists to evaluate. A dashboard may look complete while underlying data is weak. A project schedule may look structured while dependencies are not understood. A supplier may appear credible while accountability is diffused through subcontracting layers. A system may be technically functional while governance, security, documentation, or knowledge transfer remain incomplete.
This is where strong delivery controls matter.
Good governance is not bureaucracy for its own sake. It is how complex work becomes legible.
It is how leaders can see what is happening.
It is how teams know what they are accountable for.
It is how suppliers demonstrate that they are doing the work they were trusted to do.
Digital Talent, Contracting, and the Right Use of External Support
The Directive on Digital Talent adds another important layer to this conversation. It makes clear that departments should consider government-wide digital talent capacity before defaulting to external contracting for digital or IT-related services.
That is a reasonable and important principle.
Government should build and protect its internal digital capability. Public institutions should not become unnecessarily dependent on outside suppliers for knowledge they should reasonably own, retain, or develop. Digital service delivery is now core public infrastructure, and internal talent matters. At the same time, there will continue to be legitimate cases where external support is needed.
Specialized expertise may be required. Temporary capacity may be necessary. Independent review may be appropriate. A complex implementation may require skills that are not available internally within the needed timeframe. A department may need help building a control environment, stabilizing delivery, integrating systems, improving reporting, or transferring knowledge back into the organization.
That is where external suppliers should be held to a higher standard.
A responsible technology supplier should not simply provide bodies into a process. A responsible supplier should help clarify the work, reduce ambiguity, strengthen visibility, support knowledge transfer, and leave the client with a stronger understanding of the system than they had before. That is the kind of external support government should be able to trust.
Why This Matters to Manage Your Tech, Ltd.
Manage Your Tech, Ltd. was built around a simple belief: complex technology work should be made understandable, governable, and accountable.
My professional background was built across IT delivery, systems integration, project and program governance, Microsoft 365 environments, scheduling, reporting, and PMO control structures — but not in theory alone. It was formed through boots-on-the-ground delivery across enterprise, infrastructure, manufacturing, cloud, data center, and global systems environments, where technical work often had to be translated across teams, cultures, time zones, leadership levels, and operating realities.
Across my career, I have seen how quickly technology work can become difficult to explain when the right controls are missing — and how important it is for capable technical people, business leaders, and delivery teams to share a common language of trust, evidence, and accountability.
I have also seen how much trust is required to do this work properly.
When someone is asked to support a technology environment, delivery program, reporting system, or modernization effort, they are often being trusted with more than tasks.
They are being trusted with operational context, sensitive information, institutional priorities, financial decisions, project risk, and sometimes the confidence of people who do not have the technical depth to validate every detail themselves.
That trust should never be treated casually.
For MYT, this is why proof matters. Documentation matters. Clear scope matters. Delivery controls matter. Subcontractor transparency matters. Security awareness matters. Knowledge transfer matters. Reporting matters. The ability to explain complex systems in plain language matters.
These are not cosmetic features of a professional services firm.
They are the work.
The Problem With Surface Credibility
One of the challenges in the modern IT and project delivery market is that credibility can be easy to perform and difficult to verify.
Professional titles, certifications, polished profiles, and confident language can create the appearance of capability. In many cases, people are acting in good faith and simply working within the standards they have been taught. But the gap between surface credibility and real delivery depth can become dangerous when the work involves public systems, sensitive data, complex integrations, or taxpayer-funded contracts.
This is especially true in technology, where complexity can be used unintentionally or intentionally to obscure weak delivery. A non-technical stakeholder may not know whether a system architecture is sound. A project sponsor may not know whether a schedule is realistic. A procurement team may not know whether a résumé reflects deep capability or only broad exposure. A department may not know whether a supplier is truly managing subcontractors or merely passing work through a chain.
That is why the next generation of public-sector technology delivery needs more than professional appearance.
It needs evidence.
It needs accountable structures.
It needs suppliers who are comfortable being examined.
It needs people who can explain what they are doing, why they are doing it, how progress is being measured, where the risks are, and what will remain with the organization after the contract ends.
The Kind of Supplier I Am Trying to Build
MYT is being built with a different kind of discipline: not as a pass-through layer, and not as an inflated appearance of scale, but as a small, serious Canadian technology and PMO delivery company with clear accountability for the work it accepts.
The standard I am working toward is simple: be clear about capability, be honest about capacity, manage specialized support transparently, and remain accountable for delivery.
In complex technology work, trust depends on that clarity.
I am building MYT as a small, serious Canadian technology and PMO delivery company that can operate with transparency, technical fluency, governance discipline, and respect for the institutions it serves.
That includes being clear about where MYT has direct capability, where specialized subcontracting may be appropriate, how subcontractors would be managed, what outcomes are being pursued, what evidence supports delivery, and how knowledge can be transferred back to the client.
Small suppliers should not be excluded simply because they are small. But small suppliers should also be willing to meet serious standards of accountability.
That is the balance.
The public sector needs access to capable small and regional firms. It also needs safeguards against opacity, weak oversight, and supplier arrangements that make accountability harder to trace.
Those goals are not in conflict.
They belong together.
A Personal Note on Standards
This is not a moral positioning exercise. It is a professional standard.
I have spent much of my career around complex systems, high-pressure delivery environments, and organizations where technology decisions carry real operational consequences. I know what it feels like when work is not understood clearly by the people responsible for approving it.
I know how easily complexity can create distance between decision-makers and reality. I also know how difficult it can be for principled, transparent operators to be seen in a market that sometimes rewards confidence, access, and intermediation before evidence.
That experience has shaped my view of this work. At this stage of my life and career, I am proud to support a procurement direction that asks harder questions, expects better documentation, strengthens internal capacity, improves oversight, and creates space for suppliers who are willing to operate transparently.
That is not a threat to good suppliers.
It is an opportunity.
Closing Reflection
Public-sector technology delivery is not just about systems. It is about stewardship.
It is about whether public institutions can trust the people and companies brought in to support them. It is about whether work can be verified. It is about whether knowledge remains inside the organization. It is about whether suppliers understand that public money, public systems, and public trust carry a higher duty of care.
For Manage Your Tech, Ltd., that is the standard I want to keep building toward: a practical, visible form of integrity that shows up in the way work is scoped, governed, delivered, documented, and handed back.
Because in public-sector technology delivery, integrity is not a slogan.
It is infrastructure.
_______________________________________________________________________________________________________________________
Note: This reflection draws on recent Government of Canada public statements regarding alleged overbilling on federal contracts, together with related federal guidance on professional services procurement, digital talent, and supplier accountability.
____________________________________________________________________________________________________________________________________
