Your Process Is Accumulated, Not Chosen

An executive team put its own process maps on the wall and marked every step where work was being wasted. The steps nobody had chosen were easy to find. The one to fix first was the one nobody predicted.

05 FLOW
The condition

An approval step had three approvers, and two of them had not changed a decision in eighteen months.

Crosswalks and Jaywalkers

The executive leadership team of a healthcare technology company had spent the previous day mapping its own processes. The next morning the maps were on the whiteboard. The question was not whether processes existed. It was whether the steps were working the way leaders wanted, or whether teams were routing around them because the official path had become the path of most resistance.

We framed it with the way people cross a city street. Pedestrians instinctively choose the route with the least resistance, and work is no different. Processes are the crosswalks. If they take people too far out of their way, people jaywalk, because the official path costs more than the value of the work they are trying to deliver.

Before anyone stood up, one leader said that if they did this honestly, he was not going to like everything they found. Probably not, we said. The wastes that are hardest to address are usually the ones that most need it.

A Sticker for Every Kind of Waste

We gave the leaders a vocabulary of seven wastes, among them errors and rework, inactive work with no owner, missing essentials, gold-plating, where extra approvals add time without value, bottlenecks, and people factors such as overload or access constraints. Then we walked them to the first process on the wall, the intake-to-delivery flow for product work, and asked them to put a sticker on every step where one of those wastes happens today, a different color for each kind.

The first sticker went on the requirements step within thirty seconds. Missing essentials: requests arrived without acceptance criteria, without an audience, without a target date, and the team spent two weeks chasing the requestor before it could even scope the work. Two steps later came errors and rework. Once the work was built, its requirements turned out to be wrong, and the team went back again.

Then a leader put a sticker on an approval step further downstream and called it gold-plating. The step had three approvers. Two of them were honorary; they had not changed a decision in eighteen months. Another leader admitted, half laughing, that she was one of the honorary approvers. The leader holding the sticker said he was the other.

Figure 1
One flow, three stickers
  1. Request arrives
  2. Where it broke Requirements Missing essentials: two weeks chasing the requestor
  3. Where it broke Build Rework: requirements found wrong
  4. Where it broke Approval Gold-plating: three approvers, two honorary
  5. Delivery
The first process on the wall. Each marked step was a place where the official path cost more than it returned, and two of the people who owned that cost were in the room.

The Wall Filled Faster Than Anyone Expected

These leaders had looked at their processes for years, but never this way, with the wastes named out loud, in a room where everyone saw the same picture at the same time.

On the customer-facing delivery process, one stretch of three steps collected bottlenecks, inactive work, and people factors at once. All of it ran through a single person, the only one with the access needed to move the work, who had been telling leadership about it for a year. On the reporting flow, weekly reports were being generated and filed in a folder no one opened: capacity spent producing artifacts with no readers. On the strategic alignment process, one step collected four kinds of waste by itself. It had been built to do five jobs in one in order to save time, and it now cost more time than the steps it had replaced.

By the end of the morning the wall was covered, and the pattern was visible before anyone counted. Handoffs and rework were marked most often, then gold-plating and bottlenecks. Missing essentials and inactive work clustered in intake and scoping. People factors appeared wherever a role had become a single point of contact.

A small team working through a process sketch on a whiteboard beside a wall of notes.

Letting the Score Settle the Argument

Seeing the waste was the first step. Deciding what to act on needed something sturdier than whoever argued hardest. Each waste was assessed from one to five on four dimensions: how severe it is when it happens, how often it happens, how far its effects reach, and how much effort it would take to fix. Severity times frequency times reach, divided by effort, produced a ranked list.

Scoring took most of the afternoon. Most of the arguments were about severity, because a waste in one leader's area always looked larger to that leader. We held the room to evidence: what the waste actually costs when it happens, how often it actually happens, how many people it actually touches. Once the scores were on the wall, the debates settled.

The top of the list surprised everyone. The highest score went to the sprint review. A stakeholder needed information that already existed in the team's own work reports, but had no way to reach it without pulling the team into another meeting. High severity, high frequency, wide reach, and little effort to fix. The leader who had complained about it for six months had never realized the fix was small. Second was a duplicated onboarding sequence that executives and new hires each performed in parallel, known to everyone and fixed by no one. Third was a broken handoff from data analysts to teams that were either over-skilled for the work or the wrong resource for it.

Figure 2
Top of the ranked waste list
Sprint review info gap 64
Duplicate onboarding 37.5
Analyst handoff 33.3
Workshop priority scores, calculated as severity times frequency times reach, divided by effort. The top ten ran from 64 down to 20. The leader who opened the day did not have the first item on his radar that morning.

From a Workshop Finding to a Standing Register

Individually, none of the wastes were news to the room. The pattern across them was. The same kinds of waste were appearing in several processes and tracing back to the same few causes: missing inputs at the front of the flow, approvals that had stopped earning their place, and ownership concentrated in single people until it hardened into a bottleneck.

The executive team chose four workstreams from the top of the list: the sprint review, the duplicated onboarding, backlog entry points that were producing duplication, and whether teams working in parallel on overlapping initiatives should be combined. Everything else stayed on the ranked list, ready for when the first four closed. The list stopped being a workshop artifact and became a register leaders could return to as conditions changed.

The leader who had opened the day with a warning closed it at the wall. They had been refining processes for years, he said, and this was the first time they had stepped back to ask whether the whole shape of them was still right. That is the difference between a process an organization has and a process it chose.

Figure 3
Ten wastes, three causes
10 top-ranked wastes
  1. Missing inputs up frontRequests arrive without what the work needs
  2. Approvals past their useSteps that no longer change decisions
  3. Single-point ownershipOne person holds the access or the knowledge
The top-ranked wastes looked like separate problems in separate processes. Underneath, they traced back to three structural causes.

Processes grow by addition. Unless someone deliberately asks each step to earn its place, the shape of the work is whatever the years left behind.

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.