Bhani Consulting

28/08/2026

"Peaks and troughs are not verdicts. They're weather conditions."

27/08/2026

A leadership team rolls out a new system. Adoption looks fine in week one.

By week four, half the team has quietly built a workaround. Nobody said no in the meeting. They just didn't say yes afterwards.

It's one of the most common patterns we see — and one of the easiest to prevent, if you know what to look for early.

We'll walk through how in our Lunch & Learn, "How to Manage Change When People Push Back," on 9 September.

Register now: Link in the comments.

Sound familiar? Comment "SAME" if you've seen this play out in your business.

26/08/2026

Here's exactly what we'll cover in 45 minutes — no filler, no theory for theory's sake.

In our Lunch & Learn on 9 September, you'll walk away with:

— A clear way to read what resistance is actually telling you
— Language that lowers defensiveness instead of raising it
— A simple approach to bring skeptics into the process, not just inform them of it
— Time to raise your own change challenge and get real input on it

How to Manage Change When People Push Back
12:00–12:45 PM AWST | Online

Register now: Link in the comments.

26/08/2026

25/08/2026

Leading change without managing resistance is like renovating a house while everyone's still living in it.

You can have the best blueprint in the world. If the people inside don't know what's happening, why it's happening, or when the dust will settle, they'll resist the builders before they resist the plan.

That's the gap our Lunch & Learn is built to close.

How to Manage Change When People Push Back
Wednesday, 9 September | 12:00 PM AWST | Online, interactive

Register now: Link in the comments.

25/08/2026

Which costs your business more:
Bad news delivered late, or bad news that's never delivered at all?
Most leaders think they've built a culture of transparency. Most teams think they're protecting their leaders from unnecessary alarm.
Both are usually wrong — and the gap between them is where transformation programs quietly go off the rails.
I'd genuinely like to know: when someone on your team surfaces a real problem early, what actually happens to them? Are they thanked, or are they quietly marked as "not a team player"?
Drop your answer below — even (especially) if it's uncomfortable.

24/08/2026

Quick question for the leaders in our network.

Drop your answer below — we'll be tackling all four (and how to work through them) at our Lunch & Learn on 9 September.

How to Manage Change When People Push Back
12:00–12:45 PM AWST | Online | Registration link in the comments

24/08/2026

Green status reports are the most dangerous line item on your dashboard.
Not because they're wrong. Because they're comfortable.
Every program sponsor wants to hear "on track." Every project team wants to deliver good news. So status reports get curated — not falsified, just softened — until "amber" quietly becomes "green" and everyone moves on.
The problem isn't the report. It's what the report replaces: the harder conversation nobody wants to have in the room.
If your last five steering committee updates were all green, ask yourself — is the program actually healthy, or has everyone just agreed not to say otherwise?
What's the longest stretch of "all green" you've seen before a program hit real trouble?

23/08/2026

Resistance to change is not a people problem. It's a signal.

When a team pushes back, it usually means one of three things: they don't understand the change, they don't trust the reason behind it, or they don't believe it will actually work.

None of those are solved by pushing harder. They're solved by leading differently.

We'll unpack how in our Lunch & Learn on 9 September — "How to Manage Change When People Push Back."

Register now: Link in the comments.

Which of the three sounds most familiar in your business? Let us know in the comments.

21/08/2026

Knowing Is Not Learning. Learning Is Not Implementing.

Your team already knows what to do. They've read the book, sat through the training, heard the talk. Yet the same mistakes keep happening on project after project.

That's not an information problem. It's a gap between three things we treat as one:

**Knowing** — you can explain it if asked.
**Learning** — it's changed how you think, even under pressure.
**Implementing** — it's changed what you actually do, consistently, when no one's checking.

A team runs a retro after a project fails on poor scope definition. Everyone nods. Eight months later, a different project fails for the exact same reason. The retro document still exists somewhere. This isn't a knowledge failure — it's a values-enforcement failure. Nothing in the system made the lesson stick once the pain faded.

Stop asking "do you understand this?" Start asking "show me where you did this last week." What gets inspected gets done. What gets explained gets forgotten.

Full piece: https://zurl.co/Vu1MT