Start from the problem to be solved
Before choosing a solution, describe the current situation and the expected improvement. A processing delay, a re-entry, or a blocked decision provides a concrete starting point. Document the initial measure and the conditions under which it is obtained.
The people who use the process know its constraints.
Build with the people concerned
The people who use the process know its constraints. Associate them with the choice of tests, identify the necessary means and clarify who can decide. Kotter's work notably proposes to share a vision, remove obstacles and make early progress visible.
Measure usage, then results
A delivery indicator answers the question ‘Is it installed?’. An adoption indicator answers ‘Is it used in the intended situations?’. Complement these with a measure of the expected result, a comparison point and a defined period. Use deviations to adjust the approach.
Do not confuse method and guarantee
A transformation depends on its context, resources and objectives. We do not use a universal failure rate: a percentage without a population, a definition of success and a measurement method cannot assess your project.
LUCID helps clarify organisational choices. SPARK drives project execution. Support is built around the need and the skills actually available.