If Your Project Just Died in Slack, It’s Not a Communication Problem.

Unclear roles look like collaboration failures. The fix is decision rights, not more meetings.

You can usually tell when a project is dying. It doesn’t die dramatically. There’s no meeting where someone declares it. It dies in slow motion, usually in a Slack thread that stops getting replies, in a “let’s circle back next week” that never gets put back on the calendar, or in one more review nobody asked for.

How many projects in your company are quietly dying right now?

I’ve watched teams spend months building something genuinely good. The decks get polished, enablement ready, and everyone agreed the work would move the business forward. Then rollout day came, and it just stopped.

Not because the strategy was wrong. Because nobody could answer one question: Who owns the decision to ship this?

Product thought Sales needed to sign off. Sales thought Ops needed to weigh in. Ops thought Legal had to look at it. Legal wanted one more pass. The work didn’t die. It got slow enough that the moment passed.

Eventually the founder became the decider by default. Not because she wanted to, but because the system left no other option.

High talent with unclear roles doesn’t create a people problem.

This is the part most leaders misdiagnose. When projects start dying in Slack threads, the instinct is to call it a communication problem, a collaboration problem, or say “we just need better alignment.” So you add a weekly cross-functional sync, you build a RACI nobody opens, and you write a Notion doc that’s already stale by the time you publish it.

None of that works because none of that is the actual problem.

High talent with unclear roles doesn’t create a people problem. It creates a missing architecture problem. The people are doing exactly what they’re supposed to do, which is wait for someone to tell them they have permission to move.

McKinsey’s research on decision-making is one of the cleaner mirrors I’ve seen for what this costs. Executives spend nearly 40% of their time making decisions, and 60% of them say that time is poorly used. Only about 20% of organizations make high-quality decisions fast. The other 80% are running the version of the company where the founder ends up in every Slack thread, and the team is waiting.

If you’re running one of the 80%, this isn’t a smarts problem. It’s a system you haven’t built yet.

Decision rights aren’t hierarchy. They’re permission to move without asking.

The phrase “decision rights” sounds bureaucratic. It isn’t. It’s the answer to a simple question: for this kind of decision, who can act without checking?

A useful frame here comes from David Marquet, the submarine captain who developed intent-based leadership. Instead of waiting for permission to act, people operate by stating their intent and moving. They inform rather than ask. “I intend to ship this Friday unless I hear otherwise” replaces “can we ship this Friday?”

That only works when roles and decision rights are explicit enough that people know where their lane starts and ends. Marquet isn’t asking his crew to guess. He’s making the lanes visible so the default action is forward.

What to do this week

For each key role on your team, three things need to be true. Not in a deck, but in the operating rhythm.

First, what does winning look like, in outcomes, not tasks? Outcomes, not “owns sales enablement.” A real outcome is new hires hit quota in 90 days. That’s something you can see.

Second, for the recurring decisions this role touches, who decides, who contributes, and who executes? Not all three at once. One named person for the decision. If three people would each tell you they’re the decider, you don’t have decision rights. You have a meeting.

Third, where does this live so it gets used weekly? The Notion doc nobody opens is not a system. The standing slide in your team’s weekly review is. The first agenda item in your Monday operating cadence is. Pick a place your team is already looking.

Then run the smallest possible experiment. Pick three to five decisions that are dying in Slack threads right now. Name the decider for each. Tell your team you’re doing this, and that the default expectation is intent, not permission. Watch what happens in two weeks. If the throughput moves, you have your answer.

The bigger move

Role clarity isn’t HR hygiene. It’s a speed strategy. The companies that scale without the founder in every conversation aren’t the ones with more meetings or better Slack etiquette. They’re the ones that made the lanes visible so people stopped having to ask.

If your projects are dying in slow motion, your team isn’t broken. The architecture is, and that’s the version of the problem you can actually solve.