A3 Problem Solving
A3 problem solving is a concise, evidence-led way to describe a problem, understand the current condition, test causes, select countermeasures and follow results. The page matters less than the thinking, observation and collaboration used to create it.

On this page · 16 sections
- 1What A3 problem solving is
- 2Frame the problem at the actual place
- 3Move from symptoms to causes
- 4Select countermeasures, not slogans
- 5Check results and standardise
- 6Inside V5: keeping the A3 connected
- 7Explain it for your operation
- 8Build a coherent evidence story
- 9Use coaching and cross-functional review
- 10Fit A3 into a regulated quality system
- 11Run disciplined review points
- 12A practical A3 sequence
- 13A proportionate implementation plan
- 14Internal review questions
- 15Records and evidence to retain
- 16Questions to ask when evaluating software
How does A3 Problem Solving apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What A3 problem solving is
An A3 normally presents the background, current condition, target, analysis, countermeasures, implementation and follow-up on one large sheet or equivalent digital view. Its limited space encourages a logical story rather than a collection of attachments.
A3 is not a regulatory form and it is not a substitute for a required deviation, CAPA or safety record. In a regulated operation it can structure the reasoning while controlled records retain approvals, evidence and formal decisions.
02Frame the problem at the actual place
Describe the gap between the expected and observed condition using time, place, product, equipment and measurable impact. Observe the work where it happens and speak with the people doing it. Avoid beginning with a preferred solution.
A useful current-state picture distinguishes facts from assumptions and shows the process boundary. Trends, photographs, process maps and samples can help, provided source and context remain traceable.
03Move from symptoms to causes
Break the problem into a manageable slice, ask where and when it occurs, compare where it does not occur, and test candidate causes against evidence. Five Whys or a fishbone diagram can organise questions but cannot validate a cause by themselves.
A cause should explain the observed pattern and be capable of being confirmed or disproved. If the team cannot show that changing the cause should change the outcome, more investigation is needed.
04Select countermeasures, not slogans
A countermeasure changes a condition that produced the problem. Define the owner, due date, affected procedure or equipment, risk review, training and evidence needed. Consider unintended effects before implementation.
Separate containment from correction and longer-term corrective action. Additional inspection may protect the next shipment but may not prevent recurrence.
05Check results and standardise
Define the target measure and observation period before implementation. Compare results against the same baseline definition, investigate side effects, and state whether the countermeasure worked. If not, revise the analysis rather than declaring success.
When the change works, update the controlled method, training and relevant risk information. Share learning at the level appropriate to the operation.
06Inside V5: keeping the A3 connected
V5 can keep quality records linked to affected production records, corrective actions, owners and due dates. Documents, signatures and audit history can support accountable follow-through when an A3 is used alongside the approved quality process.
V5 does not generate a verified cause or approve a countermeasure. Human investigators gather evidence, assess risk and make closure decisions.
07Explain it for your operation
Start with one recurring operational problem whose boundaries are clear enough to observe. Nominate an owner and a small cross-functional team, reserve time at the process, and agree which formal quality record the A3 supports.
At each review ask: what did we learn, what evidence changed our view, what remains uncertain, and what decision is now required? Concision should expose weak reasoning, not hide it.
08Build a coherent evidence story
The sections should connect: the current condition supports the target, the analysis explains the gap, countermeasures address confirmed causes, and follow-up measures the target. If a proposed action cannot be traced back through that chain, it may be an unsupported idea.
Use diagrams and concise facts where they communicate better than prose. Reference controlled attachments for detailed evidence rather than shrinking unreadable data onto one page.
09Use coaching and cross-functional review
The owner develops the A3 through repeated observation and discussion; a coach asks what evidence supports each claim and where the logic jumps. Operators, maintenance, quality and technical specialists should contribute when their work or expertise is affected.
Consensus is not proof. Record unresolved views and the test that will distinguish them. The authorised quality process still governs formal approval and closure.
10Fit A3 into a regulated quality system
Open the required deviation, nonconformance or CAPA record according to procedure. Link the A3 as analysis support and retain original data, approvals, signatures, change controls and effectiveness evidence in controlled records.
Do not use a visually complete A3 to bypass impact assessment, validation, training or product disposition. Separate immediate containment from changes requiring formal review.
11Run disciplined review points
At each review confirm the problem boundary, new observations, tested causes, action status and risks. A red action is information, not a reason to rewrite the due date without explanation.
Close only when the defined result has been observed for a meaningful period and remaining risks are accepted by the right role. Capture lessons that can prevent similar issues elsewhere.
12A practical A3 sequence
A team investigating repeated seal wrinkles begins with the expected seal condition, actual defect rate and where the issue occurs. Observation shows it appears after warm restarts on one line. The team tests temperature recovery and web tension rather than jumping straight to retraining.
A countermeasure changes the restart setup and adds a verified check. The implementation plan covers instruction revision, risk review, training and defined trials. Follow-up compares wrinkle rate over enough warm restarts and records whether the hypothesised mechanism changed.
13A proportionate implementation plan
- Confirm the applicable requirement, product scope and decision owner.
- Map the current method and the records already available.
- Define terms, responsibilities, evidence and exception handling in the approved procedure.
- Pilot the method on one representative process and challenge a difficult exception.
- Train affected roles, approve the change and monitor whether the method works as intended.
- Review after significant change and retain a transparent history of decisions.
Scale the formality to risk and complexity. A small operation still needs clear responsibilities and reconstructable evidence, while a multi-site operation also needs harmonised definitions, governance and comparison rules.
14Internal review questions
- Can a reviewer identify the source, owner, method and current approved version?
- Do summaries reconcile to original records and include unfavourable or missing evidence?
- Are exceptions visible, assessed and linked to the affected material, product or process?
- Are actions assigned, overdue items escalated and effectiveness reviewed?
- Have changes in product, supplier, equipment, method or regulation triggered reassessment?
- Does the record distinguish system support from the decision an authorised person made?
15Records and evidence to retain
- Approved scope, definitions and responsibilities for a3 problem solving.
- Source records and identifiers that let a reviewer reconstruct the work.
- Methods, assumptions, calculations, exclusions and any data-quality limitations.
- Exceptions, investigations, decisions, approvals and resulting actions.
- Version history showing when the approach changed and why.
Records should be proportionate to the decision and usable by someone who was not present. Preserve original evidence and corrections rather than replacing it with an unexplained summary.
16Questions to ask when evaluating software
- Can users trace every summary value back to its source record and version?
- How are roles, permissions, signatures and corrections recorded?
- Can the workflow reflect our approved procedure without inventing a universal rule?
- What happens during an outage, and how are later entries distinguished?
- Can we test the highest-risk exception with realistic data before committing?
- Which decisions remain explicitly assigned to an authorised person?
Frequently asked questions
Q.What is a3 problem solving?+
A3 problem solving is a concise, evidence-led way to describe a problem, understand the current condition, test causes, select countermeasures and follow results. The page matters less than the thinking, observation and collaboration used to create it.
Q.Is a3 problem solving required in every operation?+
The applicable product rules, market, risk and approved quality system determine what is required. The method should be justified for the operation rather than copied without context.
Q.Can software make the final quality decision?+
No. Software can organise records, calculations and workflow, but authorised people remain responsible for scientific, quality and disposition decisions.
Q.How should a site start?+
Choose one bounded process, define the decision and evidence, test the method with real records, correct gaps, then expand under change control.
Q.What evidence should be retained?+
Keep the approved method, source records, assumptions, exceptions, review, decision, approval and any resulting action with enough context to reconstruct the work.
Q.How often should it be reviewed?+
Use the applicable requirement and a risk-based cycle, with earlier review after significant change, failure, complaint, deviation or new knowledge.
Primary sources
Want to see how A3 Problem Solving could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
