Who does what: a roles chart for 3 to 5 person student projects
· buildtolaunch
You have a team of three to five students, a deadline, and nobody has said who does what. This guide gives you a roles chart you can copy, a split for each team size, and a way to adjust it when everyone can prototype with AI tools. It is part of the full guide to building with teammates.
Short answer
Give every project four jobs and name one owner for each: Builder (makes it work), Design (makes it clear), Users and growth (talks to people and brings them in), and Pitch and ops (plan, deadline, demo). In a team of three, people double up; in a team of five, add a second builder or a researcher. Write the chart in week one and review it weekly.
The four jobs every student project has
| Role | What the owner is responsible for | Example output |
|---|---|---|
| Builder | A working version people can open | A live link, a bug list that shrinks |
| Design | The product is understandable in under a minute | Screens, copy, a simple logo and colours |
| Users and growth | Real people try it and say what they think | 10 interviews, a signup page, first 20 users |
| Pitch and ops | Plan, deadline, demo and who decides what | Weekly goals, demo script, submission |
"Owner" means one person answers for the job, not that they do all of it. Others can help, but if the job slips, everyone knows whom to ask.
Roles by team size
| Team size | Suggested split |
|---|---|
| 3 people | Builder + Design, Users and growth, Pitch and ops. The builder also covers design basics. |
| 4 people | One owner for each of the four jobs. This is the easiest size to run. |
| 5 people | Four owners, plus a second builder or a researcher who runs interviews and tests with users. |
Not sure how many people your project needs? See how many people is the right team size (Vietnamese).
How vibe coding changes the split
Tools that let you describe an app in plain language mean almost anyone on the team can make a clickable prototype. That changes roles in three ways:
- Everyone can prototype, so the builder becomes the reviewer. The Builder decides what is safe to ship, fixes what AI got wrong, and keeps the product running. Teammates can still try ideas on their own screens.
- Design and building overlap. A designer can build their own screen with an AI tool and hand a working version over, not a picture.
- The scarce jobs are now users and decisions. Talking to real users and choosing what to build next are what slow teams down, not typing code.
If your team mixes coders and non-coders, read how IT students can work with teammates who do not code (Vietnamese).
Copyable roles chart
Paste this into a shared note. Fill every line before you start building.
PROJECT: [name] DEADLINE: [date] TEAM: [names]
ROLE OWNER BACKUP DECIDES ABOUT
Builder [name] [name] how it is built, what ships
Design [name] [name] screens, wording, look
Users and growth [name] [name] who we talk to, how we reach them
Pitch and ops [name] [name] weekly goals, demo, submission
HOURS PER WEEK: [name] [h] [name] [h] [name] [h]
HOW WE DECIDE: [e.g. role owner decides in their area, tie goes to Pitch and ops]
REVIEW DATE: [every Sunday]
Two columns matter most. "Backup" stops the project dying when someone has exams. "Decides about" ends arguments, because the owner has the final word in their area.
Rules that keep the chart useful
- One owner per job. If two people own it, nobody does.
- Match roles to what people want to learn, not only what they already know. A student who has never interviewed users may want that job, and a trial period shows who is good at it.
- Check hours honestly. Write down real hours per week. A team of five with 3 hours each has about 15 hours, so the scope should fit that.
- Rotate the demo. Everyone should be able to explain the product, not only the person who pitches.
- Review weekly. Move jobs when someone is overloaded. A short weekly meeting works; use the weekly meeting template (Vietnamese) and a free board from free project tools for student teams (Vietnamese).
When roles and ownership collide
A roles chart says who does the work. It does not say who owns the result. Before the project has real users, write down who owns the code and the brand, and what happens if someone leaves. The simple founder agreement checklist covers that in one page. If you are deciding whether to hire outside help or build it yourself, see technical co-founder, agency, or build it yourself.
Fill the chart with real teammates on buildtolaunch
buildtolaunch is a free community of about 300 students in Vietnam and Southeast Asia, and you do not need to code to start. You can open a project Space and build with an AI teammate, practise skills with the AI tutor at Practice, and post what you ship on the Launch League, which resets every Monday. Browse opportunities for students when your team wants a deadline to aim at. Join free.
FAQ
What roles does a student project team need?
Four jobs cover most projects: a builder who makes the product work, a designer who makes it clear, someone who talks to users and brings them in, and someone who runs the plan, deadline and demo. In a small team one person holds two jobs. Name one owner for each so nothing falls between people.
How do we split roles in a team of three?
Combine builder and design, then give one person users and growth and one person pitch and ops. Be honest about hours, because a three-person team has little slack. If the builder is also doing design, keep screens simple and use a ready-made layout.
Do we need a team leader?
Not a boss, but you need clear decision rights. Give each role owner the final say in their area, and decide in advance who breaks ties (often the Pitch and ops owner). Rotating a "meeting lead" each week also spreads the load.
What if one person is doing most of the work?
Raise it at the weekly review with the chart and real hours in front of you, not in a group chat. Move or split jobs, shrink the scope, or add a backup. If it keeps happening, see signs it may be time to stop working together (Vietnamese).
Should everyone learn a bit of everything?
Yes, a little. When AI tools let anyone prototype, each person should be able to try the product, read the plan, and explain it to a user. But keep one owner per job so decisions stay clear.
How often should we change the roles?
Review the chart every week and change it only when it is not working: someone is overloaded, someone wants a different job, or the project's needs have shifted. Constant reshuffling confuses everyone, so make changes at the review, not in the middle of a week.