Impediment Resolution System

# Your people are busy. The question is what with.

Every organization has more capacity than it can see. It leaks into workarounds, firefighting, and problems solved twice. Agileon builds an impediment resolution system inside the tools you already run, so that time gets counted, routed to whoever can clear it, and given back to the work.

parts of the system

- 1 **Surface***How work enters*
- 2 **Scope***How work is understood*
- 3 **Rank***How priorities are ordered*
- 4 **Cascade***How strategy becomes work*
- 5 **Flow***How work moves*
- 6 **Bridge***How groups connect*
- 7 **Signal***How the system reads itself*

Hover a part of the system to see how this service works on it. Select it to learn more.

You will recognize this

## What it looks like from inside.

Capacity leaks into workarounds, firefighting, and problems solved twice, none of it in the plan, so commitments are made against capacity that does not exist.

- Dates slip, and nobody can say exactly where the time went.
- Your best people spend their weeks firefighting instead of building.
- The same blockers come up in meeting after meeting and never seem to close.
- Teams say yes to work before anyone knows what it costs, then absorb the difference.
- The hardest cross-team problems quietly disappear instead of getting decided.

Why it keeps happening

## Capacity has a visibility problem, not a motivation problem

A real share of every week goes to what is in the way: chasing access, restoring what broke, re-solving a problem someone fixed last quarter, waiting on a decision nobody owns, and talking about issues without closing them. None of it lands in the plan. So leaders plan as if their teams have full capacity, commit dates against it, and watch the plan slip while the overrun is absorbed quietly, team by team. The time is already being spent, just with no owner, no cost attached, and no record that would stop it from happening again.

Where your capacity goes

## Capacity is never 100%.

Every team and every leader also spends time on what is in the way. Today that time runs on borrowed hours: no record, no cost, nothing carried forward. The system puts it on the record, and the record is what lets you take it back.

**Delivery workFirefightingTalking about problemsInvisible: workarounds and problems solved twice**

Today: the plan assumes the whole bar is delivery. The hatched share is real time, spent with no owner and no record.

With the system: the hidden share is named and counted, repeat fixes become policy, and delivery gets its time back.

Illustration of the pattern, not a measurement.

Where it leaks

## The time is already being spent.

- Working around blockers Hours go to getting past something instead of moving the goal.
- Firefighting Fixes that only restore what worked yesterday: access lost, a tool down, a license expired.
- Problems solved twice No record of how it was fixed, so the next person solves it from scratch.
- Talking, not resolving The same issues fill meetings and side channels without ever closing.
- Untracked asks Quick requests arrive by message, become work, and never reach the plan.
- Decisions nobody owns Problems that need authority above the team wait, or quietly get canceled.

What one impediment log showed

## 147 impediments raised in six months. Almost none of the knowledge kept.

A global manufacturer already had a tool for impediments. Six months of its log told the story every organization without a system lives with.

**0 of 53**
closed impediments had any record of what was done to close them, so every fix had to be found again.

**32 of 38**
urgent impediments still open were past their own target date. None had ever been escalated.

**27 of 53**
closed impediments were firefighting: restoring something that worked yesterday, not building anything new.

**45% vs 5%**
closure rates across regions using the same tool. The difference was whether someone worked the queue.

**2 to 8 hours a week.** What senior leaders at a health technology company estimated they each spend on issues discussed but not resolved.

Anonymized. Manufacturer figures from a six-month export of its impediment log; leader hours are the leaders' own estimates.

What we build

## The mechanisms that change the outcome.

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

### Count what is in the way

The person held up raises it where it happens, in your existing tool, with what it blocks, who else it affects, and what has already been tried. Borrowed time gets a record.

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

### Weighed, not argued

Impact, urgency, and benefit are weighed against the effort to clear it, and each effort level keeps its own bar, so hard problems still reach the top of their queue.

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

### Cost on every close

Nothing closes without what was done, who cleared it, and what it cost, confirmed by the person who raised it. Cycle time and hours lost become measurable.

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

### Routed to who can clear it

Effort decides the route: the person's own plan, the team board, a cross-functional forum, or leadership only when it needs budget or policy authority.

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

### Fixes become policy

Closed impediments are cataloged, and the same fix three times becomes a standing policy with an owner and a response time.

Why it stays hidden

## People absorb it instead of raising it.

Silence is rarely indifference. Raising a problem usually costs more than living with it, so capable people absorb the cost and the capacity disappears with it. The system is designed to remove each of these costs.

- It feels like blaming a colleague A record of what is in the way says where capacity went, not who caused it.
- Raising it never changed anything When nothing happened last time, people stop asking.
- Workarounds are quicker Problems get solved quietly through whoever knows whom, so only the unsolvable ones surface.
- It feels like more overhead The time is already being spent. The system moves it onto the record instead of adding work.
- It seems outside our control If leadership cannot fix it, why log it? Yet most impediments never need leadership.
- Talked about, never owned Issues get discussed in the standing meeting, then left without an owner or a date.

