Field story 5 min

# Escalation Is the Most Expensive Way to Decide

At a medical technology company, a week of hard negotiation produced one forum to own priority. The group that had lost authority kept resequencing work around it until leadership made the shift visible and gave that group a legitimate seat.

The condition

A prioritization model every group ratified on Friday was being quietly reversed by the following Monday.

## The Problem Was Never Downstream

A medical technology company had already paid for one improvement effort. It focused entirely on the development teams, on the assumption that the dysfunction lived where the product was built. Nothing moved, and the company brought us in.

We reached a different conclusion quickly. The development teams were doing what they were told. The trouble sat upstream and in the middle: in the space between the business partners who needed things built and the teams who built them, and in who controlled that space. A project management office owned it. Its leaders decided what the developers worked on and in what sequence. That control gave them influence over the entire delivery organization, and it was not something they intended to give up.

The model we were there to design would connect the business directly to the development teams, with the project office acting as facilitator and communication layer rather than as the authority over what got built and when. Everyone involved understood what that meant for the project office.

## A Week to Reach a Negotiated Model

The company convened a week-long reset with leaders from the business, the project office, and development. These groups had been struggling to work together for months, and the mistrust in the room was open. The arguing began on the first slide. A development leader would signal openness to something, and the project office would push back. The project office would propose something, and the business would counter it. The business would state a priority, and development would question whether it was realistic. By the end of day one, almost nothing had been agreed.

That evening the structural problem came into focus. The project office was not resisting the model. It was resisting what the model would do to its position. Day two was another slog, but edges of agreement started to appear. By day three we were brokering rather than teaching, moving between the groups to find the version of each decision every party could accept without feeling it had lost. The diagram on the whiteboard at the end of that day was not clean. It was negotiated, with caveats in the margins and contingencies noted at each step.

The next day went into detail: process steps, role definitions, and decision rights at each stage of the workflow. The result was a single weekly forum where business partners, the project office, and development leads would review demand, agree priorities, and move work into development through a defined intake with explicit definitions of ready and done. On Friday the group took a photograph together. People were smiling. The model was ratified.

## Then Monday Arrived

The first signal was subtle: an email from one of the project managers suggesting the implementation timeline might need to be revisited. Over the following days, development leaders reported that the project office was still reprioritizing work directly with developers, bypassing the new forum entirely.

It was not an accident. The project office leaders had agreed in the room to a model that removed their control over sequence. Back in their own operating environment, they still held local authority, and their working day began hours before the executives who could question them were awake. Decisions made in their morning went unchallenged until the other side of the business came online. Work the forum had ordered was quietly resequenced, and none of the changes were communicated back to the business partners who had set the original order. The model was implemented in name and circumvented in practice.

The developers now had two sources of authority. Faced with conflicting direction, the work they did reflected whoever had asked most recently, not what the organization had agreed mattered most. This is the hidden price of deciding by escalation and side channel. Each reversal looks small and fast. Together they mean the published order describes one thing while the work follows another, and the people doing the work are left to resolve the conflict themselves, usually in favor of whoever holds the most authority over them.

## Moving Authority in Public

We took what we were seeing to the senior leaders sponsoring the work, including the CIO, and were direct about it. The model worked. The resistance was to what it did to the project office's position. As long as the project office could reprioritize directly with development teams outside the forum, the forum could not function. Prioritization authority had to move, and it had to move visibly, with leadership's explicit support.

Leadership approved two changes together. The project office leaders became attendees and contributors in the forum, with their input valued and included. Their authority to reprioritize outside the agreed process was removed. The forum became the single place where priority was set, and the regional demand councils on each side of the business fed into it through a defined workflow that no group could bypass on its own.

The two halves of that decision depended on each other. Removing the side channel without offering a seat would have pushed the same people further outside the system. Giving them a legitimate voice gave them a reason to use the front door.

## The Relationships Did Not Change. The System Did.

Nobody became friends. The business and development leaders who had argued all week still disagreed, and the project office did not embrace the new model with enthusiasm. What changed was the structure around them.

Once resequencing outside the forum could no longer happen without being seen, it stopped. Once the project office was included as a legitimate voice rather than excluded as a threat, its leaders found ways to contribute that did not require going around the process. One of them, newest to the role and the only relaxed face in the room on the first morning, became a genuine advocate once the structure gave him something to advocate for.

The model that had been agreed in a week, refined in detail, and nearly undone by a time zone was finally operating as designed. Escalation had felt like the fast path to the people using it. It was the most expensive path for everyone else.

An agreement that can be bypassed in private is not yet a decision. It becomes one when going around it is both visible and unnecessary.

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-036-escalation-expensive%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dfield-note-036-escalation-expensive)

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-036-escalation-expensive%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dfield-note-036-escalation-expensive)

Email

Components

[Rank](https://www.agileon.com/insights?component=Rank)[Bridge](https://www.agileon.com/insights?component=Bridge)

Seen in practice
[The work that fixes this Portfolio Governance](https://www.agileon.com/professional-services/portfolio-governance)

Keep reading
[Rank Approvals That Took Months Started Closing in Weeks](https://www.agileon.com/insights/approvals-that-took-months-began-taking-days)[Rank Portfolio Governance Without Bureaucracy](https://www.agileon.com/insights/portfolio-governance-without-bureaucracy)[Rank Prioritization Is a System, Not a Meeting](https://www.agileon.com/insights/field-note-042-system-not-meeting)[Rank The Meeting That Stopped Serving the Work](https://www.agileon.com/insights/the-meeting-that-stopped-serving-the-work)
