The Bridge Lived in Leaders' Heads

At a global manufacturer, regional leaders spent a week turning the informal network they used to clear blockers into a visible escalation path any team member could use. On the last day they walked across the street and handed it to the delivery teams.

06 BRIDGE
The condition

Blockers that crossed teams and regions could only be cleared by leaders who knew who to call, and that knowledge lived nowhere the teams could reach.

Two workshops on opposite sides of the street

A blocker inside one team can usually be cleared by that team. A blocker that crosses teams and regions waits for someone with the reach to move it, and the teams who feel it most rarely know who that someone is.

At a global manufacturer, two workshops ran the same week on opposite sides of the same street. On one side, the company's internal coaches worked with delivery teams on norms and working agreements to improve how they coordinated and delivered. On the other, we worked with the leaders whose job was to remove what those teams could not remove themselves.

The room was full of experienced leaders who had been told to attend. We opened by telling them something they already knew. Each of them held a leadership role because they had learned how to solve problems. They knew who to go to in order to move work forward, and they had the authority to remove obstacles their teams could not.

Then we asked them to rate their confidence, from one to five, on seven statements about handling impediments, from how to write one to who resolves which kinds. One leader observed, half smiling, that we wanted them to grade themselves so we could show how little they knew. We wanted to show by the end of the week how much had changed.

Bigger than me, and not mine to fix

The leaders surfaced impediments from their own experience, employee pain points, and survey input. Broad frustration took shape as specific blockers, then as recurring categories that pointed toward systemic friction. Their feedback at the door that evening was skeptical about their role in removing problems for teams and whether any of this would help.

The next morning we read that feedback aloud and pulled the concerns into the agenda. Then came the hardest moment of the week. The leaders realized how many of the impediments on the wall could not be solved by anyone in the room. They depended on more senior people. One said these problems had always existed and would never be addressed. Another pointed to a blocker every team had reported and said, close to despair, that he could not help them. Asked why, he said it was bigger than him and it was not his to fix.

We stopped the activity. These impediments crossed teams and regions. But the leaders already had what they needed to begin. They knew how the company actually worked, and even when they could not resolve a problem themselves, they knew who to call.

Knowing who to call is not a process

A skeptic in the second row pushed back that knowing who to call is not a process. He was right, and that was the point. Each leader carried a private network for getting things unstuck. It worked for the person who held it and nobody else.

The resolution pathway was designed to capture that organic network and make its steps visible, so teams could draw on leaders' experience and resolve more on their own. The skeptic pressed: what about problems leaders could not solve either? That was what the pathway was for. Anyone could make a problem visible and raise it to a higher level of leadership when it was beyond their own connections, experience, or authority.

Over the third day the pathway took shape: how to write an impediment clearly, bring it in through intake, and triage, prioritize, and resolve it. During the workshop we built the workflow in the organization's work management tool, with structured fields, custom screens, and escalation driven by ticket status. An impediment could move from a team to a regional action group and on to a leadership action group in a few clicks. Any member of the organization could raise one, and the ticket captured urgency and impact at the moment it was submitted.

Figure 1
The resolution pathway
  1. What changed Anyone raises it Written clearly, urgency and impact captured
  2. Team level Resolved locally where possible
  3. Regional level Regional action group takes it on
  4. Leadership level When it needs more reach or authority
What had lived in leaders' personal networks became a visible route. Anyone could raise an impediment, and it moved up only as far as it needed to.
Warehouse colleagues coordinating work beside a forklift and inventory racks.

Doubt in the evenings

Not everyone was convinced yet. The internal leader running the team workshops across the street had overheard some leaders complaining about the week over lunch, and in the car one evening he asked whether we were losing them. Our read was the opposite. The leaders were vocal about regional problems and doubted headquarters would ever address the bigger ones. That was why he would need to champion their impediments early, so quick wins gave the pathway visible proof. One of his coaches added that leaders arguing was a good sign. Silence would have been the worry.

The walk across the street

On the fourth day we repeated the self-assessment. Self-reported confidence had risen on all seven statements. The largest gain was in knowing where to log an impediment, which moved from an average of 3 to 5. Understanding how the action groups contribute to removing systemic impediments rose from 2.63 to 4.14, and knowing what to include when documenting an impediment rose from 3.38 to 4.86. The skeptic noted that he had rated himself a two on Monday for logging an impediment and a five that day.

The smallest gain is the honest one. Knowing who is responsible for resolving different types of impediments moved only from 3.13 to 3.43. A week can make a path visible. It does not settle every question of ownership along it.

By the end of the week the leaders were talking through action plans, not just naming impediments, and volunteers stepped forward to serve on the regional action group. The senior leader who had despaired on the second day asked to be put down, saying that if this got built, he wanted to be one of the people who kept it running.

The session ended with the leadership group walking across the street to present the resolution pathway to the delivery teams. It was a short walk and a long one. Four days earlier these leaders had wondered what a workshop could teach them. Now they stood in front of the teams whose blockers they had learned to clear. The bridge across teams and regions had always existed. It had existed in leadership's heads. Now the organization could use it.

Figure 2
Leaders' self-rated confidence, day one and day four
StatementDay oneDay four
Where to log one3.005.00
Action groups' role2.634.14
What to include3.384.86
Writing one clearly3.564.57
Path to resolution3.254.14
Updating status3.884.71
Who resolves which3.133.43
Average workshop self-ratings on a one to five scale, not measured performance. Every statement rose; knowing who resolves which impediments rose least.

If the path across a boundary lives in someone's head, the organization does not have a path. It has a person.

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.