A product lead sits in a meeting with the team describing a new feature:
“We need a way to export data in bulk,” she says.
The whole team nods. No one asks:
- what “bulk” means
- which data
- for whom, how often
- what “done” looks like
Three weeks later, the product lead verifies what they built.
A CSV download for admins. One click. Full table. Fine for support. But it’s not what she meant.
The intention was to have a nightly job that pushes filtered datasets to a partner. Audit logs, retries, and a way to stop a bad run.
The delivery was not exactly wrong. Adjacent. Off by about 90 degrees.
PO: “This isn’t what I asked for.”
Engineer: “But this is what you described.”
Both were right.
Leadership described one thing, but meant another. The gulf between them cost three weeks. And a week of quiet resentment on both sides.
Ambiguity is Comfortable
This happens everywhere — not because people are incompetent.
Because ambiguity is comfortable.
When a request is unclear, everyone fills in the blanks themselves.
Everyone imagines context that doesn’t exist and assumes shared understanding that was never actually shared.
And everyone nods like they’re on the same page.
Until they’re not.
I’ve watched rooms end fast because “everyone understands,” while the work is already forked.
Fast people, foggy rooms
Here’s what I’ve noticed:
The people who move the fastest are often the ones creating the most ambiguity.
They’re decisive. Action-oriented. Volatile. They hate sitting in the fog. So they skip the part where you make sure everyone sees the same problem.
It feels like leadership. It often isn’t.
The trust bill
The cost isn’t just wasted effort.
It’s the loss of trust.
When someone does work based on a misunderstanding, they feel unheard. The person who explained it feels unlistened-to.
Next time, both of them are more cautious. More defensive. They add process. They add slides. They add “alignment meetings” that still don’t ask the one question that would have saved the first three weeks.
The team slows down. Not because they got lazy. Because they got burned.
The question that feels like friction
Clarity requires a specific kind of courage.
It means asking:
“Wait, what exactly do we mean by that?”
It means:
- sitting in the discomfort of not knowing for five more minutes
- someone saying: “I don’t think we’re talking about the same thing”
- admitting you don’t know — or don’t understand — and making yourself vulnerable
That line feels like friction in the moment. It’s cheaper than three weeks of adjacent work.
The thing is: ambiguity feels faster.
You don’t have to have the hard conversation. You can just move forward and hope it works out. You don’t need to create plans.
Of course sometimes it does. But that’s the trap.
At some point I heard: “We don’t need to create plans, plans are a waste of time, we can just move forward and see what happens.”
Not wrong, not true. It depends on the situation.
Ambiguity scales
The dangerous part is that ambiguity scales beautifully.
- A small unclear request becomes a large unclear initiative.
- A misaligned pair becomes a misaligned team.
- A misaligned team becomes a misaligned department, still nodding in the same meeting.
By then nobody remembers what “bulk” meant. They only remember that delivery “keeps slipping.”
What clear enough looks like
The teams that move fastest aren’t the ones that skip clarity.
They’re the ones that normalize it.
- Where asking “What do we actually mean?” is seen as intelligence, not obstruction.
- Where a decision isn’t “we all nodded.”
- Where a decision is: we can write it down so a stranger could check it.
Empty requirement:
Export data in bulk.
Clear enough to build:
Nightly export of orders for partner X. CSV to their SFTP. Last 24 hours only. Fail the job loud if the file is empty. Success means they confirm receipt in staging before we touch prod.
Same meeting length, if you spend the minutes on the right question. Different three weeks.