Project Background

As the sole UI/UX designer, I collaborated directly with business stakeholders to understand their goals, existing workflows, and technical requirements. Starting with user research, this project was requirement-driven; the client had already gathered input from their internal research and provided clear pain points and feature requests.

Given the MVP timeline and pre-existing internal research, I reframed my role from discovery to synthesis and translation. I led stakeholder interviews and discovery meetings focused on:

1. The organization’s existing workflows and pain points
2. Defining key user roles (athlete, coach/faculty, staff) and their responsibilities
3. Feature prioritization to determine which features would form the MVP and how they should work together

‍

Design Process

Given the project’s fast-paced and collaborative nature, I adopted an Agile UX approach to design the MVP. This method allowed me to work iteratively, be flexible to stakeholder feedback, and continuously refine the platform as requirements and needs evolved.

My Agile UX process followed these key steps:

1. Requirement Discovery: Worked closely with stakeholders to clarify MVP goals, define user roles, and prioritize core features for each sprint.
   
   
2. Rapid Prototyping: Translated requirements into user flows and low-fidelity wireframes to visualize ideas early and gather quick feedback.
   
   
3. Iterative Design Reviews: Presented progress to stakeholders regularly for input and refinement before moving to high-fidelity design.
   
   
4. Developer Collaboration: Delivered design components with clear specifications, collaborating on implementation adjustments to maintain consistency and feasibility.
   
   

‍

Competitive Analysis

‍

Since this was an MVP project focused on launching quickly and validating the platform concept, the research phase was centered around business interviews and requirement analysis rather than direct user testing. I collaborated with the founding team and technical stakeholders to understand the platform’s goals, constraints, and success criteria.

The objective of this phase was to translate strategic business insights into actionable design directions — ensuring that the MVP addressed both organizational needs and end-user workflows for athletes, coaches, and staff.

Challenge Statement:

The client, Complete Sports Co., identified a major gap in how athletic organizations manage operations and communication. Many teams used multiple tools for scheduling, nutrition tracking, mental health check-ins, and progress monitoring — creating inefficiencies and limited visibility across staff and athletes.

‍

Stakeholder Insight Map

To synthesize insights from the business interviews, I created a stakeholder insight map to capture key goals, pain points, and design implications. This helped ensure every design decision remained aligned with stakeholder priorities and technical feasibility.

‍

‍

Ideation:

HMW Questions

To bridge business goals with user-centered thinking, I synthesized stakeholder feedback into a series of How Might We (HMW) questions. This helped reframe the requirements as design opportunities and guide my ideation phase.

Documentation:

Business Requirements

Based on the synthesized insights, I translated business goals into formal requirements to guide the MVP design and development. This structure ensured alignment between business objectives, UX priorities, and technical implementation.

‍

‍

Website Ideation:

For the website ideation phase, I created a sitemap to shows page hierarchy and content organization and a task flow to show a simple key conversion path for website CTA. This visually showed me what screens I would need to design and got me thinking about how the user would navigate between them.

Sitemap

Task Flow

‍

Platform Ideation:

For the platform ideation phase, I created a user flow to show different

User Flow

‍

‍
Visual map of the steps an athlete or coach takes to complete a key task — e.g.,
Athlete logs in → views today’s schedule → completes task → logs progress → receives coach feedback.

You can have one per role (Athlete Flow, Coach Flow) or one combined flow showing conditional paths.

Website Wireframes

I translated the sitemap and task flows into low- and mid-fidelity wireframes to determine layout structure, content hierarchy, and navigation patterns for the website. These wireframes helped validate the placement of key elements like hero messaging, feature previews, CTA buttons, and the separation between Professional and Collegiate offerings before visual design work began.

‍

Platform Wireframes

For the athlete-facing platform, I created wireframes outlining core screens such as the dashboard, daily schedule, tasks, and wellness modules. Because the platform needed to scale for future features, I focused on designing clean, modular layouts that could easily adapt to new components and data types. These wireframes helped stakeholders visualize how the athlete workflow would function end-to-end.

‍

Website Mockups

Using the approved wireframes, I created high-fidelity mockups that applied the brand’s visual direction, color palette, and component system.
I purposely designed the landing page to be simple, straightforward, and informative for prospective clients.
To support deeper exploration, I included multiple CTA buttons and created interactive on-click feature pages that provided more detailed descriptions of the product’s capabilities.

Wanted to keep the landing page simple, straight forward and infromative for interested clients. Emphasis on onboarding/contact so added lots of cta and on-click pages to show more info about features

Platform Mockups

The platform mockups expanded the athlete screens into a refined UI using the updated color system, typography, spacing, and reusable components. My priority was developing a clear, easy-to-scan visual language so athletes could quickly understand their daily tasks, progress, and feedback. These mockups also aligned with the existing coach/staff modules to ensure cross-role consistency.

Design System

To bridge business goals with user-centered thinking, I synthesized stakeholder feedback into a series of How Might We (HMW) questions. This helped reframe the requirements as design opportunities and guide my ideation phase.

Testing

Based on the synthesized insights, I translated business goals into formal requirements to guide the MVP design and development. This structure ensured alignment between business objectives, UX priorities, and technical implementation.

Final Prototype

To synthesize insights from the business interviews, I created a stakeholder insight map to capture key goals, pain points, and design implications. This helped ensure every design decision remained aligned with stakeholder priorities and technical feasibility

‍

Business Impact

To bridge business goals with user-centered thinking, I synthesized stakeholder feedback into a series of How Might We (HMW) questions. This helped reframe the requirements as design opportunities and guide my ideation phase.

Design Impact

Based on the synthesized insights, I translated business goals into formal requirements to guide the MVP design and development. This structure ensured alignment between business objectives, UX priorities, and technical implementation.

Reflection

This project marked my first experience leading end-to-end UX design to full developer handoff, a shift from my previous roles of designing and building independently to team collaboration. While this introduced challenges, my experience as a Business Analyst and Scrum Master significantly shaped how I approached the work. Instead of seeing requirements as limitations, I used them to my advantage to inform structure, clarity, and feature prioritization.

Throughout this design process, evolving requirements, working within tight deadlines, and limited access to end-users forced me to reconsider what constitutes a “good design” in an MVP context. One of the most challenging lessons I faced was learning when to stop designing. I learned to prioritize functionality and educational value over visual perfection for Complete.

This project reshaped my perspective on early-stage product design. I now view MVPs not as incomplete products, but as deliberate frameworks that guide behavior, learning, and future iteration.