Skip to content
Knowledge beta

Framing

Alignment Team Dynamics Facilitation Strategy Framework

Most alignment problems are not strategy problems. They are framing problems. Teams that cannot articulate what they are trying to accomplish, how they will know if it is working, and how they work together will struggle no matter how good their strategy is.

Overview

A frame is a living 1-2 page alignment document a team creates and maintains together. It bundles a statement of purpose, a short list of objectives with success measures, and the team’s working agreements into a single source of truth that anyone — team members, stakeholders, leaders dropping in — can point at. It replaces scattered Confluence pages, Slack threads, and tribal knowledge. The frame is not documentation; it is a working tool that shapes how the team spends its next week, and if the team can ignore it, it is not a frame yet.

The frame is the centerpiece of Nerd/Noir’s operating model, a seven-component system that connects vision and strategy to day-to-day execution. This page focuses on the frame itself: what goes in it, how it evolves, and how to scale it across teams.

Anatomy of a Frame

A frame is the document a team creates and maintains to stay aligned. It has required components that every team needs and optional components that add value in specific contexts.

Required

  • Statement of Purpose — one sentence describing why this team exists. “Our team exists to [what we do] so that [why it matters].”
  • Time Horizon — when the frame expires, usually 6-12 weeks. Shorter horizons force faster learning cycles.
  • Objectives and Success Measures — 1-3 specific goals for the current period, each with concrete indicators of progress. Objectives are aspirational but achievable; success measures are testable within the time horizon.
  • Working Agreements — how the team collaborates, makes decisions, and handles conflicts.
  • Community — who is involved: core team members, enablers providing coaching or expertise, collaborators from other teams, and stakeholders who care about outcomes and provide feedback.

Optional

  • Metrics — operational dashboards for process health (flow metrics, quality, team health, product data)
  • Strategies — key principles guiding decisions, often inherited from a higher-level team
  • Related Frames — connections to other teams’ frames (hierarchical, collaborative, or dependency-based)
  • Design Targets — personas or segments you are building for, and who you are intentionally not serving
  • Skills Matrix — team capabilities and learning objectives, valuable during skill-building phases
  • Constraints — budget, timeline, or regulatory limitations that shape your approach
  • Pivot Log — a record of significant changes to the frame, tracking learning velocity and decision patterns

Frame Lifecycle

Creation. A team builds its first frame in a 3-4 hour workshop. The facilitation sequence was refined through hundreds of immersive learning engagements, where framing kicked off every six-week coaching challenge. See the Frame Creation Workshop for the facilitation guide. The goal is a working frame that answers: why do we exist, what are we trying to accomplish, how will we know, and how do we work together?

Execution. The frame guides daily and weekly decisions. Check the pipeline daily, review progress on success measures weekly, and use objectives and strategies to evaluate incoming work. If objectives are not influencing daily decisions, the frame is not working yet.

Review and Refinement. Every 1-2 weeks initially, then monthly. Review success measures, assess whether working agreements are holding, check if objectives are still the right goals, and make small adjustments. See the Frame Review Meeting format in the Frame Creation Workshop.

Pivot. Major changes triggered by shifts in business priorities, significant team composition changes, or objectives proven impossible or irrelevant. Document the change, understand why, update affected components, communicate to stakeholders, and reset expectations.

Expiration. Two weeks before the time horizon ends, schedule a renewal workshop. Gather stakeholder feedback, assess what worked, document learnings, and build the next frame. Every frame expiration is an opportunity to refine purpose and recalibrate ambition.

Frame Patterns by Team Type

Product Teams. Stream-aligned teams building user-facing capabilities. Purpose focuses on user outcomes. Funnel is discovery-driven (user research, analytics, feedback). Objectives target user behavior or business metric changes. Pipeline includes both discovery and delivery work. Add Design Targets and Strategies as optional components.

Platform Teams. Teams providing foundational capabilities to other teams. Purpose focuses on developer experience and enablement. Funnel is request-based (tickets, capability requests). Objectives target adoption, reliability, and developer satisfaction. Funnels should identify higher-leverage work that enables more reuse. Working agreements include SLA definitions and support processes.

Leadership Teams. Senior decision-making groups. Purpose focuses on organizational outcomes and culture. Funnel is leadership-directed (strategic initiatives, organizational needs). Objectives are usually the highest-level OKRs. Pipeline includes decisions, resource allocation, and strategic initiatives. Success measures include team health and business metrics alongside revenue.

Enablement Teams. Teams focused on capability development and upskilling. Purpose focuses on skill building and practice improvement. Funnel manages coaching engagements and learning programs. Objectives target learning outcomes and practice adoption. Success measures track independent sustained improvement, not just workshop completion.

Scaling Frames

Small organizations (5-20 people). A single frame for the whole group. Informal relationship tracking. Weekly all-hands can serve as the work review.

Medium organizations (20-100 people). Frame per team or squad. Monthly cross-team relationship reviews. Quarterly leadership frame review. Departmental frames bridge leadership and teams.

Large organizations (100+ people). Hierarchical frames: team, department, division. Formal relationship documentation. Dedicated time for frame maintenance. Structured cascade and rollup processes.

Multi-team alignment works through three patterns: shared objectives (multiple teams commit to the same outcome), complementary objectives (teams have different but supporting goals), and sequential objectives (teams hand off outcomes to each other). Joint frame review sessions and aligned time horizons keep these patterns coherent.

Common Challenges

“Our objectives keep changing.” Usually signals unclear strategy or stakeholder misalignment. Establish clearer strategy principles, involve stakeholders in frame creation, and use shorter time horizons until stability improves.

“We cannot measure our success measures.” Start with leading indicators or proxy metrics. Include “establish measurement” as an objective if needed. Qualitative measures beat no measures. Focus on directional improvement rather than precise numbers.

“Leadership keeps bypassing our agreements.” A cultural and communication issue. Include leadership in frame review sessions, create an explicit escalation process for urgent work, and make the cost of constant reprioritization visible.

“Our frame feels like busywork.” The frame is not connected to real decisions. Connect objectives directly to current work, use the frame as a decision-making tool in team meetings, and simplify to focus on what actually matters. If a frame component is not influencing choices, drop it.

“We have too many dependencies.” Focus objectives on what the team controls. Create shared objectives with dependent teams. Include dependency management in working agreements. Break large objectives into smaller, less dependent pieces. See Dependency Management.

Resources