Ficohsa Seguros — Mobile App for Health Insurance Management
My involvement was crucial to the MVP development process, as the UX/UI design solution provided a clear roadmap for the various teams. The prototype provided clarity for both the sales team and the product engineers.
Situation
Ficohsa Seguros, one of Honduras’s leading insurance providers, needed a native mobile app to give policyholders self-service access to their health insurance — claims, pre-authorizations, payments, provider network, and 24/7 medical support — all in one place.
The brief arrived with strong technical requirements (JWT auth, Face ID, fingerprint, 5-minute session timeout) and a long feature list, but with significant ambiguity around the actual user experience: what does each screen need to show, what tasks should users complete, and what information matters most at each step?
The scope was ambitious for a 10-day timeline:
- 6 modules covering claims, payments, provider network, profile, forms, and 24/7 support
- ~40 distinct functionalities
- Both individual and corporate policyholders as user types
- An atomic design system to support future development
Task
As the sole UX/UI designer, my job was to:
- Resolve the ambiguity in the brief — turn a feature list into a clear product
- Define the information architecture, user flows, and protopersonas
- Deliver high-fidelity mockups and an interactive prototype
- Build a complete atomic design system that engineering could hand-off cleanly
All within a 10-day window with a single client review session.
Action
1. Surfaced the unknowns before designing anything. Instead of jumping into screens, I audited the brief and produced a structured list of open questions for each module — what “SHM1” meant, how policies and certificates relate, what info goes on a carnet, how Ficolinks are generated, what data each provider listing should show. This document drove the client conversation and unblocked the design phase.
2. Built protopersonas to anchor decisions. Defined the primary users (individual policyholders and corporate beneficiaries) with their goals, tech comfort levels, and the moments where they’d actually open the app — usually under stress (a medical emergency, a pending claim, a payment due). This shaped which actions needed to be one tap away vs. buried.
3. Designed the navigation map and user flows in FigJam. Mapped 6 primary sections to a bottom nav + hamburger pattern, with the 24/7 medical hotline as a persistent, high-visibility CTA — because in an insurance app, the most important moment is when something goes wrong. Flows were drawn for the 8 most critical paths (login with biometrics, file a claim, request pre-authorization, pay a pending invoice, find a provider, etc.).
4. Built high-fidelity mockups in Figma. Designed the full app across the 6 modules, with native patterns for iOS (Face ID) and Android (fingerprint), session-timeout handling, and forms tuned for the claim and pre-authorization flows — the two most complex tasks in the app.
5. Built an atomic design system. Tokens, typography, color, primary/secondary/tertiary buttons, cards, form fields, search components, filters, progress indicators, notifications, dropdowns, tables, and iconography — all componentized so engineering could implement without re-deciding visual details.
Result
- Shipped to production. The full scope was delivered within the 10-day timeline and the app was launched to Ficohsa Seguros policyholders in Honduras.
- 40+ functionalities designed and documented across 6 modules, with the atomic design system covering every component engineering needed.
- Single review cycle. Because the open-questions document resolved ambiguity upfront, the project moved through one consolidated client correction session instead of multiple revision rounds.
- Positive client feedback throughout the process on the structure, clarity, and completeness of the deliverables — particularly the design system, which became the foundation for ongoing iteration after launch.
Key takeaway
The most valuable thing I did on this project wasn’t a screen — it was the question list at the start. In B2B and Fintech, briefs are almost always under-specified, and senior UX work is as much about making the unknowns visible as it is about designing the visible layer. That’s what made it possible to ship 40 features in 10 days without compromising the system.
Deliverables
- Protopersonas
- Sitemap
- User flows
- Atomic Design System
- Wireframes
- Components
- Hi Fidelity Prototype
