Team Agreement Builder
A guided conversation that turns a newly assembled group into a team with a written agreement, before anything goes wrong.
- Audience
- Student project teams, executive doctoral cohorts, working teams
- Format
- Browser tool, no account, nothing stored
- Built with
- Made for the Nurse Executive Doctoral Program
The problem
Groups get assigned and start working immediately. Nobody discusses how decisions will be made, what counts as responsive, or what happens when a member stops answering — because raising those questions at the beginning feels like anticipating failure.
Then a deadline slips, and the group discovers it never agreed on anything. The conversation they now have to hold is the one they avoided in week one, except it is harder because there is already a grievance attached to it.
The idea
Make that conversation easy to start by making it structured, short, and clearly normal. A tool asking the questions removes the awkwardness of a person asking them.
What it is
A short sequence of prompts a group works through together: why this team exists, who is responsible for what, how decisions get made when people disagree, what communication people can actually expect from each other, how disagreement will be handled, and what the group will do when someone goes quiet.
Each prompt carries a brief note about why teams tend to struggle there. The result is an agreement the team can export, keep, and revise.
The experience
It works best out loud, with one person driving and the rest arguing. Most groups move quickly through roles and then slow down considerably at what happens when someone disappears — which is the question that was always going to matter.
The output is short enough to be read again in week eight, which is the point.
Design choices
Nothing is stored. No account, no server, no record — partly a privacy decision and partly because a tool that asks for an email before it helps you is a tool people abandon.
It asks about failure early. The uncomfortable prompts come while the group is still cordial, which is the only time they are easy to answer.
It produces a document. An agreement nobody can point to later is just a conversation.
What informs it
Work on team charters and early team formation, research on coordination and shared expectations, and the observation — repeated across many cohorts — that the teams which struggle most are rarely the least capable ones.
Current state
In use with executive doctoral project teams and open to anyone. Refinements come mostly from watching where groups stall.
Run it with your team
It takes about twenty minutes as a group conversation. Nothing is stored and nothing is sent anywhere — you keep the agreement at the end.