The starting point
I joined an undisclosed digital-health company as a Frontend and UX Consultant. The work covered the public website, product and UX workshops, interface direction for a new system and the redesign of a related health product.
The main difficulty was not a missing interface. It was that product ideas, content and technical possibilities had grown ahead of a clear launch path. More screens and more flexibility would not make that easier to understand.
Reducing the problem before building
I started by reviewing the existing user experience and information hierarchy. In workshops, I helped separate immediate user needs from ideas that could wait, and translated broad discussions into clearer journeys and priorities.
That meant treating removal and simplification as product work. The goal was not to preserve every earlier decision. It was to find the smallest coherent experience that could explain the offer, support the next step and remain credible in a sensitive health context.
Content and interface as one system
I redesigned and implemented the public-facing interface while working with structured content in Contentful and Prismic. I defined content models and reusable frontend components so editors could change the content without breaking the relationship between information and presentation.
The useful boundary was not simply CMS versus frontend. Content, presentation and application logic needed clear responsibilities. That kept the system flexible where change was expected without turning every part of the interface into a configurable abstraction.
Working across product, UX and delivery
The engagement moved between discovery and implementation. I facilitated conversations about user needs and priorities, proposed interface directions, and stayed close enough to the frontend to test whether those ideas were practical.
This made trade-offs visible early. A direction could be evaluated as a user journey, a content workflow and a technical implementation before it became an expensive commitment.
What changed
The public experience became clearer and the product work had a more focused set of journeys and interface directions. The engagement ended after the project lost its funding, so I do not present the work as a completed commercial outcome.
The lasting lesson was that a product reset is often an exercise in choosing boundaries. The frontend matters, but the most useful work can be deciding which complexity deserves to reach it.