A Value-First Approach to Federal Transformation

The Capstone

Edith A. Hughes, D.Sc.  ·  Adaptive Value Design LLC  ·  2026

I.  Assembling the Case

The first four articles in this series build a case. This article assembles it.

The series begins with an observation that is simple to state and consequential to act on: federal agencies are called to adopt a product operating model. But first they need to answer the questions that form the structural foundation of that model: What value are we here to deliver, and to whom? Everything that follows explains how to answer those questions, how to create the leadership conditions that surround them, the methods that enable them, and the structural reforms and disciplines that make them operational at scale.

Article 1 establishes the conceptual foundation. Value is defined by the customers who receive it, and federal agencies have three distinct categories of customers — Consumers, Producers, and Approvers — each with multiple specific roles that must be mapped and understood before an operating model can be designed. The language matters: a product operating model, as Mik Kersten defines it in From Project to Product, is organized around value streams — the end-to-end flow of work that delivers value to customers through products or services.¹ The word “product” in the operating model label can obscure this: in a federal context, where most value delivery takes the form of services rather than products, the value stream is the more precise organizing concept. What flows through a value stream is not necessarily a product. It is value — delivered to a specific customer, through whatever combination of products or services the mission requires. Defining those value streams correctly requires first answering the foundational questions this series has traced. The sequence runs from mission to domain to customer to value stream: the domain scopes the area of work, the customer mapping within that domain identifies who receives value and what they need, and the value stream traces the end-to-end flow that delivers it. The product operating model is built to govern and optimize that flow — once the flow has been correctly defined.

Article 2 examines the system conditions that determine whether that foundational work can happen, and what changes are needed to make it the norm. Federal executives do not define value together as a cohesive team when the system surrounding them — the norms, the incentive structures, the development pathways, the statutory performance management framework — does not provide the conditions for it. The challenge is not leadership capability. It is system design.

Article 3 describes how to execute that foundational work. The Census Bureau engagement of 2013 demonstrated that a leadership team can build shared understanding of its mission, customers, and value streams, if someone asks them to do the work, allocates the resources for the effort, and provides the conditions that make it possible. The engagement did not solve the problem. It built the team that could.

Article 4 explains how to align the core elements of the operating model. Shared understanding alone does not change how an agency is organized, how decisions are made, or how technology is built. Intentionally designing an operating model for structural isomorphism — the alignment of mission domains, decision authority, and technical architecture around the same boundaries — is what translates foundational alignment into organizational effectiveness. Domain-Driven Design, Technology Business Management as a discipline, and Team Topologies are the disciplines that make isomorphism operational at enterprise scale. USCIS demonstrated that a federal agency can achieve it.

The four articles form a sequence for change. But leveraging the sequence requires stepping back to view the whole system: how each element depends on the others, what enabling conditions are needed at the agency, executive branch, and Congressional levels, and why the sequence cannot be executed piecemeal. That whole-system view is what this article provides.

II. The Operating Model as a System

The Public Value Aperture is referenced in every article of this series as a visual anchor. By now, all six of its blades have been grounded in argument and evidence. This section shows how they work together, not as a checklist of operating model elements, but as an integrated system in which each element depends on the others and the sequence of their development is as important as their content.

The aperture’s two groupings correspond directly to the work the series has described. The Institutional Direction — Mission Domains & Strategy, Customer Insight, and Measures — is the work of Articles 1 and 3. It is the foundational layer: defining why the agency exists, who its customers are, and how value flows through the system. This work cannot be delegated to a strategy office or contracted to a consulting firm. It requires the executive team to do it together, in the sequence Article 3 describes, grounded in the statutory authorization that Article 3 names as the starting point. And critically, the Measures blade closes the loop: it feeds performance data back into Mission Domains & Strategy to quantify how well the agency is performing in its delivery of mission value based on customers’ needs and expectations and where it needs to improve.

The Enabling Systems — Organization Design, Service Delivery, and Technology Enablement — is the work of Article 4. Once the executives define the mission domains and map the customer landscape, they can redesign the organization to mirror those domains. Service delivery flows can be structured around the value streams the foundational work identified. Teams are defined and structured around the type of value they deliver and the type of interactions that allow the value to flow with minimal constraint. Decision authority can be aligned to delivery accountability at every level of the organizational stack. Technology investments align to the domain structure that Organization Design establishes. These steps build the structural isomorphism across the org chart, the governance structure, the service architecture, and the technology portfolio — reducing the friction that occurs when these elements are out of alignment.

