Unmask Friction

The fourth principle is about making the invisible visible. Most of what damages a practice is not a dramatic failure but a small, recurring friction, the lab that is always late, the workflow step that always stalls, the task that always spills over. Because each instance is minor, it never gets named. It is absorbed, worked around, and forgotten by the next morning.

What the science says

Safety science has a name for these buried problems: latent conditions. In Human error: models and management (BMJ, 2000), James Reason distinguishes the “person approach,” which blames the individual, from the “system approach,” which looks for the standing weaknesses built into how work is organised. His principle: “we cannot change the human condition, but we can change the conditions under which humans work”, but only conditions you have first made visible.

The operational counterpart comes from Steven Spear and H. Kent Bowen’s study Decoding the DNA of the Toyota Production System (Harvard Business Review, 1999). After four years inside Toyota’s plants, they found the system’s real engine was the habit of surfacing problems the instant they occur, rather than working around them. Every abnormality is treated as a signal and made visible immediately. Friction tolerated is friction lost as data.

Inside Loguaron

This principle lives in the Weekly Review, completed at the end of the week, the first feedback loop. Here you record any friction: EHR problems, workflow problems, staffing problems, lab delays. The rule is cumulative: if the same problem appears again, record it; if it keeps appearing, investigate the pattern. The question it answers is What is repeating? Not How do I feel about the week?