Split a group project so everyone knows their part
Lay out the project's scope on one map, give each teammate a branch, and share a link so the whole team reads the same plan.
Start from a template
A group-project template you can clone and fill in for your team, with roles, milestones and deadlines.
How it works
One person builds the map and shares it with the team as a link. Each part of the project becomes a branch with an owner, so everyone can see who is doing what and where the parts meet.
-
Agree on the scope. Describe the project, the team size and the deadline, and ask for the main parts of the work. Edit the branches together, on a call or in person, until the team agrees on what is in and what is out.
-
Give each branch an owner. Put each teammate’s name on their branch and give each person a color with Cmd+B, so whose work is whose shows at any zoom.
-
Mark where work depends on work. Under each branch, ask what it needs from the others. If the economics section needs cost data from the case studies, add a node with the date under both branches.
-
Share the plan. Publish the map from the share dialog. Anyone with the link can read it without an account, and a teammate can clone it to work from their own copy.
A published map is read-only for everyone except its owner, so one person keeps the plan current.
Planning where sections meet
When four people write four sections alone, the joins show in the final paper. With the sections side by side, overlaps show up early: two branches that need the same data, or one branch with fifteen nodes under it and another with three.
Example
Say three of you are presenting on the ethics of AI for a philosophy course. The map starts with three branches: privacy and surveillance, algorithmic bias, and autonomous decisions. Each person takes one. After a week, all three branches have a node about who is accountable when a system causes harm. You move accountability into a fourth branch, give it to one person, and the other sections refer to it.