Project leader guide · Chapter 1
Focus on users
Find your first users, learn from them by talking to them, and work out how to reach them at scale.
You are trying to build a high-impact project. If you build the world’s best product and nobody uses it, it doesn’t matter how good it was. So the most important thing at the start of a project is to identify your users and learn from them.
Users and distribution first
Look at any project that has achieved great things and you’ll see it connected a great product to users who needed it badly. The users’ need is central, and the “great product” comes from what those users needed.
But success doesn’t come from the users or the product alone. It comes from figuring out how to connect them: how to get the product to the people who need it. This is your go-to-market strategy. Early in your project, your job is to solve this puzzle:
- Who are my target users?
- How can a product like mine help them?
- How can I reach them at scale?
We often hear some version of “we’ll build the product, then get someone to do marketing for it”. This is how projects fail. You waste your own time and the time of the volunteers and people who help you, and in the end you don’t help Palestine.
Identify your users
If you don’t know who your users are, start there. Many projects think “everyone is our user”, and that kills them.
Find the first niche group that will use your product. They might be the people you can reach, or the people most interested in what you offer at the start (your early adopters). Tailor your early product and your conversations to them.
A good niche is “students who take part in encampments at US universities”. It isn’t all students, and it isn’t all encampments. It’s a specific group you can reach and build for.
Learn from your users
Speak to your users. Not surveys, not focus groups: actual conversations, one to one. You want to learn a lot about them. Why are they interested in your idea? What excited them? Why did they agree to talk to you? What do they do now instead of the thing you’re building? What happened that led them to you? If they won’t talk to you, why not?
Why not surveys? A survey can only answer the questions you thought to ask. You want to draw information out of people so you truly understand them. When a new question comes up, you should know your users well enough to answer it as they would.
Why not focus groups? They have the same problem as surveys, and the whole group moves together: the first person to suggest something anchors the conversation, and you learn less than you would from one person.
Your goal is not to show people your product and ask “would you use this?”. Any question where they might give you the answer they think you want is suspect. Ask open questions that show you how they think about the problem.
Questions to avoid
- “Would you use this?” (while showing a demo)
- “Do you need an app that does X?”
Better questions
- “Do you think about X? How are you dealing with it?”
- “If I tell you I’m trying to solve X, what comes to mind?”
- “Do you already use a product or service that does X?”
- “When you need to do X, how do you go about it?”
- “Are you part of [a group, such as organizers or activists for Palestine]?”
- “Can you walk me through the last time you did X?”
- “If you could change one thing about [product, service or feature], what would it be?”
- Lots of follow-up questions on their first answers.
An example
Say you’re building a tool to help people boycott films. This is a bad question:
- “I’m building a product to boycott movies, with features X and Y. Would you use it?”
These are good questions:
- How many films do you watch a month?
- How do you pick a film?
- Where do you watch films? Netflix, the cinema, somewhere else?
- Who do you watch films with?
- Who do you talk about films with?
Use the T4P community
The T4P community chat has thousands of members, and hundreds visit every week. Your project gets a public channel there, which works as a live, free source of feedback. Use it to test and validate features, find pain points such as bugs and confusing screens, build advocates who share your work, and find people with the skills you need.
