The Status Quo Is a Competitor, Not a Baseline
- Rahul Kulkarni
- 2 days ago
- 4 min read
“You’re not competing with other ideas. You’re competing with “leave me alone”.
You’ve seen this happen: You call a meeting. You explain the logic.
People nod. Some even say, “Yes, correct.”
And then… nothing changes.
Not a fight. Not a refusal. Not drama.
Just a slow, polite slide back to the old way.
Most leaders call this laziness.
I don’t. I think it’s something more precise:
The status quo is doing its job.
Quick recap if you’re joining mid-series
Week 1: You inherited an equilibrium, not a business.
Week 2: People don’t oppose improvement; they oppose loss disguised as improvement.
Now Week 3: even if you reduce the fear of loss, there’s another force sitting quietly behind it:
“Do nothing” is not neutral. It’s a protected strategy.
Which seat are you stepping into?
Inherited seat: People will smile and wait for your “phase” to pass.
Hired seat: People will test whether you can enforce, or whether you’ll get tired.
Promoted seat: People may agree publicly and revert privately because habits don’t ask permission.
Different entry doors. Same default: do nothing.
The shortcut route problem
Every industrial area has that one shortcut road.
It’s narrow, broken, sometimes risky. But it avoids signals and saves a turn. So everyone keeps taking it even when a better road exists.
That’s how organizations behave.
Your “new process” might be cleaner and smarter.
But the old route is familiar. And familiarity feels like safety.
Researchers call this status quo bias where we stick with what’s already in place even when a better option exists (Samuelson and Zeckhauser wrote about it decades ago).
But you don’t need a paper to believe it. You just need to watch what happens after your first improvement announcement.
Why “do nothing” wins
Incoming leaders often treat the current way of working like a baseline:
“Okay, this is where we are. Now we improve.”
But inside the system, the status quo is not baseline. It’s a competitor.
It protects people in very specific ways:
It keeps accountability soft: everything stays “situational”.
It preserves informal power: who can “manage”, who has access, who gets heard.
It avoids hard data, which avoids hard blame.
It keeps old loyalties intact.
It keeps flexibility for firefighting even if that firefighting is the problem.
So when you introduce a new system, you’re not offering a better idea.
You’re threatening a survival arrangement.
That’s why resistance here is rarely loud. It’s quiet. Continuous. Patient.
The real competition is friction
Here’s the practical truth:
People don’t choose the best option. They choose the easiest option.
This is where the idea of defaults matters. Thaler and Sunstein popularized it in Nudge: if you make something the default path, most people follow it … not because they love it, but because opting out takes effort.
In MSMEs, effort is expensive. Not because people are incapable, but because they’re overloaded. Understaffed. Running on memory, calls, WhatsApp, and urgency.
So “small extra steps” are not small. They become the place where change goes to die.
If your new system adds friction, the status quo wins.
One example (you’ll recognize it)
A new leader joins a trading/manufacturing business and introduces a basic rule:
“Every quotation must be logged.”
Week one: decent compliance.Week two: it drops.Week three: it collapses.And by week four, the old shortcut route is back.
Not because the team disagreed with the idea.Because logging stayed an extra step. And extra steps don’t survive in high-velocity environments unless the leader redesigns the flow.
Then the leader tries to fix it with pressure.Shouting. Threats. Long lectures.
That doesn’t reduce friction. It just adds fear. And fear creates smarter avoidance.
Field Test: Make the new behavior the easiest behavior
Pick one change you want in the next 30 days.
Now ask one question:
How do I make the new behavior the path of least resistance?
Use these four rules:
Remove one step, don’t add one.
If your change adds steps, it will lose. Kill one existing step immediately (a duplicate approval, a manual register, a second reporting format).
Attach it to an existing moment.
Don’t create a new ritual. Piggyback on something that already happens (dispatch call, purchase huddle, daily production chat). Change travels on existing rails.
Make it visible and usable.
If the new behavior produces something people need (a live queue, a simple list, a shared status board), it becomes real. If it produces a report nobody reads, it becomes theater.
Create a soft gate.
Not punishment. A gate.
Example: “Only logged quotations will be discussed in the pricing huddle.”
Calm rule, consistently applied. No drama, no exceptions-by-loudness.
If you do only this much, you’ll notice something powerful: adoption starts rising without motivation speeches. Because you stopped trying to win by persuasion and started winning by design.
The close
A lot of incoming leaders lose their first year because they keep trying to “convince”.
But the system isn’t debating you.It’s outlasting you.
So treat the status quo like what it is: a competitor with home-ground advantage.
Don’t just make your change correct.Make it easy.
Next week, Rashmi will show you how to create a “new normal” without chasing perfect compliance ... by installing one focal point that everyone can coordinate around.
Comments