Teams and collaboration
Solo, classmate pair or mixed-discipline squad. Pick the working style that matches the work, not the one that is easiest.
You can work alone, with classmates or in a mixed-discipline squad. The choice is yours, and most challenges allow all three.
But this matters: the team format you pick shows up on your credential. A recruiter looking at your portfolio will see whether you shipped that market analysis solo or as part of a team. Both are fine. They signal different things.
The three formats
Solo
You do everything yourself, end to end. Solo submissions read as: "This person can scope, structure and ship a piece of professional work without supervision."
This is the right format when:
- You want to show breadth across the whole project, from scoping to research to deliverable.
- The challenge is sized to be doable by one person.
- You are early in your portfolio and want clear, attributable wins.
Classmate pair
You and one peer, typically from the same programme, split the work. Pair submissions read as: "This person can ship in tandem with someone. They negotiated scope, divided the work and integrated it cleanly at the end."
Right when:
- You and a classmate want to tackle something bigger than either of you would alone.
- The challenge has natural seams, for example a market analysis where one of you owns the competitive landscape and the other owns the financial modelling.
- You want a faster turnaround than working solo.
Mixed-discipline squad
A team of several people, typically spanning more than one discipline, for example an engineer, a designer and a business student on a hardware-launch challenge. Squad submissions read as: "This person can work with people whose vocabulary is not their vocabulary."
This is the closest format to what most working teams look like. Recruiters from larger organisations often look hard at it, because it tests a skill they care about.
Right when:
- The challenge is genuinely multi-disciplinary, such as hardware plus software plus go-to-market, or clinical plus regulatory plus market sizing.
- You want to build the muscle that solo work cannot: translating between professional vocabularies.
- You have peers in adjacent programmes you would like to work with.
Each challenge shows its own team size, so check the brief before you form a team.
What good team collaboration looks like
Whether you are a pair or a larger squad, the same patterns hold.
Divide work along the seams, not down the middle. If two people own halves of a brief that do not talk to each other, you will integrate badly at the end. Look for natural interfaces and let one person own each side.
Write things down. A shared scoping document, a shared pitch deck, a shared "what we decided this week" page. Teams that only talk produce inconsistent deliverables.
Name a single editor for the final submission. Group-edited deliverables tend to read inconsistently: the voice changes from paragraph to paragraph and the structure drifts. Whoever has the strongest writing or design skill does the final pass.
Surface disagreement early. A team that did not disagree during scoping almost always disagrees during final submission. It is better to argue about scope early than about conclusions at the end.
Credit and attribution
Every team member gets a credential, and each credential records the team's composition. Your record shows you shipped this brief as part of a team, with the role you played. Recruiters reading your profile see this. They prefer it to ambiguity.
If team members contributed unevenly, reviewers can take that into account. This is rare, because most teams sort it out before submission, but the option exists.
When teams go wrong
Two failure modes show up most often:
- The free-rider. A team member who attends meetings but does not ship. Raise it early with your teammates and your reviewer. Solutions vary. Sometimes a smaller team is the answer.
- The lone wolf. A team member who insists on doing everything and treats teammates as observers. The fix is the same: raise it. A challenge done solo with a team's name on it is not a team submission.
Both are normal. Both are recoverable if you address them in week one rather than week six.
Next
When the work is done, you ship. See Final submission.
Scoping and pitching
The two early milestones, scoping and pitching, are where most strong submissions are won. What each is for, what reviewers look for and the mistakes to avoid.
Final submission
The submission is the work your credential is built on. What reviewers look at, which formats are accepted and how review leads to a credential.