Describe the event
The person explains the issue, observation or opportunity in plain language.
← Applied work & examples
Applied work · Quality & continuous improvement
Make it easier to report a problem—and put it right.
Reporting a non-conformance can feel like pointing a finger. This quality workflow made it easier to describe what happened, ask useful questions and follow up the fix.
- Context
- Industrial operating business
- Function
- Quality & improvement
- Constraint
- NCR reluctance and inconsistency
- Response
- Guided issue and action workflow
Applied experienceAn example from the founders’ work in an operating business. Names are withheld. This is their experience, not a FUSED client case study.
The management problem
People worried about what an NCR implied.
A non-conformance report (NCR) can feel like an accusation. People may soften an issue, handle it informally or call it an opportunity for improvement because the formal classification feels personal.
The signal was a recurring question: is this really an NCR, or can we call it something less uncomfortable? The process was asking the individual to carry a classification burden the system could help resolve.
THE DESIGN INSIGHT
Remove the classification argument from the person raising the issue.
Let people describe what happened in ordinary language. Use structured questions and agreed logic to help identify the right path.
What changed
Start by asking what happened.
The workflow supported consistency without pretending AI could own risk, cause or closure.
Ask structured questions
The workflow gathers the facts needed to distinguish non-conformance, risk, defect, customer issue or improvement.
Support classification
Defined logic and AI-supported reasoning prepare a consistent classification for the accountable person to review.
Create visible action
Owners, dates, evidence, follow-up and closure requirements become part of the workflow rather than somebody's memory.
Root cause
Better questions moved the investigation beyond the safe answer.
A blank root-cause field rarely creates a disciplined investigation. The workflow prompted users through the reasoning, challenged surface explanations and made difficult questions feel less personal.
Quality activity relied on confidence and memory.
- Issues were delayed, softened or handled informally
- Classification varied by person
- Root-cause explanations stopped at the visible symptom
- Actions depended on manual chasing
- Repeat patterns were hard to see
The right behaviour became easier to follow.
- Issue capture used a guided path
- Classification used consistent questions and logic
- Investigation prompts encouraged deeper reasoning
- Actions carried owners, dates and evidence
- Trends and recurring themes became more visible
What remained human
The workflow organised the process. People retained the judgement.
Responsible people still assessed materiality and risk, accepted the cause, approved corrective action, authorised closure and changed the management system.
See the control model
System contribution
Questions, structure, evidence, reminders, grouping and review preparation.
Human authority
Risk, cause, adequacy, priorities, acceptance and closure.
Leadership visibility
Recurring themes, overdue actions, ownership and improvement focus.
FUSED responsibility
Workflow design, operating logic, monitoring, failure handling and improvement.
What this demonstrates
The useful change started with understanding the people.
The useful insight was recognising why good people avoided the process. The technical work then made classification easier, investigation safer, actions clearer and evidence more visible.
This experience shapes the way FUSED works: understand why the process is difficult for people, then build the colleague and skills around what would help.
Explore AI and ISO 9001One useful conversation
Start with one
cloud colleague.
Tell us about your business. We’ll help you find a first role, explain the service and give you a clear proposal before you decide.