Unowned Work Is the Real Startup Killer

Looking at you, fancy dashboard no one believes in.

There’s a dashboard almost every growing startup has.

It technically works.
It updates.
It lives somewhere important.

The problem? No one actually trusts it.

Each department pulls its own numbers from its own tool. Sales has a figure they believe. CS has a different one. Finance has a third. The dashboard becomes a reference point everyone politely ignores while doing mental gymnastics to arrive at the number they feel safest repeating. This is what we call a responsibility problem, friends.

That dashboard didn’t break overnight. It was built early, when speed mattered more than structure. The systems underneath it were never designed to speak to each other. Then traction arrived. Customers came in. Pressure increased. And no one stopped to re-architect the foundation until the cost of doing so felt too high.

So the work kept going.
Just without an owner.

What unowned work looks like in practice

Unowned work doesn’t announce itself loudly. It shows up sideways.

A customer issue floats between Sales and CS because no one is accountable for the handoff.
A number gets rebuilt three times because no one owns its definition.
A decision resurfaces in different meetings with different context because no one owns the call.

Everyone is busy.
Everyone is contributing.
No one is responsible for the outcome.

Founders usually describe this as a bandwidth issue. “Things are moving fast.” “There aren’t enough bodies.” “It’s early. This is normal.”

They’re not wrong. Early-stage companies do move quickly. They do make tradeoffs. They do duct-tape systems together to get momentum.

The problem isn’t that this happens.
It’s that it quietly stays this way.

Where the real cost shows up

The first thing unowned work consumes is founder time.

When systems don’t carry decisions, founders do. They become the connective tissue between tools, teams, and interpretations. They answer the same questions repeatedly. They re-litigate decisions that were never properly documented or owned. They are pulled into details they thought they had already delegated.

The second cost is morale.

When work has no clear owner, people start protecting themselves. They over-explain. They point sideways. They build quiet narratives about who dropped the ball. There is almost always one operations person holding everything together in the background, happy to help, slow to complain, and last to say how much weight they’re carrying. (This one comes from A LOT of personal experience.)

Burnout doesn’t arrive dramatically in these environments.
It seeps in.

The data

This pattern isn’t just anecdotal.
Research by CMA Consulting on decision effectiveness shows how costly this becomes at scale. In a global study across industries and company sizes, organizations that scored highest on decision clarity and execution delivered shareholder returns nearly six percentage points higher than their peers.

The gap wasn’t subtle. Most companies scored below 30 out of 100 on decision effectiveness, while top performers averaged more than double that. The difference came down to one thing: decisions that had clear owners and stuck.

Why this keeps happening

In most startups, no one insists on shared clarity early. Everyone assumes they’ll circle-back once things slow down. (Honestly, who wants a circle-back moment?)

They rarely do.

What I see instead is a reluctance to pause long enough for teams to explain how their work actually flows end-to-end. Sales knows their piece. CS knows theirs. Product has its own mental model. Finance has another. Each is reasonable on its own. Together, they don’t align.

No one is doing this maliciously. Most people want to be understood. They want to explain their constraints. They just aren’t given a structure that forces alignment.

So the system keeps running on goodwill and heroics.

How I diagnose unowned work quickly

I trace one customer.

Not a hypothetical one. A real account. From first conversation to renewal.

I ask different leaders to walk me through what they believe happens at each stage. The gaps show up immediately. Definitions shift. Ownership blurs. Handoffs disappear. Everyone is surprised by something they assumed another team handled. The effort was almost always there. The clear, forward-thinking design? Not so much.

The part I usually don’t say out loud

Simple systems created early prevent expensive rewrites later.

Think about transparency as kindness. Not overhead. Over time, it becomes a superpower.

When people can see how their work connects to everyone else’s, they stop performing competence and start building momentum. Decisions stick. Numbers mean something. Founders get their time back. Teams feel safer because the ground under them is solid.

The takeaway for you this week…

Pay attention to the work that keeps resurfacing.

The questions that never quite get answered.
The numbers that get re-derived instead of referenced.
The tasks everyone touches but no one owns.

That’s where scale quietly breaks.

And that’s where it can be rebuilt—before it costs you more than time.