Vívela
Head of Experience & Product Design, Growth Coach
Led the brand's Design System from the ground up, and the migration, redesign and growth of its core product for mortgage credit acquisition — owning KPIs, stakeholders, product/marketing backlog and roadmap.
I led the Design team and partnered with development to build the Design System end to end: strategy, component library, usability validation and documentation for adoption.
Vívela operated with isolated, inconsistent digital platforms — different design patterns, visual components and interaction behavior across products — which hurt the user experience and made maintenance and scalability harder.
An audit of the existing platforms surfaced real inconsistency across design patterns and components, and analysis of conversion and retention metrics showed how much that inconsistency was costing the user experience and the business.
The rollout had to happen in phases across live products without disrupting the business, while still keeping scalability, accessibility and development efficiency as core requirements.
Development happened in three phases: building a modular, accessible component library; validating it through usability testing and A/B experimentation; and documenting it in detail so designers and developers could adopt it consistently.
Prioritized a phased, disruption-free rollout over a full relaunch, and treated documentation and adoption as first-class deliverables rather than an afterthought to the component library itself.
A scalable, accessible Design System integrated into Vívela's digital products with a growth-oriented lens: redesigned conversion flows, reusable standardized components, and dashboards to track impact and adjust based on data.
Higher conversion from a redesigned user journey and visual interface, less development time and operational cost from reusing standardized components, and more consistency and scalability across Vívela's digital products.
A Design System pays off fastest when documentation and adoption are designed as deliberately as the components themselves — a well-built library that nobody adopts consistently doesn't solve the original inconsistency problem.
