Business partners were committing to delivery dates for large outcomes that had never been broken into work a team could carry.
One Month to Produce a Roadmap
The CIO of a global enterprise was under pressure. Two years into his role, his CTO said, the business still did not feel supported. The CIO took that pressure to his business partners, the leaders who connected each business area to IT. Each had been in the role for more than a year, and from the start he had asked each of them for the same thing: a roadmap. He had not seen one.
One of them tried to explain. The problem was the tools. They could not really build roadmaps, and the partners needed more time to align their business processes first. The CIO did not accept it. They had had a year. Now they had a month, and he wanted a roadmap for every business area so he could show how IT was creating value for the business.
One of the business partners was already working with us on a separate effort. She had spent more than two decades in the company, most of it on the application side. The business partner role was new to her, and so was building a roadmap. At the end of a working session she asked whether we knew how to make one. Her peers had told her there was no clear example because they lacked the right tools.
It Was Never the Tool
Her delivery teams already used a tool that could build roadmaps, so her first thought was to have them produce one. It was not that simple. The teams were in the middle of reforming, so the old estimates in the tool were no longer reliable, and a roadmap built on them would mislead everyone who read it.
The deeper problem sat upstream. The business's outcomes had not been laid out clearly, and none had been broken down into pieces the delivery teams could digest. All the organization had was the micro view of work: stories and tasks representing less than two weeks each. A roadmap is a macro view. It needs a clear strategy and a backbone that connects that strategy to the work.
Each party saw a different gap. The real one was that there was no process for turning large outcomes into smaller, executable work, and no flow data from the teams to forecast when anything would finish. Meanwhile, business partners were committing to delivery dates with no view of delivery capacity, and one regional office was feeding work straight to a remote team that was already overloaded. The business was not really asking for roadmaps. It wanted delivery it could count on.
| Saw the gap as | |
|---|---|
| The CIO | No roadmap |
| Business partners | Tools that can't build one |
| The work system | No path from outcome to task |
Too Many Outcomes, Too Big to Hand Over
We started by pulling the work scattered across the tool into a single project space, with a common board for each team. Then the business partner and her fellow leaders came back from their planning council with a long list of outcomes. It was far more than could be done in a year, and the outcomes were too big to hand directly to any team.
Two standing groups took the outcomes from there. A small group of leaders, including her, made each outcome easy to understand and recorded how it related to existing products. A second group of product owners and leaders refined the roadmap every two weeks, breaking outcomes into pieces of one to three months, small enough for a team to work on. Nothing reached that group until it had been prioritized and marked ready.
Three disciplines made the pieces usable. Acceptance criteria spelled out, plainly and testably, what each piece had to satisfy before anyone called it done. Every piece had to match a minimum viable version of the product, which freed capacity almost at once in a group with a long habit of over-designing. And each piece was scored for value on a five-level scale while product owners sized its effort, so the order could be read directly: high value and low effort first, low value and high effort not at all. For the first time, prioritization was not a debate between regions. It was a calculation the loudest voice could not bend.
- Outcome from the councilToo many, too big for one year
- Clarified outcomeTied to existing products
- One-to-three-month piecesRefined every two weeks
- Stories and tasksUnder two weeks, on team boards

The Forecast Nobody Wanted
Product owners and teams broke the prioritized pieces into estimated stories and tasks. With everything in one place, she could see what was in flight and feed work to teams with room. The order and the teams' real pace told her when work could realistically finish.
She took her laptop into the CIO's office and turned the screen to face him. Every outcome was on the plan, the highest-priority ones broken down, and the teams' boards showed a pace that made a forecast possible. Then she showed him one. An outcome the business had been promised was close to seven hundred points of work. The teams had finished about two hundred since it started the year before. At their current pace, it would not be done that year, and it would certainly miss the date already committed.
The CIO saw what it meant: they had committed to something they could not deliver. They had, she agreed. But now they could see it ahead of time and manage the business's expectations. She had the same view for every outcome on her roadmap: when it would be done, whether it was slipping past its committed date, and what would have to be deprioritized to pull a date in.
A Number Worth Taking Upstairs
At his next monthly review, the CIO showed the CTO the minimum viable products IT had committed to, how many it could actually deliver by the agreed dates, and the roadmaps behind those forecasts. The CTO was surprised, and for the first time in a long while, he looked pleased.
The roadmap had never been the real deliverable. What the business partners built was the path their goals had been missing: from an outcome leaders agreed on, through pieces a team could finish, to a pace anyone could forecast from. Once the goals reached the work, the work could report back on the goals, including the uncomfortable news that one of them was already late, delivered while there was still time to act on it.
A goal reaches the work only when it is broken into pieces a team can finish, and only then can anyone say honestly when it will be done.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


