Why unowned work sinks projects
Most projects don't fail because the work was hard.
They fail because two people thought they owned the same task, or nobody did.
Mapping roles and responsibilities before you start is a small investment that prevents exactly that.
This guide explains when the exercise is worth your time, how to run a simple mapping session, and what to do with the gaps you find.
It draws on a documented team exercise from Atlassian's Team Playbook, adapted for small teams, freelancers, and early-stage founders.
When responsibilities live only in people's heads, every assumption is private.
You believe you're handling the launch email.
Your teammate believes the same.
Neither of you checks until the week it's due.
The reverse failure is just as common: a task everyone assumes someone else will pick up.
In small teams this is especially dangerous, because there's no middle manager whose job is to notice the gap.
A written roles map turns those private assumptions into shared, checkable statements.
Once they're on paper, disagreements surface early, when they cost a conversation instead of a deadline.
When mapping roles is worth the time
You don't need a formal exercise for every effort.
A solo project with one contributor rarely needs a table.
The exercise earns its keep in these situations:
- Two or more people will contribute, especially across different organizations or time zones.
- The work mixes skill areas, such as design, build, and outreach, where overlap is likely.
- People will hold more than one role, which makes ownership ambiguous.
- You're working with volunteers, collaborators, or contractors who each assume different norms.
If outside parties are waiting on updates, pair the roles map with a stakeholder communication plan.
This makes both ownership and reporting explicit from day one.
How to run a roles and responsibilities session
Atlassian's Team Playbook documents a structured exercise for this, sometimes run before a project kicks off.
The steps below follow that documented approach, with time estimates drawn from the source.