I have an interview for a UX designer role on Wednesday and I need to build a case study…
- User
I have an interview for a UX designer role on Wednesday and I need to build a case study of a design feature. This means I need to come up with a plan fora fake design and strategy brief with business goals, KPIs, strategy and design goals, as well as wireframes, example prototypes, A/B testing information with outcomes and learnings, iterations of the UX Design, the final UX feature design and a walkthrough of how the design ultimately impacted business growth goals.
Assistant
Of course. This is an excellent way to prepare for a UX interview. A strong case study tells a story, showcases your process, and demonstrates your impact.
Here is a complete, ready-to-use case study for a fictional feature. You can adapt this, create your own simple visuals for it, and practice presenting it.
Case Study: Introducing "Community Circles" to the Habitual App
Project Overview
The Product: Habitual is a mobile app designed to help users build and track positive habits. It's a solo experience where users check off daily tasks.
The Challenge: While initial user acquisition is strong, user data shows a significant drop-off after 30-45 days. Qualitative feedback from exit surveys frequently mentions "losing motivation," "feeling isolated," and a "lack of accountability."
My Role: I was the Lead UX Designer on this project, collaborating with a Product Manager, two Engineers, and a User Researcher.
1. The Brief: Strategy & Goals
The leadership team provided a clear brief focused on a single business problem.
Business Goal:
- Increase user retention and combat churn. Specifically, increase Month 2 user retention by 15%.
Key Performance Indicators (KPIs):
- Primary KPI: Month 2 Retention Rate (the % of users who are still active in their second month).
- Secondary KPIs:
- Daily Active Users (DAU).
- Average Session Length.
- Adoption rate of the new feature.
Initial Strategy & Design Goals:
Based on the problem, we formed a strategic hypothesis:
"By introducing a social and community-oriented feature, we can create a network of support and accountability that will motivate users to stay engaged with the app and their habits for longer."
This led to our core design goals:
- Foster Connection: Make users feel like they are part of a team.
- Encourage Positive Reinforcement: Focus on encouragement, not competition.
- Provide Gentle Accountability: Create a sense of shared purpose.
- Seamless Integration: The feature should feel like a natural extension of the core habit-tracking experience, not a separate social network.
2. Research & Discovery
To validate our hypothesis, we started with research.
User Interviews & Surveys: We interviewed 15 users who had been active for over 3 months and 15 who had churned after the first month.
- Key Insight (Retained Users): "I share my progress with a friend outside the app. They keep me accountable."
- Key Insight (Churned Users): "It just felt like a chore. After the initial excitement wore off, I had no reason to open the app."
- Survey Data: 78% of users stated they would be "more likely" to stick with a habit if they were doing it with others.
Persona: We focused on our primary persona, "Alex, the Ambitious Professional."
- Age: 28
- Goal: Build consistent habits like "meditate 10 mins daily" and "read 20 pages a day."
- Frustration: "I get really motivated for a few weeks, but life gets in the way. Without someone to check in with, I just let my habits slide."
Problem Statement (How Might We):
How might we foster a sense of community and accountability within Habitual to help users like Alex stay motivated and achieve their long-term goals?
3. Ideation & Design (Low-Fidelity)
We brainstormed several concepts (leaderboards, direct messaging, challenges) but settled on "Community Circles"—small, private groups focused on a shared habit or theme.
User Flow: I mapped out the core user flow: Discover Circle -> Join Circle -> View Circle Progress -> Post Update -> React to Others' Updates
Low-Fidelity Wireframes: I sketched out the key screens to establish the basic layout and hierarchy. The focus was on clarity and function over aesthetics.
(In an interview, you'd show these sketches. For now, here are descriptions.)
- Screen 1: Discovery Page: A scrollable list of available Circles, using cards with the Circle name, a brief description, and number of members. A clear "Join" button on each card.
- Screen 2: Circle Detail Page: At the top, a visualization of the group's collective progress. Below, a feed of members' check-ins and encouraging comments. A list of members is easily accessible.
- Screen 3: Main Dashboard Integration: A new module on the user's main habit list showing a summary of their Circle's activity to draw them in.
4. Prototyping, Testing & Iteration
I created a clickable prototype in Figma to test the core flow with 5 users.
Initial Usability Test Findings:
- Finding 1 (Positive): Users immediately understood the concept of Circles and were excited by it.
- Finding 2 (Negative): 3 out of 5 users expressed "performance anxiety." They were worried about being judged if they missed a day and their progress was visible to everyone.
- Finding 3 (Confusion): Users were unsure how to find Circles relevant to their specific habits.
Design Iterations: Based on this feedback, I made two key changes:
- Iteration 1: Privacy & Tone. I changed the feed to focus on positive actions (checking in) rather than streaks or missed days. I added copy like "Cheer them on!" and focused on reactions like "🎉" and "👍". This shifted the tone from surveillance to support.
- Iteration 2: Improved Discovery. I added a "Recommended for You" section at the top of the Discovery page that surfaced Circles based on the user's current habits (e.g., showing a "Daily Readers" circle to a user tracking a reading habit).
5. A/B Testing a Key Assumption
Before building the full feature, we wanted to validate a key assumption: Would users even click to explore a community feature? We ran an A/B test on the main dashboard to measure interest.
- Hypothesis: A prominent and visually engaging entry point for "Circles" on the main dashboard will lead to a higher click-through rate (CTR) and feature discovery than a subtle one.
- Variant A (Control): A small banner at the bottom of the habit list: "New! Join a Community Circle."
- Variant B (Challenger): An integrated card placed within the user's habit list that read: "Find your team. Join a Circle for your [Meditation] habit." This was personalized.
- Metric: CTR on the entry point.
Outcome:
- Variant B had a 65% higher CTR than Variant A.
Learning:
- Integrating the feature's entry point directly into the user's primary workflow and personalizing it was significantly more effective. This learning informed the final design.
6. Final Design & Walkthrough
The final design incorporated all the learnings from user testing and A/B testing. It featured a clean UI, our brand's calming color palette, and motivational micro-interactions.
(In an interview, you'd show high-fidelity mockups or a Figma prototype. Here is the walkthrough.)
The User Journey (Alex):
- Discovery: Alex opens his Habitual app. On his main dashboard, right below his "Meditate 10 mins" habit, he sees a card saying, "You're not alone. Join the Mindful Mornings Circle." Intrigued, he taps it.
- Joining: He's taken to the Circle's page. He sees there are 15 members, a shared goal of "75% weekly completion," and a feed of recent check-ins with encouraging comments. It feels supportive, not intimidating. He taps "Join Circle."
- Engagement: The next day, after he checks off his meditation habit, a prompt asks, "Share with your Circle?" He adds a quick note, "Felt great today!" and posts it.
- The Payoff: A few hours later, he gets a push notification: "Sarah and 3 others cheered on your check-in! 🎉" He opens the app, sees the encouragement, and feels a sense of connection and motivation.
7. Impact & Business Results
We launched the "Community Circles" feature and tracked the KPIs over the following quarter. The results were outstanding.
- Month 2 Retention increased by 18%, exceeding our 15% goal.
- We performed a cohort analysis and found that users who joined a Circle had a 40% higher retention rate than users who did not.
- Daily Active Users (DAU) saw a sustained lift of 12% post-launch.
- 35% of all active users joined at least one Circle within the first month of launch, showing strong feature adoption.
Our initial hypothesis was validated. By addressing the user's need for accountability and connection, we directly impacted the company's primary business goal of improving retention.
8. Learnings & Next Steps
- Key Learning: For habit-forming products, emotional needs (like connection and support) can be just as important as functional ones (like checking a box).
- Personal Learning: This project reinforced the importance of testing early and not being afraid to pivot based on user feedback. The shift away from "performance tracking" to "positive reinforcement" was critical to the feature's success.
- Next Steps:
- Iterate on the experience by giving Circle creators more admin tools.
- Explore time-based "Challenges" that Circles can opt into.
- Use machine learning to improve the personalization of Circle recommendations.
How to Present This in an Interview
- Prepare Your Visuals: Create 5-7 simple slides or Figma screens: The Problem (KPIs), The User (Persona), The Flow, The Wireframes, The Iteration (Before/After), The A/B Test, The Final Design, The Results.
- Tell it Like a Story: Start with the problem, walk them through your process, and end with the successful result. Use "I" when talking about your specific contributions (e.g., "I designed the wireframes") and "we" when talking about team efforts (e.g., "We decided to run an A/B test").
- Focus on the "Why": For every design decision, be ready to explain why you made it. "I used cards for discovery because they are easily scannable on mobile." "We chose to A/B test the entry point because it was the biggest risk."
- Keep it Concise: Aim for a 10-15 minute presentation, leaving lots of time for questions. Good luck on Wednesday
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.