Why Organizational Design is the First Technology Decision

When I stepped into the CITO role, there was a shared recognition that technology at the agency needed to evolve.

Leadership understood that existing approaches were no longer sufficient to meet operational demands and long-term sustainability needs, but there was less clarity on what that evolution should look like, how it should be sequenced, or who ultimately needed to own it.

At the outset, my role was framed around shaping strategy rather than directly leading execution.

It became clear very early, however, that strategy alone would not be enough. Technology responsibility, accountability, ownership, and decision making across both transformation initiatives and day-to-day operations were fragmented, making consistent execution difficult and obscuring risk.

As I gained more exposure through direct engagement with business owners, IT teams, and an independent assessment, one conclusion became unavoidable: strategy without execution clarity creates risk and execution without strategic ownership creates misalignment.

In that environment, organizational design was not adjacent to technology strategy, it was the first technology decision.

The Assumptions Most Executives Make

The most common assumption executives make with technology is that execution will sort itself out in the absence of a clear strategy and ownership.

When there is no explicit direction, work still happens, but it happens based on what is already in motion, what is externally driven, or what feels most urgent at the time.

In that environment, execution reflects structure. It reflects how responsibility is distributed, how decisions are made, and where accountability ultimately lands.

When those elements are unclear, execution becomes reactive rather than intentional.

From the surface, this can appear functional.

• Systems stay up.

• Projects move forward.

• Teams remain busy.

But underneath, complexity accumulates quietly.

• Workarounds become normalized.

• Technical debt grows incrementally.

• Risk does not announce itself, it becomes part of the environment.

Over time, leaders sense friction without a clear line of sight to its source. Operational issues feel disconnected from long-term objectives, and modernization efforts struggle because the system itself was never designed to support them.

What the CITO Sees That Others Don’t

One of the earliest signals that strategy alone would not be sufficient came from the technical reality underneath the organization.

Not in the form of outages or failures, but through less obvious indicators:

• Systems that were tightly coupled.

• Environments that depended on institutional knowledge.

• Changes that carried more downstream impact than they appeared to on the surface.

From a purely operational standpoint, things functioned. But function and resilience are not the same.

As engagement with the environment deepened, it became clear that complexity had accumulated unevenly. Some systems were stable but rigid. Others were adaptable but fragile. In many cases, the ability to change depended less on design and more on who happened to be involved.

These technical conditions had enterprise implications. They limited how quickly priorities could shift, how confidently risk could be managed, and how effectively modernization could be sequenced.

Without ownership of execution, it was impossible to know whether the strategy was achievable or merely aspirational.

This is where the role of the CITO comes into focus.

The work was not just to define a future state strategy, but to understand how the current system would respond to change, and to design a path forward that accounted for both. Strategy without exposure to technical reality creates blind spots, and technical execution without strategic context leads to misalignment.

Running The System While Redesigning It

One of the realities of stepping into technology leadership in a complex organization is that there is no clean starting line. Systems still need to run, operational commitments remain, and externally driven initiatives continue.

At the same time, it is often clear that the environment was not designed to support the future being asked of it.

Early on, it became evident that this work would need to unfold in phases.

The first year has been focused on discovery, understanding the current state, assessing skills and capabilities, clarifying ownership, and realigning the organization to support a more intentional future. That work happened alongside operations.

This meant addressing day-to-day delivery while simultaneously building clarity around what needed to change. Funding constraints, workforce capacity, and skill gaps were not considerations, they shape the pace and sequencing of progress.

Modernization could not be treated as a single initiative or a clean handoff from “old” to “new.”

As discovery continues, focus is beginning to shift toward strengthening the core and making the basics great, laying the foundation required for future redesign and innovation.

Replatforming from on-premise environments to the cloud, simplifying the technology stack, and reducing unnecessary complexity are active efforts, informed by what is being learned through discovery and constrained by operational reality.

This is the point where the role of the CITO becomes tangible.

The work is about responsibly managing the present while intentionally shaping what comes next, without increasing risk or losing sight of the mission.

What This Changed for Me as A Leader

As I spent more time inside the organization, working with business owners, IT teams, and the day-to-day realities of delivery, it became clear that my role had to change.

What started as shaping direction quickly became owning outcomes. That shift was about being accountable for how decisions translated into results.

The work became about establishing the conditions under which solutions could succeed:

• Clarifying ownership.

• Resetting expectations.

• Simplifying where possible.

• Making deliberate choices about what not to pursue yet.

In an environment constrained by funding, capacity, and skills, focus and discipline mattered more than ambition.

This perspective directly shapes how modernization is approached.

Replatforming from on-premise environments to the cloud and simplifying the technology stack are mechanisms to reduce complexity, increase reliability, and create room to operate.

The goal is not speed for its own sake, but progress that holds under pressure.

What this experience reinforced is that technology leadership at the enterprise level is less about declaring a future state and more about stewarding the present responsibly while building toward it.

Strategy and execution cannot be separated without consequence. Owning both is what allows change to be intentional rather than accidental.