The Transformation Launch Sequence — A Leader's Guide  ·  Zone 4: The How

4.1 — Finding the Right Partner to Build The How

The How is where transformation either succeeds or stalls. Building it requires the right expertise, the right questions, and an honest partnership. Here's what to look for — and what to ask.

SR
Susan Rohde
The What
The Why
The Resistance
● The How

This post covers Zone 4: The How — how to find the right partner to build a credible transformation plan.

After being parachuted into more than a few failing projects and transformations over the course of my career, I've arrived at a reliable observation: almost every problem these efforts encounter can be traced back to how they were started. Specifically, to the questions that weren't asked before the starting gun fired.

A common scenario: a leader declares a bold transformation goal — "We need to be completely in the cloud within two years to improve our security" — and the organization lurches into motion. Resources are allocated, teams are assembled, progress is reported. Eighteen months in, it becomes clear that almost nothing is working as intended. The timeline was arbitrary. The scope was unknown. The business case was assumed, not proven.

This is not an unusual story. It is, in my experience, the norm. The title of this series is Pragmatic Transformations — and the most pragmatic thing I can offer is a set of questions that, if honestly answered before launch, dramatically improve the odds of success.

In the first post of this series, I introduced two outcome-focused questions that every leader must be able to answer throughout a transformation — the north star questions that keep the effort anchored to business value:

From Post 1 — The Strategic North Star Questions

1. What measurable business value will improve — and by how much?

2. How will we prove it early?

Those two questions are your compass. They tell you where you're going and how you'll know you're making progress. But a compass alone doesn't prepare you for the journey. The six questions in this post are different in nature — they are diagnostic and operational, designed to be asked before you launch. Think of them as the pre-flight checklist that the strategic questions alone can't replace. Used together, they form a complete framework for starting transformations the right way.

The Six Questions

Question 1

"Why this solution for this problem — and what's the expected business value?"

This is the foundational question. Too many transformations begin with a solution already selected before the problem has been clearly defined. Cloud, AI, Agile, DevOps — these are tools. The question is whether the tool actually addresses the most pressing organizational risk. If you can't articulate a clear, specific, measurable business outcome that this transformation will improve, you are not ready to launch.

Question 2

"Why this timeframe — and what actually happens if you don't hit it?"

Transformation timelines are frequently picked out of the air to create urgency or satisfy an executive's instinct for ambition. The problem is that arbitrary timelines create artificial pressure without changing the underlying capacity of the organization to deliver. Ask: what is the real consequence of missing this deadline? If the honest answer is "not much," the timeline needs to be grounded in something real — or reset entirely.

Question 3

"What is your current baseline?"

You cannot measure progress without knowing where you started. Yet organizations routinely launch transformations without establishing a baseline for the very metric they're trying to improve. Security posture, delivery speed, cost per transaction, customer satisfaction — whatever the goal is, measure it now. Without a baseline, "improvement" is just a story you tell. With one, it becomes something you can prove.

Question 4

"How much effort, money, and political capital are you prepared to invest?"

This question has three components — and all three matter. Financial investment is the easiest to quantify. Effort is harder: transformation work competes with the day-to-day operational demands that never stop. And political capital — leadership credibility — is the most finite resource of all. If the answer to this question is "as much as it takes," that is not an answer. Name the number, name the capacity, and name the credibility you are willing to spend. Then track all three as carefully as you track the budget.

Question 5

"What are you willing to stop doing to start this?"

Every organization has more initiatives underway than it has capacity to execute well. Launching a new transformation without stopping something else is one of the most reliable ways to ensure that nothing succeeds. This question forces an honest conversation about organizational bandwidth. If the answer is "nothing" — if everything currently underway is too important to pause — then you do not have the capacity to launch this transformation. Full stop.

Question 6

"What can you deliver in the next 30 to 90 days — and how will you prove it?"

Transformation momentum is built through early, visible wins. If you cannot identify a concrete, measurable outcome that can be demonstrated within the first quarter, the transformation lacks the near-term definition it needs to sustain energy and credibility. This question also serves as an early warning system: if you can't answer it before you launch, you almost certainly haven't thought through the first mile carefully enough.

What Honest Answers Look Like — A Real Example

Let me apply these six questions to a real transformation I observed: a large organization that declared it would migrate 200 applications to the cloud within two years to improve security.

