Designing Movement With R&D, Not At Them

Movement spanned a glance-able dashboard, booking, results, post-visit summaries, and a set of experiential questionnaires — surfaces that all pull live data from a hospital system. That's not a design I could throw over a wall and hope for. I worked with R&D early on what the dashboard could realistically show at a glance: which checkups are purchased, the next appointment, latest body measurements, recent results. Knowing what data was actually available, and how fresh it was, shaped the design more than any aesthetic preference. For an engineering leader, I think the useful thing is that I treated technical constraints as design inputs rather than obstacles. When the questionnaires needed to feel conversational and icon-rich but still produce structured, loggable answers, that was a conversation about data model and UX at the same table, not in sequence. I'd rather design a slightly simpler dashboard that R&D can ship reliably than a richer one that fights the backend on every load. Mobile-first wasn't only a UX stance — it set clear performance and layout expectations the team could build against without ambiguity.