Field story 3 min

# Surface the Work Before It Surfaces as a Crisis

A stand-in scrum master at a global research and advisory firm kept staring at three items nobody would touch. A simple skills inventory showed why: the work waited on a specialist assigned to the team for a fifth of his time. With the evidence on screen, leadership moved him over before the stall became a missed delivery.

The condition

The same few backlog items sit untouched for weeks on a team that is cross-functional on paper, and nobody can say why.

## Three items nobody touched

The scrum master was not this team's regular scrum master. She was filling in at a global research and advisory firm, and the problems seemed to grow every time she looked at the board. The same three items had been sitting there for weeks. Nobody touched them.

We asked who normally did. One person, she said, when he had time. Then she added the part that bothered her most: he was not even on this team.

On paper the team was cross-functional. Anyone was supposed to be able to pick up anything in the backlog. In practice, certain items barely moved, because they waited for that one specialist, and when he was busy elsewhere they simply sat. Nothing about the board said so. The items looked like any other unstarted work. The delay was real, it was growing, and it was invisible to everyone who was not staring at those three cards.

## A hunch with nothing behind it

She had started to suspect the truth: the work was not being picked up because most of the team could not actually do it. But she had no way to prove it. There was no list of who could do what, no record of skills, nothing to point at. She did not even know whom to ask, and that, she said, was the part that got to her.

This is how stalled work usually stays hidden until it becomes a fire. A hunch from a stand-in is easy to wave away. A board full of unstarted items looks like a prioritization question, not a capability one. Left alone, the gap would have announced itself the usual way: as a slipped date, explained after the fact.

## Writing the skills down

A senior leader at the firm had asked us to drop in on a few teams, and this was one of them. We ran a chartering session, and the part that mattered most for this problem was the skills inventory.

It started with the team's mission: what is this team actually here to deliver? From the mission we built a catalog of the skills that delivery required. Then each team member rated themselves on every skill. Beginner meant limited knowledge and no real practice, needing help to apply the skill. Advancing meant able to work independently. Expert meant mastery, enough to teach and mentor others. The standard was at least one expert on the team for every skill.

One team member eagerly marked himself expert in most areas. We pointed out that an expert would be expected to train everyone else in those skills. He quietly moved several ratings back to advancing. The finished matrix was more honest for it, and it confirmed what the scrum master had suspected. For some of the work in the backlog, the skills simply were not on the team.

## Evidence instead of a hunch

She took the matrix to leadership. Their first answer was the one she expected: the specialist could not be pulled onto her team, because he was only twenty percent dedicated to it.

She put the matrix on the screen. More than twenty percent of the work in this cycle needed his skill set, she said, and right now that skill set was not on the team. Did they want the work delivered, or did they want it to wait? A stand-in, pushing back on a room of senior people, won the argument. Not on seniority. On data. Leadership moved the specialist onto the team full time for the next couple of weeks.

The root cause was structural. The team had been assembled from the job roles people were hired into, not from the skills the current work demanded, which produced a roster that looked cross-functional and was full of bottlenecks. The matrix did more than settle one argument. It showed where the team needed to invest in upskilling, mentoring, and working together so that the next stalled item would not depend on borrowing one person.

That is what surfacing early buys. The three stuck items had been a crisis in waiting, visible only as a vague unease to one person filling in. Written down, the same gap became a staffing decision leaders could make in one meeting, while there was still time for it to matter.

Work that waits quietly on one person is not idle. It is a crisis that has not been scheduled yet, and the only cheap moment to deal with it is before it arrives.

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-010-before-it-is-a-crisis%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dfield-note-010-before-it-is-a-crisis)

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-010-before-it-is-a-crisis%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dfield-note-010-before-it-is-a-crisis)

Email

Components

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

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

Keep reading
[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)[Surface By the Time You Feel It, the Cost Is Already In](https://www.agileon.com/insights/field-note-001-demand-already-cost-you)[Surface From 83 Observations to Five Things to Build](https://www.agileon.com/insights/from-eighty-three-observations-to-five-things-to-build)[Flow The Better Practice Was Already in the Division](https://www.agileon.com/insights/field-note-055-one-backlog)
