Draft the escalation and check-in operating agreement
Drafts the team's start-of-engagement operating agreement — escalation norms, async vs. scheduled check-in rules, first-sprint rhythm, and how to flag blocked or behind.
In / outTeam composition + engagement timeline + working arrangement preferences → Drafted operating agreement (escalation criteria, async/sync norms, check-in cadence, blocked/behind protocols)
You might say…
“Everyone knows their workstream but no one knows when to ping me versus just handle it, or how to flag that they're behind without it becoming a big deal — I need that agreed at the start, not discovered mid-project.”
What it does
Drafts the team's start-of-engagement operating agreement — what counts as an escalate-vs-decide call, async-ping vs scheduled-check-in norms, the first-sprint check-in rhythm, and how to flag blocked/behind. Used once at engagement kickoff to set communication norms before the first check-in.
Trigger: Use once at engagement kickoff to set team communication norms before the first check-in cycle begins.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation