by Braden Kelley and Chateau G Pato
What Does It Mean When a Transformation Manages the Deck, Not the Work? (Short Answer)
Your transformation is managing the deck, not the work, when governance energy goes to RAG colors, narrative polish, and workstream theater while the median employee’s Tuesday — tools, handoffs, incentives, and authority — stays the same. Eleven signs: RAG greener than reality, slide time over floor time, status agendas without decisions, activity reporting instead of behavior, risks that only live in registers, change as cascade and completions, dependencies as Gantt arrows, problems parked until next steering, go-live as finish line on the roadmap, vendor demos owning the room, and shadow process “managed” as residual risk.
A deck is a mirror. When the program starts performing for the mirror, the work has already left the room.
Green Decks, Red Tuesdays
I have sat in enough steering rooms to recognize the smell of a program that has become a reporting product. The slides are crisp. The RAG is mostly green. Workstreams have spoken. Risks have been “mitigated.” Someone thanks the PMO for the pack.
Then you walk the floor — or talk to the median person trying to do the new job with the old incentives — and Tuesday is still red.
That gap is not a communication problem. It is governance theater: managing the artifacts of transformation as if they are the transformation. The work — redesigned jobs, owned handoffs, killed shadow processes, practiced capability, and behavior after go-live — never gets the same energy as the deck.
| Sign | Deck reality | Work reality |
|---|---|---|
| 1. RAG greener than Tuesday | Status looks healthy | Workarounds still run the day |
| 2. Slides over floor time | Pack is polished | Nobody watched the median user |
| 3. Status, not decisions | Tour complete | Nothing killed or funded |
| 4. Activity, not behavior | Milestones hit | Old path still preferred |
| 5. Risks in the register | Rated and reviewed | Broken handoff still daily |
| 6. Cascade = change | Completions high | Capability thin |
| 7. Dependencies as arrows | Gantt looks integrated | Seams have no owner |
| 8. Problems parked | On next month’s agenda | Blocker lives this week |
| 9. Go-live as climax | Roadmap peaks at cutover | Adoption is a footnote |
| 10. Vendor demos own the room | Product theater | Adopters absent |
| 11. Shadow process “managed” | Labeled residual / out of scope | Old path still easy |
1. Why Is a Green RAG a Warning Sign When Tuesday Is Still Red?
The sign: Status is amber or green while frontline effort, workarounds, and adoption quality are clearly red.
Why it seduces: Color coding is legible in fifty minutes. Lived experience is not. Leaders can leave the room feeling informed.
Manage the work instead: Dual truth — system status and human success. A green RAG cannot close the review if the experience is red. If status and Tuesday disagree, Tuesday wins.
2. What Does It Mean When Slide Production Outruns Floor Time?
The sign: The team’s scarce hours go to deck assembly, appendix hygiene, and “story alignment” — not ride-alongs, floor walks, or watching the median user struggle.
Why it seduces: The pack is a visible deliverable. Floor time looks soft and does not photograph in the steering invite.
Manage the work instead: Cap slide hours. Require evidence from contact with the work in every steering pack — a quote, a timed task, a workaround still in use. No floor signal, no green story.
3. How Do You Spot a Steering Agenda That Is Status, Not Decisions?
The sign: Steering meetings are tour updates. Few tradeoffs named. Few things stopped. Few owners assigned for next Tuesday.
Why it seduces: Status feels safe. Decisions create losers, vendors, and uncomfortable clarity.
Manage the work instead: Decision-first agenda — what must we choose, kill, fund, or unblock before we leave? If the meeting ends with “thanks for the update,” you managed the deck.
4. Why Is Reporting Activity Instead of Behavior a Transformation Trap?
The sign: Workstreams celebrate milestones, tickets closed, training launched, and “progress against plan” — not whether humans stopped the old path or succeeded on the new one.
Why it seduces: Activity is countable. Behavior change is political and harder to put in a chart.
Manage the work instead: One behavior metric per workstream — adoption quality, workaround retired, time-to-confidence. Progress that cannot name a human behavior is still theater.
5. When Do Risk Registers Become Governance Theater?
The sign: Risks are rated, mitigated on paper, and reviewed monthly — while the broken handoff still happens daily.
Why it seduces: Registers look like governance. Fixing the workflow looks like operations, which someone else is supposed to own.
Manage the work instead: Every top risk must map to an owned workflow change this sprint — or it is a slide, not a control. Mitigation without a Tuesday owner is fiction.
6. Why Isn’t Cascade Decks and Training Completions Real Change Management?
The sign: Comms plans, town halls, and training completion percentages are the change scorecard. Practice, coaching, and permission to stop the workaround are missing.
Why it seduces: Completions are procurable and reportable. You can screenshot the cascade. You cannot screenshot someone’s third Tuesday failing with the old incentives still in force.
Manage the work instead: An enablement scorecard — practice on real work, manager coaching, protected learning time. Informed is not enabled.
7. What Goes Wrong When Dependencies Are Arrows Instead of Owned Handoffs?
The sign: The Gantt shows neat dependencies. Nobody can name who owns the seam between teams when it breaks on Tuesday.
Why it seduces: Planning software creates the illusion of integration. Arrows feel like ownership.
Manage the work instead: Name seam owners. Design the handoff. Test the seam before you celebrate the milestone. Integration that only exists in the plan does not exist.
8. Why Is Parking Problems Until the Next Steering Pack a Red Flag?
The sign: Issues escalate into “for discussion next month” rather than a 48-hour fix with an owner. The deck becomes a waiting room.
Why it seduces: Cadence protects calendars. Urgency threatens the narrative and the RAG.
Manage the work instead: Fast-path ownership for anything blocking the median user’s success this week. If it can wait a month, it was never blocking the work — only the story.
9. Why Shouldn’t Go-Live Be the Finish Line on the Roadmap Slide?
The sign: The visual climax of the program is cutover. Hypercare is a thin bar. Adoption and BAU ownership are footnotes.
Why it seduces: Vendors and PMOs get paid at go-live. Steering committees want a date they can declare. Adoption is someone else’s Tuesday.
Manage the work instead: Make the roadmap climax a durable new way of working. Go-live is a technical event. Transformation is behavior that survives after the PMO leaves.
10. What Does It Mean When Vendor Demos Own the Room and Adopters Don’t?
The sign: Steering time goes to product walkthroughs and roadmap theater. The people who must live the change are absent, summarized, or reduced to a survey chart.
Why it seduces: Demos photograph well. Adopters complicate the story with workarounds, missing authority, and truths that do not fit the narrative.
Manage the work instead: Adopter voice as a standing agenda item — what broke, what workaround returned, what decision rights are missing. If adopters are not in the room, you are managing a brochure.
11. Why Is “Managing” Shadow Process as Residual Risk Still Failure?
The sign: The old spreadsheet, parallel path, or “just in case” process is acknowledged on a slide and left alive — draining adoption while status stays green.
Why it seduces: Killing the old way is political. Labeling it residual or out of scope feels tidy and keeps the RAG calm.
Manage the work instead: Explicit kill date and owner for the shadow path. Make the new way the only easy way. A residual risk that still runs the business is not residual. It is the operating model.
How Do You Test Whether You’re Managing the Deck or the Work?
Before the next RAG review, run five go/no-go questions. If you cannot answer them, you are performing transformation for an audience that can leave the room:
- What evidence from the floor is in this pack — not only from the plan?
- What decision will we make today — choose, kill, fund, or unblock?
- What behavior changed since last month for the median person?
- What will we stop — not only mitigate on a register?
- Who owns the median user’s Tuesday after go-live when the PMO leaves?
If the beliefs underneath the theater need naming, see 8 Change Myths Leaders Still Believe in 2026. If the pilot worked and scale did not, use 9 Reasons Digital Transformations Stall After the Pilot. Before the next funded experiment, run 11 Questions Before Funding Any Innovation Pilot.
If the deck is healthier than the work, you are not transforming. You are managing the mirror. Put the energy back into Tuesday — and let the slides catch up to reality, not the other way around.
Frequently Asked Questions
What does it mean when a transformation manages the deck, not the work?
It means the program optimizes RAG status, narrative polish, and workstream reporting while the median person’s tools, handoffs, incentives, and authority stay unchanged. Governance energy goes to slides instead of redesigned work, owned seams, killed shadow processes, and behavior after go-live.
How do you know a transformation is failing?
Warning signs include green status with red frontline experience, steering agendas that never make decisions, activity metrics instead of behavior change, risks that only live in registers, go-live treated as victory, and old shadow processes left alive while labeled “mitigated.”
What should a transformation steering committee focus on?
Focus on decisions — what to choose, kill, fund, or unblock — plus floor evidence, behavior change since last month, and who owns the median user’s Tuesday after go-live. Status tours and vendor demos are insufficient if adopters and seams have no voice or owner.
Why are transformation RAG statuses misleading?
RAG colors often track plan, milestones, and system readiness — not human success, workaround retirement, or adoption quality. A green RAG can coexist with a red Tuesday when the scorecard rewards narrative hygiene over lived experience.
How do you fix transformation governance theater?
Require floor evidence in every pack, run decision-first steering, add one behavior metric per workstream, map top risks to owned workflow changes, fund enablement over cascade completions, name seam owners, kill shadow paths on a date, and treat go-live as a technical event — not the finish line.
Image credits: Google Gemini
Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Google Gemini and Cursor to clean up the article, add images and create infographics.
Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.