Many leaders think teams overcommit because teams are careless.
I don't think that's true.
Most teams do not need a leader to pressure them into overcommitting.
Teams will usually do it on their own.
That may sound surprising, but in my experience, software teams often are deeply optimistic.
They believe they can solve hard problems.
The believe that they figure things out.
Believe they make things work.
That optimism is part of what makes them good.
It also shows up in their estimates.
Overcommitment usually starts before a leader says a word.
A team looks at the work, they imagine a path through the works.
They make assumptions about what will go well.
And because they're optimistic, they often lean toward the best case or near best-case without realizing it.
That does not make them irresponsible.
It makes them human.
I learned this early in my career.
When I was first promoted into leading a team, my management philosophy was basically this.
Ask people for estimates, assume the estimates are optimistic, then hold people to those optimistic estimates.
It didn't work.
I treated optimism like a contract.
Think about driving across town for an appointment.
You look at the distance, you think about the time of day, consider normal traffic, and you conclude that 30 minutes is enough.
Most of the times you're right.
But one day a train blocks the tracks for 10 minutes and suddenly you are late.
That doesn't mean your estimate was bad.
Like any estimate, it had a certain probability of coming true.
And on this day, you ended up on the wrong side of that probability.
That happens to teams all the time.
So if teams are already a little optimistic, what happens when a leader adds pressure?
Usually, the problem gets worse because pressure does not remove uncertainty.
It changes how teams behave around uncertainty, When teams feel pressure, they choose the optimistic estimate instead of the realistic one.
They become less willing to expose risks.
The stop looking very hard for what could go wrong because discovering bad news becomes uncomfortable.
And once that happens, the risks go unnoticed.
A lot of leaders apply pressure without meaning to.
I once worked with a leader named Erin, who was upbeat, positive, and well-intentioned.
As she walked through the office, she would greet people with, getting a lot done today?
She didn't mean to imply schedule pressure.
It was just her way of saying hello.
In fact, her bigger concern was quality.
But what the team heard was daily pressure about productivity.
When I pointed this out, Erin changed her greeting to something deliberately silly.
Staying bug free today?
That small shift mattered.
It signaled what she actually cared about.
And because it was a little funny, it broke the pattern.
That example has always stuck with me because it shows how easy it is for leaders to communicate one thing and be heard another way.
Even a simple, how are things going, can sound like pressure if the team hears it as, tell me you're on track.
Pressure does something else, too.
It creates rushing.
Urgency is fine.
Rushing is not.
I like this admonition from basketball coach John Wooden to his players.
Be quick, but don't hurry.
That is exactly what leaders should want from teams.
Move with energy, not with panic.
There's another way leaders accidentally create overcommitment.
They anchor the answer before the team has done its own thinking.
A leader asks, can you deliver these features in three months?
That sounds harmless, but it's not neutral.
Now the Team knows the leader's expectation.
This much work in that timeframe.
So instead of independently deciding what's realistic, they start looking for a path to yes.
I saw this very clearly when I was a VP of development at a public company.
My boss asked whether a product could be delivered by the end of the year.
We needed the revenue that year, and the product can help.
He told me that if we couldn't deliver by end the of year he'd have us work on something else.
My team and I worked on a plan and came up with mid-February for the release.
We cut some things, revised the plan, and got the planned to show mid December.
Great, we thought.
But we'd missed one important fact.
Our customers were not going to make beta testers available in November and December, they were too busy.
So the released slipped into January.
Now, on an 11-month effort, missing by a couple of weeks is actually pretty good planning.
But because the whole point was revenue in that fiscal year, the outcome was a failure.
The failure was my fault.
But it started with the way the question was framed.
If instead of telling me he needed it by the end of the year my boss had asked when we could deliver, I probably would have said February.
That would have led to the right business decision.
Don't do the project.
But can you do it by the end of the year?
Anchored us to a desired answer.
And we found a way to almost get there.
Almost was not good enough.
So what should leaders do instead?
First, make it clear what kind of answer do you want.
Do you wanna forecast a plan, a commitment?
Second, Make it safe to tell the truth.
Ask questions like, what assumptions are you making?
What could derail this plan?
what dependencies are there?
Is this your optimistic case, your most likely case or your pessimistic case?What should I know about the thinking behind this Those questions are very
different from asking for reassurance.
And that difference matters.
When a leader hears bad news, one of the most important first responses may simply be, thanks for telling me.
Because that tells the team that truth is valued.
So if your team keeps missing deadlines, don't assume they need more pressure.
Start by assuming they may already have enough pressure, and then ask yourself, what am I doing that makes realistic planning easier or harder?
The best leaders do not squeeze harder.
They create the conditions for truth.
That is how you get better plans and, over time, better outcomes.