The core challenge of this project was to give hospitals and content managers configuration freedom (setting precedents for all future administrative tools) while ensuring patients encountered clear instructions.

Key Constraints:

• No 3rd party integrations
• Two-language support
• Tight deadline (2 to 3 months)

Success metrics:

• On-schedule feature delivery
• Positive customer feedback during beta testing
• Minimal support requests post-launch (target: near zero critical tickets)

Working with our UX researcher, I conducted stakeholder and customer interviews, identifying two primary user groups:

This feature required connecting our web application to our content management system (CMS), a technical challenge with multiple possible solutions, each affecting the UX differently. I realized right away that product, design, and engineering needed to align before we chose a path forward. I prepared a few wireframes and organized a workshop where we discussed competing priorities, reviewed user needs, evaluated the pros and cons of each approach, and agreed on a solution that worked for everyone.

I was particularly proud of this process as it not only solved the immediate challenge but established a cross-functional alignment framework we reused in future projects.

The technical solution enabled content managers to edit text directly in the web application, making the feature easy to find and use. However, managing multiple languages in a compact interface introduced risk of user error or confusion. To ensure I got this right, I brought the design team together for a thorough Design Critique session to establish interaction and navigation patterns that would scale across future features and prevent mistakes.

The final design enabled hospitals to customize document requests without technical expertise while giving internal teams efficient tools to manage translations and content.

Configuration flow: it provided a clear entry point with on/off toggles, real-time patient preview, and confirmation steps to prevent errors.

Content management flow: it offered a dedicated translation tab with language selector, inline editing, character validation, and bulk actions for efficiency.

Key design principles: usage of scalable patterns for future features.

• Successfully launched on schedule
• Positive feedback from hospital clients during beta and post-launch
• Zero critical support tickets in first 60 days post-launch

1. As this was the first configuration feature, every design decision carried extra weight. I learned the importance of thinking beyond the immediate feature to create patterns that would scale.
2. The workshop format I developed proved highly effective at surfacing hidden constraints and building shared ownership. The key takeaway was that early and structured collaboration prevents expensive misalignment later.
3. Our success metrics were relatively lightweight and very focused on launch timing and basic satisfaction. While we got positive outcomes, I saw the need for more rigorous UX metrics in future projects.