Research & Discovery

Table of Content

Table of Content

Table of Content

1.01 Define & frame the problem

I’m working on a project about [describe your domain/product/idea briefly]. Right now, the potential problem I want to explore is: [write your version of the problem, even if rough]. Can you help me with: 1. Clarifying if this is really a problem worth solving (why/why not). 2. Reframing the problem from different perspectives (user, business, technical, market). 3. Suggesting 2–3 structured problem statements (e.g., “How Might We…”, JTBD style, or design challenge framing). 4. Identifying possible root causes (not just symptoms). 5. Defining success criteria – how I’ll know if this problem is solved. Format the response in a clear, structured way so I can directly use it in my design process documentation.

Copy Prompt

Copied

Copy Prompt

Copied

Copy Prompt

Copied

Use this when

You’re at the very start of a project and want to clarify, structure, and reframe the problem before diving into solutions.

Example input:

"I’m working on a project about closet maker.   Right now, the potential problem I want to explore is: cluttered cloths.    Can you help me with:   1. Clarifying if this is really a problem worth solving (why/why not).   2. Reframing the problem from different perspectives (user, business, technical, market).   3. Suggesting 2–3 structured problem statements (e.g., “How Might We…”, JTBD style, or design challenge framing).   4. Identifying possible root causes (not just symptoms).   5. Defining success criteria – how I’ll know if this problem is solved.    Format the response in a clear, structured way so I can directly use it in my design process documentation."

Example output (from ChatGPT)

1. Is this a problem worth solving?
	•	Why it is worth solving:
	•	Many people struggle with limited space vs. increasing number of clothes.
	•	Leads to frustration (hard to find items, clothes get wrinkled, forgotten, or unused).
	•	Direct impact on daily routines (wasting time choosing clothes → stress).
	•	Economic loss (people re-buy items they already own but can’t find).
	•	Growing interest in minimalism, organization hacks, and lifestyle apps shows existing demand.
	•	Why it might not be worth solving:
	•	Existing solutions already dominate (IKEA organizers, Marie Kondo method, wardrobe apps).
	•	Users might not consistently engage with digital/organizational tools → adoption risk.
	•	Problem may be perceived as “low priority” compared to bigger life issues.

⸻

2. Reframing from Perspectives
	•	User Perspective
	•	Problem: “I can’t find what I need when I need it.”
	•	Pain: Time wasted, decision fatigue, clutter stress.
	•	Need: Easy access, visibility, and decision support (outfits, laundry tracking).
	•	Business Perspective
	•	Opportunity: Growing market for home organization + digital lifestyle apps.
	•	Monetization: Subscription, affiliate links (outfit ideas → buy missing item), partnerships with brands.
	•	Differentiation: Go beyond storage → smart assistant for clothing usage + shopping.
	•	Technical Perspective
	•	Problem: Capturing/organizing user’s wardrobe data without being tedious.
	•	Challenge: Image recognition (auto-tagging clothes), syncing with laundry, cross-device usability.
	•	Opportunity: AI for outfit recommendations, voice/chatbot interface, AR try-on.
	•	Market Perspective
	•	Trend: “Productivity meets lifestyle” → Notion, Habit apps, Closet apps.
	•	Gap: Many wardrobe apps fail due to bad UX (manual data entry pain).
	•	Niche: Target students, professionals in urban setups, or fashion-conscious users.

⸻

3. Structured Problem Statements

a) How Might We (HMW)
	•	HMW help people organize and access their clothes so they save time and reduce daily stress?
	•	HMW make clothes visible, trackable, and usable instead of forgotten and cluttered?
	•	HMW create a system that reduces decision fatigue in outfit selection?

b) Jobs To Be Done (JTBD)
	•	When I am getting ready for my day, I want to quickly find and assemble outfits, so that I can save time and feel confident.
	•	When I buy new clothes, I want an easy way to add them to my closet system, so that I don’t lose track of what I own.

c) Design Challenge Framing
	•	Design a solution that helps users manage their clothing inventory in a way that is effortless, intuitive, and integrated into their daily routine.

⸻

4. Possible Root Causes

(not just symptoms like “clothes are cluttered”)
	•	Over-purchasing → More items than storage capacity.
	•	Poor storage design → Closet layout doesn’t support visibility or categorization.
	•	Low organization habits → Users don’t consistently fold/hang/return items.
	•	Decision fatigue → Too many choices → clothes pile up, remain unused.
	•	Lack of system support → No easy way to track laundry, seasonality, or outfit history.

⸻

5. Success Criteria
	•	Efficiency: Users find and select clothes/outfits in under 2 minutes.
	•	Visibility: 90%+ of clothes are seen/used at least once per cycle (month/season).
	•	Adoption: Users engage with the system at least 3–4 times per week (or integrate seamlessly into daily routine).
	•	Satisfaction: Reported stress reduction and ease of getting ready improves in surveys/interviews.
	•	Sustainability

Create a free website with Framer, the website builder loved by startups, designers and agencies.