Why polite kickoffs kill projects

Every kickoff starts the same way.

A plan is presented. The solution sounds reasonable. Everyone nods, and that’s the problem.

Not the nodding itself, but the reason behind it.

We’re all too polite to ask the questions that actually matter.

“We’re building an AI writing assistant for sales. Emails take too long. This should help.”

The real question?

“Is writing actually the bottleneck, or is something else slowing them down?”

But asking that? It feels like interrupting a toast at a wedding.

So we stay quiet. We nod. We agree.

And six months later, we’re wondering why no one uses the shiny new thing we built.

When no one questions the premise:

• You solve the wrong problem.

• You build on top of assumptions.

• You waste time chasing certainty that was never real.

The irony? The very politeness meant to keep things smooth is what derails them later.

In every kickoff, someone’s thinking:

• “Didn’t we try this before?”

• “Is this really our biggest problem?”

• “Are we sure people even want this?”

But there’s also someone in the room who just wants to move.

Someone who’s already attached to the solution.

So we trade truth for momentum and keep going.

Every now and then, someone breaks rank:

“Honestly, writing isn’t the issue. People can’t track follow-ups.”
“We tried templates last year. No one used them.”
“The real blocker is the CRM. Everyone’s using spreadsheets.”

That’s the moment.

The crack in the façade.

What happens next determines everything.

Does the room pause, or push past?

You don’t have to be a contrarian, but you have to…

Ask awkward questions:

• “What’s already been tried (and failed)?”

• “How do we know this is the real issue?”

• “What if no one actually wants this?”

Surface the tension:

• “I’m hearing different views on the actual problem.”

• “Can we take five minutes to test the premise before we dig in?”

Give others permission:

• “What are we not saying right now?”

• “What concerns haven’t made it into this room?”

Every uncomfortable question in kickoff saves hours of rework later.

Every assumption you test now is one less regret mid-sprint.

The most expensive projects aren’t the ones that fail fast.
They’re the ones that succeed at solving the wrong problem.

Say it up front:

“The goal isn’t to agree. It’s to make sure we’re not wrong.”

“Pushback isn’t resistance, it’s a safety check.”

“If you’re thinking ‘but what about…’, this is the time to say it.”

Kickoffs feel productive because everyone leaves aligned.
But alignment around the wrong thing?
That’s worse than no alignment at all.

The politeness that makes kickoffs smooth
is the same politeness that makes projects fail.

Ask the uncomfortable questions.
You’re not slowing things down.
You’re keeping them real.

Because the most expensive mistake isn’t challenging assumptions in a meeting.
It’s not challenging them at all.

Until next time,
Pragati

Share