Bhani Consulting

27/05/2026

What if the biggest project risks aren't the technology — but the warning signs everyone overlooks?

Something practical is coming this June. Stay tuned for our next Lunch & Learn. More details soon.

26/05/2026

Everyone's Doing Their Job. The Program Is Still Failing.

ERP programs don't fail because people are careless.

They fail because everyone is doing their job too well.

That's the part that confuses executives.

Project Manager is on top of the schedule. Change Manager is hitting training metrics. Vendor is delivering to contract. SteerCo is approving on time. SMEs are turning up to workshops.

Each is rational. Each is competent. Each is winning their game.

And the program is still failing.

Why? Because each stakeholder is playing a different game with a different scoreboard:

→ The Project Manager plays the Delivery Game. Wins on milestones.
→ The Change Manager plays the Adoption Game. Wins on training attendance.
→ The Vendor plays the Margin Game. Wins on contracted scope.
→ The Sponsor plays the Assurance Game. Wins on reports staying green.
→ The SMEs play the Survival Game. Wins on getting the day job done.
→ The SteerCo plays the Governance Theatre Game. Wins on packs being reviewed.

Local optimisation. Global failure.

The biggest blind spot is the unspoken assumption: "If everyone does their job well, the system will work."

It will not.

Until someone is explicitly accountable for end-to-end business outcomes — not delivery, not training, not configuration — the program will produce a system that does not improve the business.

Project success ≠ business success. Delivery ≠ capability. Implementation ≠ transformation.

I broke each of the six stakeholder games down — and the blind spot each one creates — here: https://zurl.co/c9qqt

Which game is your program currently winning while losing the war?

ERP Blind Spots - Why do we experience them? ERP blind spots are not caused by failure of individuals.

25/05/2026

A leadership team once asked why their transformation initiative was struggling.

They had:
• the right technology
• experienced consultants
• detailed plans
• weekly governance meetings
Everything looked “correct.”

But after several conversations, one issue became obvious.

Nobody could clearly answer:
“What problem are we actually trying to solve?”
The organisation had tactics.

But no clarity.
And without clarity, even good tactics create noise.

Sometimes the issue is not ex*****on.
Sometimes the issue is direction.

24/05/2026

24/05/2026

The Wrong Definition of Power

Most executives are chasing the wrong kind of power.

We call it power. What we usually mean is the ability to get what we want — a bigger budget, a better title, a yes when we need one.

That isn't power. That's dependency with a confident face.

Real power looks completely different.

Real power is when you genuinely don't need anything from anyone.

Not as a posture. Not as a negotiating stance. As a lived reality.

When you need nothing, you can't be controlled. When you can't be controlled, you can act from principle instead of pressure. That is where freedom lives — and freedom has absolute power.

How you actually get there:

→ Need less than you think you do. Stop inflating your requirements.
→ Material things are immaterial. Don't let your standing depend on what you own.
→ Zero reliance on others. Zero expectations. People are gifts, not infrastructure.
→ Give more than you get. Stop keeping score.
→ Keep learning, keep expanding — for the practice, not the outcome.
→ Stay alert to the world within you and the world around you.

What you get on the other side of this is not comfort. It is something better.

You are complete within yourself. You have alternatives. You can create options — because your thinking isn't clouded by desperation, and your decisions aren't hostage to whoever is currently withholding something you think you need.

That is the real definition of a powerful person.

Not someone who always gets what they want.

Someone who has quietly arranged their life so they don't need to.

The freedom isn't in the having. It's in the not needing.

Full essay here: https://zurl.co/nF2xm

21/05/2026

The Gap Between Knowing and Changing

There is a gap between seeing the problem and changing the behaviour.

That gap is where most leaders break themselves.

If I know I am distracted, I should stop being distracted. If I know I am wasting energy, I should redirect it. If I know I am repeating an old pattern, I should just move on.

Reality does not work that cleanly.

The gap is real. Frustrating. Personal. Why am I still doing this? Why do I keep coming back to the same place? Why can't I just move on?

This is where the real struggle lives.

Not because the issue is unknown — but because it is known and still difficult.

We assume growth means removing the problem. Often, growth begins by accepting the problem exists. Not as permanent. Not as an excuse. Just seen clearly, without adding another layer of frustration on top.

Resisting reality wastes energy fighting that something is happening.

Accepting reality returns that energy to you. You can use it to observe, practise, adjust, try again.

This is not passive. It is starting from the truth:

I am distracted. I am repeating a pattern. I am not where I want to be yet.

Once that is accepted, the next step gets simpler. Not easy. Simpler.

Keep practising. Keep noticing. Keep correcting. Keep learning.

Progress is rarely a dramatic breakthrough. It is a quiet return to the same place with slightly more awareness than before.

We do not improve by hating where we are.

We improve by seeing where we are clearly enough to take the next honest step.

https://zurl.co/u22Oy

One mistake I often make is thinking that if I understand something, I should fix it immediately, but I’m learning about Accepting Reality.

20/05/2026

The Bad One-Way Decision

You greenlit the ERP. Eighteen months later, you regret it.

You signed the business case. You shook hands with the vendor. You stood in front of the board and called it transformational.

Now you're sitting across from a project that is over budget, under-delivered, and politically radioactive. Your CFO is asking questions you don't have clean answers to. Your team is exhausted.

And quietly, in the back of your mind: I made a mistake.

This is the part nobody puts in a leadership textbook.

The single most dangerous thing a C-suite executive does after a bad ERP decision is double down to protect the original call. The escalating commitment. The "we just need to push through." The refusal to re-scope because re-scoping feels like admitting failure.

It is not failure. It is adaptation. Adaptation is the only currency that matters now.

Five things to do — in order:
→ Name the situation clearly inside the leadership team. Stop calling it "challenges."
→ Separate sunk cost from the forward decision. What's spent is gone.
→ Change the relationship with the vendor. Today. Not at the next SteerCo.
→ Do real work on yourself as the sponsor. ERP fails at governance and sponsorship far more often than at technology.
→ Project the future you can credibly construct from where you actually stand. Then own it publicly.

The executives who navigate a failing ERP with honesty don't just survive. They become markedly better leaders. The judgment that comes from this experience is worth more than any embarrassment you're trying to avoid.

I wrote this as a direct letter to the sponsor sitting alone with this exact thought: https://zurl.co/8HVa9

The decision is behind you. The direction is still yours.

19/05/2026

The "We'll Do It In-House" Trap

"We'll just do the ERP in-house. Saves us the consulting fees."

This sentence has cost organisations more money than any single line item I have seen in twenty years of ERP work.

Not because the people are incapable.

Because ERP is not a routine activity. It is a once-in-a-decade capability shift.

What gets called "saving fees" is usually "shifting cost."

External spend goes down. Internal cost goes up — quietly, in places that are harder to see and harder to measure:

— SMEs balancing day jobs and project workshops. — Decisions slowing as fatigue rises. — Operational performance dropping mid-build. — Key people becoming single points of failure. — Avoidable mistakes corrected through rework. — A program that goes live with compromised outcomes — the most expensive form of "success."

Knowing your business is not the same as delivering a transformation.

The right model isn't fully external. It isn't fully internal. It's structured augmentation:

Internal teams own business knowledge, decisions, and adoption. External capability owns governance discipline, pattern recognition, and challenge.

The objective is not to minimise external spend. The objective is to optimise total investment.

Before any council, board, or executive committee commits to "running it in-house," the honest question is this:

Are we truly saving cost — or are we transferring it into parts of the organisation where it is harder to see, measure, and control?

Full piece on why "doing ERP in-house" becomes the most expensive option: https://zurl.co/yyHiy