Week 3: Defining Success — Designing for Better Decisions, Not Better Dashboards "A dashboard doesn't improve patient flow. Better decisions do." Where we are in the journey Every architecture project should reduce uncertainty before introducing technology. Our journey so far has been deliberately slow—and that's by design. ✅ Week 1 – Define the Problem We asked why patients were experiencing delays. Not what dashboard needed building. ✅ Week 2 – Understand the Current State

Week 2: Understanding the Current State — Mapping the Patient Journey Before Designing the Data Platform "You can't improve what you don't fully understand." If Week One was about understanding the problem, Week Two is about understanding today's reality. Last week, we deliberately stayed away from Microsoft Fabric. Instead, we focused on a much more important question. What problem are we actually trying to solve? Our fictional NHS Trust wanted to understand why patients who

Architectural process for any Data Project. Week 1: Before You Build Anything, Understand the Problem Why successful data platforms don’t start with technology Spend enough time around data projects and you’ll notice a familiar pattern. Someone asks for a dashboard. The data team starts building pipelines. A Lakehouse is created. Reports appear. New technologies are introduced. Months later, people are still exporting data to Excel because they don’t trust what they’re seeing