Part 1 · The Team Agreement

Your Team Agreement

Draft it yourself during the session. Take it to your team this week as a starting point, not a finished decision. Use it for a new tool or any change you need your team to adopt.

The change

What are we changing, and from when?

Why we're doing it

The problem in one sentence, and the real example from the last 30 days that proves it.

Our three agreements

Specific rules, not good intentions. “We always log client requests in the tool” beats “We'll be more consistent.”

Who owns it

Names, not teams.

What we're retiring

The old way we're switching off, and when it stops.

How we'll know it's working

One signal anyone can see, and the date we'll check.

Sign-off

I can live with this, and I will use it.

Part 2 · The Rollout Plan

Your Rollout Plan

Plan the people, not just the tool. Fill in who is affected, then the four steps that get them from announcement to habit.

Who this affects

List the four people or roles most affected. Name what changes for each of them, and be honest about what they may lose.

Person or roleWhat changes for themWhat they might lose or worry aboutWhat I'll do about it

Four steps

StepWhat we'll doWhoBy when
1. AlignWho gets a say before we announce, and who simply gets told? Talk to the “gets a say” people first.
2. AnnounceWhat will you say, who says it, and when? Lead with the problem, then the change.
3. SupportWhat will people need in the first two weeks: training, a champion, a place to ask questions?
4. ReviewAt day 14 and day 30, what's working, what isn't, and what do we change in the agreement?

An agreement isn't final until the people who live with it have had a say. Draft it here. Finish it together.

Haven't scored your decision yet? Start with your Tool Decision Score. Your answers stay in this browser unless you choose to share them. LGN Collaborations · lgncollab.com