Regulated Fintech Environment
Overview
This case is anonymized due to confidentiality agreements.
Context
Large-scale public financial institution
Role
Product Designer | Consultant
Product
Digital loan application journeys
Metodology
Agile Scrum | Sprints & Co-creation
Plataforms
Native App → WebView → SuperApp
Teams
Product Managers, Engineers, Business Stakeholders, Design System Team
Duration
Ongoing [iterative product evolution]
Tools
Figma, Docs and paper
The loan application experience served a broad Brazilian audience and operated under strict regulatory, accessibility, and business constraints. The product ecosystem was highly complex, covering multiple loan categories, each with distinct business rules, post-sales steps, and portability flows.
Discovery insights had already been generated by a dedicated research team. The main challenge during the design phase was translating those insights into scalable, accessible, and technically feasible solutions, while aligning with existing business rules, platform constraints, and the company’s design system. Throughout the project, strategic shifts required the solution to be continuously adapted:
An initial native app experience with high platform-specific complexity;
A transition to a WebView-based delivery model due to technical and strategic changes;
A later redesign for a new native app, leveraging standardized templates to accelerate delivery.
Design decisions needed to balance robustness, accessibility, speed, and long-term scalability across all these stages.
I led the design and prototyping of end-to-end loan application journeys, working closely with engineering and business teams to translate discovery insights into implementable solutions. My responsibilities included:
Designing and adapting complex loan flows under strict regulatory and accessibility requirements;
Applying and evolving design system components across multiple platforms;
Defining and validating detailed accessibility handoff documentation;
Supporting delivery through close collaboration with engineering and business stakeholders;
Adapting solutions to significant changes in product strategy and technology.
First scenario
Designing for platform-specific robustness at Native App
The first iteration of the product focused on a native app experience with high fidelity and platform-specific considerations. Separate interfaces were designed for Android and iOS, respecting each platform’s interaction patterns and accessibility behaviors.
A critical part of this phase was ensuring accessibility compliance at a granular level. Each screen and component was documented in detail, including:
Accessibility behaviors;
Content hierarchy;
Screen reader expectations.
These specifications were reviewed screen by screen with the engineering team. Once implemented, developers validated the flows using screen readers to ensure alignment with the documented guidance.
This approach prioritized robustness and inclusivity, ensuring that accessibility was not treated as an afterthought but as a core design requirement.
Second scenario
Adapting complex journeys to a webview model
Due to changes in product and technical strategy, the native app delivery was canceled, and the solution needed to be adapted to a WebView-based experience.
This transition required revisiting all loan journeys, including full contracting, post-sales, and portability flows, across multiple loan categories. Design decisions focused on:
Simplifying interaction patterns to fit WebView constraints;
Preserving clarity and usability despite reduced platform flexibility;
Revalidating critical steps to reduce cognitive load and user uncertainty.
New handoff documentation was created to reflect these changes, and close alignment with engineering and business teams ensured that all adaptations respected technical feasibility and regulatory rules.
This phase reinforced the importance of adaptability in large-scale products and demonstrated how validated design logic could be preserved even when delivery strategies change.
Third scenario
Accelerating delivery through design system templates to SuperApp
In the most recent phase, the product evolved again with the development of a new native app. This iteration adopted a market-standard approach: the use of predefined templates provided by the internal design system team.
Instead of redesigning flows from scratch, previously developed journeys were mapped onto the template structure. This shift enabled:
Faster construction and development of interfaces;
Greater consistency across the broader application ecosystem;
Reduced design and development effort for recurring patterns.
As a result, journey construction and development became approximately 90% faster, allowing the team to focus on content, rules, and critical decision points rather than structural UI concerns.
This approach also improved alignment with the overall app experience, recognizing that the loan journey represented a small but critical part of a much larger product ecosystem.
The final solution structured loan application journeys into clear and predictable steps, including eligibility validation, data input, confirmation, contracting, post-sales, and portability flows. Rather than emphasizing visual customization, the design focused on:
Clarity at decision-making moments;
Consistent application of design system patterns;
Accessibility and inclusive access;
Reusability across platforms and future iterations.
Diagrams, flows, and abstracted wireframes were used to validate logic and ensure alignment, without relying on sensitive or proprietary visual assets.
Improved alignment between design, business, and engineering teams across multiple delivery phases;
Reduced friction during design reviews and accelerated approval cycles;
Ensured accessibility compliance across all developed journeys;
Enabled faster delivery through reusable templates and validated patterns;
Reduced risk during major product strategy changes by leveraging existing design logic.
