Built to Present, or Built to Use

A global IT organization's change team put its whole redesign on a single page: where it stood, where it was going, and the sequence in between. The page exposed an overloaded quarter before it happened, priced the effort in hours, and gave the CIO a plan he could read whole.

04 CASCADE
The condition

A CIO who had funded change efforts before saw a complete redesign in one place for the first time, and found it more concrete than anything his organization had produced.

Information Buried in Decks

The PMO leader of a global IT organization was not short of information. It was buried in tools, spreadsheets, and presentation decks that did not connect to one another. She could not see the big picture clearly enough to make informed choices, and she was still being asked for commitments. Executives who cannot see the whole of their organization's work ask managers and staff to assemble decks that explain progress. The decks take real time to build, their data goes stale quickly, and decisions made from them suffer.

When her internal change team began redesigning how work moved through the organization, we gave it a different kind of artifact: a plan on a single page.

The layout is simple. The desired future state sits in the top right. The current reality sits in the bottom left. The work between them is split into phases, bands of time that can be as general as now, next, later, and last, and grouped into a few focus areas that contain related work. One page for an entire multi-year change is usually too much, and at that size it tends to stop a team before it starts, so we build one page per stage of the work.

Figure 1
Built to present versus built to use
Built to present
  • Compiled by staff for executives
  • Takes real time to build
  • Data goes stale quickly
  • Cost to people left unstated
Built to use
  • Built by the team that owns it
  • Start, target, and path together
  • Overload visible before it hits
  • Time cost estimated by role
The deck reports on the work after the fact. The page is the plan itself, built by the people who will carry it, with the start, the target, and the cost in view together.

Writing Down Where They Stood

Every page starts with a vision. For the first stage, the change team ran a working session of about ninety minutes. Each member imagined the stage finished and wildly successful, wrote silently for five minutes, and shared one or two ideas. The group clustered them into themes, voted for the three to five that resonated most, drafted a statement, and stopped for a gut check: did it energize them, and did it reflect what they actually wanted?

The page for the redesign itself was harder, and the hardest box was the current state. The first draft was honest and heated, and it assigned blame to the business, to leadership, and higher. We suggested a more objective tone. The version the team kept described an approach that was reactive, with multiple intake processes, conflicting priorities, and fragmented workflows; data tools that were maturing but inconsistent; collaboration that relied on meetings; and ad hoc fixes that served a few people rather than scaling. No one objected. One team member noted it was the first time anyone had written down the current state without blaming anyone for it.

The vision box held a plain statement: within a year, a scalable, end-to-end value delivery system that improved visibility and decision-making, so the organization could prioritize and deliver high-value work more predictably. It described the system the organization would have, not the symptoms it was trying to escape.

Two colleagues reading single pages pinned to a board.

The Squeeze in Month Four

Between the two boxes went the work: five outcomes, each with its activities, laid across the four columns. When the grid was full, the team checked the load. The first column held six activities. The second held eleven. The last two held eight each.

One team member saw the problem at once. The second column was the squeeze point. In about four months, when everything in the first column finished and everything in the second started, the team would feel it all at the same time. They debated. One leader thought some delivery and reporting activities could move later without breaking the sequence. Another pushed back: the reporting requirements had to be designed alongside the prioritization tooling so the two would fit together. They settled on moving one delivery activity, which lightened the column without breaking any dependency.

The PMO leader made the call. Move it, she said. If they were wrong, they would see it at the first checkpoint and could move it back. Better to start with a load the team could survive than one that broke it in month four. A deck could have presented the same plan. The page let the team see the overload months before it arrived, while it was still cheap to fix.

Figure 2
Activities per column, before rebalancing
Now 6 activities
Next 11 activities The squeeze point
Later 8 activities
Last 8 activities
Laid out on one page, the second phase was visibly overloaded. The team moved one activity later before the work began.

Pricing the Plan in Hours

One more element went on the page before it was finished: what the plan would cost in people's time. For each outcome and each role, the team estimated the hours of workshops and one-on-one sessions the pilot would need. Portfolio managers carried the most, about three hours a week over the year. Tooling owners came in around two and a half. The pilot's leadership team needed roughly one meeting every other week, and the IT leadership team about one checkpoint per outcome: enough to govern without micromanaging.

The PMO leader called it the artifact that had been missing from every transformation she had funded. They had been asking people for their time without knowing what they were asking for. Now they could ask honestly, because they knew. In our experience, putting the time cost on the table up front is one of the things that separates change pilots people support from ones they merely endure.

Figure 3
Estimated hours per role, over the pilot year
Portfolio managers 165 hours
Tooling owners 139 hours
Each pilot team 32 hours
Pilot leadership 27 hours
Business representatives 11 hours
IT leadership 5 hours
Planning estimates, not measured time. The pilot team figure is per team. Seeing the cost by role turned the sponsorship conversation into an honest request.

Seen Whole for the First Time

The following week, the PMO leader invited the CIO into the session. He had sponsored the effort from the beginning, but this was the first time he saw the complete design in one place. We walked him through the page: the five outcomes, the roadmap, and the time investment.

He took it in quietly, then leaned back. It was, he said, the most coherent transformation plan he had seen come out of the organization, and more concrete than he had expected. The five outcomes felt real. He singled out the capacity estimate. They had funded efforts before without understanding what they would cost the people involved, and both the efforts and those people's own work had suffered for it.

Then he asked the question the page made possible: how would they know it was working? The rest of the session built the answer, a set of measures across five dimensions from pilot readiness to release execution, because no single number could say whether the pilot was succeeding. The page had done its job. It did not perform the plan for the CIO. It showed him enough of it, all at once, for him to ask the next right question.

A plan earns alignment when the people it depends on can see all of it at once, including what it will cost them.

Share With Your Team

Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.

Not sure where to start?

Answer five questions about where work stalls. We send back a starting plan: where to begin and what to look at first.