That sounds unfair as methods are useful. They give people a shared language, a sequence to follow and a way to avoid jumping straight to a favourite answer. Naturally, I use them myself like all my colleagues. The trouble starts when the method becomes the purpose of the work.
A team can fill every cell in an FMEA and still fail to understand the risk. It can complete a five-whys exercise and identify a cause that is tidy, plausible but so wrong. It can produce a colourful SWOT matrix that says very little about what management, or anybody, should do next. A PDCA diagram with corporate logo can be displayed in every meeting room while decisions, evidence and support remain stuck in separate departments.
The form is complete, yet the thinking is not.
The question comes before the tool selection
Every method has its purpose, and it makes some things easier to see. That is its value, but it also makes other things easier to ignore. A failure-mode lens draws attention to how something can fail and what might prevent it. Root-cause analysis looks backwards from an existing problem. Five Whys helps a team keep asking what sits underneath the first answer. SWOT frames a position through internal capability and external conditions. PDCA logic gives management a way to learn and adjust while work proceeds.
Those are different jobs and treating them as interchangeable worksheets is careless. Treating them as sacred territories is just as bad.
Suppose deliveries are repeatedly late. The first question may be causal: what is causing the delay? A process view may then reveal an odd handover that nobody seems to own. FMEA may help to see that the same weakness can create several future failures. Where’s the Beef? -path, which is my adaptation of Theory of Change, may expose that the team is discussing delivery speed while the customer is actually waiting for reliable promises. PDCA logic or a Management Operating System may be the right way to carry the agreed change into practice and learn whether it worked.
The method follows the question. The question does never get bent to fit the darling method.
What must continue when the method changes
Changing lenses does not mean starting from zero. That is where many improvement efforts lose their red thread. One workshop produces a list of causes, another produces risks and the third produces actions. But each group uses its own isolated vocabulary. Therefore, nobody can say what and how the next plan was supposed to change the original situation.
The continuity has to sit above the methods.
At minimum, the team needs to retain two points: the condition it started from and the result it is trying to reach. I use the simple logic of bookends: Beginning situation is the first one, and intended better situation is the second bookend. The terms are less important than the discipline. What was the situation when we began? What we want to be true when we are finished?
If those bookends disappear, a method can produce excellent local work that no longer answers the original question. The team has been busy, but the reasoning has changed subject without anybody noticing.
A new lens should therefore inherit the relevant understanding, evidence, uncertainty, open questions and intended result. It should add something that the current lens cannot provide. When it has done its job, its conclusion must return to the same line of reasoning for further assessment or actions, not vanish into a separate report.
Interchangeable does not mean interchangeable results
The methods are interchangeable lenses, not interchangeable outputs. You should not expect an FMEA to tell you what a root-cause investigation tells you, or a SWOT to provide the control logic of a risk review. The point is to choose the lens that makes the next material question visible.
That choice requires judgement. A method should be chosen because it has a reasonable prospect of changing the decision, the priority or the next action. It should not be chosen because somebody has a template, a certificate or a workshop slot to fill.
This is also why I am wary of automatic method chains. “We always do SWOT, then FMEA, then RCA, then apply PDCA logic” sounds systematic until you ask what each step is expected to change. Sometimes the sequence is justified. Sometimes it is only the consulting equivalent of taking every tool out of the toolbox and laying them on the floor.
A professional method is a means of seeing more clearly. It is not proof that the problem has been understood or acted on.
Where the Interactive Services fit
That is the logic behind the Interactive Services I am developing at the moment. RCA, 5 Whys, Ishikawa, FMEA, SWOT, Where’s the Beef? and the other lenses are not competing mini-consultancies. They are bounded ways of asking better questions inside a continuous piece of professional reasoning.
The user should not have to remember which service contained an important fact. The reasoning should remember. A finding may begin as an observation, become a question about cause, expose a risk, lead to an action and return later as evidence about whether the action worked. The lens can change, but the thread cannot be allowed to break.
This also puts a useful limit on technology. An interactive service should not manufacture certainty because a screen has a next button. It should preserve what is established, what is assumed, what is disputed and what still needs to be learned. It should know when a different lens is relevant—and when another method would merely create more paperwork.
My aim is not to automate professional judgement. It is to keep professional judgement from being lost between tools, meetings and departments. Yes, a bit ambitious, but Life is!
The practical test
Before starting a method, ask three questions:
What are we trying to understand or decide?
What could this lens reveal that we cannot currently see?
How will its result change the line of reasoning we are already following?
If those questions have no clear answers, you have chosen the method probably too early. And after the work is done, ask one more question: are we closer to the intended result, or have we simply become better at describing the problem?
That is the difference between using a method and hiding behind one.
A final position
I do not believe there is one master method for serious organisational work. Reality is too untidy for that. Nor do I believe that every method is equally suitable for every question. That is the comfortable version of pluralism, and it is not useful.
My position is more demanding: methods should be selected by professional relevance, carried by a continuous line of reasoning and judged by whether they improve the next decision. The method is a lens. The reasoning is the work.
I will develop this series from there, including FMEA, action, behaviour change, learning systems and the boundary between useful psychology and manipulation.
My service: It always includes discovery and diagnostic as well as briefing of findings and actionable plan on how to deal with those. Best way to initialize this is to contact me here in LinkedIn and book the initial discussion. Or go straight to my work at www.baleteworks.com. No strings attached.