Everyone Agreed. Except One Person
- Feb 8
- 4 min read
The project was approved unanimously.
This fact was repeated often, loudly, and with PowerPoint.
Unfortunately, it was also meaningless.
The kickoff meeting was a masterpiece of corporate harmony.
There were donuts.
There was coffee.
There was a slide titled “Shared Vision” that featured a stock photo of people high-fiving over laptops.
Fourteen people attended.
Fourteen people nodded.
Fourteen people said, “Looks good to me.”
The PM felt something rare and dangerous.
Hope.
The First “Concern”
The concern arrived at minute 47.
“I’m generally supportive,” said Greg from Legal, adjusting his glasses, “I just want to flag a potential risk.”
No one asked what kind.
Greg did not specify.
The room nodded gravely, the way people nod when a priest mentions sin without naming it.
The PM wrote “Legal concern — TBD” in the meeting notes.
This would turn out to be a mistake.
The Second Meeting (Consensus Deepens)
The second meeting was scheduled to “address Greg’s concern.”
Greg was not available.
Instead, eight people discussed what Greg might have meant.
“It’s probably minor,” someone said.
“But still,” said someone else, “we should make sure everyone is comfortable.”
Comfort, it turned out, was now the success metric.
The PM suggested a decision.
The room suggested another meeting.
The Third Meeting (Consensus Expands)
By the third meeting, the concern had evolved.
It was no longer Greg’s concern.
It was the team’s concern.
Someone from Finance had a thought.
Someone from Ops had a feeling.
Someone from Marketing wanted to “revisit assumptions.”
The PM watched the scope expand like a Marvel villain monologue.
Week Three: The Consensus Turtle Appears
The PM recognized the creature immediately.
It sat quietly in the corner of the meeting room, wearing a blazer and the expression of someone who had never missed a deadline because it had never chased one.
The Consensus Turtle.
It spoke calmly.
“I just want to make sure no one is uncomfortable moving forward.”
Fourteen people nodded.
No one moved.
The PM Tries Reason
The PM tried logic.
“We’re aligned on the goal, right?”
“Yes.”
“And we understand the risk?”
“Yes.”
“And we have mitigation?”
“Yes.”
“So can we decide?”
The Consensus Turtle blinked slowly.
“I just don’t think we’re there yet.”
No one asked where there was.
The PM Tries Process
The PM brought charts.
RACI charts.
Timelines.
Decision trees.
The Turtle admired them politely.
“These are helpful,” it said.“But I’d feel better if we had broader alignment.”
Broader than fourteen people, apparently.
The PM Tries Heroics
The PM did what all desperate PMs eventually do.
They promised a miracle.
“I’ll mock it up by Friday,” the PM said.
“What kind of mockup?” someone asked.
“An end-to-end demo,” the PM replied, lying confidently.
The room leaned in.
The Turtle nodded.
“Let’s review it,” it said. “Together.”
Friday: The Absurdity Peaks
The PM did not build a demo.
The PM built a theater.
They created:
a fake launch site
a dummy approval screen
a simulated failure mode
a banner that read: ‘THIS IS WHAT HAPPENS IF WE DON’T DECIDE’
They staged scenarios.
They acted them out.
They had a colleague pretend to be a furious executive asking why nothing shipped.
The room laughed.
The Turtle frowned.
The Decision (Sort Of)
“Well,” the Turtle said slowly, “I still have one concern.”
Fourteen people froze.
“But,” the Turtle continued, “I’m comfortable proceeding with conditions.”
The PM seized the moment like a hostage negotiator.
“Great,” the PM said. “Let’s document those.”
The Turtle hesitated.
Documentation, it turned out, was dangerous.
The PM’s Final Move
The PM did something reckless.
They wrote the decision down.
They assigned owners.
They listed conditions.
They sent it out as if it were already real.
The email subject line read:
Decision Confirmed — Moving Forward
No question mark.
What Happened Next
No one objected.
No one replied.
No one wanted to be the person who reopened the conversation.
The project moved.
Slowly.
Cautiously.
But undeniably.
The Consensus Turtle watched it go, mildly surprised.
The Postmortem
Later, leadership asked the PM how they got past consensus.
The PM didn’t say:
“I outsmarted them”
“I forced the issue”
“I escalated”
The PM said:
“I made indecision uncomfortable.”
Why This Works (And Why It’s Rare)
Consensus isn’t collaboration.
It’s a weapon when:
one concern outweighs ten commitments
comfort outranks accountability
and delay feels ethical
PMs who survive learn something counterintuitive:
You don’t defeat consensus by arguing.
You defeat it by making reality louder than hesitation.
That’s why some PMs quietly rely on:
ownership clarity
documented decisions
artifacts that survive meetings
You’ll find those in the PMTales Armory — not to reduce collaboration, but to keep it from becoming paralysis.
Others go deeper and learn how to:
move with partial agreement
protect delivery without becoming “the bad guy”
operate inside consensus cultures without drowning
That’s the work of the PMTales Academy.
Final Field Note
Next week, someone will say:
“I’m not comfortable yet.”
The room will nod.
And a project will wait.
Unless someone decides to move anyway.
Seen this before?
You’re not alone.
PMTales exists to name the absurd systems we all work inside — and help you survive them with your credibility intact.
👉 Get the weekly Dispatch
Because consensus feels safe…right up until delivery depends on it.
— PMTales
Behind the Gantt Chart
Comments