Skip to content
Kamoto

The Kamoto Approach

A diagnostic should change what leaders do next.

A beautiful report that confirms what everyone already suspects will not change much.We connect what people experience with how the company works—then turn it into a small number of decisions and changes.

Explore the Diagnostic

01 — Align

Before we measure anything,
we agree on what matters.

Imagine starting every call with one question: “Am I adding value here?” If nobody can give you a clear answer, you leave.

Most people would never do it. Yet they sit through meetings nobody needs, follow processes nobody can explain and ask for approvals nobody really uses. We start by asking the same uncomfortable question about the diagnostic itself: what does leadership actually need to understand, and what will they do differently once they know?

What is happening now?

Where does work slow down, become unnecessarily difficult or depend on somebody stepping in to rescue it?

What do we need to understand? We agree on the problem worth examining.

What should become easier?

Faster decisions? Clearer ownership? Fewer handovers? We define what useful progress would look like.

02 — Diagnose

We look at how work actually happens.

You rewrite an email to an executive three times. You remove the background, keep the essential facts and make the decision required completely clear.

Why don’t we give our peers the same courtesy?

Org charts show how the company is supposed to work. People tell us what happens when two teams disagree and somebody needs an answer by Friday.

People

Capability, engagement and alignment.

Process

How work flows and connects.

Data

Quality, access and insight.

15–20
minutes
Anonymous
by design

Structure

Roles, spans and accountabilities.

Culture

Behaviours, norms and decisions.

Technology

Enablers and adoption.

Short enough to complete. Detailed enough to be useful. Anonymous by design.

03 — Understand

The numbers tell us where to look.
People tell us why.

A leadership team tells us decisions are delegated. Ten minutes later, a manager says:

“Yes, I can decide—but I need approval first.”

Both may be telling the truth. The policy says one thing. Daily experience says another. Our job is to make that gap visible without turning it into a debate about who is right.

01

Signal

What is happening?

We find recurring patterns across teams, roles and responses.

02

Meaning

Why is it happening?

We test the pattern against real situations with the people doing the work.

03

Decision

What changes next?

We turn the evidence into a small number of choices leadership can actually make.

The tool captures the pattern. The conversation tells us what it means.

04 — Prioritise

Not every problem deserves a programme.

Ask ten people what the company should improve and you may get fifteen priorities.

That does not mean they are wrong. It means leadership still has to choose. We filter the findings using three practical questions.

Evidence

Does it affect work that matters?

Confidence

Do we understand it well enough?

Consequence

What happens if nothing changes?

  1. Focus area
  2. Focus area
  3. Focus area

If everything is a priority, the old problems will still be there next quarter.

05 — Intervene

The problem decides the intervention.

Someone suggests another weekly meeting. Everyone knows the calendar is already full. The meeting is scheduled anyway.

Three weeks later, the original problem is still there—now with minutes.

We do not begin with a programme we want to deliver. We begin with the cause we found and choose the smallest intervention capable of changing it.

Align

Create shared direction when priorities compete.

Shift

Change habits built around escalation and rescue.

Scale

Build clearer roles, routines and handovers.

Retain

Reduce avoidable pressure on people and knowledge.

No standard package. No intervention pulled off a shelf.

06 — Prove

We changed something.
Did the work get easier?

Everybody leaves the workshop energized. The slides are excellent. The action plan has owners, deadlines and three shades of green.

Then an ordinary Tuesday happens.

That is the real test. Are decisions moving faster? Are fewer tasks bouncing back? Do managers spend less time chasing and rescuing work?

Kamoto Diagnostic dashboard showing the stability index, critical gaps and open actions
One view of what needs attention, what is already moving and what still needs an owner.
  1. 01

    Baseline

    Keep the original picture.

  2. 02

    Focused action

    Give the change an owner and a next step.

  3. 03

    Remeasurement

    Ask the same questions again.

  4. 04

    Proof

    See what improved—and what did not.

No second measure, no victory speech.

Leadership alignment

Leadership stays part of the method.

We have seen leaders nod in complete agreement—and leave the room with three different interpretations of what was agreed.

Presenting the findings is not enough. Leaders agree on what the evidence means, what will change and who owns it.

Kamoto organization snapshot showing teams, reporting eligibility and anonymity checks Enlarge

Before the diagnostic starts, leadership agrees on who should be heard, what can be compared and where anonymity must be protected.

01

Shared reality

Agree on what the evidence shows, even when views of the cause differ.

02

Selected priorities

Choose the few problems that deserve leadership attention now.

03

Continued attention

Keep owners, progress and results visible after the workshop ends.

Evidence changes the conversation. Leadership decisions change the company.

Bring us the problem people keep working around.

The meeting everyone attends but nobody needs. The approval nobody can explain. The task that returns to the same person every Friday. You do not need to diagnose it first. Tell us what keeps happening. We will start there.