# Team Formation > Find the right people, define roles, and create a winning team dynamic. Canonical: https://thehackathonplaybook.dev/playbook/team-formation Last updated: 2026-06-24 --- ## Find Your Persona Which role do you gravitate toward? Take the 8-question quiz. TL;DR Know your default role so you can recruit teammates who cover the other three. ### What's Your Hackathon Persona? 8 scenario-based questions. No wrong answers. Discover which role you naturally gravitate toward in hackathon teams. ## The Four Personas Every winning team needs four roles. You don't need a big team, just the right mix. One person can cover several roles. TL;DR Cover four roles (Designer, Pitcher, Architect, Strategist), not four headcount. Composition beats size. #### The Designer A polished UI signals quality instantly in a sea of terminal demos. The Designer makes your 4AM code look intentional. First impressions decide hackathons. Traits Strengths - Buys credibility before you say a word; judges form opinions in seconds - Owns online judging: your project IS your screenshots - Simplifies complex features into something approachable Watch Out For Over-polishing under pressure when "good enough" ships. Like a cinematographer: they define how the world sees the project. Spot them: they open Figma before VS Code. #### The Pitcher Can't explain it in 60 seconds? You lose. The Pitcher translates engineering into impact: when to lead with the problem, when to show the demo, how to answer "so what?" Traits Strengths - Maximizes the 2-5 minute demo window; every second counts - Handles tough judge Q&A without breaking a sweat - Separates "cool project" from "first place" Watch Out For Over-promising unbuilt features, or prioritizing pitch prep over helping build. Like a trial lawyer: they make the case and handle cross-examination. Spot them: they naturally command a room. #### The Architect Sees the whole board. While others go deep on features, the Architect makes everything connect (API to frontend, ML model to UI, auth to database). They're the technical glue. Traits Strengths - Prevents integration failure, the #1 killer of hackathon projects - Cuts scope ruthlessly to keep the project feasible - Connects frontend and backend; unconnected = no demo Watch Out For Building for scale when you need to build for demo. Like a city planner: they design how everything connects. Spot them: they ask "how will this integrate?" before "how will this look?" #### The Strategist Says "no" to feature creep at 3AM. Runs the check-ins, makes the hard calls on what to cut. Their decisiveness separates a working demo from an unfinished mess. Traits Strengths - Aligns the team on path and timeline via lightweight check-ins - Surfaces trade-offs: "What gets cut if we add this?" - Buffers builders by owning logistics, submissions, and scope Watch Out For Over-planning and rigidity; too much process slows a 48-hour sprint. Like a film producer: they own the schedule, scope, and ship date. Spot them: they time-box debates and ask "is this in scope?" [Meredith Belbin](https://www.belbin.com/) — management researcher, Henley Management College > “Nobody is perfect, but a team can be.” Belbin's research at Henley Management College identified eight team roles (a ninth, the Specialist, was added in Team Roles at Work in 1993), and teams with complementary coverage beat equally talented teams with overlapping strengths. Our four personas map directly: the Designer is Belbin's Plant (creative thinker), the Pitcher is the Resource Investigator (external communicator), the Architect is the Monitor Evaluator (analytical judge), and the Strategist is the Co-ordinator (team leader). — Belbin's often-quoted maxim; team roles from [Management Teams: Why They Succeed or Fail, 1981](https://www.belbin.com/) ## Where to Find Teammates The best teammates rarely come from a single search. Here's where to look. TL;DR Source teammates from many channels, but the strongest signal is hacking alongside someone at a fun event. Hackathon Discords Jump into team-matching channels early; the best teammates get claimed fast. Hackathon Communities Tap WeCracked (4K+ members), MLH groups, and local clubs for a steady pipeline. University Clubs CS clubs, ACM chapters, and hackathon orgs are goldmines; the building culture already exists. Devpost Scouting Browse past winners and reach out to people whose projects impress you. Most are happy to connect. Fun Hackathons Hacking alongside someone is your best pipeline. One "fun" event can reveal a future varsity teammate. Social Media LinkedIn groups, Twitter/X tech communities, and hackathon subreddits are underrated sources. Remember: Attitude and communication are the foundation of any winning team. You can teach skills, but the willingness to learn, adapt, and support each other under pressure separates good teams from winning ones. TL;DR Pick attitude over raw skill: a toxic genius costs more than they add under 24-48 hour pressure. > “Hire character. > Train skill.” — [Peter Schutz, CEO of Porsche AG from 1981 to 1987](https://en.wikipedia.org/wiki/Peter_Schutz), his often-quoted hiring maxim A toxic genius is still toxic. However skilled, if they create friction, slow communication, or sour the environment, they're a net loss. Under 24-48 hour pressure, chemistry beats individual brilliance. The right attitude means - Speak up when stuck instead of going silent - Pivot when the plan isn't working - Back the team decision even if it wasn't their first choice - Stay positive at 3AM when everything is breaking Amy Edmondson — Harvard Business School > “Psychological safety is a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes.” Edmondson's research shows teams where members feel safe to take interpersonal risks learn faster and perform better. Her hospital studies famously found the best teams reported the most mistakes, because people felt safe enough to report them. — [The Fearless Organization, 2018](https://fearlessorganization.com/) Google Project Aristotle Across 180+ teams over two years, Google found psychological safety was the #1 predictor of performance, ahead of dependability, structure, meaning, or impact. How members interact matters more than who is on the team. — [Google re:Work, 2015](https://rework.withgoogle.com/guides/understanding-team-effectiveness/) ## How serious are you about hackathons? Most people do one or two for fun, and everything above is all you need. The squad-building system below is for people chasing repeat wins. ### TL;DR Train rookies on a JV list, then promote proven teammates to varsity for high-stakes wins. Like a sports team, you train rookies through the season before the championship game. Hackathons work the same way. #### JV Teammates Your development squad. High-potential teammates you're actively training and building chemistry with. - Proven attitude and work ethic over 1-3 hackathons - Still developing time management, prototyping, and pitching - Building chemistry with you at training hackathons - One good hackathon usually earns a JV spot 1-3 hackathons to join 2-8 hackathons 2-8 hackathons #### Varsity Teammates Your championship squad. Battle-tested over many hackathons, with deep trust and communication shortcuts. - Deep trust and rhythm from 3-8+ hackathons together - Self-directed: each person owns their role, no micromanagement - Shared toolkit: templates, favorite APIs, deployment pipeline - Reserved for high-stakes competitions where winning is the goal 3-8+ hackathons to earn varsity The key factor isn't skill level but how well you work together under time pressure. A varsity teammate may be a worse coder than a JV one, yet communicate better, pivot faster, and never go silent at 3AM. This mirrors what psychologist Anders Ericsson calls deliberate practice: improvement needs repeated, structured effort with feedback, not just showing up. — [Anders Ericsson, Peak: Secrets from the New Science of Expertise, 2016](https://en.wikipedia.org/wiki/Peak:_Secrets_from_the_New_Science_of_Expertise) #### Tuckman's Group Development Tuckman found that groups move through forming, storming, norming, and performing, and that every stage is necessary before a team reaches full effectiveness. Tuckman's 1965 model maps onto JV/Varsity. JV teammates are forming and storming: learning styles, navigating disagreements, building trust. Varsity teammates have reached norming and performing: shared norms, fluid execution, zero coordination overhead. — Bruce Tuckman, psychologist, U.S. Naval Medical Research Institute, [Developmental Sequence in Small Groups, Psychological Bulletin, 1965](https://en.wikipedia.org/wiki/Tuckman%27s_stages_of_group_development) #### The Progression Path Forming → JV List First hackathon together: learning how each person works and setting communication expectations. Storming → Training Hackathons Disagreements over scope, stack, and approach surface. This friction is necessary; working through it builds trust. Norming → Late JV / Early Varsity Shared norms emerge. You know who handles what. Code reviews and communication shortcuts develop naturally. Performing → Varsity Peak effectiveness. The team executes as a unit: shared toolkits, minimal overhead, maximum output. ### TL;DR Use fun events to scout, training events to build your JV, and competitive events for varsity-only wins. #### Fun Hackathons Low stakes, high discovery. Team up with people you meet or match with. Less about winning, more about scouting. TEAM WITH New people, team-matching channels, friends trying hackathons Pro Tip Treat every fun hackathon as a scouting event. Whoever vibes well here might become your next JV member. 1 event to earn JV consideration #### Training Hackathons JV list only. Develop technical and soft skills together. Practice the full workflow: ideation, architecture, execution, pitching. TEAM WITH JV teammates only; the point is chemistry and shared muscle memory Pro Tip Simulate competition conditions: set internal deadlines, practice the pitch early, do a full dress rehearsal before submission. 2-8+ events to train a team to varsity #### Competitive Hackathons Varsity only. One goal: first place. Backed by extensive training, shared tools, and battle-tested teamwork. TEAM WITH Varsity only: pre-planned roles, shared templates, proven tools and APIs Pro Tip Pre-plan the stack, ready your boilerplates, and assign roles before kickoff. Minimize decisions during the event. Win mode first place or bust [J. Richard Hackman](https://en.wikipedia.org/wiki/J._Richard_Hackman) — Leading Teams Hackman names a compelling direction, a purpose that is clear, challenging, and consequential, as one of five conditions for team effectiveness. Hackman's Harvard research explains the three categories. Fun hackathons have no shared direction (you're still exploring). Training hackathons have a learning direction (the purpose is growth). Competitive hackathons have a winning direction that is clear, challenging, and consequential. Sharper direction, better performance. — [Leading Teams: Setting the Stage for Great Performances, 2002](https://en.wikipedia.org/wiki/J._Richard_Hackman)