It is worth naming a distinction that has been implicit throughout this series. The Public Value Aperture is the operating model framework: the six-element model that describes the elements of an operating model and how the elements relate to each other. These operating model elements always exist in every organization, whether they were deliberately designed or not. Every agency has a governance structure, an organization design, a service delivery approach, a technology architecture, and a set of measures.

The question is not whether the operating model elements are present. It is whether they were designed to work together, and whether they are aligned around a shared definition of the public value the agency exists to deliver.

Alignment enables efficiency. A misaligned operating model is like a car out of alignment: the vehicle still moves, but the wheels pull in different directions, steering requires constant correction, and the effort of keeping it on course consumes energy that should be going toward the destination. The value-first approach this series describes is the transformation methodology: the sequence of work that federal agencies must execute to build a well-aligned, functioning operating model. It answers the question of what steps to take to achieve that alignment.

The camera aperture metaphor is intentional in the Public Value Aperture model. A camera aperture does not work if any blade is misaligned with the others. Neither does an operating model. Agencies that design their technology before defining their domains in the context of mission value produce systems that entrench misalignment. Agencies that define their measures before mapping their customers produce metrics that optimize for the wrong outcomes. Agencies that reorganize around domains without aligning governance structures produce new org charts without changing how the organization actually operates. The sequence is not optional because the interdependencies are real.

The aperture focused on value is the destination. The sequence this series describes is the path that leads to it. Both are necessary. An agency that understands the destination but not the path will produce the pattern this series has diagnosed repeatedly: the right operating model concept adopted without the foundational work required to make it function. The tools are not new. Conway’s Law, Domain-Driven Design, Team Topologies, Mark Moore’s public value framework, and G. Lynn Shostack’s service blueprinting are established disciplines with substantial evidence behind them. An agency that executes the path without the destination in view will produce activity without structure or measurable outcomes of public value. The series makes the case for both, in sequence, as a system.

III. What Each Component Requires of the Others

The operating model’s components are mutually dependent, but they do not require “big bang” change to move toward alignment. “Big bang” approaches seldom yield positive results: the private sector has repeatedly shown that changing complex systems requires a start small, iterate rapidly, and scale thoughtfully approach. USCIS’s adoption of these practices is a continuing evolution that now spans more than a decade. But a journey of a thousand miles begins with one step; building a skyscraper must start with the foundation. One agency example in this series illustrates what happens when the structural work is attempted without the foundational work: a sophisticated framework was proposed, the scope felt overwhelming because the shared understanding that would have made it approachable had never been built, causing the framework adoption to stall. The Census Bureau demonstrates how to achieve success: a foundational engagement that produces genuine leadership alignment and continuing transformation. The Census engagement ventilated the silos; structural isomorphism keeps them ventilated to this day.

Federal transformation stalls when change is attempted before a holistic operating model design is in place. Not because the attempted component is wrong, but because it has no foundation to stand on.

One additional implication deserves naming, though it warrants fuller treatment than this article allows. Federal agencies are under growing pressure to adopt AI as an instrument of government efficiency. The approach this series describes is not in competition with that agenda. It is the precondition for it. AI amplifies existing organizational structures, well-aligned ones and dysfunctional ones equally. Agencies that have done the foundational work will find AI to be a genuine accelerant. Agencies that have not will find that AI accelerates the entrenchment of the dysfunction they were trying to escape.²

A well-defined, well-aligned operating model built around the flow of delivering public value is the right destination. The sequence of steps presented in this series is what makes it reachable.

IV. What Leaders, Congress, and the Executive Branch Must Do

The foundational work this series describes is executable today. No legislation is required to convene an executive team, work through the statutory foundation of the agency’s mission, map its customers, and trace its value streams. No new authority is needed to design an engagement like the one the Census Bureau conducted in 2013. The foundational work is available to any agency whose leadership team is given the directive, the time, and the tools. That is where the work must start, and it is where agency leaders have the most direct control.

But agency leaders cannot implement the full transformation alone. The structural conditions that Article 2 diagnoses — the norms, the incentive structures, the development pathways, the performance management framework — are not within the control of any single agency. They require action at the executive branch level and, for the most durable reforms, at the Congressional level. What follows is not an exhaustive policy agenda. It is a minimum set of foundational changes that the framework requires to become the norm rather than the exception.

