Pourquoi on écoute avant de concevoir — et ce que ça change
There’s a mistake a majority of process improvement specialists make: they arrive with a ready-made solution, even before really understanding the problem.
It’s done in bad faith, it’s market logic: clients want fast answers, service providers bring bundled offers. We layer a framework to a reality without taking the time to read it.
At TAKOMA, we’ve made the opposite choice. Not out of idealism, but rather because experience has taught us one thing: in complex industrial systems, the problems are rarely where we first look for them.
Knowledge before solutions
Our methodology – TAKOMA Flow – starts by a COLLECTION phase. This is a deliberate word choice. It’s not only about “leading a diagnostic”. It’s about gathering material.
This material is what the teams know, but have never had the opportunity to actually formulate. It’s daily irritants that never work their way back to managements, workarounds invented through lack of proper adapted procedure, tacit knowledge that flows between two workers but doesn’t exist anywhere beyond them.
Field interviews, mapping of irritants, identifying real challenges behind visible symptoms: this step takes time. Despite that, it remains the most precious, because it produces something no other benchmark can remplace: an accurate comprehension of context.
An objective approach to prioritise
The next step – ANALYSIS – consists in attaching numbers to what the field has expressed. VSM mapping, measuring time with added value, bottleneck analysis, error rates, reworking… Operational insight is precious, but it has to be corroborated by data to be actionable.
This work allows us to prioritise. In any degradated system, there’s ten visible problems with two root causes. Analysis helps us distinguish them.
Designing and deploying with the teams
The DESIGN phase produces the target process, standards, documentary kit, organisational model. The DEPLOYMENT phase accompanies the implementation: training, piloting procedures, feedback loops.
But what’s the difference between a sustainable transformation and one that runs out of steam? It’s the first steps of collection and analysis that allow us to conceive a tailor-made solution. Were the teams listened to? Does the solution come from the field or is it imposed on them?
Field knowledge always precedes designing the solution: that’s our first principle.