Read the System, Not the Symptom

Read the system, not the symptom The first thing you learn in the ICU is that the patient who's screaming isn't necessarily the one who's dying. The quiet bed in the corner — the one where the numbers are drifting in a direction nobody's flagged yet — that's where the real problem lives. You learn to scan the room before you respond to the loudest signal. You learn that documentation isn't paperwork, it's pattern recognition slowed down enough to be shared. And you learn that the moment you intervene based on what you think is happening rather than what you've observed is happening, you've introduced a new variable into a system you don't fully understand yet. I spent six years inside healthcare. Three years of nursing certification at Catholic Clinics Oberhausen — anesthesiology specialization, which means you're responsible for a patient who can't tell you what they're feeling. Two semesters of pre-clinical medicine at Marburg. Then qualified nursing at Alfried Krupp Krankenhaus, a 900-bed academic teaching hospital, rotating through nearly every department including the ICU and stroke unit. Four hospitals. Thousands of shifts. And one discipline that outlasted all of them: observe before you intervene. That discipline didn't stay in healthcare. It transferred — fully intact — into every environment I've worked in since. At Unibail-Rodamco-Westfield, I watched millions of people move through shopping centers I'd helped design. The seating areas were consistently empty. The junctions sent people the wrong way. The food floors contradicted their own traffic logic. The architects had designed for an imagined user. I was watching the real one. The instinct to document what's actually happening rather than what the blueprint assumes — that's ICU thinking applied to spatial behavior. At Grau, I walked into a 30-year-old premium lighting manufacturer mid-generational transition and did the same thing. Scanned the room. The organization believed it understood its customers. It didn't. The gap between what customers actually experienced and what leadership assumed was happening — across B2B dealer channels, B2C retail, ordering, delivery, after-sales — was enormous. But nobody had documented it. Nobody had built the feedback infrastructure to make it visible. So I built it. Journey maps, behavioral gap analyses, reporting structures that connected the frontline to leadership. Not because I'd been trained in CX methodology at that point — but because the ICU had taught me that if you don't document the system's actual state, you can't intervene meaningfully. The NPS moved from 58 to 82. The systems are still running after my departure. But the methodology wasn't customer experience management. It was clinical observation, applied to a different kind of patient. People sometimes ask how a nurse ends up building CX infrastructure for a lighting company. The answer is: the method is the same. Read the system. Document what's actually happening. Identify the gap between assumption and reality. Build the process that keeps that gap visible. Then — only then — intervene. The symptom is what the organization brings you. The system is what you find when you look underneath it.