Applied Example — Cloud Migration Transformation
Q1: Why this solution, and what's the expected value?
The security rationale was assumed, not quantified. No one had established what specific security outcomes would improve, or by how much.
Q2: Why two years — what happens if you miss it?
The timeline was chosen to be aggressive and apply pressure. In reality, the organization had moved 3 of 200 applications to the cloud in three years prior. The timeline had no grounding in actual capacity.
Q3: What's the current baseline?
The organization didn't know its current security posture in measurable terms, didn't know the on-premise operating cost per application, and hadn't identified which of the 200 applications were even cloud candidates. (An eventual inventory revealed only about 60 were.)
Q4: How much investment are you prepared to make?
Millions were committed financially. But IT paid for on-premise infrastructure and business lines paid for cloud costs — with no budget shift anticipated. The financial model was structurally broken before the work began.
Q5: What will you stop doing?
Nothing specific was identified. The migration was positioned as additive work on top of an already full organizational plate.
Q6: What can you deliver in 90 days?
No near-term milestone was defined. The two-year destination was the only stated goal.

The result was predictable: the organization didn't know where it was starting, didn't know the true scope of the target, and didn't have the organizational capacity to hit it. Years of effort produced modest results at significant cost.

"Organizations almost never know the answers to these questions when they start. What's critical is that you ask them — and revisit the answers on a predictable cadence."

You Don't Have to Have All the Answers — But You Have to Ask the Questions

Here is the most important thing I can tell you about these six questions: you are not expected to have perfect answers before you begin. In reality, organizations almost never do. What matters is that you ask them honestly, document your best current answers, and establish a cadence — monthly or quarterly — for revisiting and refining those answers as you learn.

The organizations that do this well build a feedback loop into the transformation itself. They treat early answers as hypotheses, not commitments. They adjust when reality diverges from the plan. And over time, as they get better at this discipline, they wrap an OKR — Objective and Key Results — framework around the transformation to measure and communicate progress with precision.

A note on OKRs

Objectives and Key Results (OKRs) are a powerful tool for connecting transformation goals to measurable outcomes. An Objective answers the question "where are we going?" A Key Result answers "how will we know we've arrived?" Once your organization can consistently answer the six questions above, OKRs become the natural next layer — turning transformation intent into transformation accountability.

Closing the Series

This is the fourth and final post in the Pragmatic Transformations series. We started with the uncomfortable truths about why transformations fail at the leadership level. We named the three recurring sources of failure. We walked through a practical approach to surfacing smoldering platforms before they explode. And we've closed with the six questions that every leader should be able to answer — or at least honestly grapple with — before launching a major transformation.

The thread running through all of it is the same: transformation is not primarily a technology problem. It is a leadership problem. The tools exist. The talent exists. What's consistently missing is the clarity, discipline, and honesty to start transformations the right way — grounded in real problems, realistic capacity, and a commitment to measuring what actually matters.

If any of this resonates with what you're experiencing in your organization, I'd genuinely welcome the conversation.


The Transformation Launch Sequence — A Leader's Guide · Full Series Roadmap
Zone 1: The What
Published1.1 — Getting "The What" Right: Why Most Transformations Start with the Wrong Goal
Coming1.2 — How to Extract The What from Your Strategic Plan
Coming1.3 — When The What Changes Mid-Transformation — What to Do
Zone 2: The Why
Coming2.1 — How to Identify and Articulate Real Value — Not Just Aspiration
Coming2.2 — Why "10x Productivity" Is a Hope, Not a Plan
Zone 3: The Resistance
Published3.1 — Three Sources of Transformation Failure
Published3.2 — Smoldering Platforms: How to Find Them Before They Explode
Coming3.3 — The Silver Bullet Trap
Coming3.4 — The Big Ball of Mud — How Fuzzy Priorities Guarantee Failure
Zone 4: The How
This Post4.1 — Finding the Right Partner to Build The How
Coming4.2 — OKRs as the Measurement Layer for The How
Coming4.3 — Navigating the Transformation Launch Sequence — A Practical Course for Leaders

Stay ahead of the series

New posts are published regularly across all four zones of the Transformation Launch Sequence. Subscribe to be notified when new content is live — no spam, ever.

Ready to build your own Transformation Launch Sequence?

Try our free interactive tool — it guides you through all four zones and generates a completed diagram you can share with your leadership team.

Try the Free Tool → Talk to Rohde, Inc.