Imagine a 20-million-row operational database. Every hour, your analytics platform needs to know what changed. The traditional approach? Copy the table again. But if only 5,000 rows changed, why move 20 million? As data grows, full loads become slower, more expensive and harder on source systems. Deletes are also difficult to track reliably, and data freshness suffers. This is the problem Change Data Capture (CDC) is designed to address. Logical activities flow Instead of ask

“Good architecture removes complexity from the business, not hides complexity in technology.” Where we are in the journey We’ve deliberately taken our time. Not because we’re avoiding technology. Because we’re avoiding expensive assumptions. So far we’ve answered three questions. ✅ Week 1 What problem are we trying to solve? ✅ Week 2 How does the organisation operate today? ✅ Week 3 What decisions need to improve? This week we answer a fourth question. What principles should

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