Team Design Canvas

Purpose & Outcomes

Describe why the team exists and the outcomes that will show success.

• Prompt: What problem do we solve and for whom?
• Prompt: Name 2–3 primary outcomes we must deliver in the next 6–12 months.
• Example: "Deliver a stable payments integration reducing failed transactions by 50% for e-commerce partners."

Measures of Success

Choose 3–5 measurable indicators that show progress toward outcomes.

• Prompt: What metrics will tell us we are succeeding? (quality, time, cost, engagement)
• Example: "Payment success rate, mean time to resolve payment incidents, partner satisfaction score."

Primary Stakeholders

List internal and external stakeholders and their top expectation.

• Prompt: Who needs this team to succeed? What do they expect?
• Example: "E-commerce product owner — reliable volume support; Finance — accurate settlement reports."

Roles & Accountabilities

Define the core roles (not necessarily job titles) and the accountabilities for each role. Use short role names and one-line accountabilities.

• Prompt: Who is responsible for delivery, who supports, who approves?
• Example roles:
  • Team Lead — owns roadmap, priorities, stakeholder alignment.
  • Engineer — implements features, owns code quality.
  • Operations — owns deployment and monitoring.
• Tip: Consider a lightweight RACI mapping for 3–5 critical decisions (see Decision Rights).

Decision Rights

Clarify who decides what, and what decisions need broader approval.

• Prompt: For product scope, technical architecture, vendor selection, who is Accountable and who must be Consulted or Informed?
• Example: "Production releases — Team Lead (A), Engineering (R), Security (C), Product (I)."

Communication Rhythms & Tools

Specify meeting cadence, core channels, and their purpose so people know where to go for what.

• Prompt: What regular meetings will we have (daily standup, weekly planning, monthly reviews)?
• Prompt: Which channels are for async updates vs. decisions?
• Example: "Standup — 15m daily for blockers; Planning — 2 hours biweekly for scope; #team-channel for async updates; Jira for work tracking."

Dependencies & Handoffs

Identify upstream and downstream partners, data or deliverables you depend on, and expected SLAs.

• Prompt: Who do we wait on and who waits on us? What does 'ready' look like for a handoff?
• Example: "Depends on Data Team for nightly batch (SLA: by 6am); provides feature flag toggles to Ops within 24 hours of request."

Working Agreements

Write short norms that guide behavior. Keep them actionable and reviewable.

• Prompt: How do we handle missed deadlines, conflict, and urgent incidents?
• Example agreements:
  • "We keep JIRA updated before standup."
  • "Major incidents: team responds within 30 minutes and posts a status update every 60 minutes."
  • "If you disagree on a technical approach, propose an experiment and test it for two sprints."

Risks & Mitigations

List the top 3–5 risks that threaten your outcomes and a short mitigation plan for each.

• Prompt: What could prevent us from delivering and how will we reduce that risk?
• Example: "Risk: Key vendor delay. Mitigation: maintain backup vendor and freeze non-essential scope."

30 / 60 / 90 Onboarding Checklist

Concrete, time-boxed milestones to help new members become productive and aligned.

1. First 30 days — Learn & Observe
   • Access to systems, accounts, and repositories
   • Meet primary stakeholders and read key docs (roadmap, metrics)
   • Shadow an operating cadence (standup, planning)
   • Complete a small scoped task and get feedback
2. Next 60 days — Contribute & Own
   • Deliver a planned increment or feature
   • Own a recurring work item or technical area
   • Suggest at least one improvement to a working agreement or process
3. By 90 days — Integrate & Improve
   • Lead a planning session or retrospective
   • Demonstrably improve a metric or reduce a friction point
   • Document handoffs and onboarding notes for future hires

Facilitation tips & versioning

• Timebox the workshop: 30 minutes for small teams, up to 90 minutes for larger groups.
• Keep entries brief and testable (avoid vague language like "improve collaboration").
• Record Owner, Date, and Version at the top of the canvas. Schedule a follow-up at 30 days.

Examples & Next steps

After filling the canvas, turn the measures into a short KPI list and add the 30/60/90 items to the onboarding checklist in your team's workspace. Treat the canvas as a living artifact: update it when roles change or when you run a major retrospective.