Asked what they called a large piece of work, one leadership team produced six different structures in under ten minutes.
Two Organizations, Two Vocabularies
A fast-growing company had recently brought another company into the business, and the combination came with something the leadership team had not expected to negotiate: a vocabulary. The acquired company had its own way of describing work, its own hierarchy, and its own names for the layers between strategy and execution. The existing organization had its own. Neither was wrong. They were simply not the same, and the leaders who now had to run one organization had never been asked to agree on what a piece of work was called, let alone what it meant.
That sounds like a naming problem. It is a structural one. A shared hierarchy is what every other link between strategy and daily work depends on. Without agreement on what the layers are and what each one means, decomposition is inconsistent, progress reports cannot be compared, and conversations about priority have nothing common to anchor to.
Six Answers in Ten Minutes
We opened the session with a simple question: when you describe a large piece of work to someone on your team, what do you call it? The answers came quickly and from every direction.
A leader who had come over with the acquisition described a four-level structure his organization had used for years, with a large container at the top and epics, stories, and tasks beneath it. A leader from the existing side said his teams used four levels too, but with a different name at the top, and he was not sure what the other leader's term was even supposed to mean. A third wanted the hierarchy to reflect how the business thinks rather than how sprints run: the mission at the top, then three-year goals, annual goals, quarterly goals, sprint goals, and tasks. Another objected immediately. The mission never changes, so a layer for it would be one nobody ever touched. Start at three-year goals. A fifth leader said his team did not run Scrum, did not use stories, and did not want its work called stories. Call it a backlog item, he said, because that is what it is.
The room had produced six different structural preferences in under ten minutes. Each one was defensible from where its owner sat.
- Delivery laddersFour levels down to tasks, with rival names at the top
- Goal laddersFrom the mission, or from three-year goals, down to tasks
- One plain itemCall it a backlog item; not every team runs Scrum
We Stopped Arguing About Labels
The obvious next move was to debate the options and pick a winner, or blend them into a compromise. We did neither. A debate about labels in the abstract rewards whoever argues hardest, and nothing in it is anchored to work anyone has actually done. Instead we asked the room to set the labels aside and walk us through something real: a three-year goal the organization was actually working toward.
A senior leader named a multi-year revenue target without hesitating. What would need to happen this year to stay on track? Another answered: reduce client churn and hit a retention target. What would that take this quarter? Two new enhancements to the company's application, live with clients. And this month? Two leaders answered at almost the same moment, talking over each other: create a data baseline, get the data to the client, test and train, market the enhancements, measure the impact thirty to sixty days later, and analyze and report back.
Then we turned the screen so the room could see what had been built while they were talking: a strategic goal at the top, an annual commitment beneath it, a quarterly commitment beneath that, a set of monthly deliverables, and five teams contributing to those deliverables in their own lanes.
- Three yearsA revenue target
- This yearReduce client churn to a retention target
- This quarterTwo enhancements live with clients
- This monthBaseline, deliver data, train, market, measure
- TeamsFive teams contributing in parallel lanes

The Names Mattered Less Than Anyone Thought
The point was hard to miss. The leaders had decomposed a three-year goal into monthly work across five teams without arguing about the name of a single layer. The hierarchy already existed in how they thought about their work. The only open question was which names they were willing to share.
The room was quieter than it had been all session. One of the senior leaders looked at the diagram and remarked that the names mattered less than he had thought half an hour earlier. The leader who had objected to the mission still did not want it in the structure, and that was fine. The hierarchy would start at three-year goals and work down.
The negotiation that followed was shorter and far less contentious than the one that had opened the session, because the room was no longer arguing about whether a structure made sense. It was choosing names for a structure everyone had just built and agreed on.
A Reference Point Built by the Room
The session ended with three things: a shared hierarchy with names everyone could work with, starting at three-year goals; a live example of how a real revenue goal decomposed through every layer of it; and a reference point leaders could return to whenever the definitions started to feel abstract.
The last of those may matter most. Definitions written into a document drift as soon as teams start applying them under pressure. A worked example built by the people who will use the hierarchy is harder to drift from, because anyone can point back to it and ask whether a new piece of work sits at the same level as the thing they decomposed together. The order of operations was the lesson. Decompose real work first, and the shared language follows.
Agree on the structure of real work first. The names then become a short negotiation instead of a long argument.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


