Teams calcify fast. Whoever talks most in the first meeting becomes the de facto leader. Whoever volunteers for slides owns slides for ten weeks. The person who stays quiet on day one is usually still quiet in week eight. None of that gets decided deliberately—it just sets, and afterwards it's much harder to change than it would have been to choose.
Which makes the first 48 hours disproportionately valuable. Here's what to settle while everything is still soft.
Hour one: the skills and constraints inventory
Before any work is divided, go around the table twice.
First pass—what you're actually good at. Not job titles. Specific capabilities: "I can build a three-statement model fast," "I write clean prose," "I've run client interviews," "I'm good at making ugly decks look finished." Job titles hide this. A former consultant might be a mediocre modeler; a marketer might be your strongest analyst.
Second pass—what your term actually looks like. Recruiting timelines, work travel, the week someone's in another country, the class everyone underestimates. Get the constraints on the table while they're abstract and nobody is defending a missed deadline.
This second pass is the one teams skip, and it's the one that prevents the worst pattern in MBA teamwork: someone disappears during their interview crunch, nobody saw it coming, and the team reads a scheduling reality as a character flaw.
Hour two: the four agreements
Write these down somewhere everyone can find them. Four items, not fourteen—longer charters don't get read.
- Where the work lives. One place for deliverables, tasks, owners, deadlines. Everything else points at it.
- What response time we owe each other. Input requests inside 24 hours, reviews inside 48, urgent means "blocks someone today." Now silence has a defined meaning.
- How a decision gets made. The default that works: whoever owns the question writes a short proposal with an objection deadline. No objections means decided.
- What happens when someone can't deliver. The most important one and the most skipped. Agree now that the expectation is tell the team early, and that early notice is treated as responsible rather than as failure. Teams that don't say this out loud get silence instead, because silence feels safer than admitting you're behind.
There's a fuller treatment of these communication norms if you want the reasoning behind each. MBA Lab's free team charter builder is a fast way to turn agreements like these into a document the whole team can actually find again later.
Day one, later: definitions of done
For each major deliverable, write what "finished" means concretely enough that two people would agree on whether it's met. Not "competitor analysis"—three named competitors, sourced share figures, one exhibit, recommendation in the opening paragraph, deck template applied.
Ten minutes per deliverable. It prevents the single most common form of rework on student teams: someone delivering exactly what they understood was asked, and the team needing something different.
Day two: owners and the dependency map
Now split the work—one named owner per deliverable, no shared ownership. Then do the step most teams miss: draw the arrows.
Which pieces block which? The market sizing feeds the model; the model feeds the recommendation; the recommendation drives the deck narrative. That chain means the market sizing owner starts first and finishes early, even if their piece is smaller than everyone else's.
Teams that split work evenly by volume and start simultaneously spend week three with four people idle, waiting on one. Twenty minutes with the arrows recovers more hours than any productivity habit, because it removes waiting rather than compressing work.
While you're here, set the internal deadlines a full working period before the real one, and put the integration session on the calendar now. Integration is real work, it's harder than any individual piece, and it arrives when there's no slack left.
Day two: name the roles nobody wants
Two jobs exist on every team and get absorbed silently by whoever has the lowest tolerance for chaos:
- The integrator, who makes five pieces into one coherent artifact.
- The scheduler, who tracks what's due and chases what's late.
Unnamed, these land on the same person, who ends up doing a second invisible project and quietly resenting everyone. Name them, and rotate them if the course has multiple deliverables. A lightweight responsibility matrix is a good place to put them so they're visible rather than assumed.
What you'll be tempted to skip
The constraints conversation, because it feels like negativity at a moment when everyone is friendly and optimistic. Skip it and you'll have the same conversation in week six, except it'll be about a specific missed deadline and a specific person, and it will not be friendly.
The other temptation is starting work in the kickoff meeting. Don't. An hour of setup feels slow against the urge to make visible progress, but you're choosing between an hour now and a week of rework later. That trade is not close.
A test for whether it worked
At the end of 48 hours, everyone should be able to answer four questions without checking: What do I own? When is it due? Who am I blocking? What does done look like for my piece?
If any answer requires a message to find out, you have a specific gap, and you can close it today while it's cheap.