In this article
An employee survey does not, by itself, change an organization. People have to understand its results, agree on a priority, make a change in daily work, and return to the evidence. Stephan Wesely described this connection in his dissertation as the OQM improvement cycle. Its center is an ongoing dialogue, not a one-time score. Source: dissertation, pp. 38–40.
The dissertation was published in 2011 and concerns historical OQM versions. It explains the method’s logic. The features of today’s OQM 80 are a separate question that requires current product documentation.
Step 1: Prepare the process
Everyone involved needs to know what will be examined and what will happen after results arrive. That may sound routine, but it shapes whether people experience a survey as a way to learn together or as an exercise in control.
Preparation includes defining the unit of analysis, setting a realistic schedule, and identifying who can answer questions. The organization should know how results will be discussed and who will make decisions about actions. Waiting until after the survey to settle these points can create expectations the project cannot meet.
Wesely describes assessing either a selected group or everyone, depending on the setting. Participation, privacy, and the technical safeguards for a current project need their own review. A historical description is not evidence of how a contemporary platform handles data.
Step 2: Collect a profile
In the second step, selected participants complete a questionnaire. The resulting profile shows how eight quality characteristics appeared in the unit being studied. It provides a starting point for inquiry, not a ready-made action plan.
The unit matters. Results from one department should not casually be presented as results for the entire organization. For larger organizations, the dissertation describes profiles for separate units that can contribute to an overall view. Its historical questions and scales also should not be assumed to match the current OQM 80 instrument simply because both use eight factors.
Step 3: Interpret the results together
Wesely says the profile should be shared with everyone involved. Strengths and weaknesses become visible, and attention turns first to the minimum factor: an essential condition that currently limits progress.
Dialogue matters because a number does not explain itself. Do different teams experience the same issue differently? Which examples support one interpretation, and which challenge it? What is an observation, and what is still a hypothesis? The dissertation emphasizes that participants must understand the profile’s message. Misunderstandings can block implementation.
This step can be uncomfortable, especially when leadership is part of the constraint. A useful process makes room for that possibility without treating one score as a judgment on an individual manager.
Step 4: Choose goals and measures
Only after interpretation do participants decide what to change. Goals should address the constraint that matters, and measures should be examined through the six organic principles that Wesely presents as guidance for how change is carried out.
“Better collaboration” expresses an aspiration. “After each initial customer call, one named person owns the request until it is resolved” describes an observable change. The second example is a practical illustration, not a reported OQM case study. It gives the team something to test and refine.
The measure also needs a plausible connection to the diagnosed issue. Adding another survey when the problem is unclear authority, for example, may collect more data without changing the condition.
Step 5: Put the change into daily work
The fifth step is implementation. The dissertation mentions removing unnecessary work, simplifying complexity, and aligning responsibilities more closely with people’s capabilities. Change therefore means more than presenting a slide deck or hosting a workshop. It must alter the conditions under which people work.
Start at a scale that permits learning. If a team changes a handoff, it can observe whether fewer tasks are lost and whether the new routine is manageable. Assign an owner and a time to review the result. A plan is allowed to change when the evidence shows it should.
This is especially relevant in distributed organizations where a central decision can look sensible on paper but create extra coordination work for local teams. Include the people who have to carry out the change in its design and review.
Step 6: Reassess and begin again
The final questions are whether the measures supported the goals, whether the minimum factor improved, and what happened in other areas. Wesely’s cycle includes a new profile. A different constraint may then deserve attention, and the cycle starts again.
A later score does not prove that one intervention alone caused a change. Organizational conditions interact, and outside events matter. Numbers and experience should be read together: what changed, what did not, and what alternative explanation is plausible?
The cycle can be summarized as assess, understand, act with focus, and reassess. Our research overview and source-backed FAQ place that process in its historical context. For measurement figures from the older instrument, see the 2008 questionnaire evidence brief.