The KAPER method
- KnowKnow deeply
- AimAim truly
- PavePave the way
- EmpowerEmpower fully
- ReflectReflect honestly
Contents
We do not claim to have invented the acronym. What binds us is the method as Kaper Group defines and practises it, the same in our five domains: customer experience, decisions and execution, data and AI, risk and compliance and digital journeys.
K · Know
We propose nothing before understanding what your clients come to do and what already exists.
In a digital project: before the mock-up of a practice portal, we list the requests the practice receives by phone and messaging app, the data it collects, and who owns the domain and the hosting today.
A · Aim
Your goal remains the starting point; we make it precise and measurable.
In a digital project: “patients book online without calling”, measured by the share of appointments booked online, with its starting level written down.
P · Pave
A concrete path, with a written scope, price and owners, then the build itself.
In a digital project: scope and price agreed before work starts, then design, build, and accessibility, security and performance tests.
E · Empower
Empowering means passing on the ability to act without us.
In a digital project: domain, code, accounts and data in your name; a person on your team publishes a change and restores a backup themselves before handover.
R · Reflect
An honest look at what has changed, on a date agreed from the start.
In a digital project: the 90-day review compares the measure with its starting level, and also states what has not changed.
Why R leads back to K
The method is not a straight line. The lessons of the review become the starting point of the next cycle. This is the principle of Kaizen, continuous improvement, combined with hansei, honest reflection on what did not work.
A customer journey, an information notice or a portal is never finished: your clients change, regulation evolves, and so does your organisation. Improving in verified steps beats rebuilding everything every three years.
What the X means
The X in KaperX is not a sixth step. KAPER describes how we work; the X stands for the experience you have when the method meets your situation. This is what we call the Kaper experience.
The method in our five domains
| Domain | How the method applies |
|---|---|
| Customer Experience | Start from the client's real tasks, and measure over time |
| Decisions & Execution | A named owner, a checking rhythm, a decision log |
| Data & AI | Know which data is processed, why, and who can access it |
| Risk & Compliance | Separate what is mandatory from what is announced, and document it |
| Digital Journeys | A service usable without help, and a tool you own |
What the method is not
- A standard or a certification. No text governs it, and nobody certifies it.
- A promise of results. It organises the work and the measurement; the result also depends on factors we do not control.
- A dependency. If you cannot keep what was built running without us, the Empower step has not been done.
Know · Aim · Pave · Empower · Reflect. This is the Kaper experience.
Next step
Everything starts with the first step: Know. Describe your project in a few lines from our contact page, or read what we build.
Frequently asked questions
Is the KAPER method a standard?
No. It is a working method; no text governs it and nobody certifies it.
Is it free?
Yes. Anyone may use it freely.
How does it relate to the PDCA cycle?
It is compatible with it: plan, do, check and act are all there, with one more step, Empower.
Should the steps be followed in order?
Generally, yes; and Reflect leads back to Know for the next cycle.
Why “Empower”?
Because the client must be able to carry on without us: owning their tools and knowing how to keep them running.