Building the team — roles, chemistry, and operating rhythm
The most common team in any competition is three friends from the same section with the same skills and the same blind spots. The judges never see the team — but they see its gaps on every slide.
TL;DR · Key Takeaways
Key takeaways
- Four jobs — analyst, researcher, designer, storyteller — each with a named owner; the captain is a hat the storyteller usually wears.
- Recruit for your gaps across sections and batches; agree hours, season load, and the tie-breaker rule before the first deadline.
- Split workstreams, never slides; one designer assembles one deck in one visual language.
The four-role architecture
A competition deliverable needs four distinct kinds of work. In a team of 3, people double up; in a team of 4, each owns one. What matters is that every role has a named owner — unowned roles are where decks fail.
Recruiting in practice
Audit yourself first
Which of the four roles are you, honestly? Most people overrate their storytelling and underrate design. Ask someone who has seen your work.
Recruit across sections and skills
An engineer-CA-designer-debater team beats four finance majors. Look in classes, clubs, and last year's competition shortlists — past finalists are public on Unstop and LinkedIn.
Consider a senior–junior mix
Where rules allow cross-batch teams, one senior who has seen a finale changes everything: they know what judges punish. In exchange, juniors carry more execution hours.
Agree on the contract before the first deadline
Three questions settle 90% of future fights: how many competitions this season, how many hours per week, and who decides when we disagree. Say the answers out loud.
The operating rhythm of a two-week sprint
| Phase | Days | Who is on point |
|---|---|---|
| Decode the problem statement together | Day 1 | Whole team — never split before alignment |
| Research sprint + structure the issue tree | Days 2–5 | Researcher + Analyst |
| Solution build + financials | Days 6–9 | Analyst leads, all contribute options |
| Deck build | Days 8–12 (overlaps) | Designer leads; storyteller writes headlines |
| Freeze, rehearse, stress-test Q&A | Days 13–14 | Storyteller leads; everyone defends |
The classic failure
Splitting slides on day 1 ("you take slides 1–3, I take 4–6") produces four mini-decks stapled together. Split workstreams, not slides — the deck is assembled by one designer from everyone's inputs, in one visual language.
Name the team like a brand
You will register dozens of times. A short, memorable, professional team name ("Team Meridian" beats "Case Crushers 69") becomes your scoreboard identity across seasons — finalist lists are public, and recruiters do notice repeat names.