Chapter 2 of 10
Who Is This For? Defining Your First 1,000 True Users
Instead of trying to reach “everyone,” zoom in on the specific people who will actually care about your app—and uncover the real problems, contexts, and triggers that make them download and keep using it.
Start Here: Why You Need Specific Users, Not 'Everyone'
Why Specific Users Matter
If your app is "for everyone," it is really for no one. You need to define your first 1,000 true users: the specific people who will really care, download, and keep using your app.
Why Early Users Are Critical
Early users matter more than big download numbers. They give honest feedback, stay long enough to show what works, and tell friends if you solve a real problem.
From Vague to Concrete
You will move from vague ideas like "people who like fitness" to clear ones like busy 18–24 year old students who want 15-minute cheap healthy recipes for shared kitchens.
Your Goal in This Module
By the end, you will define 1–2 target segments, extract real problems from basic research, and write a short profile of your ideal early adopter user.
Step 1: Think in Jobs, Not Just Demographics
Jobs, Not Just Demographics
Age or gender alone do not explain why someone uses your app. Instead, think in terms of jobs-to-be-done: the task or progress a person wants in a situation.
What Is a Job-to-be-done?
A job-to-be-done is something a user "hires" your app to do, like stopping forgotten deadlines or splitting bills fairly with roommates.
Spotting Good Jobs
Good jobs are specific, tied to a situation, and do not mention apps or features. They start with phrases like "I want to" or "I need to".
Your Turn
For your app, list 2–3 jobs: what users want to achieve and in what situations (late at night, on the bus, at a desk, etc.).
Activity: Write 3 Job Statements
Use this space (or your notebook) to write three job statements for your app.
Follow this pattern:
- "When I am [situation], I want to [action] so I can [result]."
Examples:
- "When I am on the bus going to campus, I want to quickly check my tasks so I can use the ride well."
- "When I sit down to study at night, I want a simple plan so I can avoid scrolling social media."
Now do it:
- Think of 3 real situations where someone might use your app.
- For each, write one sentence using the pattern.
- After writing, underline or highlight the result part (the "so I can..."). That is the real motivation.
Reflection questions:
- Which job feels most painful or urgent?
- Which job happens most often in real life?
You will use these answers to narrow down your first 1,000 users in later steps.
Step 2: Turn Jobs Into Concrete User Segments
What Is a User Segment?
A user segment is a group of people who share a similar job-to-be-done, context, and often life traits like role or life stage.
Beyond "All Students"
Instead of "all students," you might target first-year engineering students in dorms who feel overloaded and want a simple way to track assignments on their phone.
Questions to Define Segments
Ask: Who has this job now? Where are they when it appears? What tools do they use today? How often does this job happen?
Write Rough Segment Descriptions
Create 2–3 short, human descriptions like international first-year students who plan everything on their phones and feel lost about deadlines.
Example: From Vague Users to Two Clear Segments
Starting Vague
You build a study-planning app and think it is for all university students. That is too broad to be useful.
Spotting Patterns
Interviews and reviews show patterns: many students work long hours, some are international, and most plan on their phones.
Two Jobs, Two Segments
Jobs like planning after work shifts or logging new assignments lead to segments: working students on tight schedules and international first-years.
Choosing a Launch Segment
For launch, you pick one main segment, like working students who plan on-the-go, and design features and marketing mainly for them.
Step 3: Understand Usage Contexts (Mobile vs Web, On-the-go vs At-desk)
Why Context Matters
Your app is always used in a context. Device and situation change what users need and what they will tolerate.
Key Context Dimensions
Think about device (mobile vs web) and situation (on-the-go vs at-desk). Each mix supports different types of tasks.
Examples of Contexts
Mobile on-the-go is for quick checks, while web at-desk is for deep work and detailed planning.
Apply to Your Segment
For each segment, ask where and how they use your app. Let this shape your first version and your marketing message.
Activity: Map Contexts for Your Top Segment
Choose the one segment you are most interested in right now.
Answer these questions for that segment:
- Where are they most often when using your app?
- Options to consider: bus, train, dorm room, library, office, kitchen, gym, etc.
- What device are they using?
- Mostly phone?
- Mostly laptop/desktop?
- A mix? If so, for which tasks?
- How long is a typical session?
- Under 30 seconds
- 1–5 minutes
- 10+ minutes
- How are they feeling in that moment?
- Rushed, bored, stressed, relaxed?
Write 2–3 sentences like:
- "Working students mainly use the app on their phones on the bus home after a shift. They are tired and only have 2–3 minutes."
This will help you later when you design screens and write marketing text.
Optional challenge:
- Note one thing you would remove from your app idea because it does not fit this context (for example, long forms on a tiny screen).
Step 4: Do Simple User Research (Without a Big Budget)
You Can Start Small
You do not need a big budget or lab. Start with short interviews, simple surveys, and competitor reviews to learn about users.
Short Interviews
Talk to 5–10 people in your segment. Ask how they currently solve the problem, what is hardest, and when it shows up.
Surveys and Reviews
Use short surveys to measure frequency and pain. Read recent app store or web reviews to see what people love and hate.
What to Look For
Highlight repeated phrases, repeated problems, and the situations where the problem is worst. These are powerful clues.
Activity: Extract Problems From a Fake Review
Read this fake app store review for a study app and then answer the questions.
"I am a first-year student working 20 hours a week. I tried this app to organize my assignments, but it expects me to sit at my laptop and plan everything for the whole week. That never happens. Most days I only have a few minutes on the bus to campus. I just want the app to tell me the next best thing to work on. Also, the notifications come at random times and I usually ignore them."
Questions (answer in your own words):
- What job-to-be-done is this person describing?
- What context are they in when they want to use the app?
- What are two problems they have with the current app?
- What motivation do you see behind their complaints?
Pause and write your answers. Then compare:
Possible answers:
- Job: "When I have a few minutes, I want to know the next best assignment to work on."
- Context: On the bus, on mobile, short sessions.
- Problems: Requires long weekly planning at a laptop; notifications are random and easy to ignore.
- Motivation: They want to stay on top of work despite a busy schedule, with minimal planning effort.
Quick Check: Identifying a Strong Target Segment
Test your understanding of what makes a strong initial target segment.
Which of these is the BEST example of a clear target segment for your first 1,000 users?
- All people who use smartphones.
- University students who want to get better grades.
- First-year nursing students who commute by bus and use their phones to study in 10–15 minute gaps.
- Anyone interested in productivity apps.
Show Answer
Answer: C) First-year nursing students who commute by bus and use their phones to study in 10–15 minute gaps.
Option 3 is best because it is specific about life stage (first-year nursing students), context (commute by bus), and usage pattern (10–15 minute phone sessions). The others are too broad and vague.
Step 5: Prioritize 1–2 Primary Segments for Launch
You might see many possible segments, but for your first version, focus on one or two. This makes your product and marketing much clearer.
To choose, score each segment (from 1 to 5) on:
- Pain level: How painful is the problem for them?
- Frequency: How often do they face this job?
- Access: How easy is it for you to reach and talk to them? (Are they around you at university, online communities, etc.)
Activity:
- List 2–3 segments you wrote earlier.
- For each, give a score 1–5 for pain, frequency, and access.
- Add up the scores.
- Pick the top 1–2 segments as your launch focus.
Example:
- Working students on tight schedules: Pain 5, Frequency 4, Access 4 → Total 13
- International first-years: Pain 4, Frequency 3, Access 2 → Total 9
In this example, you would launch for working students on tight schedules.
Write one sentence:
"For launch, we are focusing on: [your chosen segment]."
Step 6: Write Your Ideal Early Adopter Profile
Now you will write a short, concrete profile of your ideal early adopter.
Keep it to 5–7 sentences. Include:
- Who they are (life stage, role)
- Their main job-to-be-done
- Their typical context (device, place, time)
- Their main frustration today
- What success looks like for them
Template you can copy:
"[Name] is a [age range] [role/life stage]. They [brief situation]. Their main struggle is [biggest pain]. When [situation trigger], they want to [job-to-be-done] so they can [result]. They usually use [device] while [context]. If our app works, they will feel [emotion] because [success outcome]."
Example:
"Alex is a 19–22 year old first-year nursing student. They work 15–20 hours a week in a part-time job and commute by bus. Their main struggle is staying on top of assignments without spending hours planning. When they sit on the bus after work, they want to quickly see the next best task to work on so they can feel in control. They usually use their phone during 10–15 minute gaps. If our app works, they will feel calmer and more confident because they always know what to do next without complex planning."
Now write your own profile using the template.
Review Key Terms
Use these flashcards to review the core ideas from this module.
- Job-to-be-done
- A specific task or progress a person wants to make in a situation. It describes why they would "hire" your app, independent of features.
- User segment
- A group of people who share a similar job-to-be-done, context, and often traits like life stage or role.
- Early adopter
- A person who feels the problem strongly, is willing to try new solutions early, and gives useful feedback, even if your app is not perfect yet.
- Usage context
- The real-world situation in which someone uses your app: device (mobile/web), place, time, and emotional state.
- On-the-go usage
- Short, distracted sessions, usually on mobile, while commuting or moving between places. Best for quick checks and simple actions.
- At-desk usage
- Longer, more focused sessions, often on a laptop or desktop, suitable for deep work and detailed planning.
- Competitor review analysis
- Reading reviews of similar apps or tools to find patterns in what users love, hate, and still need.
Key Terms
- User segment
- A defined group of users who share similar jobs-to-be-done, contexts, and characteristics.
- At-desk usage
- Using an app while seated and focused, usually on a laptop or desktop, for longer, deeper work sessions.
- Early adopter
- An initial type of user who strongly feels the problem, adopts new solutions early, and provides feedback.
- Usage context
- The combination of device, location, time, and emotional state in which a user interacts with your app.
- Job-to-be-done
- A specific task or progress a user is trying to achieve in a given situation. It explains why they would use your app.
- On-the-go usage
- Using an app in short, mobile sessions while moving between places, like on a bus or in a queue.
- Competitor review analysis
- The process of studying reviews of existing apps or tools to understand user needs, pains, and expectations.