Claim My Flight helps air passengers receive compensation for delayed, cancelled, or disrupted flights under EU Regulation EC 261/2004. The client had independently developed and launched an MVP, but early testing revealed a serious problem: users were dropping out of the claim form before completing it. The process felt bureaucratic and stressful, the UI logic was confusing, and too many people couldn’t get through the six-step form without abandoning it entirely. The client brought me in to diagnose the issues, restructure the experience from the ground up, and lead a small cross-functional team to deliver a complete redesign — from the landing page to the personal claim dashboard.
- Market & audience research: analysis of the EU flight compensation sector, user behavior patterns, and the emotional context of the claim process (stress, distrust, confusion about legal procedures).
- Competitive audit: review of 3 key competitors in the European flight claims market (identifying UX gaps, trust signals, and form design patterns).
- User research: written blitz surveys with 25 participants and in-depth interviews with 10 real users to identify drop-off reasons, anxiety triggers, and expectations from the claim process.
- UX architecture: complete restructuring of the claim form — from 6 steps to 4, with a logical grouping of questions and adaptive branching based on user input.
- Illustration system: development of narrative scenarios and storylines for a custom illustration series, executed by a dedicated illustrator to communicate a human, approachable tone throughout the product.
- Project management: coordination of a small team (illustrator, advertising specialist, HTML developer).
The MVP had a real product and real demand, but the experience was losing users at the most critical moment: the claim form itself. The original six-step flow was structured around the client’s internal assumptions about what information was needed and when, rather than how users actually think and feel when they’ve just had a stressful flight disruption. People arrived confused, anxious, and unfamiliar with their legal rights, and the interface did nothing to address that.
My task was to understand exactly where and why people were dropping off, then restructure the entire claim flow around user psychology: reducing cognitive load, building trust at every step, and making a complex legal procedure feel manageable. The goal wasn’t just a cleaner UI: it was a product that converts hesitation into completed claims.
- Reduce form drop-off by eliminating unnecessary steps and restructuring question logic.
- Build trust at every stage: the user should always feel safe, informed, and in control.
- Design a visual language that is professional yet human (avoiding the cold, bureaucratic aesthetic typical of legal services).
- Create an adaptive experience that works consistently across all screen sizes.
- Establish a component system ready for future language and market expansion.
Filing a compensation claim after a disrupted flight is already a stressful experience. The design challenge here wasn’t just simplifying a form, it was rebuilding trust at every step of a process that users approach with anxiety, skepticism, and very little knowledge of their legal rights. The highlights below reflect the key decisions that turned a high-dropout MVP into a structured, human-centered claim flow.
- All design layouts are created for desktop, tablet and mobile, with consistent handling of breakpoints, content reflow, and touch targets across all screen sizes.
- The necessary active states are defined and visualized across all interactive elements: form inputs, validation errors, hover states, dropdowns, step progress, upload areas, and empty states.
- A custom illustration system was developed with defined narrative scenarios — all characters and scenes were drawn by hand, not generated, ensuring visual consistency and brand ownership.
- HTML templates were prepared and handed off to the development team with full component documentation, interaction notes, and layout specifications for all three breakpoints.
- The project’s working files are structured and organized in Figma (components, auto-layouts, variants, and a shared UI kit) and fully prepared for developer collaboration and future language/market expansion.
Working with Alex was a turning point for us. Before we brought him in, our initial MVP had too many issues: frequent errors, confusing steps, and a lot of users dropping off before finishing the application. Alex quickly got to the root of the key problems and fixed them in a structured, product-minded way. He simplified the flow, improved the logic, and made the whole process feel clear and trustworthy. What impressed us most is that he didn’t stop at “just fixing”. He also spotted additional gaps we hadn’t noticed and предложил improvements that made the product more user-friendly and genuinely customer-oriented.