How it works

## From raised to resolved, in the tools you already run.

- 01 **Raise** The person held up writes it in their own words, including what has already been tried.
- 02 **Weigh** Impact, urgency, and benefit are weighed against the effort it takes to clear.
- 03 **Route** Effort decides where it is worked, so it reaches someone who can clear it.
- 04 **Work** It has an owner and a clock. When the clock runs out, it escalates or gets re-rated.
- 05 **Close** Nothing closes without what was done and what it cost, confirmed by the person who raised it.
- 06 **Catalog** Closed impediments are recorded. The same fix three times becomes a standing policy.

Effort decides the route

## Most impediments never need leadership.

The effort it takes to clear an impediment decides where it is worked. Each level keeps its own bar for acting now, so the hardest problems can still reach the top of their queue instead of waiting behind easy ones.

**One person***Their own plan*

Name the person and a date.

**One team***The team board*

It goes into the team's next planning.

**Several functions***A cross-functional forum*

An owner on each side, worked in a slot that already exists.

**A decision above the functions***Leadership*

Only what needs budget or policy authority, with the decision it needs written down.

What closing impediments returns

## What you get back.

- Capacity comes back Hours spent working around the same blocker go back into the goals.
- You see where time goes Firefighting versus building, by team and by category, every month.
- Commitments get honest Plans are set against measured capacity, not the capacity everyone assumes.
- Decisions rest on evidence Weighed factors replace whoever argues loudest, so priorities are defensible.
- Leaders see only what needs them The few items that truly need budget or policy authority arrive with the facts already found.
- Fixes become policy Repeated fixes become standing answers with an owner and a response time.

One honest boundary: the system routes the work, it does not create capacity. It shows the gap clearly, and closing that gap is a staffing decision you can now make with evidence.

What you keep

## Working assets, not a recommendations deck.

- Impediment work item and intake
- Effort-based routing and forum slots
- Resolution write-up standard
- Impediment knowledge base
- Resolution policies
- Monthly impediment signals

How you will know

## Signals the system is changing.

- Impediments close with the raiser's confirmation
- Leadership sees only items that need its authority
- Repeated fixes turn into standing policies
- The firefighting share becomes visible and falls

How the engagement runs

## Five stages, from evidence to ownership.

Every engagement runs the same five stages. What happens inside them is specific to this work. We pilot in weeks, not quarters.

- 01 **See the system** Find where work is actually being slowed, including the workarounds people never report, and what has already been tried.
- 02 **Find the few causes** Group what surfaces into a few categories the organization can own, and see where capacity is quietly going.
- 03 **Design the fix** Configure the impediment item, intake, routing by effort, the close gate, and slots in meetings that already exist.
- 04 **Prove it in live work** Run the system in live work, train the people who raise and carry impediments, and tune routing as real items move through it.
- 05 **Hand it back** An internal owner runs the cross-functional pass, catalogs closures, and turns patterns into policy without outside support.

From the field

## Stories that show the pattern.

[Field story The Meeting That Stopped Serving the Work An audit of standing meetings in a large IT organization showed how much of the week they consumed. The more important finding was what those meetings had been trying to compensate for.](https://www.agileon.com/insights/the-meeting-that-stopped-serving-the-work)[Field story When More Work Tripled the Wait A delivery team more than doubled the work it carried at once and watched its cycle time nearly triple. It finished slightly more, and paid for it in burnout and a resignation.](https://www.agileon.com/insights/when-more-work-tripled-the-wait)[Field story The Front Door Is Not Real Until Leaders Use It A global technology organization rebuilt its intake process and still found people being asked to work outside it. The process held only after the leadership team admitted the habit, closed the urgent-work loophole, and committed to using the front door themselves.](https://www.agileon.com/insights/the-front-door-is-not-real-until-leaders-use-it)

Often paired with

[Adaptive Delivery Approach Each team runs its own method, and nobody can see or improve delivery across them.](https://www.agileon.com/professional-services/adaptive-delivery-approach)[Work Management Systems Requests come from everywhere, priorities shift weekly, and every report is built by hand.](https://www.agileon.com/professional-services/work-management-systems)[Organizational Health Diagnostics Something is wearing our people down, and nobody agrees on what it is.](https://www.agileon.com/professional-services/organizational-health)

Where this applies

[Global IT If the same blockers keep resurfacing across teams and nobody owns them, start here.](https://www.agileon.com/industries/global-it)[Health Tech If implementation keeps stalling on problems everyone already knows about, start here.](https://www.agileon.com/industries/health-tech)[Manufacturing If sites solve the same problem separately and the fix never travels, start here.](https://www.agileon.com/industries/manufacturing)
