Featured Case Study
An early-stage healthcare startup connecting families with vetted caregivers. Embedded in the product team for five years, I shaped the platform from early concept through production — across web, mobile, an operations dashboard, and a conversational care assistant.
Flexxi is an early-stage healthcare startup connecting families with vetted caregivers across Germany. Embedded in the product team for five years, I worked directly with founders and developers — contributing to product strategy, designing across every platform, and taking work through to production-ready implementation. Every interface had to serve three completely different user groups while sharing one coherent underlying system.
Families needed trust. Caregivers needed speed. Operations teams needed control. Everything had to work together — across web, mobile, and internal tools — without compromising any one of them. In a startup environment, those decisions had to be made fast, with limited resources and evolving product requirements.
Making emotional decisions about care. Every touchpoint had to feel safe, clear, and confident enough to act on.
Working on the go, often under pressure. Interfaces had to be fast, reliable, and instantly readable on mobile.
Managing a growing marketplace at scale. Tools had to surface the right data and reduce manual effort at every step.
Not a client engagement — an embedded partnership. Working directly inside the founding team meant contributing to product decisions, not just executing against a brief.
Mapped user journeys across all three roles to identify friction, redundancy, and gaps in system logic before touching any UI.
Synthesized research into a clear friction map — prioritizing problems by frequency, severity, and impact on user confidence.
Designed role-specific experiences that felt simple from the outside while sharing a coherent system underneath.
Defined reusable UI components and interaction logic early — foundations that held up as the product grew across platforms and years.
Stayed close to implementation throughout — working through technical constraints with engineers, refining specs iteratively, and making sure designs shipped as intended.
I designed onboarding flows across families and caregivers, handling multiple entry points (email, phone, social login) and complex edge cases.
Families in complex emotional situations make fast judgments about trust. Every page was designed to establish credibility immediately and guide users toward a confident first action — not just look polished.
Two distinct user types with completely different needs — families making high-stakes decisions calmly at home, and caregivers working fast under pressure. Each app had to feel purpose-built, while sharing a coherent visual and interaction language underneath.
Families can request support, compare care options, and manage bookings directly from their phone.
Caregivers receive matched requests, manage active shifts, and track earnings in one simple workflow.
The operations dashboard was designed to surface critical information first — booking status, caregiver availability, and escalation signals — without burying teams in data tables. The challenge was showing enough context for fast decisions while keeping the interface calm under high volume.
Transforming a 200+ question healthcare form into a guided conversational experience
Users previously had to complete a long PDF form with over 200 questions to access government healthcare support. The process was complex, confusing, and especially overwhelming for elderly users unfamiliar with bureaucratic systems.
A conversational assistant replaces a complex 200+ question form, guiding users step by step through a simplified and accessible process.
Key Design Decisions
200+ questions transformed into small, manageable interactions.
Replaced traditional forms with a guided, human-like interaction.
Only relevant information is shown at the right moment.
Friendly assistant reduces stress and builds trust for elderly users.
"What used to feel like paperwork now feels like a conversation."
Flexxi wasn't a client project or a spec exercise — I was embedded in the founding team. That meant contributing to product direction, designing under evolving requirements, and staying close enough to implementation that decisions actually held in production.
Direct collaboration with developers — translating designs into production specs and iterating through technical constraints
Adapted to evolving product requirements as business priorities shifted across five years of growth
Production-level ownership — responsible for implementation accuracy, not just visual quality
Built design patterns that scaled with the platform as it grew in complexity, user volume, and product scope
Complex multi-user healthcare processes simplified into clear, navigable interfaces — reducing decision friction across all three user types.
Consolidated overlapping UI patterns into a unified system — fewer inconsistencies, faster shipping, lower maintenance overhead.
Transformed a 200+ question government form into a guided conversational experience accessible to elderly and non-technical users.
Built reusable component foundations the team could extend independently — design decisions that held up across years, not just sprints.
Maintained pace with a fast-moving founding team — adapting quickly to shifting requirements while keeping quality and consistency across every platform.
Stayed close to implementation throughout — iterating directly with developers to close the gap between design intent and what shipped in production.
Working inside Flexxi long-term shaped how I approach design at scale. Consistency across multiple platforms doesn't happen by accident — it requires systems thinking, direct collaboration with developers, and the discipline to build patterns that hold up across years of product evolution. Being embedded in an early-stage team meant owning the design process end-to-end, from early product strategy through to shipped, production-ready interfaces.
Available for senior design roles, long-term product partnerships, and freelance engagements.