The slowest team I ever worked with wasn't slow at building things. It was slow at deciding what to build.
Everyone on it was talented. The Jira board moved. Standups were crisp, sprints closed on time, velocity charts looked healthy. And yet three weeks in, we shipped a feature nobody had actually signed off on — because six people had opinions about it and zero people owned it.
That's not a technical problem. That's decision debt.
Decision Debt Is the Loan Nobody Remembers Taking Out
Technical debt gets a name, a ticket, a line item in someone's roadmap review. Decision debt doesn't. It just quietly compounds every time a call gets deferred, split three ways, or made by whoever happened to speak last in the meeting.
Here's the mechanism: a decision that isn't clearly owned doesn't disappear. It gets made anyway — by default, by inertia, by whoever's loudest — and then re-litigated later when it turns out wrong. You pay for it twice. Once in the delay, once in the redo.
I've sat in enough rooms across enough companies to notice the pattern doesn't care about company size. Enterprise or startup, the symptom looks the same: a team that's busy, executing, and moving — on the wrong thing, because nobody actually decided.
The Meeting Where It Became Obvious
The team wasn't stuck because the work was hard. It was stuck because everyone assumed someone else had already made the call.
The project was a rebuild of an internal approval process — the kind of unglamorous system that touches everyone and excites no one. The kickoff went fine. People nodded along, took notes, agreed it made sense. What nobody said out loud was that "makes sense" isn't the same as "decided."
Weeks in, heads-down and executing well, the team had built exactly what they thought they'd agreed to. Then someone senior sat in on a review and asked the one question that stopped the room: does this replace the old process, or does it run alongside it?
Nobody answered right away. Not because it was a hard question — because three different people in that original kickoff had each quietly assumed a different answer, and none of them had said it out loud. The build wasn't wrong. The decision underneath it had just never actually been made. It had been assumed, three separate ways, by three separate people, and the team spent far longer unwinding that than they would have spent just asking the question up front.
That's the part that sticks with me. Nobody in that room was incompetent. Everyone was moving. The only thing missing was one person willing to say "wait, who's actually deciding this?" before the work started instead of after it broke.
The Two-Question Decision Filter
The fix isn't "decide faster." Fast decisions with no information are just gambling with better PR. The fix is making sure every decision that matters gets a name and an owner before the work starts, not after it breaks.
Before any project kicks off, ask two questions:
- Is this decision reversible? If you ship it and you're wrong, can you undo it in a week without real damage?
- Who owns it if it goes wrong? Not who's in the meeting. Who has to answer for it.
Run those two answers through a simple filter:
- Reversible + owned → decide today. Don't let a low-stakes, correctable call sit in a Slack thread for a week.
- Irreversible + unowned → stop and escalate. This is exactly the kind of decision that should never get made by default. Force the ownership question before a single line of code gets written.
That's it. No spreadsheet, no framework you need a workshop to explain. Just two questions, asked out loud, in the room, before the work starts — not discovered three weeks later when someone finally asks the obvious one.
Where This Breaks Down
Fast isn't automatically wrong, and I want to be honest about the edge here: some teams use "let's slow down and be sure" as a permanent excuse to never commit to anything. That's not decision discipline. That's just a nicer-sounding version of the same avoidance.
The two-question filter isn't a call for more caution across the board. It's a call for clarity about which decisions deserve caution and which don't. Most decisions are more reversible than they feel in the room — the fear of being wrong makes low-stakes calls feel heavier than they are. The filter is there to catch the genuinely irreversible ones before they get made by accident, not to slow down everything else.
The Question Worth Asking Tomorrow
The next time a project is behind schedule, resist the instinct to ask "why is this taking so long." Ask something sharper instead: was this slow, or was this actually never decided?
You'll be surprised how rarely anyone on the team knows the difference — and how often "we're still working on it" actually means "we're still waiting for someone to admit they're the one who has to call it."
