On Service Design: Diagnosis comes before design. The initial assumption was that dashboards needed improvement. The actual problem was service-level clarity. Most of my impact came from fixing the earlier layer - the website and patient journey - not from UI optimization.

On Strategic Prioritization: Start where users drop off, not where you're asked to design. The website wasn't the "flashy" design work, but it was where the business problem manifested. Fixing it first prevented rework and multiplied impact downstream.

On Scaling Through Systems: You can't design for every new condition or market. You have to architect a system that new conditions can inherit. Modular thinking isn't about components - it's about foundational logic that flexes without breaking.

On Multi-User Design: Design for different user types simultaneously, not sequentially. The patient, coach, and specialist dashboards weren't separate projects. They were three role-based views of one coherent system. This prevented fragmentation and reduced implementation complexity.

On Simplification: Eight steps became three stages. Separate programmes became a unified spectrum. Complex clinical logic became explainable alerts. Simplification is systems work — it requires understanding what can be removed without losing critical information.

What I'd Do Differently: I'd validate the three-stage framework through user testing earlier, rather than discovering its power through implementation. Rapid testing of different journey structures before full design would have accelerated alignment.