The Tradeoffs That Define Transformation

Part 1: Why Organizational Design is the First Technology Decision

In the first article, I wrote about how clarifying ownership and accountability reshaped the foundation for transformation. Once that clarity begins to take hold, a different challenge emerges: how change unfolds within real constraints.

In regulated environments, the definition of transformation is rarely controlled by a single organization. Legislative priorities, enterprise mandates, funding structures, and contractual models all shape the path forward.

Technology leaders operate within that framework and the resulting complexity is technical and structural.

Aging Systems and Modern Expectations

Legacy, on-premise systems often support critical operational functions, including those directly tied to public safety. They are stable because they have been maintained for years by dedicated staff who understand them deeply.

But stability built on institutional knowledge creates fragility over time.

Expertise becomes concentrated. Fewer people understand how systems connect, and change becomes harder to execute safely. Modernization requires new platforms and broader capabilities across the organization.

During discovery, it became clear that transformation is as much a workforce challenge as it is a technology one.

When a significant portion of the organization is oriented around supporting legacy systems, modernization must account for that reality rather than assume it away.

Lift and Shift & Modernization

Enterprise transformation programs often define progress in terms of migration, moving systems from on-premise environments to the cloud. That step can reduce infrastructure risk and align with broader mandates.

But migration alone does not equal modernization.

In practice, both approaches have a place. Some services can be lifted and shifted pragmatically and deliver immediate benefit. Others require deeper replatforming or architectural redesign to reduce long-term complexity and improve resilience.

The leadership question is not which approach is “correct,” but which is appropriate, and in what sequence. The answer depends on operational impact, funding constraints, workforce readiness, and long-term sustainability.

Vendor Reliance & Internal Capability

In the early stages of transformation, particularly when internal cloud capability is limited, reliance on external vendor “tower” models can provide scale and immediate delivery capacity. That was the initial direction, structured vendor towers to accelerate lift-and-shift activity.

As clarity improved, I paused that trajectory.

It became clear that outsourcing execution without building internal ownership would limit long-term resilience. Migration might occur, but institutional capability would not grow.

Transformation needed to be something the organization understood and owned, not simply something delivered to it.

That decision directly informed organizational changes now underway:

• Redefining roles.

• Clarifying operating models.

• Increasing internal accountability for how modernization is delivered.

Over time, the objective is to reduce dependence on external delivery while strengthening internal capability in a sustainable way.

Funding Priorities & Foundational Work

Competing legislative and operational priorities often direct funding toward visible initiatives. Foundational improvements like governance, simplification, refactoring, and skill development rarely carry the same urgency.

During discovery, it became evident that without strengthening the foundation (core), even well funded initiatives would struggle to scale.

This is where a phased approach becomes practical. Discovery brings clarity to the current reality. Strengthening the core and making the basics great, creates foundational stability to build from. Innovation follows from that foundation.

Each phase builds on the last, creating the structure, durability, and flexibility required for transformation to endure.

Naming the Real Tradeoffs

Transformation is often framed as a technical upgrade. In practice, it is a reallocation of responsibility, funding, and capability.

Leaders must decide:

• Are we migrating, modernizing, or intentionally balancing both?

• Are we renting expertise, or building it?

• Are we prioritizing visible change, or foundational strength?

Answering these questions clarifies the decisions that must follow.

In complex environments, transformation advances when leaders are willing to name them and move forward deliberately. In the next article, I’ll explore how trust determines whether transformation can scale.