MAAT
From expert knowledge to a scalable, user-friendly product
Context
Context
Context
Context
CLIENT
MAAT: Combat Sport Management app for gyms. Mid-stage startup preparing for new app launch
BUSINESS CONTEXT
Early-stage startup.
Existing product already visually designed by a freelance graphic designer. Public launch imminent
Early-stage startup.
Existing product already visually designed by a freelance graphic designer. Public launch imminent
ROLE
Intervene on high-risk UX flows pre-launch. Worked directly with founders and developers.
TIMELINE
Year: 2025
One-month engagement (Nov–Dec)
Year: 2025
One-month engagement (Nov–Dec)
Problem Statement
Problem Statement
Problem Statement
PROBLEM:
The app had strong visual appeal but lacked UX basis in conversion-critical and progression flows.
Contraints: The product looked ready, but key flows weren’t yet reliable enough for real users at launch.
GOAL:
Identify and refine key flows and improve overall progression flows (class reservation, checkout, personal statistics)
The wireframes at the start of the process
Approach
Approach
Approach
Approach
Audited existing designs through a UX risk lens:
Audited existing designs through a UX risk lens:
Identified flows where experience needed to be improved: checkout, motivation & retention (belt tracking)
Systems before screens
Scalability over short-term speed
Identified flows where experience needed to be improved: checkout, motivation & retention (belt tracking)
Chose surgical interventions over broad redesigns due to time constraints
Chose surgical interventions over broad redesigns due to time constraints
Designed and improved existing visual language to avoid disruption before launch
Designed and improved existing visual language to avoid disruption before launch
Exectution
Exectution
Exectution
Exectution
Established the foundation
→ Clear payment summary
→ Visible promo code entry
→ Reduced modal stacking
Exectution
Exectution
Created the stats page
→ Improve users motivation and progress
→ Clear progression logic
→ Stronger status visibility
Exectution
Exectution
Exectution
Created the stats page
→ Improve users motivation and progress
→ Clear progression logic
→ Stronger status visibility
Outcome & Learnings
Outcome & Learnings
Outcome & Learnings
Outcome & Learnings
learnings
In pre-launch phases, UX impact is about removing risk, not adding features
Short engagements demand ruthless prioritization
Knowing what not to redesign is as important as knowing what to improve
Fit matters: I do my best work where UX/UI is valued as a discipline, not a catch-all role
outcomes
App launched with improved UX in the most critical flows
Checkout and progression shipped using my designs
learnings
In pre-launch phases, UX impact is about removing risk, not adding features
Short engagements demand ruthless prioritization
Knowing what not to redesign is as important as knowing what to improve
Fit matters: I do my best work where UX/UI is valued as a discipline, not a catch-all role
outcomes
App launched with improved UX in the most critical flows
Checkout and progression shipped using my designs
Problem Statement
Problem Statement
PROBLEM:
The app had strong visual appeal but lacked UX basis in conversion-critical and progression flows.
Contraints: The product looked ready, but key flows weren’t yet reliable enough for real users at launch.
GOAL:
Identify and refine key flows and improve overall progression flows (class reservation, checkout, personal statistics)
The wireframes at the start of the process