Case Study 1
Navigating Stakeholder Pressure While Protecting Product Integrity
Many healthcare platforms try to show all patient information at once. Through UX research, we learned that this actually overwhelmed users and made critical workflows harder, not easier. We proposed reducing on-screen clutter by introducing progressive disclosure — adding a click to surface information only when needed. Stakeholders were hesitant because the legacy pattern favored maximum visibility, and changing it felt risky. I anchored the conversation in research and user behavior rather than preference. Over time, the focus shifted from “more information” to “better usability.” After validating the design through testing, stakeholders aligned around the change, and the interface became cleaner and easier to navigate without sacrificing access to key data. The project reinforced an important lesson: protecting product direction sometimes means challenging what feels familiar in order to build something better.
When Everything Is a Priority: Rebuilding Product Focus
A roadmap should reflect input from stakeholders, engineering, business, and design — but there was a point where we couldn’t keep saying yes to everything. We ran into performance issues when rendering large datasets. Once we hit around 10,000 items on screen, the platform lagged. Even though we weren’t expecting that scale immediately, the risk was clear: if we didn’t invest in engineering now, we’d pay for it later in bugs and instability. I chose to shift the roadmap toward performance work and deprioritize planned features. That meant pushing timelines and having difficult conversations with stakeholders who were expecting visible wins. I focused those conversations on risk, long-term product health, and the cost of ignoring technical debt. It wasn’t the most popular decision in the moment, but it protected the platform and set us up to scale. Sometimes rebuilding focus means choosing sustainability over speed.