Skip to content

How I work

A method to connect decision and execution.

Understand the context, choose priorities, validate the solution and monitor its use. Each step has a function and an output that helps guide the next one.

The nine steps

The nine steps of the method, in sequenceVertical diagram with nine numbered steps, from Context to Evolution. An arrow returns from the last step to the first, representing the cycle of continuous improvement.01ContextDefinition of the problem.02DiagnosisBottlenecks and hypotheses to verify.03PrioritizationA reasoned sequence of actions.04ArchitectureDesign of the solution.05ValidationAdjustments and criteria to proceed.06ImplementationImprovement delivered according to the scope.07GovernanceControl rules.08MeasurementReading of the result, with limitations.09EvolutionImprovement plan.CYCLE

The nine steps

What each step asks, does and delivers.

Each step has a central question, an activity and an output that guides the next one.

Governance and the definition of indicators are not left for the end: they begin in context and accompany the whole work. The order below is the order of execution — controls are built from the start.

Context

Central question

What does the company need to achieve?

Activity
Understand objectives, priorities and limitations.
Expected output
Definition of the problem.

Diagnosis

Central question

Where does the operation lose capacity?

Activity
Analyze flows, information and responsibilities.
Expected output
Bottlenecks and hypotheses to verify.

Prioritization

Central question

What deserves attention first?

Activity
Compare impact, effort, risk and dependencies.
Expected output
A reasoned sequence of actions.

Architecture

Central question

How should the improvement work?

Activity
Connect people, data, systems and rules.
Expected output
Design of the solution.

Validation

Central question

Do the assumptions hold in practice?

Activity
Test behavior, exceptions and costs.
Expected output
Adjustments and criteria to proceed.

Implementation

Central question

How does the solution enter the routine?

Activity
Configure, integrate, document and guide use.
Expected output
Improvement delivered according to the scope.

Governance

Central question

Who can do what?

Activity
Define owners, access and approvals.
Expected output
Control rules.

Measurement

Central question

What changed compared with the start?

Activity
Compare indicators and context.
Expected output
Reading of the result, with limitations.

Evolution

Central question

What needs to be adjusted?

Activity
Observe use, changes and new priorities.
Expected output
Improvement plan.

Illustrative example

The solution depends on the investigation.

The same symptom can lead to different decisions. Before choosing between simplifying, integrating, automating or using AI, the work investigates where the real problem is.
  • Simplify the processWhen there are steps or approvals that can be removed before any technology.
  • Integrate informationWhen the problem is information that does not flow between areas and systems.
  • AutomateWhen the task is repetitive, stable and already well understood.
  • Use AIWhen there is volume, variation or language that requires interpretation, with supervision.

The decision depends on what the investigation finds — not on a preference for technology.

Ready to apply the method to your operation?

The method guides the work; the starting point is always your operation's problem. We can begin with a conversation about it.