Government Architecture and GSRM: Why Public Sector Transformation Keeps Failing at the Operating Model
In 2003, Canada ranked sixth globally on the United Nations E-Government Development Index. By 2022, that ranking had fallen to thirty-second. Only 23 percent of Government of Canada services are available online end-to-end. Only 35 percent of Canadians are satisfied with their digital government service experiences, according to Adobe's 2025 Digital Government Index for Canada. In 2025, 60 percent of public servants attending the AccelerateGOV conference identified legacy systems and integration challenges as a major or significant barrier to digital transformation.
The decline in Canada's relative position is not primarily a technology investment problem. The federal government spends billions annually on IT. Shared Services Canada's Digital Together program, Budget 2025 priorities, and the Government of Canada's Digital Ambition all represent substantial and sustained commitment to digital modernization. The problem, as Scott Jones, President of Shared Services Canada, articulated precisely at AccelerateGOV 2025, is architectural: government is organized in departmental verticals and the need to connect those together horizontally, to enable enterprise platforms rather than isolated departmental solutions, is the structural challenge that technology investment alone cannot solve.
That is a business architecture problem, and it is one that the Government of Canada has been working to address for over two decades through the GC Enterprise Architecture Framework, the GSRM, and a sustained effort to embed architecture thinking into how the public service plans and transforms. Understanding what those frameworks are, why they matter, and where they consistently fall short is useful for everyone working in or with the Canadian public sector on transformation programs.
What the GSRM Is and What It Is For
The Government of Canada Strategic Reference Model, or GSRM, is the GC's equivalent of the industry reference models described in the industry reference models post in this series. It is a government-wide reference architecture that provides a common vocabulary and taxonomy for describing what the federal government does, organized as a hierarchy of business lines, programs, services, and activities.
The GSRM was developed by Treasury Board Secretariat to serve several specific purposes. It provides the standard business classification used in the Program Activity Architecture, which is the structure through which departments report on their programs and activities for accountability and performance measurement purposes. It enables portfolio and investment management by providing a common language for comparing what different departments do and identifying where similar functions are being performed in parallel across the government. And it supports architecture governance by giving the GC Enterprise Architecture Review Board a consistent framework for assessing whether proposed investments align with government-wide capabilities and reduce duplication rather than compound it.
The GSRM has been tested as an extension of the UN's Universal Meta-Model, with the objective of creating a pan-Canadian and potentially internationally adoptable government business reference model. That ambition reflects the GSRM's position as one of the more mature government business reference models globally, at least in its design intent if not always in its operational application.
The honest assessment of the GSRM in practice is similar to the honest assessment of BIAN in banking: it is most valuable as a vocabulary and a classification tool for government-wide portfolio management and investment comparison, and less valuable as a prescriptive framework for how individual departments should design their operating models, programs, or service delivery approaches. The GSRM describes what government does at a level of abstraction that is appropriate for government-wide governance. Individual departments need a more specific capability model to inform their own transformation decisions, and the GSRM provides the taxonomy within which that more specific model should be expressed rather than the model itself.
The GC Enterprise Architecture Framework
The Government of Canada Enterprise Architecture Framework, updated through 2025, establishes the principles, standards, and review processes that govern enterprise architecture across the federal government. It defines five architecture domains: business, application, data, technology, and security, and provides guidance on how each domain should be designed and governed in alignment with the GC's Digital Ambition.
The GC EA Framework is the governance structure that operationalizes the GSRM and other GC-wide architecture standards. The GC Enterprise Architecture Review Board, co-chaired by Treasury Board Secretariat, reviews proposals for new digital solutions and investments above defined thresholds to assess their alignment with enterprise architecture principles and their contribution to the overall GC digital ecosystem rather than to departmental IT inventories.
The business architecture domain within the GC EA Framework is described as critical for the successful implementation of the GC Enterprise Ecosystem Target Architecture. It encompasses the mandate, programs, and services of the GC, as well as the business capabilities that support them. The framework explicitly recognizes that business architecture is the foundational layer that should inform all other architecture decisions, and that investment in application, data, and technology architecture without a clear business architecture basis produces the departmental verticals problem that the President of Shared Services Canada identified at AccelerateGOV as the primary structural constraint on government-wide digital progress.
Why Government Transformation Keeps Failing at the Operating Model
The structural challenges of government transformation in Canada are distinct from those in the private sector in several ways that are worth being explicit about, because applying private sector transformation frameworks to government contexts without accounting for these differences consistently produces frustration and underperformance.
Departmental Sovereignty and the Horizontal Problem
The Canadian federal government is organized around departments that are legally independent entities with their own Ministers, Deputy Heads, and accountability structures. This legal and constitutional structure creates organizational incentives that are aligned with departmental performance rather than whole-of-government outcomes. A department that builds its own HR system, its own grants management system, or its own citizen service portal is meeting its mandate and its accountability requirements. The fact that seventeen other departments have done the same thing at collective cost many times greater than a shared solution would have required is not primarily that department's accountability problem.
This structure is not a governance failure. It reflects the constitutional reality of responsible government and the separation of ministerial accountability. But it creates the horizontal connection problem that Scott Jones identified: the architecture of government is designed for vertical accountability, and the technology solutions that have been built over decades reflect that design. Connecting them horizontally requires either enterprise platforms with sufficient mandate and funding to override departmental preferences, or architecture governance with sufficient authority to prevent new departmental verticals from being built, or both.
The operating model design work required to address this problem is genuinely difficult because it requires changing the decision rights, governance structures, and resource allocation mechanisms that produce the departmental vertical pattern, without overriding the accountability structures that make responsible government work. That is a more constrained design space than most operating model design challenges in the private sector, and it requires architecture practitioners who understand the public sector governance context rather than those who apply private sector operating model frameworks directly.
Legacy Systems That Cannot Be Turned Off
The Government of Canada Service and Digital Target Enterprise Architecture White Paper describes the legacy system problem precisely: the life cycle evolution of individual systems tended to limit their scope to those individual systems, reinforced by a desire to restrict procurement, technical, and change complexity and risk. Current technologies that could implement cohesive enterprise approaches were introduced relatively recently, many years after most government systems were implemented.
The result is a technology landscape where core business processes are embedded in systems that cannot be easily replaced because they encode decades of policy logic, program rules, and operational procedures that are not fully documented anywhere. Replacing them requires understanding exactly what they do, which requires either reversing-engineering code that was written before many current public servants were born, or accepting that the replacement will behave differently in edge cases that nobody can fully enumerate in advance.
This is the context in which the GC Enterprise Architecture Review Board's guidance on capability-based investment planning matters most. Decisions about which legacy systems to modernize, in what sequence, and toward which target architecture need to be grounded in a capability model that identifies what each system does for which programs and services, how critical that capability is to the GC's priority outcomes, and what the dependency chain looks like for replacing it. Without that model, modernization decisions are made on the basis of technical age rather than strategic importance, and the result is technology renewal that improves the parts of the estate that are easiest to replace rather than the parts that most constrain government's ability to serve Canadians.
Political and Mandate Cycles That Interrupt Long Programs
Government transformation programs that take five to ten years to complete span multiple elections, multiple ministers, multiple deputy heads, and often multiple changes in government. Each transition brings the risk of reprioritization, scope change, or cancellation of programs that were designed and funded under a different political direction. This structural risk is not present in private sector transformation to the same degree, because corporate leadership changes do not typically carry the same mandate reset that political transitions do.
Architecture governance in government needs to be designed to survive these transitions rather than assuming their absence. The frameworks, the capability models, and the governance structures need to be embedded in the public service's operational processes rather than in any particular political program, because the operational processes persist through political transitions in a way that specific programs do not. The GC EA Framework's approach of embedding architecture governance into project management policy and budget processes, rather than maintaining it as a separate architecture program, reflects this principle: architecture that is woven into how the public service operates is more durable than architecture that depends on continued political sponsorship.
The Capability-Based Investment Case in the Public Sector
The capability heat map approach described earlier in this series applies in government with important modifications. The two dimensions of strategic importance and current performance remain relevant, but their content needs to reflect the public sector context.
Strategic importance in government is not defined by competitive differentiation or revenue generation. It is defined by the centrality of the capability to delivering the programs and services that constitute the department's mandate, and by the degree to which the capability's performance affects citizen outcomes. A capability that is central to delivering a major benefit program affecting millions of Canadians is strategic regardless of whether it is technically interesting or whether it offers competitive advantage. A capability that supports an internal administrative function that could be consolidated across departments into a shared service is a candidate for rationalization regardless of how much the department has invested in it historically.
Current performance in government needs to account for both the technical performance of the systems supporting the capability and the operational performance of the processes using those systems. A capability supported by a modern, well-maintained system that is poorly utilized because the processes around it are designed for a different era is performing poorly from a citizen outcome perspective even though the technology is adequate. The capability model needs to assess both dimensions to produce a meaningful investment case.
The investment case that connects capability gaps to budget requests is the mechanism through which capability mapping produces its primary public sector value. Treasury Board Secretariat's Program Activity Architecture and departmental planning processes require departments to justify investments against program outcomes. A capability model that traces specific investment proposals to specific capability gaps, and traces those gaps to specific program performance limitations, produces a budget request that is more defensible and more likely to survive scrutiny than one based on technical obsolescence alone.
Where Business Architecture Produces the Most Value in the Canadian Public Sector
Three specific application areas consistently produce the most defensible return from business architecture investment in the federal and provincial public sector contexts.
Shared services design and consolidation. The horizontal connection problem is most tractable at the level of enterprise shared services: functions that every department needs but that each department currently maintains independently. HR, finance, procurement, case management, grants management, and citizen identity verification are all candidates for shared service consolidation. The architecture work required to design a shared service that actually serves multiple departments is a capability analysis problem: what capabilities do different departments need from this function, where do those capabilities converge enough to be served by a common platform, and where do they diverge enough to require department-specific design? The shared services design capability at ClarityArc works through exactly this analysis.
AI governance and digital transformation readiness. The GC's Digital Ambition and the AIDA legislation advancing through Parliament are creating an AI governance imperative for federal departments. The responsible AI framework and AI readiness assessment described in this series apply directly to the public sector context, with the added complexity of the Privacy Act, the Access to Information Act, departmental security requirements, and the algorithmic impact assessment requirements that the federal government's Directive on Automated Decision-Making imposes on AI systems that affect citizens' rights or access to services.
Service redesign and citizen journey mapping. The gap between citizen expectations for digital services and the reality of the government service experience is an operating model problem. Citizens experience a service journey that crosses departmental boundaries. Government manages that journey as a series of departmental touchpoints with no shared view of the citizen or the journey they are on. Value stream mapping applied to citizen service journeys reveals where the handoffs between departments are creating the friction that produces the satisfaction gap documented in the Digital Government Index. That analysis produces a design basis for service improvement that is grounded in the citizen experience rather than in departmental process optimization.
The Carney Government's Digital Transformation Agenda
Prime Minister Carney's early actions, including appointments focused on government transformation and AI and acceleration of interprovincial trade barrier reform, have been interpreted by public sector leaders as a signal that the current government is serious about public service modernization in a way that goes beyond previous digital government programs. The Clerk of the Privy Council has called on departments to embrace transformation as a necessary evolution rather than a threat, and significant spending reduction commitments across the public service are reinforcing that the status quo is not sustainable.
The call for a Digital Government Executive Office anchored at the centre of government with Cabinet mandate and delivery authority, articulated by Canada's former Chief Digital Officer at Transport Canada and echoed by other public sector transformation practitioners, reflects a broader recognition that the architecture governance mechanisms currently in place are necessary but not sufficient for the scale of transformation the current political moment is calling for. The Office of the Chief Information Officer within Treasury Board Secretariat has deep expertise in standards and governance, but as practitioners note, a policy shop alone cannot cut through institutional inertia or mobilize delivery at scale.
What architecture practitioners can do in this context is ensure that when the political momentum and organizational energy for transformation exists, the business architecture work required to translate that energy into well-sequenced, well-scoped, and governable transformation programs has been done. The departments and agencies that enter the next cycle of transformation with current capability models, clear operating model designs, and a defensible investment prioritization framework will be better positioned to move quickly without the years-long current-state assessment that has historically consumed the first phase of every major government transformation program.
Talk to Us
ClarityArc's business architecture practice supports federal and provincial government clients on capability mapping, operating model design, shared services architecture, and AI readiness. If you are working on a government transformation program and want architecture support that understands the public sector context, we are ready to help.
Get in Touch