What leaders who get transformation right
do before anyone is watching.
Brandon Freitag · workthatholds.com · June 2026
It is in what happens before the launch.
Papers 1–4 diagnosed the patterns that cause transformation to fail — incentive fragmentation, process friction, the technology illusion, the momentum mirage.
Paper 5 answers the question they leave open: so what do I actually do?
A cloud modernization at a financial services firm. An operating model redesign at a healthcare system. In both, the breakpoints were visible from the start. By the time anyone named them, the political cost of addressing them was higher than the cost of continuing to manage around them.
When she took her next role, she did something different.
She wrote one outcome statement and did not proceed until every senior leader described it the same way.
She mapped every leader with veto power and had direct conversations about incentives — before the kickoff.
She redesigned the handoffs she recognized would slow everything down.
The initiative took 22 months. It delivered. She would describe it as the only logical approach given what she had seen before.
"Improve the customer experience" protects the leader.
"Reduce resolution time 40% in two quarters" creates a commitment that can fail.
That discomfort is the point. The outcome is ready when the CFO would recognize it as a financial event — not a program milestone.
The most dangerous resistance is the kind that looks like support.
Before the initiative is announced: map every leader with meaningful power to accelerate or veto. For each — if this initiative succeeds but their metrics stay flat, will they prioritize it?
If no, resolve the conflict before the announcement. Silence before a kickoff is not alignment. It is latency.
Most process failures are not wrong people or wrong tools. They are skilled people inside broken handoffs.
Map how work actually flows — not how it's supposed to flow. Find every handoff that adds time without adding value. Redesign or eliminate it before the new work lands on top of the old machinery.
Most initiatives don't fail at launch. They fade.
What will the initiative deliver in the first 90 days that is real, visible, and financially meaningful?
Not infrastructure for future value. Not a foundation. Actual value someone outside the program team can point to.
A proof of concept tells the organization the approach might work. A delivered result tells the organization it is working.
The launch event activates every skeptic simultaneously.
The alternative: identify the leaders, teams, or functions already closest to the desired state. Make participation in the first cohort selective — people who opt in are more committed than people who are assigned.
Let the results of that cohort do the persuasion work an announcement never can.
| Phase | Discipline | Breakpoint Prevented |
|---|---|---|
| Anchor | 1. Define the outcome | Strategic Disconnection |
| Anchor | 2. Resolve incentive conflicts | Incentive Fragmentation |
| Build | 3. Redesign the delivery system | Process Friction |
| Build | 4. Test organizational readiness | Technology Illusion |
| Sustain | 5. Build the momentum system | Momentum Mirage |
| Sustain | 6. Sequence for value | Momentum Mirage |
| Sustain | 7. Design for adoption | Strategic Disconnection |
The leaders who get this right are not operating
on different information.
They are acting on it earlier, more specifically, and more honestly than the system typically rewards. The disciplines stay invisible. That coincidence is structural.
workthatholds.com · brandonfreitag.com