In this article
An organization can be strong in several areas and still struggle because one essential condition is missing. A team may collaborate well but lose work during handoffs. Leaders may agree on a strategy while new employees receive too little guidance to carry it out. In those situations, investing only in the strongest existing capability may leave the practical constraint untouched.
Stephan Wesely called that constraint the minimum factor in his 2011 dissertation on OQM. He described it as the starting point for a dialogue-led improvement cycle, not a permanent label for an organization or its people. His work addresses historical questionnaire versions. Claims about today’s OQM 80 require their own current documentation.
What the eight-stave barrel explains
Wesely uses a barrel metaphor adapted from Christian A. Schwarz. Eight staves represent eight quality characteristics. The shortest stave limits how much water the barrel can hold. Making an already long stave longer will not raise that limit; improving the shortest one can.
The dissertation itself warns against pushing the metaphor too far. A barrel is a teaching aid, not a law of organizational performance. It does not show that every low score has the same cause, or that a single intervention will reliably produce growth. It prompts a more useful question: what experiences produced the result, and what would make the limiting condition stronger? Source: dissertation, pp. 39–41.
When to focus on a weakness and when to use a strength
Wesely distinguishes an essential condition from the choice among several workable solutions. If a necessary condition is absent, extra strength elsewhere cannot simply replace it. He compares this to a vitamin C deficiency: more vitamin A does not solve that particular problem. Once the need is clear, however, an organization’s strengths can help determine how to address it.
Imagine that decision rights are unclear. Strong customer relationships might help a company design a better decision process, because customer-facing employees understand where delays occur. Those relationships do not, by themselves, make the decision rights clear. A minimum-factor perspective and a strengths-based approach therefore complement each other: the constraint sets the priority, while strengths help create a response.
This distinction matters in US organizations where leadership teams can be under pressure to launch another initiative quickly. The method does not say to fix every low score. It says to examine whether a weak condition is essential to the organization’s current purpose, then agree on a focused response.
A low score is a prompt, not a diagnosis
If employees rate structures poorly, the reason could be unclear ownership, repeated approvals, inaccessible information, or an old routine that no longer fits the organization’s size. A survey result alone does not choose among these explanations. Treating it as a finished diagnosis can lead to a fashionable program that addresses the wrong problem.
Wesely’s cycle includes sharing and interpreting the profile with everyone involved. Participants need to understand what the results mean before setting goals and measures. He explicitly notes that misunderstandings can block implementation. Our guide to the six-step OQM cycle shows how the assessment connects to action and reassessment.
A useful hypothesis might be: “Customer requests stall because ownership after the first call is unclear.” A team can test a change to the handoff, watch whether requests move more reliably, and revise the hypothesis if the evidence points elsewhere. That is more informative than declaring “structures are broken.”
When yesterday’s solution becomes today’s constraint
Another image in the dissertation is a potted plant. Water, nutrients, location, and pot size can each limit growth. More watering may have helped before. Once the pot is too small, more water will not address the new limit.
In organizational terms, a previously useful practice can become a constraint as work changes. Informal coordination may suit one team. With several teams and locations, the same company may need explicit handoffs. This is an illustration of the principle, not an OQM case study or a promise that one structural change will increase revenue.
Turn a priority into a testable next step
- Name the condition. What currently limits the organization’s real purpose or the work needed to achieve it?
- Examine experience. Which concrete situations support that interpretation? Whose account differs?
- Choose one manageable change. Which action addresses the suspected cause without shifting avoidable costs to another team?
- Assign responsibility. Who will act, who needs information, and when will the team review the result?
- Reassess. Did the condition improve? Did another constraint become more important?
This sequence reflects the broader OQM research account: assessment, dialogue, implementation, and another look at the organization. A minimum factor is a working priority, not a verdict. It should change when better evidence or a new profile changes the picture.
Our research FAQ answers related questions about the historical method and its limits. Wesely’s original explanation appears on printed pages 39–41 of the dissertation.