Nothing Is Lost, Everything Improves (with Method)

A brief return to basics: the Deming wheel

In the wonderful world of quality, there is an icon that keeps coming back like a catchy refrain: the Deming wheel, also known as PDCA (Plan-Do-Check-Act). This simple and powerful loop was born from the desire to create an endless improvement cycle. There is no finish line, but you find a permanent playground.

Its creator, William Edwards Deming, popularised this method in the 1950s in Japan. Since then, it has been found in all quality approaches, notably as a pillar of the ISO 9001 approach.

PDCA in four steps

1. Plan: Identify a problem, analyse the causes, imagine solutions.
2. Do: Test the solution (on a small scale if possible).
3. Check: Evaluate the results obtained.
4. Act: Generalise the solution if it works... or start another turn of the wheel.

The idea is to never stop. You are never "good enough", you can always be better.

Continuous improvement, at the heart of the system

It does not work in isolation. It is deeply interconnected with the other pillars of a quality approach:

• Processes: each improvement often starts from a malfunction in a process. And it is in the processes that changes are implemented.
• Documents: procedures, instructions, audit reports... they formalise improvements, make them traceable and reproducible, or themselves need to be modified.
• Risks: identifying a risk is already the beginning of an improvement. Each preventive or corrective action is a step towards better.
• Stakeholders: their feedback, their expectations, their dissatisfaction are all levers for improvement. But you still need to listen to them...

Uscope, the tool that keeps you moving forward

With Uscope, continuous improvement is not just a nice word in a Quality charter: it is a living function integrated at all levels.

Improvement declarations directly from any object: whether it is a process sheet, a project activity, a task or a document, you can create a contextualised improvement request. No more searching for where to report: everything is a click away.

Direct links between actions and related objects: to avoid information loss and promote traceability. You know exactly what you are improving, why, and with what impact.

Integrated action tracking: each improvement can be planned, tracked, verified... Did we mention we love the Deming wheel?

Concrete example: improving a recruitment process with Uscope

Context

The HR team of an SME uses Uscope to formalise its internal processes, particularly recruitment. A colleague notices that a candidate never received a response after an interview. She wants to prevent this from happening again.

1. Accessing the relevant process

She opens the "Recruitment" process directly in Uscope, which contains:

• The process steps
• The associated deliverables (interview form, offer template, etc.)
• The competencies mobilised
• The roles involved

2. Declaring an improvement

From the process sheet, she clicks on "Declare an improvement", specifying:

• Description: "Add a systematic follow-up step for unsuccessful applications"
• Type: corrective action
• Improvement proposal: "Insert a step after the interview: automatic sending of a rejection email if the candidate is not selected within 5 days"
• Link: "Recruitment" process linked automatically.

3. Action plan (PDCA) — handled by the quality manager

The request is automatically forwarded to the quality manager, who enters the PDCA loop directly in Uscope:

Act: if effective, validation of the improvement and publication of the new version of the process

Plan: analysis of the situation → why was the email not sent? (lack of clear responsibility, absence of a formal step)

Do: proposal to add a step in the process: "Send a rejection email within 5 days following the interview"

Check: monitoring for one month to ensure that responses are sent

4. Automatic process update

The new version of the process is published in Uscope, with modification history, notification to relevant people, and update of the associated document. Nothing is lost, everything is tracked.

This type of case illustrates several strengths of Uscope:

• Centralisation of information
• Traceability of improvement actions
• Team responsiveness
• Alignment between the field and quality documents

Conclusion

Continuous improvement is not optional. It is the engine of quality. And with Uscope, you have not only the keys to the engine, but also the GPS, the map and even the co-pilot.