Product Intake Management: The Ownership Gap Between Requests and the Roadmap

The engagement behind this page was an organisational change programme run in one of the biggest business units of a global research and advisory company. Product and technology work there was split across nine teams, billing hundreds of millions of dollars annually, with a stated ambition to double that. A programme like that needs evidence to steer by, so we ran an assessment: scoring on twenty-five dimensions, and a qualitative pass to catch what the scores flatten out.

As always, the analysis started with the map.

The map opens centred on product intake management: how new work enters the system. We didn’t pick it for its score. We picked it for where it sits. Among the strong relationships on this map it carries thirteen connections, more than any other dimension we measured, and three of the five strongest relationships measured anywhere in the data have intake at one end. When a system is this connected, treating the loudest complaint gets you the wrong node: the leverage sits wherever the connections concentrate, not wherever the pain is loudest. That is a leverage point, which is why the way work arrives, rather than any single team’s delivery, became the centre of this analysis.

Look at the neighbourhood around it: stakeholder management, the product roadmap, the architecture roadmap on one side; smooth flow of work, cross-team cadence and one-team cohesion on the other. Deciding what to build, and moving it once decided, with intake as the hinge between them. The rest of this page walks that hinge.

The scores came back with a median of 7 out of 10, and most assessments would file that under “fine” and move on. But look at the left side of the strip: of sixty-one respondents, thirteen scored this dimension at 4 or below. The comfortable middle has a long, uncomfortable tail.

Comfort didn’t survive the written observations. This dimension drew twelve coded units, six of them negative against only two positive. Put on the score axis, the words settle around 4; the scores settle around 7. And the words are specific about where it hurts:

“Business has no formal new proposal/request intake process, which leads to difficulties in prioritization, accountability and triaging new requests.”

“For other requests, there is no clear business owner who is accountable.”

“Enterprise projects are brought to us at a latter stage, which then puts pressure on the team in terms of planning and development.”

Notice what none of these complaints are about: nobody says the requests are bad ideas, or that there are too many of them. Every sentence is about the handling. No process, no owner, no timing. The most telling observation is the calmest one:

“Often times, business wants to understand the technical effort/scope of a proposal before they formally prioritize it into a roadmap.”

Read it twice and you can hear the deadlock forming: prioritization waits on an effort estimate, and nothing in the sentence says whose job the estimate is.

Intake wasn’t felt evenly. Team medians spread from 9 at the top to 4.5 at the bottom: the best-scoring teams sat at 9 and 8.5, while the lowest sat at 4.5 with its whole distribution shifted left. A spread that wide on the same intake question is itself information, which makes sense if work reaches different teams through different doors: some teams sit behind a functioning triage, others take requests straight from the business.

The averages alone would have said intake was fine. The connections said it was the busiest junction in the system, and the words said why: requests entered without an owner, and everything downstream of that vacancy degraded together. That reading fed the engagement’s target list, and some of the money that followed paid to train the product and portfolio teams, the people who own how work is scoped, prioritized and admitted. From there, the organisation kept watching the teams as things shifted. Whatever the numbers did next is not something I will claim credit for, that outcome belongs to them. What is worth copying is the approach: they acted on the connections in the data rather than chasing the averages.

A real engagement; an unnamed client, and it stays that way. Team names and identifying details are removed, and quotes are lightly edited for anonymity. Nothing here is asserted. Every figure and chart on this page comes straight out of the underlying assessment data, roughly 2,000 data points drawn from both the qualitative and the quantitative sides. This is one organisation’s measurement: correlations, not causes, and a pattern worth checking in your own intake, not a rule to import wholesale.