Give your student startup team a clear first project.

Write a one-page team brief

1. Problem: who faces it and what evidence have we seen?
2. Question: what single assumption will this project test?
3. Output: what can another person inspect at the end?
4. Owners: who is responsible for each task and how will decisions be made?
5. Time: how many hours can each person give during this part of term?
6. Review: when will we decide to continue, change or stop?

Keep the document short enough that everyone reads it. Each person should agree to their own commitment, rather than have it assigned to them.

A two-week example

The goal is learning whether the proposed change helped, not showing a polished pitch deck.

Agree on work and information boundaries

List which accounts, files, code, designs and interviews each person brings. Ask permission before using a campus logo, student list or class project in a public product. Keep interview notes limited to what the test needs and do not share access credentials in group chat. If the project may use university intellectual property, grants or other people's contributions, check the applicable rules and seek advice before commercial use.

Do not treat an informal checklist as a legal founder agreement. Use the agreement discussion guide to prepare questions for professional review if the venture develops.

Review the working relationship

At the review, compare the output with the original question. Then ask: did we tell each other early when we were stuck? Were decisions clear? Did the work fit around study? Would we choose another project together? Write down the next decision, even if it is to stop.

If you continue, agree on a new scope rather than silently extending the old one. The general working-trial planner can help with the next test.