A team's output dips before it climbs. Skip the dip, and it never climbs at all.
One pattern repeats across most bids:
Week 1: the team agrees too fast, to keep the peace.
Week 4: the disagreements surface, too late to fix.
Week 6: the contract goes to whoever had the harder conversations early.
Bruce Tuckman mapped why, sixty years ago.
His five stages of team development (1965, revised with Mary Ann Jensen in 1977) explain what most procurement leaders get wrong: they read early calm as strength.
1 Forming
QA, regulatory, supply chain and finance meet at kickoff.
Polite. Cautious. Nothing committed.
2 Storming
Someone challenges the API sourcing plan. Someone else pushes back on margin assumptions. This is where bids are actually won.
3 Norming
Roles settle. Specs freeze. Dossier ownership is clear.
4 Performing
The bid moves as one unit. Decisions happen without meetings.
5 Adjourning
Contract closes. Lessons captured, or lost forever.
Five clean stages on paper. One of them is where it all goes wrong.
Here's the trap.
Most leaders treat Storming as dysfunction. So they suppress it. Reschedule the meeting. Ask everyone to "align offline."
The team never storms. It just quietly underperforms.
And here is the part the data keeps showing: the teams that let the dip happen early are the ones performing at their peak within days, not weeks.
In a regulated industry, the bill comes later. A team that never fought over specs in drafting will meet those same gaps again during audit. The only difference is who is watching.
Conflict is not the failure mode.
Avoidance is.
The strongest bid teams force the hard debate into the open by day three, in the same room, while there is still time to act on it.
Argue today. Win the contract tomorrow.
If your team feels comfortable too early, you are probably already behind.
Be honest: is your team Storming, or just being polite?
