Off-shift
Make decisions when the expert isn't there.
Situation that creates key-person dependency
Decisions come up at night, on weekends, or at a remote site or plant, and the person who knows isn't always available.
Decisions worth capturing
- Which signals require immediate action.
- What can wait until the next shift.
- When to call someone or escalate.
What this looks like
What's scattered today comes together as knowledge the team can draw on.
Documents and history record what was decided. They almost never explain why.
Interviews about real cases capture the expert's judgment: what they looked at, what they ruled out, and when the answer would change.
The team asks and receives validated knowledge, with its author and date. If the knowledge doesn't cover the case, the question gets escalated.
When the expert decides differently from what was recorded, their reasoning comes back and becomes new knowledge.
Documentswhat is already written
Historydecisions already made
Judgmentthe expert's reasoning
Questionswhat the team asks
Document
Log of positive results from the past year
Past decision
Repeated positive: treated as persistent.
Quality expert's judgment
“It depends on where it came from and the history of that sampling point.”
Question from the shift
“Do I sanitize and keep going, or stop the line?”
The expert's digital twin
their knowledge, structured and validated
- signals
- zone of the sampling point, its history and that of adjacent points, product contact
- rule
- A positive that repeats in the same zone is not an isolated finding
- exception
- first positive with no product contact: sanitize and resample
- validated
- Pedro, Head of Quality, July 14, 2026
Their reasoning comes back as new knowledge
