We Love Quick. We Hate Root Causes. Your Technology Program Is Paying for It.

Look around. The pattern is everywhere.

The market for influence is enormous. Books, courses, frameworks — all promising to help you win trust, build authority, shape perception. Tactics and hacks, mostly. What’s harder to find, and far less popular, is the quieter proposition: be truthful, serve with genuine intent, and trust will manifest on its own. That path is slower. It requires something from you that tactics don’t. So we buy the tactics.

The market for looking young and beautiful is worth billions. Clothes, cosmetics, accessories — products that change how you appear. The market for actually being healthy — for the unglamorous work of sleep, movement, food, stress — is a fraction of the size. Appearance is immediate. Health is cumulative. We know which one sells.

Medications for sleep, stress, and fitness anxiety sell fast. Not because people don’t care about their health — they do. But a pill that addresses tonight’s insomnia is available now. Understanding why you can’t sleep requires sitting with something uncomfortable. Most of us would rather not.

Social media platforms have made it easy to associate yourself with interesting places, impressive people, and compelling ideas. What they haven’t made easier — what no platform can make easier — is the slow, effortful work of genuine human connection. So we curate. We associate. And human connection keeps deteriorating. Superficial. Lonely. But the feed looks good.

There is a common thread.

We love what is quick, easy, cheap, and ego-boosting.

We struggle with what is slow, demanding, simple, and selfless.

This is not a character flaw. It is a deeply human pattern. The quick path presents itself as sensible. The slow path asks for something most environments don’t reward. So we take the quick path, again and again, and wonder why the same problems keep returning in slightly different form.

Perhaps this, as the observation goes, is the reason for much of our suffering too.

The same dynamic runs through your organisation’s technology programs.

Not because your executives are careless. Not because your team isn’t trying. But because the same human pull — toward the visible, the fast, the manageable — operates inside institutions just as it operates inside individuals. And when it goes unnamed, it shapes decisions in ways nobody quite intends.

Here is what it looks like.

Symptom 1: Your steering committee is active, but the same problems keep returning.

Meetings are well-run. Papers are prepared. Actions are logged. Yet three meetings later, a version of the same issue is back on the agenda — reworded, reframed, but structurally identical.

This happens because resolving root causes requires someone to say something uncomfortable — to a vendor, to a project team, sometimes to a peer. That’s costly. Running a clean, productive-looking meeting isn’t. So the meeting becomes the product, not the resolution.

What to try: Pull your last three sets of minutes. List every issue that appeared more than once. For each one, ask honestly: what specifically changed — not how it was reported, but what actually changed? That gap is where the drift lives.

Symptom 2: Your status reports are green, but something feels wrong.

The vendor is confident. The project manager is across the detail. Every metric says on track. And yet there’s a signal — quiet, hard to name — that something isn’t right.

This happens because status reporting systems are designed to track motion, not meaning. Milestones hit. Tasks completed. Risks logged. None of that tells you whether what’s being built still matches what the organisation actually needs. Green means the machine is running. It doesn’t confirm it’s heading in the right direction.

What to try: Ask your project lead one question, outside of a formal meeting: “If you could change one thing about how this program is being run, what would it be?” What they say — and how quickly they say it — will tell you more than the last six reports.

Symptom 3: Your vendor fixes things quickly, but the same class of problem keeps appearing.

Responsiveness feels like partnership. A vendor who resolves issues fast reads as competent and engaged. But look across the last ten issues and a pattern emerges — different names, same structural cause.

This happens because fixing the symptom is faster and less disruptive than identifying what’s underneath. This is true for the vendor and for your team. Both sides have a quiet incentive to keep the cycle moving rather than stop and examine why the same problem keeps returning in new clothes.

What to try: Ask someone with no stake in the answer to categorise your last ten issues by type, not by resolution status. You’re looking for patterns, not incidents. Repeated categories point to something that hasn’t been touched yet.

Symptom 4: The system is live, but nobody can tell you what value it’s delivering.

Go-live happened. The vendor handed over. The team is using the system. But ask what’s materially better — in process efficiency, decision quality, cost control — and the answers are vague.

This happens because we invest enormous energy getting to go-live and almost none in defining what “working” was supposed to mean. The business case had numbers. The implementation had milestones. The bridge between the two — the sustained discipline of confirming whether the investment is actually producing what was intended — rarely gets built. Go-live feels like completion. It isn’t.

What to try: Go back to the original business case or problem statement. Pick two or three specific outcomes that justified the investment. Ask whether you could, today, demonstrate progress against each one. If you can’t measure it, you can’t steward it.

Symptom 5: Your best internal people have quietly stopped pushing.

They’re still attending. Still contributing when asked. But they’ve stopped volunteering, stopped flagging things they’d have flagged a year ago, stopped investing in the outcome the way they once did.

This happens because capable people disengage when they’ve learned that raising hard things doesn’t change hard things. They’ve been through enough cycles to know the program’s appetite for difficult truths is limited. So they conserve themselves. They do the job. They stop caring about the result.

What to try: Have a direct, private conversation with the person whose judgment you trust most on this program. Not in a project context. Ask them what they’d want you to know if they were confident you’d act on it. Then sit with what comes back.

None of this requires a failing program.

Most of these symptoms are present in programs that look, from the outside, completely normal. That’s precisely what makes them dangerous.

The pull toward visible progress, managed optics, and quick resolution isn’t a sign of bad leadership. It’s a sign of human leadership operating inside a system that hasn’t been designed to counteract it.

The question worth asking is a simple one: are the structures around your technology program designed to surface what’s actually happening — or are they, quietly, designed to make it easier not to look?

I write about drift and the discipline required to hold standards. If this is describing something you’re currently navigating, I’m at spsingh@bhaniconsulting.com.