Field story 5 min

# Half the Portfolio Was Keeping the Lights On

A healthcare technology leadership team expected a tidy exercise in sorting its work into categories. A quiet question about new work versus keeping the lights on changed what its intake process recorded, and the first dashboard showed the portfolio split almost evenly.

The condition

A leadership team believed its portfolio was mostly new building, and nothing in its intake process could tell it otherwise.

## A Pop Quiz About the Front Door

The executive leadership team of a healthcare technology company was on a video call, placing notes on a shared whiteboard in answer to one question from us: what categories of work exist in your backlog? The answers came from wherever each leader sat: the work that held the culture together, such as town halls and team meetings; client work like quarterly reviews and renewals; the sales pipeline.

As the notes piled up, we grouped them into broader families. Four major categories emerged, covering the work that brought in revenue, the work that built the product, the work that served existing clients, and the work that shaped the company itself. Then we zoomed out and asked the room how many of those categories fit the existing intake process.

One leader answered immediately, as if it were a pop quiz. They used the intake process the same way regardless of what kind of work it was. The leader responsible for client success saw the consequence at once. That, she said, was why her team's requests kept getting less attention than they deserved: enhancements customers asked for daily were competing in the same lane as new product work, and losing. The product leader did not enjoy the remark.

## One Lane for Every Kind of Work

The problem was not that the company had different kinds of work. Every company does. The problem was that every request entered through the same process, followed the same path, and was judged the same way, as though the differences did not exist. The intake process assumed all work should be evaluated alike, and the leadership team was starting to see that the assumption was false.

We walked through what each category actually needed. Revenue work moved at the speed of opportunity and often needed fast decisions. Product work needed deeper scoping, because getting it wrong was expensive downstream. Client work arrived in a steady operational rhythm and at high volume. Work that shaped the organization itself needed leaders able to weigh long-term trade-offs. Each called for different information, different reviewers, and different decision criteria. The aim was to receive all of them through a single front door without forcing them to be treated as the same thing.

One leader named it plainly: they had been treating everything the same way. The product leader added the point that made it practical. The categories were not only for leaders organizing a backlog. They were for the people submitting requests, so those people could understand how their work would enter the system.

## The Question Nobody Had Planned For

Then a leader who rarely interrupted raised his hand. He was struggling, he said, with the difference between work that creates something new and work that keeps the lights on. The intake process seemed designed for new work that crossed several groups. What about all the operational work the teams did every day? Shouldn't intake recognize that too?

For a moment the room went still. He had found a second dimension we had not expected to surface until later. Work category was one dimension. Work class was another. Categories describe what the work is about. Classes describe the basic nature of the work itself. Some work creates something new. Some work keeps existing systems running. Both are essential, and both compete for the same capacity.

We named the distinction with obvious examples. New features, roadmap initiatives, and research efforts were build work. Defects, maintenance, access requests, and operational support were run work. The leaders sorted everything on the whiteboard without difficulty. What had started as a categorization exercise had turned into something more useful: a shared vocabulary the leadership team could hand to its own reports to describe their work.

## The Chart That Took a Moment to Load

Over the following weeks, the intake process was changed to capture both dimensions at the moment work entered the system. Every request now had to name its category and its class. At the next leadership meeting, we showed the first dashboards built from that data.

The first divided the portfolio by class. When it finally loaded, the room was quiet. Build work was forty-eight percent of the portfolio. Run work was fifty percent. Only two percent was uncategorized.

The leader who had answered the pop quiz reacted first. It was almost an even split, she said. She had always assumed they were mostly building, and half of what they were doing was keeping things running. The leader who had raised the question nodded. He had known the difference mattered, he said, but not how much of their capacity went to run work until he saw it, and he suspected it was part of why it was so hard to get where they wanted to go.

The second chart, by category, surprised them again. Work for existing clients was by far the largest share. Revenue, the subject the leaders talked about most, was the smallest slice of effort. The product leader worked out why: the company spent its effort on client work with revenue implications, and the chart finally separated the two.

## Different Demands, Finally Visible

For the first time, the leadership team could see its portfolio as data rather than as assumptions and anecdotes. It had started the exercise believing it had one backlog full of work. It finished understanding that it had fundamentally different kinds of work competing for the same capacity.

That changed the diagnosis. The teams had not been struggling because people ignored the intake process. They had been struggling because the process could not tell fundamentally different demands apart, so no one could see how the company's capacity was actually being divided between building the future and running the present.

Nothing about the work itself had changed. The front door now recorded what kind of work each request was, and that made the balance between building and running something leaders could see and argue about with evidence. It came soon after the same leaders had learned how little of their work was planned. Together, the two findings described an intake process built for a simpler company than the one walking through it.

Leaders cannot balance kinds of work their intake process cannot tell apart.

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%2Fhalf-the-portfolio-was-keeping-the-lights-on%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dhalf-the-portfolio-was-keeping-the-lights-on)

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%2Fhalf-the-portfolio-was-keeping-the-lights-on%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dhalf-the-portfolio-was-keeping-the-lights-on)

Email

Components

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

Industry
Health Tech, Global IT

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

Keep reading
[Signal Global IT Tool Sprawl Fragments the Truth](https://www.agileon.com/insights/tool-sprawl-fragments-the-truth)[Surface Global IT 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 Global IT From 83 Observations to Five Things to Build](https://www.agileon.com/insights/from-eighty-three-observations-to-five-things-to-build)[Signal Global IT The Consultants Left. The System Stayed.](https://www.agileon.com/insights/the-consultants-left-the-system-stayed)
