Team Frame

Artifact Alignment Team Dynamics

A team frame is a living document that captures why a team exists, what it is trying to accomplish, and how it works together. This template provides two variants: a basic frame suitable for any team type, and an extended product team frame that adds design targets, strategies, and a discovery-oriented pipeline. Both follow the structure described in Framing.

Frames are intentionally brief; 1-2 pages maximum. If your frame is longer, you are over-documenting. The frame is a coordination tool, not a project plan. It should be referenced weekly and updated as the team learns. For guidance on facilitating a team through their first frame, see the Frame Creation Workshop. For the change management equivalent, see the Change Initiative Frame.

Basic Team Frame

# [Team Name] Frame
**Time Horizon:** [Start Date] - [End Date]

## Statement of Purpose
[One sentence: why this team exists and what it is working toward]

## Community
**Core Team:** [Names, roles, dedication %]
**Enablers:** [Who coaches or supports the team]
**Collaborators:** [Part-time contributors from other teams]
**Stakeholders:** [Who cares about outcomes and provides feedback]

## Objectives & Success Measures
1. **Objective:** [What you want to achieve]
   **Success Measure:** [How you'll know you're progressing]

2. **Objective:** [Second objective if needed]
   **Success Measure:** [Corresponding measure]

## Working Agreements
- **Meeting Rhythm:** [When and how you meet]
- **Decision Making:** [Who decides what]
- **Communication:** [How you stay aligned]
- **Definition of Done:** [When work is complete]

## Work Pipeline
**Backlog:** [Committed but not started]
**In Progress:** [Currently being worked]
**Done:** [Recently completed]

## Metrics Dashboard
- [Key operational metrics you track]

Product Team Frame

The product team variant extends the basic frame with components that support discovery-driven work: design targets to clarify who you are building for, strategies inherited from the product group, and a pipeline that includes discovery alongside delivery.

# [Product Team Name] Frame
**Time Horizon:** [Start Date] - [End Date]

## Statement of Purpose
We exist to [improve specific user experience] so that [user benefit / business outcome].

## Design Targets
**Primary Users:** [Who we are designing for]
**Non-targets:** [Who we are intentionally not serving]

## Community
**Core Team:** Product Manager, Designer, 2-3 Engineers
**Enablers:** User Research, Data Analytics
**Collaborators:** [Part-time contributors]
**Stakeholders:** [User segments], Sales, Customer Success

## Objectives & Success Measures
1. **User Outcome:** [User behavior change]
   **Success Measure:** [User metric improvement]

2. **Business Outcome:** [Business result]
   **Success Measure:** [Business metric change]

## Strategies
- [Key principles guiding decisions, inherited or team-specific]

## Working Agreements
- Weekly user research review
- Bi-weekly user testing sessions
- Feature decisions based on user evidence
- [Other collaboration agreements]

## Work Pipeline
**Discovery:** [Research, experiments, validation]
**Delivery:** [Features in development]
**Analysis:** [Measuring impact]

## Metrics Dashboard
- User engagement metrics
- Feature adoption rates
- User satisfaction scores
- Business conversion metrics

Resources

Framing — the framework these templates support
Change Initiative Frame — the equivalent template for change initiatives
Statement of Purpose — the exercise for drafting the purpose statement
Working Agreements — guidance on what to include in the agreements section