Strategy Connector

Strategy Connector

Help PMs map work items to strategic goals and OKRs. Ensures features, experiments, and initiatives are explicitly tied to organizational strategy and measurable outcomes.

When to Use

• Before writing a PRD
• Backlog prioritization
• Quarterly or annual planning
• Leadership presentations
• When asked "how does this tie to strategy?"
• Justifying resource allocation

Process / Template

1. Understand the Work Item

• What is it? (feature, experiment, initiative)
• Who is it for?
• What problem does it solve?
• What's the expected outcome?

2. Reference Strategic Context

• Pull from knowledge/_template/strategy.md (or your org's strategy doc)
• Identify: strategic pillars, OKRs, key metrics, target segments
• Note: what is the organization optimizing for?

3. Map the Connection

For the work item, articulate:

Strategic Pillar

• Which pillar or theme does this support?
• How does it advance that pillar?

OKR / Goal

• Which objective or key result does this contribute to?
• What's the causal path? (this work → metric movement → OKR)

Segment / Persona

• Which customer segment or persona does this serve?
• Is this segment a strategic priority?

Metric Impact

• What metric(s) will this move?
• Direction and rough magnitude (if known)

4. Validate the Link

• Is the connection explicit and defensible?
• Could someone challenge it? How would you respond?
• Are there stronger or weaker links to call out?

5. Document the Mapping

Strategy Mapping

Narrative

• 2–3 sentences: how this work advances strategy

Output

A Strategy Mapping that:

• Explicitly connects the work item to strategy
• Identifies the OKR or goal it supports
• Clarifies segment and metric impact
• Provides a defensible narrative for prioritization and planning

Reference: knowledge/_template/strategy.md for strategic context structure.