At the agency level

Before an agency can define how it will measure mission outcomes, its leadership must first agree on what those outcomes are. That agreement is itself the product of becoming a cohesive team. That requires the foundational engagement this series describes: working through the Why, What, Who, and How together, building the shared system picture, and arriving at a collective understanding of the public value the agency exists to deliver and who receives it. From that foundation, the discipline of developing quantifiable measures of mission delivery becomes both possible and necessary.

This gap is one of the most consequential in federal management, not because federal executives lack analytical capability, but because they have never been asked to define outcomes collectively, from the customer’s perspective, grounded in statutory purpose. Output measures are easy: applications processed, calls answered, systems deployed. Outcome measures are hard: did the value stream deliver what it exists to deliver, to the customers it exists to serve, in a way they could use? The customer roles framework and the value stream mapping produce the raw material for that question. The executive team’s shared accountability for the answer is what makes the measures practical instead of performative.

At the executive branch level

Federal Senior Executive Service performance management currently rewards individual functional excellence. Statute does not require shared accountability for enterprise outcomes. An SES leader who delivers outstanding results within their functional lane while the agency’s value streams remain misaligned and its customers poorly served is performing exactly as the system asks. Reforming SES performance management to require shared accountability for mission outcomes — measured against the customer-focused, outcome-based measures the executive team defines together — is the executive branch reform with the highest leverage. It changes what the system asks for, which is the only reliable way to change what the system produces.

The executive branch must also address the development gap. Federal executives are not given the tools, the training, or the structured opportunities to do the foundational work this series describes. A federal executive development system that builds collective capability — the ability to define value together, map customers together, trace value streams together, and design structures that align authority with accountability — is not a luxury. It is the infrastructure that makes the framework scalable beyond the agencies whose leaders happen to encounter it.

OMB has a direct role to play in both areas. Guidance that requires applying TBM as a discipline instead of only as a taxonomy for classifying technology costs is a start. Applying TBM as a discipline connects technology investment decisions and costs to mission performance. This quantifiable traceability would hold agencies accountable for outcome-based measures for technology investments and delivery, instead of serving only as a compliance checklist for budget categories. This shift would change the conditions under which federal executives operate. And a President’s Management Agenda that directs agencies to define and quantify mission value prescribing specific operating model changes would give a product operating model framework the foundational design it needs to scale. A PMA could serve as a powerful cross-agency alignment tool available to the executive branch, but its power is proportional to the quality and completeness of the guidance it asks agencies to implement.

The case for this kind of coordination mechanism is not hypothetical. A February 2026 roundtable explicitly called for a standing Executive–Legislative Management Forum to provide a regular, structured venue for addressing implementation barriers and sustaining momentum on shared management priorities.³ The forum’s proposed focus on outcome-based metrics, multi-year timelines, and sustained partnership with career civil servants reflects the same logic this series describes. A PMA that directed agencies through the foundational sequence this series describes would give that forum the upstream framework it needs to produce outcomes instead of outputs.

One structural condition undermines all of the above: executive tenure. Federal agencies are disproportionately led by political appointees whose average tenure is measured in months instead of years, or senior executives who are expected to rotate assignments every three years. An executive team that turns over soon after it completes the foundational work cannot build on what it started. A team that inherits an incomplete transformation rarely has the shared context to continue it. The structural work of aligning domains, governance, and architecture requires sustained leadership attention over years, not the span of a single appointment. A forum on driving government efficiency recommended that agencies appoint transformation leaders for terms of five to seven years — long enough to complete the foundational work and begin the structural follow-through. That recommendation deserves serious consideration.

At the Congressional level

Two structural reforms could do more than any number of management initiatives to make value delivery the organizing principle of federal operations. The first is moving toward appropriations structures that fund value streams rather than programs. Program-based appropriations guarantee that agencies cannot align their investments to their missions, because the budget boundaries and the domain boundaries were drawn by different hands for different purposes and have yet to be reconciled. The second is outcome-based oversight. Congressional oversight that focuses on whether value streams are delivering measurable outcomes for the customers they exist to serve, instead of whether agencies have complied with the procedural requirements attached to their appropriations, changes the incentives that govern every management decision an agency makes. These reforms are not partisan. They are structural, and their absence produces the dysfunction that every administration inherits — and that any administration willing to take a whole-system view is positioned to address.

