Orphaned Demand

A seed-stage SaaS company had six engineers and no designer.

The product kept shipping. Screens got designed. Workflows got defined. UX decisions got made. Nobody could point to a person whose job was Design.

The work still existed. It was just being carried by whoever happened to be nearby. Some of it landed with engineers. Some of it landed with founders. Some of it landed with product people.

At first, that arrangement worked. Then it quietly stopped working.

The company wasn't missing design work. It was missing ownership.

That's the pattern I've started noticing across teams. Not just in Design. In Product. In Sales. In Customer Success. The work exists. The demand is real. But nobody wakes up in the morning owning it.

The problem isn't that nobody is doing the work. The problem is that everybody is doing it.

When that happens, capacity starts getting borrowed from other functions. Engineers spend time on design. Founders spend time on sales. Product managers spend time on customer support. The company keeps operating, but increasingly through hidden subsidies.

That's what makes orphaned demand hard to see. The work gets done. The cost gets spread across multiple people. No single person feels the whole burden.

A simple exercise has helped me spot this earlier. List the major functions in your company. Then ask one question: who wakes up every morning owning this function?

Not contributing. Owning.

If the answer is unclear, you've probably found orphaned demand. And that is often where the next organizational bottleneck is hiding.

So before you look at headcount, budgets, or org charts, make the list. Write down the owner of each function. The blanks are usually more revealing than the names.