Design Thinking Blueprint: Beginner Fitness App Project type: User-centered mobile product prototype · Timeline: 4 weeks · Budget: Limited · Framework: Empathize → Define → Ideate → Select → Prototype → Test → Iterate ## Executive summary The proposed solution is a beginner-friendly fitness app called StartSmall — a working concept designed to help people build a consistent exercise habit without feeling overwhelmed by complicated workout plans, demanding schedules, or pressure to achieve rapid results. The central design principle is simple: make starting easy, adapting normal, and progress visible. [Workout Tracker. Daily UI: 041 by Alina Neklesa on Dribbble](https://images.openai.com/static-rsc-4/pWs8NH95fZBYx9flGJfCEgLcC2VEkyi4AQJkLZ_hsraJv1o6RVhJnmc2M970AsWkDcWsOjey5_EskBqp1n3fxpHgNE9gXIaYqJ2PaCcuNWYNMfzDSXbox6cTb3d5ze5w88N161PX2CNQ7Z9ctZlr3fZDBxAXHqldgfhx1hKuZfU?purpose=inline) [Humanitools — Mobile App Development & Digital Tools for Real-Life Impact](https://images.openai.com/static-rsc-4/URzt5IOPq9mFxkkjfROQT_oTuTudb3DFHsp_JinWPKXYssCwPwFK-ZRtzZn6DeLuCN_fn6b1FxZlLjGmRMJTnAF-iuh2V04jGPzMAxkm3YxdEpjRPZjGtrODTS2hEAIWLOLv6-t1ltKkrVfD1wsTdUWrOGG2IGPcW_ry-8yHsJc?purpose=inline) [Movyn – Your AI Home Trainer](https://images.openai.com/static-rsc-4/lFJoJDuBjjBVOsHxOR8O7Nvl06HWetfU-vkuTfQC7nOKktVKxp7d0uaxu3QpVhgGqqmhiKnyHTfuueBUALA785y74Kq9LdxnrtMUJhSauBl19owo-A59b8dJMnaDeYuu7jJEUGRUIPzRPRAvlSp4opEocyg9o65pCqUrIX3NPCk?purpose=inline) 13 The project should not begin by building a fully featured fitness platform. With a four-week timeline and limited resources, the better approach is to create a clickable prototype, test it with beginners, and use their feedback to decide what deserves development. ## Project at a glance Primary objective Help beginners complete short, realistic workouts consistently. Primary users People new to exercise or returning after a long break who struggle with motivation, time, and planning. Prototype deliverable A clickable mobile experience covering onboarding, personalized workout selection, workout completion, and progress tracking. Four-week outcome A tested prototype, prioritized usability improvements, and a clear decision about whether to proceed to a functional MVP. ### Working assumptions Because no direct user research, budget figure, platform preference, or technical specification has been supplied, this blueprint distinguishes the project's known constraints from hypotheses that need validation. - Known: The intended audience is beginners; consistency, motivation, planning, and progress are the central concerns. - Known: Development resources are limited, and the prototype must be completed within four weeks using standard mobile design tools. - Assumed for planning: The first prototype targets smartphone users, prioritizes home workouts, and avoids requiring gym equipment. - Assumed for planning: The prototype is a simulation rather than a production-ready app with live accounts, wearable integrations, or backend services. - To clarify: Whether the audience includes users with mobility limitations, chronic health conditions, or other accessibility needs; whether the product is Android-first, iOS-first, or cross-platform; and whether the budget includes development after the prototype. These assumptions should guide initial design choices, not be treated as verified user preferences. # Step 1. Empathize and understand users ## 1.1 Understand the target audience Beginners are not one uniform group. Someone who has never exercised, someone returning after a break, and someone with an unpredictable work schedule may need different kinds of support. The following table identifies plausible user needs to investigate, rather than claiming that research has already confirmed them. | Research area | Questions to investigate | Initial hypothesis | | ------------- | ------------------------------------------ | ---------------------------------------------------------------------------- | | Goals | Why do users want to exercise? | They may prioritize energy, health, confidence, or weight management. | | Behaviors | When and where can they exercise? | Available time and routines may vary considerably by day. | | Frustrations | What stops them from following plans? | Plans may feel too demanding or difficult to resume after a missed day. | | Motivation | What encourages them to return? | Small wins, visible progress, and manageable goals may help. | | Planning | How do they select workouts? | Too many options may create decision fatigue. | | Expectations | What makes an app feel approachable? | Clear instructions, low setup effort, and nonjudgmental language may matter. | | Unmet needs | What do current solutions fail to provide? | Users may need plans that adapt to changing time and energy levels. | ## 1.2 Develop provisional user personas These personas are research hypotheses, not actual interview participants. They help the team consider different situations and should be revised after real interviews. [Portrait of a young Indian professional woman at work in her office](https://images.openai.com/static-rsc-4/dBRfXZnB5iI7LIuUuPC_BNeos1ziXVR-qAGYT6HjUBCw7IixfYXSofMYrhng71g7kNTlfST5rZeaV_nEYwY7a9puYTk0xPc9h4VIp7edNex2j8gyGnlt7hDs6a1Jd1xkFLCJGIZPA-SQz2n2t0d-vRSTKqcECwzx8SwpJbZ5bxl0yoADxzLurg7pP4klxdLM?purpose=inline) ### Persona A: The Busy Beginner Illustrative age: 27 · Office professional Goal: Exercise regularly without disrupting work or personal commitments. Possible frustrations: Long workout plans, decision-making after a tiring day, and difficulty maintaining a fixed schedule. Design opportunity: Short workouts, flexible scheduling, and a quick-start action. Hypothesis to test: A realistic 5–15-minute option will feel more achievable than a rigid 45-minute plan. [Pin on Fondos de pantalla](https://images.openai.com/static-rsc-4/YbPkRZeFvqMjflUw7U4ypDJTnBS45EGwr03K_XloyiDl3m2_Gp63lHyVz7yUWOGoUVm15XXsFlb8_lcVWkEYppdI3sGEO0iC0J8RkfnEx0z7-AfDKc9g7dFPz7aMAdPgCcKSJfqjJFqEctA9p2AoJlL8azYJi6SVqJ9A_MhwvZE?purpose=inline) ### Persona B: The Uncertain Student Illustrative age: 20 · Student Goal: Build fitness with little equipment and a limited budget. Possible frustrations: Not knowing which exercises to do, worrying about technique, and losing interest in repetitive routines. Design opportunity: Guided beginner exercises, simple demonstrations, and clear session lengths. Hypothesis to test: Step-by-step guidance will reduce uncertainty enough to encourage workout completion. [Chubby woman holding yoga mat and surfing the new via smart phone](https://images.openai.com/static-rsc-4/xLMhlFNPEMXfabF1ylmtqVIQUPTO_-KZ0kh6ilhGK4kz9Rt6He8F12Q3Q_RqZPHbE6P77g__aGabL9mhhtrcX3Uh_xh6Xh5t5swwpvwDhrzAf7tyt9_47o9brRx2C39560oKKAURz-Ono3HpHdap8XASulfuFDjr02pO05_upBbdeZML2P66PjtUR9bnSD4Q?purpose=inline) ### Persona C: The Restarting Exerciser Illustrative age: 35 · Returning after a long break Goal: Restart gently and establish a sustainable routine. Possible frustrations: Comparing current ability with past performance, soreness, and feeling discouraged after missed sessions. Design opportunity: Gradual progression, adaptable difficulty, rest days, and encouraging restart flows. Hypothesis to test: Nonjudgmental recovery after a missed workout will make it easier to resume. ## 1.3 Research methods A small, focused research phase is appropriate for this budget and timeline. | Method | Suggested scope | Purpose | | ---------------------------- | ------------------------------------------ | -------------------------------------------------------------------------- | | Semi-structured interviews | 6–8 beginners | Understand motivation, routines, barriers, and emotional responses. | | Current-behavior diary | 3–5 participants for 5–7 days, if feasible | Record actual exercise opportunities, missed plans, and schedule changes. | | Competitor review | 3–5 fitness apps | Identify common interaction patterns and opportunities for simplification. | | Lightweight survey | 15–30 responses, if recruitment allows | Explore how common identified preferences may be in a broader sample. | | Task-based usability testing | 5–8 representative users | Evaluate whether the prototype is understandable and usable. | These sample sizes are practical exploratory targets, not statistically representative samples. If recruitment is difficult, prioritize interviews and task-based testing over a large survey. ### Interview questions Use open-ended questions and ask participants to recall real experiences rather than asking whether they like a proposed feature. 1. Tell me about the last time you tried to start or restart exercising. 2. What motivated you to begin? 3. Walk me through what happened during your first few workout attempts. 4. What usually prevents you from exercising when you intended to? 5. How do you decide which workout to do? 6. How much time can you realistically set aside on a typical day? What about a busy day? 7. Have you ever stopped using a fitness app or abandoned a workout plan? What happened? 8. How do you feel when you miss a planned workout? 9. What helps you feel confident that you are performing an exercise correctly? 10. How do you currently track progress, if at all? 11. What kinds of reminders feel useful, and what kinds feel intrusive? 12. If a fitness app could solve one frustrating part of your routine, what would you choose? Research technique: Ask follow-up questions such as “Can you give me an example?” and “What did you do next?” Avoid leading questions like “Would you use an app with daily reminders?” because hypothetical enthusiasm does not reliably predict actual behavior. ## 1.4 Research outputs At the end of this step, produce: - Interview notes with personal identifiers removed. - A list of observed behaviors and direct user statements. - An evidence-versus-assumption log. - An affinity map grouping similar pain points. - A draft journey map showing what happens before, during, and after a planned workout. The goal is to discover why consistency breaks down before deciding how the app should solve it. # Step 2. Define the core problem ## 2.1 Map pain points to underlying causes The key design challenge is not simply providing workouts. It is helping beginners translate good intentions into repeatable behavior. | Potential pain point | Possible underlying cause | Opportunity area | | ------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------ | | “I don't have enough time.” | Plans do not accommodate changing schedules. | Offer short and adjustable sessions. | | “I don't know where to start.” | Exercise selection feels complicated. | Provide one clear recommended workout. | | “I lose motivation.” | Rewards may feel distant or progress may be invisible. | Make small achievements visible. | | “I missed a day, so I stopped.” | The experience may frame missed sessions as failure. | Design a supportive restart flow. | | “I'm not sure I'm doing it right.” | Instructions or exercise demonstrations may be unclear. | Use simple demonstrations and beginner-friendly cues. | | “The plan feels too difficult.” | Initial intensity may exceed the user's ability. | Allow gradual progression and session adjustments. | | “Notifications annoy me.” | Reminders may arrive at inconvenient times or too frequently. | Give users control over reminder timing and frequency. | | “I don't know whether I'm improving.” | Tracking may emphasize numbers without meaningful context. | Show completed sessions and consistency trends. | These are candidate explanations to validate. A missed workout, for example, could be caused by time constraints, pain, illness, caregiving responsibilities, or a change in priorities. The design should not assume that every missed session reflects a motivation problem. ## 2.2 Problem statement ## Core problem statement Beginners who want to exercise regularly need a simple, flexible way to choose and complete appropriate workouts because rigid schedules, uncertainty about exercise selection, and discouraging progress experiences may make it difficult to establish a sustainable routine. ## 2.3 How Might We question How might we help fitness beginners fit manageable workouts into everyday life, feel confident while exercising, and return after interruptions without guilt or unnecessary complexity? This question deliberately avoids prescribing a particular feature. It leaves room for app-based, behavioral, and service-oriented solutions. ## 2.4 Establish measurable success criteria The following are proposed targets for prototype evaluation, not current performance or guaranteed outcomes. | Metric | Proposed target | Why it matters | | ----------------------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------- | | Onboarding completion | At least 85% | Users can set up a usable starting plan. | | Workout discovery | At least 90% complete the task without help | The next action is easy to find. | | Workout-start task | At least 85% start the intended simulated workout | The app reduces planning friction. | | Workout completion flow | At least 85% complete the prototype task | The experience communicates what to do next. | | Critical errors | Zero unresolved critical usability or safety issues before MVP release | The core flow is reliable and appropriate. | | Perceived ease of use | Average of at least 4/5 | The app feels manageable to beginners. | | User confidence | Improvement from pre-task to post-task rating | Guidance reduces uncertainty. | | Habit consistency | Establish a baseline and track over 2–4 weeks in a later pilot | The product supports repeat behavior, not just successful demos. | Important distinction: Prototype task completion measures whether people can use the interface. It does not prove that the app will improve real-world exercise consistency. That requires longitudinal testing with actual workouts. # Step 3. Ideate creative solutions Use divergent thinking before selecting a direction. Generate many approaches, examine the problem from different perspectives, and then evaluate concepts against user needs and delivery constraints. ## 3.1 Generate 12 solution ideas The concepts below are intentionally distinct. Each addresses a different potential barrier. 1\. The Five-Minute Start Quick win Offer a short, beginner-friendly workout when the user has little time. - Problem addressed: Time pressure and difficulty getting started. - Benefit: Reduces the commitment required for the first action. - Limitation: Very short sessions may not meet every fitness goal. 2\. The Flexible Weekly Planner Let users choose preferred workout days and adjust a session when plans change. - Problem addressed: Rigid scheduling. - Benefit: Makes the routine fit real life. - Limitation: Too many scheduling controls could complicate onboarding. 3\. One Recommended Workout Present one suitable next workout instead of a large catalog. - Problem addressed: Decision fatigue. - Benefit: Simplifies the daily choice. - Limitation: Recommendations must still allow meaningful user choice. 4\. A Progress Garden Completed sessions grow a virtual plant or garden. - Problem addressed: Progress feels invisible. - Benefit: Creates a visual reward for showing up. - Limitation: Requires illustration assets and may feel childish to some users. 5\. The No-Guilt Restart After a missed session, offer a simple restart option without negative streak messages. - Problem addressed: Discouragement after interruptions. - Benefit: Normalizes restarting and supports user autonomy. - Limitation: Encouragement must not become dismissive of genuine barriers. 6\. The Adaptive Workout Switch Offer options such as “shorter,” “gentler,” or “more challenging.” - Problem addressed: Changing energy, time, and ability. - Benefit: Preserves flexibility without requiring a new plan. - Limitation: Exercise substitutions need careful review for suitability and safety. 7\. Guided Exercise Cards Show one exercise at a time with a simple demonstration, duration, and key form cues. - Problem addressed: Uncertainty about how to exercise. - Benefit: Makes sessions easier to follow. - Limitation: Demonstrations and instructions require content review and accessibility checks. 8\. User-Controlled Reminders Let users choose a reminder window, frequency, and quiet periods. - Problem addressed: Forgetting planned workouts. - Benefit: Supports routines while respecting personal schedules. - Limitation: Notification permissions, implementation, and overuse can become obstacles. 9\. A Supportive Accountability Partner Allow a friend to share a weekly goal or celebrate completed sessions. - Problem addressed: Feeling alone or losing accountability. - Benefit: Adds optional social support. - Limitation: Privacy, invitations, and social features increase scope. 10\. Micro-Challenges Offer achievable milestones such as completing three planned sessions in a week. - Problem addressed: Distant goals feel overwhelming. - Benefit: Makes progress concrete and near-term. - Limitation: Competitive targets may pressure users or encourage overexertion. 11\. Reverse Planning Start with the user's actual available time and work backward to a realistic workout. - Problem addressed: Plans are created around ideal rather than real schedules. - Benefit: Makes constraints the starting point for planning. - Limitation: Users still need a simple way to specify availability. 12\. The Daily Check-In Ask “How much time do you have today?” and optionally “How are you feeling?” - Problem addressed: Plans do not reflect changing circumstances. - Benefit: Makes workout selection responsive to the user's situation. - Limitation: Repeated check-ins may become annoying, and self-reported readiness is not a medical assessment. ## 3.2 Use divergent-thinking exercises Run a short, structured ideation workshop with the product designer, researcher, and developer. - Brainwriting: Each person independently creates ideas before group discussion to reduce anchoring. - Reverse thinking: Ask, “How could we make a beginner abandon the app?” Generate failure patterns such as excessive setup, shame-based reminders, and complicated workout catalogs. Reverse these into design principles. - Constraint-based ideation: Imagine the user has only five minutes, no equipment, or an unpredictable schedule. - Combination thinking: Combine the strongest compatible concepts, such as a recommended workout, an adaptive duration option, and a supportive completion screen. Aim for breadth first, then cluster ideas into themes: reduce friction, adapt to circumstances, improve confidence, and reinforce progress. ## 3.3 Compare the ideas Use a five-point scale. For user value, originality, and alignment, a higher score is better. For feasibility, a higher score means easier to deliver. For implementation effort, a higher score means more effort is required. The scores below are initial expert estimates, not user-research results. Re-score them after interviews and technical review. | Idea | User value | Feasibility | Originality | Effort | Goal alignment | | ---------------------------- | ---------- | ----------- | ----------- | ------ | -------------- | | 1. Five-Minute Start | 5 | 5 | 3 | 1 | 5 | | 2. Flexible Planner | 4 | 4 | 3 | 2 | 5 | | 3. Recommended Workout | 5 | 5 | 3 | 1 | 5 | | 4. Progress Garden | 3 | 4 | 4 | 3 | 3 | | 5. No-Guilt Restart | 5 | 5 | 4 | 1 | 5 | | 6. Adaptive Workout Switch | 5 | 3 | 4 | 3 | 5 | | 7. Guided Exercise Cards | 4 | 4 | 2 | 2 | 4 | | 8. User-Controlled Reminders | 3 | 4 | 2 | 2 | 4 | | 9. Accountability Partner | 3 | 2 | 3 | 5 | 3 | | 10. Micro-Challenges | 3 | 4 | 3 | 2 | 3 | | 11. Reverse Planning | 4 | 4 | 4 | 2 | 5 | | 12. Daily Check-In | 4 | 4 | 3 | 2 | 5 | Implementation effort is a planning estimate for a prototype-level version; production complexity may differ. ### Initial recommendation Prioritize these five concepts: 1. One Recommended Workout — removes the need to browse a large catalog. 2. Five-Minute Start — makes beginning feel manageable. 3. No-Guilt Restart — helps the user return after interruptions. 4. Adaptive Workout Switch — allows the plan to accommodate changing circumstances. 5. Flexible Weekly Planner — helps translate intention into a realistic schedule. Guided exercise cards and basic progress tracking should support these concepts. Social features, advanced gamification, and sophisticated personalization should wait until there is evidence that they address the most important barriers. # Step 4. Select and refine the best concept ## 4.1 Selected concept: StartSmall StartSmall combines the highest-priority ideas into a single experience built around a small, repeatable cycle: 1\. Make a realistic plan Choose available days and a preferred workout duration. 2\. Start a suitable workout See one recommended session with clear instructions. 3\. Celebrate completion Record the session and acknowledge the effort. 4\. Return and adapt Resume after a break and adjust the next session as needed. ## 4.2 Why this concept wins The selected concept addresses three connected problems: deciding what to do, finding time to do it, and maintaining motivation over time. | Evaluation dimension | Design decision | | --------------------- | ----------------------------------------------------------------------------------------------------- | | User value | One clear workout and flexible duration reduce planning friction. | | Feasibility | A clickable prototype can simulate recommendations without AI or a backend. | | Originality | The individual features are familiar; the differentiation is the supportive, beginner-first workflow. | | Implementation effort | Core flows use reusable screens and a small number of states. | | Project alignment | Workout initiation, completion, and progress are central rather than secondary features. | This is a stronger initial direction than an all-in-one fitness platform because it focuses the four-week effort on a single user outcome. ## 4.3 Core feature scope Must have — prototype - Brief onboarding and preference selection. - A recommended beginner workout. - A choice of shorter or standard duration. - Guided exercise sequence with a simulated timer. - Pause, resume, and finish interactions. - Completion confirmation. - Weekly activity and session history. - A nonjudgmental restart state. Should have — if time permits - Editable weekly schedule. - Reminder preference controls. - Accessible text sizing and reduced-motion options. - A small library of alternative beginner workouts. Defer beyond the first prototype - AI-generated exercise plans. - Wearable and health-platform integrations. - Social feeds, competitions, and friend networks. - Paid subscriptions, complex analytics, and personalized predictive coaching. ## 4.4 Assumptions to test before development 1. Beginners prefer one recommendation over browsing multiple workouts. 2. A shorter session feels like a useful alternative rather than an inadequate workout. 3. Users understand the proposed instructions and can navigate a session without assistance. 4. A supportive restart message is preferable to a streak-based penalty. 5. Users understand the progress display and find it motivating. 6. The selected schedule controls reflect how users actually plan exercise. These are high-value questions for interviews and prototype tests. Do not invest in advanced features until the core assumptions have evidence behind them. # Step 5. Build the prototype blueprint ## 5.1 Product experience and information architecture The prototype should answer five user questions: - What should I do today? - How long will it take? - How do I perform the exercises? - What happens when I finish? - How can I see my progress or restart after a missed session? Recommended information architecture: Welcome and onboarding Goal · Experience · Available time · Preferred days Home dashboard Today's plan · Start workout · Weekly progress Workout Duration · Instructions · Controls Progress Completed sessions · Weekly summary Completion and return Session recorded · Encouragement · Next recommended action A simple bottom navigation can contain Home, Progress, and Profile. The workout flow should remain focused and should not require users to navigate through several tabs to complete a session. ## 5.2 Screen-by-screen specification [Download Hero](https://images.openai.com/static-rsc-4/oMP9wObI1L_rg2MYppaKlh7XF2qR5-iqaj-fasM4PgnzbP21su0Qqu0jz7xMhW5reCpibbgoqTNsDt8FjRqA67aqcm2K-aCyzHHx-VT5bf1fE9Hg8kxh0LbBQEiaStKu_1wEyMT2TT430gNvvdnsmW0Q3Kz5AQ5FAPaNbMiu-p8?purpose=inline) ### Screen 1 — Welcome and onboarding Purpose: Get users to a usable plan with minimal effort. Components: Welcome message, primary goal, experience level, time preference, available days, optional reminder preferences. Interaction: Users select options and tap “Create my plan.” Design rule: Ask only questions that affect the first workout. Allow users to edit preferences later. [AI to Generate Stunning Designs (UX Pilot) - DEV Community](https://images.openai.com/static-rsc-4/72wmnBy7gdzeMdiqeVb2ylFpbNnSYCJvTyid7yrSzwZg4GdHEwPHcY0kZtW34fZTCvDIDC6DOvWbLny4ztAhkCsdG1MD47Ai8n3D1O9Lr1ZCsbA1V1m0vs5XgEyBagupp_4lj5f6cFck7tVwGcwQpYU4fUqRzlEUs5kvs8OyBq4?purpose=inline) ### Screen 2 — Home dashboard Purpose: Make the next action immediately visible. Components: Friendly greeting, recommended workout card, duration, beginner level, “Start workout” button, “Shorter session” option, compact weekly progress. Interaction: Tap Start or choose a shorter session. Design rule: Avoid a crowded dashboard and unnecessary metrics. [FitMe: Home Workout for Women - ヘルスケア／フィットネスアプリ | MWM](https://images.openai.com/static-rsc-4/9wGAFIbucSuy_WStRzIp2gBPsSTTaK93ufO1PU6JUhm5B1SO5dOJGC_gBPK_4F45mkvXD65BodoOm5zdl7fzsSzfJ1BkMs06Ia1sK6rDv7eAA4roXNAud5P-c9CAapEbg4lPH-e_DaintoqONot6riyJMhpTbt_KLc4OkX2uW9M?purpose=inline) ### Screen 3 — Guided workout Purpose: Help users follow the session confidently. Components: Exercise name, demonstration or illustration, concise instructions, current step, session progress, pause and next buttons. Interaction: Move through exercises, pause, resume, or exit with confirmation. Design rule: Display one exercise at a time, with legible instructions and no distracting charts. [Fitness UI UX | Home Onboarding by Sadax Studio on Dribbble](https://images.openai.com/static-rsc-4/rtFuya54gVJv5CqwL-Is77aGEy6livO5TJOjCJm_RTQhB3D8B6ZIRHIWnhy8aCwk8ELlMnekExzUlG_tUIriw0SM0_oCbq4sGIwbV5qkSXY7v4vyCrOtwnEhTrAprP7oQTXIarUekjYwlEMcdDxpBWK3gbvtnRIp3kJ-88na9p0?purpose=inline) ### Screen 4 — Workout completion Purpose: Reinforce effort and make returning easy. Components: Completion message, session duration, session count, optional reflection prompt, “Back to home” button. Interaction: Finish session and return to the dashboard. Design rule: Celebrate the completed activity without claiming that one session guarantees a health outcome. [TrainOS — Simple Daily Workout App](https://images.openai.com/static-rsc-4/z_kXMygL5uMBdDDZ9PZnAZHfGYkbzVLFXQyWZFgzWGp6zRYWZstUCONswPja5cOqevu8zUuOv8VttDX8dc0kHBLYRYJv5Pmb08wbGDzMWi_GXUyKSKLHH3zoXeY0zCtGlWErox72GYWyC4U4E4jDvpQ51KH8a7trzTCQrU7zLaA?purpose=inline) ### Screen 5 — Progress dashboard Purpose: Make consistency visible without creating pressure. Components: Sessions completed this week, planned versus completed sessions, activity calendar, brief progress summary. Interaction: Switch between the current week and recent history. Design rule: Use understandable metrics; avoid making weight or body measurements mandatory. [Try Explosive Calisthenics for next-level agility and power](https://images.openai.com/static-rsc-4/-C1k_1seVfAd_TDyYqgXedKRGJI44MiIhXyuiBPX1LMgLTnMuGyB1100sZtLKsxEuSQXNxGCD8VELxbJOpsQWvQqaqL_7ll0Nn0_DraOAM0EMFfttV1dpKlMXMyVy_G6Ci2lWdQR3GfCh3rodmDeRNeXLEgK4DIa950PMIj7aGU?purpose=inline) ### Screen 6 — Restart after a missed session Purpose: Help the user continue without guilt. Components: Supportive message, “Resume my routine” action, option to adjust the next workout. Interaction: Return to a manageable session or update the plan. Design rule: Never label users lazy, failed, or undisciplined. ## 5.3 Example first-session journey Illustrative flow; the durations and workout are placeholders to validate. 1. Open the app: The user sees a short welcome message and chooses a fitness goal. 2. Set preferences: The user selects beginner level, available time, and preferred workout days. 3. Review the plan: The dashboard presents a suitable introductory session, for example a 5-minute low-impact routine. 4. Start exercising: The user sees each exercise, simple instructions, and the next-step control. 5. Finish the session: A completion screen records the simulated activity and offers encouragement. 6. Review progress: The user sees the session reflected in the weekly activity summary. 7. Return later: If the user misses a planned day, the app offers a supportive way to restart or adjust the schedule. ## 5.4 Key interactions and edge cases The prototype should demonstrate not only the ideal path but also common interruptions. | Situation | Expected behavior | | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | User skips onboarding | Explain that preferences are needed to personalize the initial plan, while allowing reasonable defaults where possible. | | User chooses less time | Offer a shorter, appropriately designed session rather than simply truncating instructions. | | User pauses a workout | Preserve the current exercise and session state. | | User exits midway | Confirm the exit and distinguish an incomplete session from a completed one. | | User misses a day | Keep the next action clear and supportive; do not automatically treat the missed session as failure. | | User reports pain or discomfort | Provide a clear stop instruction; do not automatically recommend continuing through pain. | | User has no equipment | Show only exercises suitable for the selected equipment preference. | | User uses a screen reader | Provide meaningful labels, logical reading order, and accessible controls in the eventual implementation. | ## 5.5 Recommended prototype fidelity and tools Recommended: a medium-fidelity clickable wireframe, upgraded to a polished interactive mockup for the main flow. A paper sketch is useful for the earliest discussion, but it is insufficient by itself to evaluate navigation, state changes, and workout completion. A fully functional MVP would add unnecessary risk before the design has been validated. [UX Design Case Study - Fitness App Design Research](https://images.openai.com/static-rsc-4/wlqlkUr322CW0TkSEdqGIDbauLgXjDUEADURiaH8EmhjZnjU8DrhvfHAZ5JrTLgksnJo1-uR8o1S_opn1Ax3G4nTTVRuLOks_4TLk1zsN5MhKOdsLV6D_cpopruE13ukbI_JkqJUmnSNqFnOWxCAqRMXFcpUnFNtmLQkHtycVJk?purpose=inline) Figma — primary design tool Create reusable components, wireframes, interactive links, screen variants, and a clickable prototype. Best for a fast, shareable design and testing workflow. [Дизайн продукта: что это, 7 элементов проектирования дизайна](https://images.openai.com/static-rsc-4/Z-dD3r5N0CVipYjDF6zxvXDJnD46Bpwg55dN4-m4uroWHVw2QIN58T7JvkKI7vzWAoN04GBrh8SJt6z3zq4eJ6cEzlkgp2Kh2dDLwdX8ex6nAkOBDaM7fJKKM_X8nV99jF_QzhsqmuPA5OBJFHMGFCBT8vzNSx8ensiizacqmmg?purpose=inline) Paper sketches or a whiteboard Map user journeys and test the basic layout before investing in visual polish. [Get actionable results from your user testing | Thirst Creative](https://images.openai.com/static-rsc-4/1I0r6JtfsbzytXKQ89M8B4rX9y606RuQBNfTYsPYxGyZXOL5HTGGOLphObpfX7NXiufwT4RSIOEDOqj_foaHWGXzwMRU337ZskVz35QiMNEUtsSWDcCspZk_xqYjzDsn14j0RgkWuv_l8U8IoLRshyYSgPAAjAbNTrPKWfvFAyQ?purpose=inline) Screen sharing or device-based testing Observe real interactions, record consented sessions where appropriate, and document usability issues. ### Build sequence 1. Create a small design system: typography, spacing, colors, buttons, cards, form fields, and navigation. 2. Sketch the six primary screens and map the main navigation. 3. Build grayscale wireframes before applying the visual style. 4. Link onboarding to the dashboard and the dashboard to the workout flow. 5. Add states for pause, completion, missed sessions, and progress. 6. Create realistic sample content and make the key screens interactive. 7. Test the prototype on a phone-sized viewport and review accessibility. 8. Prepare the test script and a separate record of known limitations. For the first prototype, simulated workout timers and sample progress data are acceptable if they are clearly treated as demonstration data rather than actual exercise records. # Step 6. Validate and test the prototype ## 6.1 Testing objectives The first usability study should answer five questions: 1. Can a beginner set up a basic plan without help? 2. Can the user identify and start a suitable workout quickly? 3. Can the user understand and navigate the workout instructions? 4. Does the completion flow clearly communicate what happened and what to do next? 5. Can the user find progress information and recover from a missed session? The study should examine usability, comprehension, confidence, and perceived usefulness. It cannot establish long-term behavior change from a single session. ## 6.2 Participant recruitment Recruit approximately 5–8 people who reflect the target audience. Suggested participant characteristics: - New to structured fitness or returning after an extended break. - Has experienced at least one barrier to maintaining an exercise routine. - Uses a smartphone regularly. - Includes a mix of busy professionals, students, and people with changing schedules, where feasible. - Has varied levels of confidence with fitness apps. Recruitment should be based on actual experience rather than assumptions about age, gender, or appearance. Obtain informed consent, protect participant privacy, and avoid pressuring anyone to disclose medical or personal information. ## 6.3 Realistic usability test tasks | Task | Participant prompt | What to observe | | ----------------------------- | ------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | | 1. Set up a plan | “Imagine you are new to exercise and usually have ten minutes available. Set up a plan that suits you.” | Completion, skipped fields, unclear choices, hesitation. | | 2. Start a workout | “Find a suitable workout and begin it.” | Time to start, navigation errors, whether the primary action is obvious. | | 3. Adjust the session | “You now have less time than expected. Show me what you would do.” | Discoverability of the shorter option and understanding of the alternative. | | 4. Navigate the session | “Move through the workout, pause it, and continue.” | Comprehension of controls and state preservation. | | 5. Finish and review | “Complete the simulated session and check whether your progress has changed.” | Clarity of completion and understanding of progress information. | | 6. Recover after a missed day | “Imagine you missed your planned workout yesterday. Show me how you would continue.” | Emotional response, clarity of the restart flow, and perceived judgment. | The facilitator should read each task neutrally, avoid explaining where controls are, and ask participants to think aloud when comfortable. ## 6.4 Measurement framework ## Prototype evaluation dashboard Select a measurement group to review what the research team should record. These are planned measures, not collected results. All measures Task performance User experience Behavior and confidence ### Task performance | Measure | Recording method | Initial target | | -------------------- | ------------------------------------------------ | --------------------------------------------- | | Task completion | Completed independently / attempted | ≥85% for core tasks | | Time on task | Seconds from prompt to completion | Establish baseline; compare across iterations | | Assistance required | Number of facilitator hints | Zero for core tasks where feasible | | Critical errors | Incorrect actions affecting completion or safety | Zero unresolved critical errors | | Navigation confusion | Misclicks, backtracking, repeated attempts | Reduce across iterations | ### User experience | Measure | Recording method | Initial target | | ------------------- | ----------------------------------------------- | ----------------------------- | | Perceived ease | Rating from 1 to 5 | Average ≥4 | | Satisfaction | Rating from 1 to 5 | Average ≥4 | | Instruction clarity | Rating from 1 to 5 | Average ≥4 | | Perceived judgment | Ask whether the app feels blaming or pressuring | No recurring negative pattern | ### Behavior and confidence | Measure | Recording method | Initial target | | --------------------- | ------------------------------------------------------- | ----------------------------------------- | | Workout confidence | Before-and-after rating from 1 to 5 | Positive directional change | | Return intention | Ask whether the user would realistically return and why | Qualitative evidence | | Plan realism | Ask whether the plan fits their actual schedule | Identify and address recurring mismatches | | Restart comprehension | Observe the missed-session task | ≥85% independent completion | These are internal prototype goals. Treat them as directional because small exploratory studies cannot provide precise estimates of the entire target population's behavior. ## 6.5 Feedback questions After the tasks, ask: - What felt easiest about using the app? - Where did you hesitate or feel unsure? - Did any part of the experience feel too demanding? - Was the recommended workout appropriate for your situation? Why or why not? - How did the app respond to a change in your available time? - How did you feel when viewing the missed-session experience? - What information did you expect to see but could not find? - If you could change one thing, what would it be? - What might prevent you from using this app again next week? Ask about specific observed behavior before asking for feature suggestions. ## 6.6 Data collection and analysis Use a simple spreadsheet with one row per participant and task. Recommended columns: `Participant ID | Task | Success | Completion time | Errors | Assistance | Confidence rating | Observation | Severity | Suggested change` Analyze the data in five stages: 1. Summarize task performance: Calculate completion percentages and median completion times. 2. Group observations: Cluster repeated problems, such as unclear labels or difficulty finding the restart action. 3. Separate evidence from interpretation: Record what the participant did before inferring why it happened. 4. Rank usability issues: Prioritize severity, frequency, impact on the main task, and implementation effort. 5. Update the assumption log: Mark each assumption as supported by initial evidence, contradicted, or still uncertain. A single critical safety issue may warrant immediate attention even if it occurs only once. ### Severity scale | Severity | Definition | Response | | -------- | -------------------------------------------------------------------- | ---------------------------------------- | | Critical | Safety concern, misleading exercise guidance, or a blocked core flow | Fix before further testing or release. | | High | Major confusion that prevents task completion | Address in the next iteration. | | Medium | Repeated hesitation or inefficient navigation | Improve when feasible in the next cycle. | | Low | Cosmetic inconsistency or minor preference | Track for later refinement. | Do not report any success percentages or user preferences as observed facts until the relevant testing has actually taken place. # Step 7. Iterate and improve ## 7.1 Plan for possible test findings The following are hypothetical scenarios, not actual test results. They illustrate how the team should respond to different types of evidence. Hypothetical scenario A Participants cannot find the shorter workout option. Possible evidence: Several users scan the dashboard but repeatedly overlook the alternative session. Interpretation: The option may have weak visual hierarchy or an unclear label. Improvement: Place “Shorter session” next to the primary workout action and use explicit duration labels. Retest: Ask new participants to adjust their workout duration without guidance. Hypothetical scenario B Users feel that onboarding asks too many questions. Possible evidence: Participants hesitate during setup or abandon optional fields. Interpretation: The setup process may delay the first meaningful action. Improvement: Reduce required questions, provide sensible defaults, and move optional preferences to the profile. Retest: Compare completion and perceived effort before and after the change. Hypothetical scenario C The progress screen is attractive but confusing. Possible evidence: Users interpret completed sessions as planned sessions or cannot explain the weekly chart. Interpretation: The display may prioritize decoration over comprehension. Improvement: Label completed and planned activity separately, simplify the chart, and include a short summary in plain language. Retest: Ask participants to explain their progress in their own words. Hypothetical scenario D The restart message feels dismissive. Possible evidence: A participant explains that the message ignores a genuine scheduling or health-related barrier. Interpretation: The language may be too generic or may push the user toward an inappropriate workout. Improvement: Offer choices to resume, reschedule, or rest without pressure. Retest: Check whether users understand their options and feel in control. ## 7.2 Prioritize iterations Priority 1 — Safety and core usability Resolve unclear exercise instructions, inaccessible controls, blocked navigation, incorrect completion states, and any interaction that could lead users to exercise inappropriately. Priority 2 — Reduce friction Simplify onboarding, make the primary action obvious, clarify duration choices, and reduce unnecessary steps. Priority 3 — Improve retention support Refine progress explanations, schedule flexibility, and the restart experience based on observed user preferences. Priority 4 — Polish and enhancements Refine illustrations, animations, decorative rewards, and optional customization after core usability issues have been addressed. ## 7.3 Next-version experiment plan For each important change, define a hypothesis, a measure, and a decision rule before implementing it. | Experiment | Hypothesis | Measure | Decision rule | | ----------------------------------- | -------------------------------------------------------- | ---------------------------------------- | ----------------------------------------------------------------------------------- | | Simplified onboarding | Fewer required choices will reduce setup friction. | Completion rate and time | Keep the simpler flow if completion improves without reducing users' understanding. | | More prominent short-session option | Clearer placement will help users adapt to limited time. | Independent task completion | Adopt if users can reliably find and understand the option. | | Simplified progress screen | Clear labels will improve comprehension. | Correct explanation of displayed metrics | Revise until users correctly distinguish planned from completed sessions. | | Alternative restart choices | User control will make recovery easier. | Task success and qualitative feedback | Retain options that improve clarity and do not introduce new confusion. | ### Validate consistency beyond the prototype After the clickable prototype passes usability testing, run a small pilot with a functional MVP for 2–4 weeks. Track: - Planned sessions versus completed sessions. - The percentage of participants who complete at least one session in successive weeks. - Time from a missed planned session to the next completed session. - Voluntary return usage and reasons for disengagement. - Participant-reported confidence and perceived sustainability. Define the measurement rules before starting the pilot. A streak should not be the only success metric: people may exercise inconsistently for valid reasons, and a short study cannot establish long-term health outcomes. # Step 8. Create an actionable implementation roadmap ## 8.1 Four-week delivery plan The roadmap assumes one product designer or UX generalist, part-time researcher or product lead support, and access to a developer for feasibility review. One person may fill multiple roles if resources are especially limited. ## Week 1 Discover Phase 1 — Research and problem definition Activities - Recruit 6–8 participants where feasible. - Conduct interviews and review existing fitness-app patterns. - Map pain points, assumptions, and the initial journey. - Finalize the problem statement and evaluation criteria. Deliverables - Research summary. - Provisional personas and journey map. - Prioritized design principles. - Initial feature scope and risk log. Exit criterion: The team can explain the main user problem and identify what still needs validation. ## Week 2 Design Phase 2 — Ideation and interaction design Activities - Generate and score concepts. - Finalize the StartSmall core flow. - Sketch screen layouts and define navigation. - Create reusable components and initial wireframes. - Review exercise content and accessibility requirements. Deliverables - Concept decision record. - Screen inventory and information architecture. - Low-fidelity wireframes. - Initial clickable prototype. Exit criterion: A participant can navigate the intended main flow in a basic prototype. ## Week 3 Prototype Phase 3 — Build and test Activities - Refine visual hierarchy and interaction states. - Complete the six primary screens. - Add simulated workout progression and progress data. - Conduct 5–8 usability sessions where feasible. - Record observations, task metrics, and issue severity. Deliverables - Medium-fidelity or polished clickable prototype. - Usability test notes. - Prioritized issues list. - Updated assumption log. Exit criterion: The core workflow has been evaluated with representative users and critical issues are identified. ## Week 4 Validate Phase 4 — Iterate and prepare handoff Activities - Fix critical and high-severity usability issues. - Retest the most important changed flows. - Review feasibility with a developer. - Document functional requirements and unresolved questions. - Recommend whether to build an MVP, conduct more research, or revise the concept. Deliverables - Updated prototype. - Retest summary and remaining risks. - MVP scope and acceptance criteria. - Implementation estimate and next-phase plan. Exit criterion: The team has sufficient evidence to make an explicit next-step decision, even if some assumptions remain unresolved. The schedule is achievable if the scope remains narrow and recruitment begins early. If participant recruitment or testing is delayed, preserve the research and validation steps rather than using all four weeks on visual polish. ## 8.2 Required resources and budget control | Resource | Role | Cost-control approach | | ------------------------------ | ----------------------------------------------------- | ---------------------------------------------------------------------------- | | UX/product designer | Research synthesis, interaction design, visual system | Reuse components and keep screen count small. | | Research support | Recruitment, moderation, synthesis | Use short remote sessions and existing recruitment networks. | | Developer | Feasibility review and MVP estimation | Involve them early; do not build backend functionality for a clickable demo. | | Fitness-content reviewer | Review beginner exercise instructions and suitability | Use a small, carefully reviewed exercise library. | | Design and collaboration tools | Wireframing, prototype, feedback | Start with existing or free-tier tools, subject to current limits. | | Test devices | Check mobile layouts and interactions | Use available devices and a responsive prototype. | No exact monetary budget can be responsibly estimated until the team, location of delivery, tool requirements, and post-prototype development scope are confirmed. ## 8.3 Product risks and mitigations | Risk | Potential impact | Mitigation | | --------------------------- | ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | Low motivation persists | Users stop returning despite a usable app. | Investigate actual barriers; do not assume gamification alone will solve them. | | Plans feel too demanding | Frustration, discomfort, or disengagement. | Offer appropriate starting levels, rest, and reviewed alternatives. | | Excessive notifications | Users mute reminders or uninstall the app. | Make reminders optional and user-controlled. | | Overambitious scope | Four-week deadline is missed. | Freeze the MVP feature set and defer social and AI features. | | Misleading progress metrics | Users misunderstand activity or feel discouraged. | Define metrics clearly and avoid judgment-based comparisons. | | Accessibility gaps | Some users cannot complete core tasks. | Check contrast, touch targets, text scaling, assistive-technology support, and reduced motion. | | Sensitive data exposure | Loss of trust or privacy harm. | Collect only necessary information and define consent, storage, retention, and deletion rules before production. | | Unsafe exercise guidance | User discomfort or injury risk. | Have exercise content reviewed by a suitably qualified professional; provide stop instructions and appropriate alternatives. | ## 8.4 MVP acceptance criteria Before the project moves into functional development, agree on concrete acceptance criteria. - A new user can complete onboarding or use an appropriate default plan. - The dashboard clearly presents a suitable next workout. - A user can choose an available duration and understand the selected session. - Exercise instructions and navigation controls are clear and accessible. - Pausing, resuming, exiting, and completing a session produce the expected states. - Only completed sessions count as completed activity. - The progress screen distinguishes planned activity from completed activity. - A missed session does not trigger shame-based messaging or force an inappropriate workout. - Core usability tasks meet the team's agreed thresholds or have documented exceptions and remediation plans. - The team has reviewed exercise safety, privacy, and accessibility requirements. ## 8.5 Suggested success dashboard Separate prototype success from actual product success so the team does not confuse a well-designed demo with a proven fitness habit solution. ## Prototype stage Evaluate during Weeks 3–4. Core task completion Can users finish the primary flows? ### ≥85% Perceived ease of use Average participant rating. ### ≥4/5 Critical unresolved issues Safety or blocked core interactions. ### 0 ## Functional MVP pilot Evaluate after prototype approval, over a defined 2–4-week pilot. Workout completion Completed sessions / planned sessions, with clear rules for cancellations and rescheduling. Repeat weekly activity Percentage of users completing a session in successive weeks. Restart behavior Time until the next completed session after a missed plan. Set product-level numerical targets only after establishing a baseline, defining the pilot cohort, and determining what level of adherence is realistic and healthy for the intended users. # Final recommendation and immediate next steps StartSmall should launch as a focused, beginner-first fitness experience, not a comprehensive fitness platform. Its strongest initial proposition is helping users decide what to do, fit it into their day, complete the session, and restart without guilt. The product's competitive advantage should come from making consistency feel achievable rather than demanding more discipline from users. ## First five actions to take ## Four-week project checklist 0 of 5 Recruit beginner participants and schedule interviews Week 1 Validate the key barriers and finalize the problem statement Week 1 Sketch the six primary screens and build the clickable flow Week 2 Run usability tests and document observed issues Week 3 Refine the prototype and decide whether to build the MVP Week 4 ## The key design principle > Help people build a routine they can return to, not a streak they are afraid to break. If research confirms that time pressure, uncertainty, and discouragement are important barriers, StartSmall's combination of short workouts, flexible planning, simple guidance, visible progress, and a supportive restart flow offers a practical starting point. If the evidence points elsewhere, the concept should change accordingly. The four-week deliverable is a validated design direction and an actionable MVP specification—not proof of long-term behavior change. That distinction keeps the project evidence-driven, achievable within budget, and focused on creating a fitness experience beginners can realistically sustain.