Field story 4 min

# Your Intake Problem Is Not Volume

A global IT organization did not lack intake tools. It had four useful ones that could not see each other. Connecting them, and deciding that work only officially exists once it enters one, gave leaders a picture of demand they could trust, and that picture exposed a problem volume had been hiding.

The condition

Leaders feel buried by incoming work, yet nobody can say how much work is actually coming in, because each request lands in a system that cannot see the others.

## Demand nobody could count

When leaders say they have an intake problem, they usually mean too much is coming in. At a global IT organization we worked with, the more precise problem was that nobody could say how much was coming in at all.

Requests entered through four primary systems, one each for incidents and service requests, enhancements, project and portfolio work, and the delivery teams' backlog. Each system served a legitimate purpose, and each was good at the slice of demand it held. None of them showed the whole. A report pulled from any one of them described a fraction of the work, and the diagnostic had already shown that a good deal of work arrived through side channels that reached none of them.

The consequence was the one leaders felt every week. They often had no way of knowing how much work was coming until their teams were already spending time on it. Demand stayed invisible right up to the point where it started consuming capacity, so every decision about that capacity was made after the fact.

## Isolated, not missing

Over the following weeks we worked with the PMO leader and her internal change team to map every significant intake channel and how it might feed a real front door. As those conversations unfolded, the root cause came into focus. The organization did not have a visibility problem because it lacked tools. It had a visibility problem because its tools were isolated from one another.

The isolation had a cost beyond the missing picture. An enhancement approved in the PMO's portfolio tracker had to be typed into the delivery tool a second time, which created duplication and versions that drifted apart. An incident fixed through a code change had no formal link back to the record that started it, or was linked by hand when someone remembered. Reconciling the systems took hours of manual effort every week, and the reports built on top of that reconciliation trailed reality by days.

The tempting answer, and the one we deliberately did not give, was to replace the four systems with one new platform and move everyone onto it. People knew their entry points and used them. Forcing a migration would have asked people to abandon systems that worked for their purpose, to solve a problem that was really about connection.

## Connect the doors, then decide what counts

So the recommendation was narrower. The formal entry points would stay, because people were already familiar with them. What had to change was the organization's ability to see the work collectively. The PMO leader summed it up in her own words: the formal channels stay open, but everything ends up in one place.

The integration rested on the policy set during the intake redesign: conversations about work could happen anywhere, but work did not officially exist until it entered one of the approved systems.

Implementation began the following week. A technical portfolio manager who knew the systems, the teams, and the configuration history led the work from inside the organization, with a small integration team alongside. Two-way links meant a change in one system updated the other. Approved enhancements now flowed into the delivery tool on their own, arriving with the title, description, estimate, owner, and value score already filled in, and delivery updates flowed back so the PMO could watch progress without asking anyone for it. Incidents carried identifiers that tied them to the delivery work they generated. Around the same time, the pilot's intake redesign cut six ways in to two clear paths, one for projects and enhancements and one for day-to-day operational work.

## Everything entering through a formal channel

The day the integration went live, the technical portfolio manager shared his screen in a review session with the PMO leader. For the first time, work arriving from across the technology organization appeared in a single backlog. An incident from the service system. An enhancement from the portfolio tracker. Then project work and delivery work, almost at the same moment. He let out a breath and said it was finally all visible in one place.

The PMO leader studied the screen and asked whether this was everything. We were careful with the answer. It was everything entering through a formal channel. That distinction was the whole point of the policy, and she understood it. A few months earlier she had been told she was seeing only part of the picture. Now, she said, what mattered was not just that the work was visible. It was that she could trust what she was looking at.

That was the real outcome. The organization had not simply connected systems. It had created a view of demand that leadership could see, understand, and hold up against the capacity it actually had.

## What the whole picture showed

Once demand could be seen in one place, leaders could see it before it landed on their teams. The more interesting result was what the picture revealed once it was complete. The constraint was not the amount of work. With every formal request visible against the people available to do it, the pilot exposed a staffing gap nobody could see before: too few business analysts for the amount of work the developers could take on. Once that imbalance was named, leaders could make targeted decisions about headcount and skill mix instead of arguing about workload in general.

The work was not finished when the pilot closed. Side channels had shrunk but not disappeared, and getting leaders themselves to route every ask through the front door took its own effort. Setting consistent expectations with business partners was still in progress. But the organization had moved from guessing at its demand to reading it, and the first thing it read was that its problem had never been volume. It had been a mix of work it could not see.

More intake capacity will not fix demand you cannot see in one place. Connect the doors, decide what counts, and then look at what the whole picture tells you.

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-007-intake-not-volume%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dfield-note-007-intake-not-volume)

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-007-intake-not-volume%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dfield-note-007-intake-not-volume)

Email

Components

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

Seen in practice
[The work that fixes this Work Management Systems](https://www.agileon.com/professional-services/work-management-systems)

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 From 83 Observations to Five Things to Build](https://www.agileon.com/insights/from-eighty-three-observations-to-five-things-to-build)[Surface Half the Portfolio Was Keeping the Lights On](https://www.agileon.com/insights/half-the-portfolio-was-keeping-the-lights-on)[Surface Six Front Doors Is the Same as None](https://www.agileon.com/insights/field-note-002-six-front-doors)