The February 2026 roundtable reached a compatible conclusion: progress has been most durable when the two branches have engaged in sustained, pragmatic collaboration focused on removing specific barriers to execution rather than debating abstract principles. The most consequential application of the domain architecture argument extends beyond any single agency. If Congress and the Executive Branch were to work together to define the domains of the federal enterprise as a whole — identifying which mission domains are unique to specific statutory purposes, which are shared enabling functions that must be intentionally configured to support mission execution, and which are genuinely generic across the enterprise — the resulting framework would provide a structural foundation for decisions that currently lack one. Shared services investments like HR 2.0 would have a classification basis for determining what can be standardized without mission risk. Citizen service journeys that cross agency boundaries would have a domain map against which hand-offs and integration points could be rationally designed. Data governance and sharing across agencies, as Kshemendra Paul has argued from the data direction, would have a common organizing structure that agency-centric ownership models cannot provide.⁴ The long-term efficiency gains from this kind of whole-of-government domain clarity would compound across every management reform initiative that follows.

This idea is not without precedent. The Federal Enterprise Architecture Framework and its Business Reference Model, last updated in 2013, made a serious attempt to map the mission and functional landscape of the federal government. The Government Extension of the Technology Business Management taxonomy approached the same problem from the investment transparency direction. Both efforts produced genuine value and both stalled — in part because the classification discipline that would make their categories rigorous and durable was never fully developed, and in part because the institutional home and sustained leadership attention required to maintain such a framework was never established.

What a renewed effort requires above all else is not a better taxonomy. It is a cohesive team — one that spans the legislative and executive branches, is dedicated to the continuous design, development, implementation, and improvement of a whole-of-government domain model, and has the authority, the tenure, and the mandate to treat that model as living infrastructure rather than a one-time deliverable. The approach this series describes is directly applicable at that scale. The foundational work — defining what government exists to deliver, to whom, through which domains — is the same work at the enterprise level that Articles 1 through 4 have described at the agency level. The sequence does not change. The scope does.

V.  From Case to Action

This article assembles the case made in this series. Four articles establish the foundation, diagnose the conditions that prevent it from being built, describe how to build it, and identify the structural reforms that make it durable. This article shows how the pieces fit together as a system, why each component requires the others, and what must change at the agency, executive branch, and Congressional levels for this approach to become the norm rather than the exception.

This conclusion is not the end of the work. It is the beginning of a different kind of work.

The reforms Section IV describes at the Congressional and executive branch levels are not technical questions. They are political and institutional ones, and they require the kind of sustained, cross-partisan engagement that policy and research organizations can provide. The appropriations structures that fund programs rather than value streams, the oversight mechanisms that measure compliance rather than outcomes, the SES performance management framework that rewards functional excellence rather than shared enterprise accountability — each emerged from institutional logic that made sense in a different era and has not yet been systematically reconsidered for what the current era of mission delivery requires.

Reconsidering them is the work of future articles. Those articles will examine, in specific and actionable terms, what Congressional and executive branch reforms would make the approach this series describes the default operating condition for federal agencies rather than an exception pursued by unusually motivated leaders. They will engage the legislative and institutional mechanisms through which those reforms could be advanced, the coalitions that would need to support them, and the evidence base that already exists for their effectiveness. They are, in the fullest sense, the next step in the vision this series has described.

This series has been written from the inside. The author has sat in the rooms where federal executives struggle to see their enterprise together. She has designed and facilitated the foundational work, and watched it produce leadership clarity that no consulting deliverable could provide. She has seen the structural misalignment that persists even after that clarity is achieved, and the dysfunction it produces at every level of the organization. The framework this series describes is not theoretical. It is a distillation of what works, grounded in practice, organized by the best available evidence from organizational theory, software architecture, investment management, and federal experience.

The federal government does not lack frameworks to adopt. It lacks the foundational work that makes frameworks function, the leadership conditions that make that work possible, the structural alignment that makes results durable, and the policy infrastructure that would make all three the expectation rather than the exception. These gaps are not inevitable, nor are they unsolvable. They are the design choices, accumulated over decades in both the Executive and Legislative branches, that leaders can redesign. This series makes the case that redesigning them is both possible and necessary.