TECHNICAL GUIDE · STRUCKEL TOOLS
PDS-01 · Continuous improvement

Basic PDSA

Records a short learning cycle with objective, questions, predictions, test, analysis and a decision about the next cycle.

PDSA · predição · teste · estudoFormulários Struckel
01
MANAGEMENT QUESTION

The problem the tool must make decidable.

Before opening a form, define the question that must be answered. A management tool is useful when it reduces ambiguity, exposes assumptions and makes clear which decision will be made from the evidence produced.

PDS-01

What specific learning do we expect from this small cycle, and which prediction will be compared with observed data?

Continuous improvement requires separating opinion from evidence and turning a broad problem into a sequence that can be observed, tested and revised. The tool creates value when it starts from an explicit current condition, applies criteria before concluding and ends with a verifiable decision — not merely a completed document.

Use it when you need to reduce variation, solve recurring problems, test changes, prioritize causes or preserve learning beyond the meeting in which it was produced.

02
METHOD ARCHITECTURE

Technical construction: from operational definition to evidence.

An improvement cycle creates temporal discipline: plan with a hypothesis, execute under control, observe effects and decide the next move. Closing the cycle should produce reusable knowledge, not merely confirmation that a task was completed.

01

Define the system and unit of analysis

Specify process, population, product, time window, boundaries and aggregation level. Without a defined unit of analysis, measures and comparisons may represent different phenomena.

02

Define criteria before evaluation

Translate abstract concepts into operational definitions, scales, classification rules and data sources. Criteria should exist before the result to reduce retrospective interpretation.

03

Preserve traceability

Link each conclusion to data, observations, assumptions and owners. When a score is used, retain its components; when a hypothesis is used, record how it will be tested.

Compare what was observed with what was expected. Record deviations, test conditions, data and the rationale to adopt, adapt, standardize or test again.

03
WORKED EXAMPLE

How the method behaves in a real situation.

A team predicts a new checklist will reduce incomplete fields from 12% to below 5%. It tests 20 cases on one shift, records deviations and compares observed results with the prediction before adapting or expanding.

The example is intentionally specific. Numbers illustrate the reasoning and are not universal benchmarks: limits, scales and targets must be defined for the process being analyzed.
04
MEASUREMENT AND INTERPRETATION

What to observe so the document does not become mere form filling.

Measures should serve reasoning. Whenever possible combine outcome, process and contextual evidence. For time series, look for patterns and variation rather than only point-in-time before/after comparisons.

01explicit prediction
02test scale
03outcome measure
04process measure
05unexpected effects
Consistency test

Ask whether another person, using the same definitions and evidence, would reach a similar interpretation. If the answer depends heavily on individual judgment, refine the operational definition, scale or data source.

05
LIMITATIONS AND GOVERNANCE

The tool supports decisions; it does not replace judgment, context and validation.

Methodological status

Established method/tool in professional and academic literature; exact implementation should be tailored to context.

Interpretation caution

PDSA is not a bureaucratic four-box sequence. Without prediction and genuine Study, it becomes a record of completed tasks rather than a learning cycle.

Governance rule

Define an owner, review frequency, official data source and condition for reopening the decision. Link actions to deadlines and indicators, hypotheses to tests, and risks to treatment and follow-up.

DefinitionEvidenceInterpretationDecisionReview
06
METHODOLOGICAL BASIS

References for deeper study of the method.

The references below support the methodological family or principle used. Struckel’s digital implementation operationalizes application, documentation and traceability; it does not change the conceptual limits of the original sources.

IHI_MFI

Langley GL, Moen RD, Nolan KM, Nolan TW, Norman CL, Provost LP. The Improvement Guide: A Practical Approach to Enhancing Organizational Performance. 2nd ed. Jossey-Bass; 2009.

Open reference
MOEN_NORMAN

Moen RD, Norman CL. Circling Back: Clearing up myths about the Deming cycle and seeing how it keeps evolving. Quality Progress. 2010;43(11):22–28.

Open reference
USE IT IN PRACTICE

Turn the method into a document ready for real work.

Struckel Forms offers a free way to structure this methodology with guided fields, contextual help and print/PDF preparation. Use the tool to organize reasoning; use consulting when the challenge requires design, implementation, facilitation or executive follow-up.