Choose a problem you can observe
Start with a situation you can see closely: a student club struggling to organise volunteers, a local shop losing track of orders or a lab repeatedly booking shared equipment by hand. Describe who has the problem, when it happens and what they do today. “An app for students” is too broad to test.
“Student societies at our college lose volunteer availability in group chats before each event. We want to learn whether a shared sign-up sheet would reduce last-minute cancellations.”
Choose a problem you can investigate without asking people to reveal private records or putting them under pressure to participate.
Talk to people before building
Ask potential users about a recent real event, not whether they like your idea. Try: “Tell me about the last time this happened”, “What did you do instead?” and “What did that cost you in time or effort?” Record patterns, not personal details you do not need. Speak with several people who face the problem; friends agreeing with a pitch is weaker evidence than specific accounts of what they already do.
Write down what would change your mind. If nobody has experienced the problem recently, narrow the audience or choose a different problem.
Build the smallest honest test
Test the riskiest assumption first. A paper workflow, simple form, manual service or clickable sketch may answer the question before a full app. Define one observable outcome: for example, whether three society organisers actually use the new sign-up process at their next event. Explain that it is a trial, ask permission for feedback and do not promise features that do not exist.
Keep track of your own time and any real costs. The runway calculator can make a spending scenario visible, but most first tests should be scoped so you can stop cheaply.
Plan around the semester
Set a weekly commitment you can keep during classes, exams and internships. Pick a review date before the next busy period. If coursework, university facilities, a sponsor or another person's work may be involved, check the relevant campus rules and discuss ownership before sharing or commercialising it. Seek appropriate professional advice when those questions become material.
If someone joins you, state who owns each small task and when you will check in. Do not treat enthusiasm as an unlimited time commitment.
A four-week plan you can actually review
- Week 1: name one audience and document five recent examples of the problem.
- Week 2: speak to potential users and write down what surprised you.
- Week 3: run a small, permission-based test of one proposed improvement.
- Week 4: compare the outcome with your original assumption. Continue, change direction or stop, and record why.
The weeks are a planning example, not a success formula. If you need a partner for the next test, read how to find a college co-founder and prepare a specific contribution brief.