Redgum Book a conversation →
Where to startEfficiency vs CapabilityHidden IPThree horizonsPeople & changeThe long game

Ideas for building capability that lasts.

Practical thinking on the difference between efficiency and capability, where value hides in a business, and how to build something competitors can’t easily copy.

Subscribe via RSS →

Featured insights

Where to start

Planning the comprehensive fix? That’s the trap most businesses are standing in when they meet us. Here’s the shape of it — and a glimpse of the smaller, faster way out.

The big overhaul

Demands faith
  • An 18-month timeline
  • A 200-slide business case
  • Perfect on paper
  • Politics, delays and drift
  • Teams lose faith before they see results

The small release

Builds faith
  • Delivered in weeks
  • One real problem solved
  • Users involved from day one
  • Relief felt immediately
  • Teams ask for the next one
Planning the big transformation? The comprehensive fix feels safe. It rarely is.
Recognise this? The project turned political, the timeline keeps stretching, the team stopped believing.
Good looks like relief in weeks — one painful workflow fixed, a team asking for the next one.
There's a method to it — seven questions, a discovery checklist, and the full story.
1 / 4

Efficiency vs Capability

Every technology decision is really a choice between making today cheaper and making tomorrow possible. Most businesses spend a decade on the first without ever naming the second.

Efficiency

Makes today cheaper
  • The same work, in fewer minutes
  • A saving you bank once
  • Built from tools anyone can buy
  • Linear returns, forever
  • Keeps you in the race

Capability

Makes tomorrow possible
  • Work that wasn’t possible before
  • Each layer unlocks the next one
  • Built around what only you know
  • Returns that compound
  • Changes which race you are in

Automating a bad process just gives you bad outcomes faster. Efficiency removes friction; capability adds strength - and the order matters.

Hidden IP

It isn’t on the balance sheet and it isn’t in the filing system. It’s in the spreadsheet everyone depends on, and in the judgement your longest-serving people make without thinking.

Trapped

A person-dependent liability
  • Lives in long-tenure heads, and leaves when they do
  • Held in spreadsheets that are critical and undocumented
  • Real workflows nobody ever wrote down
  • Hundreds of judgement calls a week, never explained
  • Capacity capped by your best people’s hours

Formalised

An organisational asset
  • Captured in systems, onboarding and quality control
  • One live model everyone works from
  • Your best thinking applied to every client at once
  • New people competent in weeks, not years
  • The business keeps working when the founder doesn’t

Not better filing. Not more thorough documentation. A fundamentally different competitive position.

Three horizons

Discovery asks what is wrong. An opportunity audit asks what could be - and the answer changes depending on how far out you are willing to look.

Horizon One only

Where most businesses stop
  • Do what you already do, more efficiently
  • The clearest business case in the room
  • The shortest path to a return
  • Exactly what your competitors are doing
  • Makes you faster, not harder to replace

All three horizons

Where the real choices are
  • Scale Up - do what you do, better
  • Scale Out - same knowledge, new customers
  • Blue Ocean - build what doesn’t exist yet
  • One starting point that opens a bigger door
  • Direct comparison becomes difficult

The organisations that build genuine capability don’t just ask what needs fixing. They ask what’s possible.

People & change

Every stalled rollout gets explained as resistance to change. Almost none of them are - people adopt tools that give them time back and avoid tools that add steps.

Process-first

Compliance
  • Map the current process, build to fit it
  • Uptake enforced by policy and training
  • Champions push usage
  • When it stalls, add more comms
  • Plateaus, and the workarounds return

People-first

Relief
  • Ask what slows people down, remove that first
  • Uptake happens because the work got lighter
  • The team uses it because Monday is easier
  • When it stalls, look for steps still to remove
  • Compounds, because each win buys belief

If a system needs champions to beg people to use it, the system is wrong. Not the people.

The long game

If the business only works because you’re holding it up, you’re at the ceiling. Here’s what that looks like from the inside — and what it looks like from above.

Life at the ceiling

The signs
  • Everything breaks when you go on holiday
  • One urgent job takes ten phone calls
  • You are the bottleneck in every decision
  • Weekend work has quietly become normal

Life above it

What good looks like
  • Systems carry the coordination load
  • New staff useful in days, not months
  • Growth without proportional overhead
  • A business worth more — with or without you
Everything breaks when you go on holiday? The business still works — it just stopped scaling.
At the ceiling? Ten calls to coordinate one job, every decision waits for you, weekend work is normal now.
Good looks like fewer decisions — systems carry the load, and the business is worth more.
The long game pays compound interest — the warning signs, the ten-day pilot, and the value story.
1 / 4

The full library

Every article, A to Z, with the topic it belongs to. Thirty-five pieces and counting.

Subscribe via RSS → The book behind the ideas →