Case Study
Transforming Government IT from Utility to Strategy
King County Information Technology
From a Federation of Silos to a Single Strategic Enterprise
CONTEXT: The Cost of a Federation of Silos
King County, the largest county in Washington State, faced a structural paradox in its information technology operations. With 450 employees and a $200 million budget, the County’s IT capacity was substantial — but it was spread across dozens of separate agencies, each operating as its own technological kingdom. The result was a federation of silos: IT staff were isolated within individual agencies, redundant systems proliferated, and the County could not act as one enterprise even when the work demanded it.
The Cultural Symptom. The fragmentation showed up first in the people. An internal engagement survey measured an Engaged-to-Disengaged ratio of 2:1.5 — a workforce roughly as disengaged as engaged. IT professionals saw themselves as process-overseers within their home agencies rather than strategic partners to the County’s mission. Talent that should have been driving modernization was instead defending turf.
The Strategic Opportunity. Meanwhile, the technology landscape was shifting under everyone’s feet. The generational move to cloud computing required exactly the kind of cross-agency coordination the County’s existing structure couldn’t produce. The window for treating IT as a strategic enterprise rather than a collection of agency utilities was open — but it wouldn’t stay open without deliberate intervention.
INTERVENTION: A People-and-Culture Project First
Technology changes quickly; people change slowly — and the fracture wasn’t in the code, it was in the relationships between the agencies. To facilitate the move to the cloud, we focused less on the code and more on the consultative value of the IT professional. The work centered on three coordinated moves:
The Consultative Business Model. We re-defined the role of the IT professional from process-overseer to engagement-driver — a strategic partner to the agencies, not a gatekeeper. This reframe was not cosmetic. It changed how IT staff were hired, evaluated, and rewarded, and it created the conditions for cross-agency collaboration that the old federation structure had actively blocked.
Unifying the Enterprise. We consolidated agency-by-agency IT operations into a single County IT enterprise, with shared infrastructure, shared standards, and a single point of strategic accountability. The technical consolidation was the visible deliverable; the relational consolidation — the move from "my agency’s IT" to "the County’s IT" — was the harder and more important work underneath it.
Coaching, Not Commanding. You cannot command modernization; you must coach it. We invested in coaching capacity across the IT leadership ranks, equipping managers to lead a cultural transformation rather than enforce a structural one. The shift had to happen in how IT professionals saw themselves and their work — not just in how the org chart was drawn.
RESULT: From Federation to Enterprise
Engagement: The Engaged-to-Disengaged ratio lifted from 2:1.5 to 4:1 — a near-doubling of engaged staff relative to disengaged staff, measured by the same internal survey instrument.
Structural: The County’s 450 IT employees and $200M operation moved from a fragmented federation into a single strategic enterprise with shared infrastructure and unified leadership.
Strategic: IT became a partner to the County’s mission rather than a back-office utility — positioning the organization to undertake the cloud transition and the next decade of digital transformation as one enterprise, not 30 separate fiefdoms.
Cultural: The "process-overseer" identity gave way to the "engagement-driver" identity, changing the kind of work IT professionals sought out and the kind of value they delivered.
THE TAKEAWAY
Technology transformations fail when they are treated as technology projects. The work at King County succeeded because we treated technology consolidation as a people-and-culture project first — and the technology followed.
“You cannot command modernization; you must coach it.”