Field story 5 min

# Same Tool Is Not the Same System

In a global IT organization's front-office delivery function, every team used the same delivery tool and no two boards meant the same thing. The fix was not another tool or a better report. It was agreeing what each step of the work means, then building that meaning into the tool everyone already had.

The condition

Every delivery team works in the same tool, and a leader still cannot tell where any piece of work actually is, because each team's columns mean something different.

## A board landscape that said nothing

The PMO leader of a global IT organization described the problem plainly. Some front-office delivery teams were in the organization's main delivery tool. The trouble was that nobody had ever defined what the workflow steps should be. Every team had built its own columns, named them whatever made sense at the time, and the result was a board landscape that told leadership nothing consistent about where work was.

The front-office delivery leader, on the same call, added the part that mattered most. It was not just the naming. The steps themselves were different. One team's in progress started where another team's discovery ended. Rolling anything up across teams meant comparing things that were not the same.

We asked whether anyone had ever mapped out what the workflow should look like. Not formally, she said. People knew what to do; nobody had written it down as a standard. The same organization had already found its project containers and its names for units of work drifting apart team by team. This was the same pattern in the steps work moved through.

## One tool, many systems

On paper, the organization had already standardized. Everyone was on the same platform. A survey we ran on how people used it showed what that had achieved. The biggest pain points were inadequate training and inconsistent configuration. The feature people used most was the board itself; much of the rest was unknown to most users. Each team had set the tool up to suit itself, and seeing across teams meant stitching data together by hand.

When leadership asked where a large piece of work stood and heard that it was in discovery, that could mean the first day of research or the thirtieth day waiting for the business to sign off. The column carried no information. The delivery leader had her own version: she had asked where something was and been told it was in progress, when it had actually been paused six weeks earlier and nobody had updated the board.

The root cause: the workflow steps had never been designed, documented, and built into the tool at the enterprise level. A board where the columns mean different things to different teams cannot produce reporting that leadership can act on.

## Design the steps before touching the tool

The strategy was to design the workflow deliberately before building anything: define what each state means, what must be true for work to move from one state to the next, and how the leadership view of the work connects to the delivery teams' view. We asked the delivery leader to walk us through it.

When something of a month or more arrives at the leadership level, she said, management has to review it before any effort starts. That review happened, but it was invisible in the system; the work just sat with no status that meant anything. If management decided it was worth pursuing, it went to a business analyst, and discovery began. Discovery was not just research: requirements and estimates from teams and vendors, then the manager's approval, then the business's sign-off. Several handoffs lived inside one column, which was why it took as long as it did. Initiation followed, when the work was funded, then planning, where the analyst shared acceptance criteria with vendors and teams before breaking the work into stories on the delivery board.

That last handoff, she said, had always been the messiest: the leadership board lost track of work once it reached the delivery teams.

## Two boards, one language

What we built was a dual workflow: two connected boards. The leadership board held the macro view of each piece of work, from new through closure. The delivery board held the micro view, the stories and tasks that made up the execution of that same work. Both used the same defined steps, so when something was in execution on the leadership board, it meant stories were moving through progress, review, and testing below it.

On the delivery side, ready for development became a gate: nothing passed it without meeting the definition of ready, and teams pulled from it only when they had capacity. Anything stuck moved to blocked, a column of its own with someone accountable for clearing it, rather than sitting silently wherever it had stopped. On the leadership side, closure meant deliverables complete, handoffs finished, and documentation in place, and separate columns for paused, cancelled, and deferred meant stopped work no longer posed as active work.

The PMO leader raised the question that could have sunk it: not all her teams ran Scrum, some ran traditional programs or Kanban, and she could not build a workflow that fit one method and tell everyone else to adapt. That was the principle the design rested on. The steps were method-agnostic, so in progress meant the same thing whether a team worked in two-week sprints or six-month programs. The reporting would work because the workflow language was shared, even where the method underneath was not.

## The same words on every board

We then built the workflow directly into the delivery tool, every column defined and every transition rule set. The teams ended up with a workflow that fit how they already worked, named in language everyone shared, inside the tool they were already using.

In the pilot that followed, every kind of work came to follow the same structure, from yearly initiatives down to daily tasks. For the first time, delivery teams shared a common language and could see all of their work in one place. Teams that had been uncomfortable with the tool started helping each other use it. The habits around how work gets entered were still settling when the pilot closed, and that is an honest limit: a defined column only means something if people move their work into it.

The shared vocabulary is also what made the next step possible. Reports could finally come straight from the work, because a status meant the same thing on every board it appeared on. The organization had owned one tool all along. Only once the steps meant one thing did it start working like one system.

Standardizing the tool buys a shared logo. Standardizing what each step means buys a picture leaders can act on.

Know someone running into this? Send it to them.

[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=http%3A%2F%2Fagileon.test%3A64380%2Finsights%2Ffield-note-022-standardize-meaning%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dfield-note-022-standardize-meaning)

Email

### Share With Your Team

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

Your Message

Open in Email

Share

[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=http%3A%2F%2Fagileon.test%3A64380%2Finsights%2Ffield-note-022-standardize-meaning%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dfield-note-022-standardize-meaning)

Email

Components

[Flow](https://www.agileon.com/insights?component=Flow)[Signal](https://www.agileon.com/insights?component=Signal)

Seen in practice
[The work that fixes this Value Stream Management](https://www.agileon.com/professional-services/value-stream-management)

Keep reading
[Rank No Urgency, No Change](https://www.agileon.com/insights/no-urgency-no-change)[Flow The Engine Nobody Builds](https://www.agileon.com/insights/the-engine-nobody-builds)[Surface The Next Reorg Will Be AI-Driven. Most Will Do It Wrong.](https://www.agileon.com/insights/the-next-reorg-will-be-ai-driven)[Flow We Stopped Making Documents and Started Building Machines](https://www.agileon.com/insights/documents-versus-machines)
