Skip to content

GFE OKR Breakdown Template

Template Type: Strategy Decomposition
Source: GFE Skill System OKR Definitions (/spec/okrs/OKR-{YEAR}-{Q}-{ID}.json)
Goal: Translate high-level objectives into executable KPIs, Processes, and Tasks.
Use with: .agent/workflows/create-okr-post.md


0. SCHEMA EXTRACTION GUIDE

Before writing, extract these fields from the OKR JSON:

Required Fields

json
{
  "id": "OKR-2025-Q1-01",
  "owner_role": "Head of Growth",
  "objective": "Increase net new ARR...",
  "key_results": [
    { "kpi_id": "KPI-REV-001", "target_change": "+25%", "period": "2025-Q1" },
    { "kpi_id": "KPI-CF-001", "target_change": "+10%", "period": "2025-Q1" }
  ],
  "notes": "Anchor OKR for lead to cash process..."
}

1. KPI Details (from /spec/metrics/): For each kpi_id in key_results[]:

  • Extract: name, description, valuation_link
  • Link: /blog/posts/[kpi-slug]

2. Related Processes (Reverse Lookup):

  • Search /spec/processes/*.json for any process where okrs[] contains this OKR ID.
  • Link: /blog/posts/[process-slug]

3. Related Tasks (Reverse Lookup):

  • Search /spec/tasks/**/*.json for any task where kpi_links[] matches any of the OKR's kpi_ids.
  • Link: /blog/posts/[task-slug]

1. ARTICLE STRUCTURE

Frontmatter

yaml
---
title: 'OKR: [Objective]'
slug: okr-[id-slug]
date: '[YYYY-MM-DD]T00:00:00.000Z'
description: >-
  [Objective]. Breakdown of Key Results, Execution Plan, and Valuation Impact for [Period].
author: GFE Strategy Lab
image: /images/blog/okr-[id-slug]-hero.png
alt: [Hero image description]
tags:
  - okr
  - strategy
  - [valuation_link items from KPIs]
sections:
  - gfe-systems
  - okrs
featured: false
aside: true
footer: true
traceability:
  valuationLayer: [primary valuation channel from KPIs]
  okrId: [this OKR ID]
  kpiIds: [array of kpi_ids]
  processIds: [array of related process IDs]
  taskIds: [array of related task IDs]
head:
  - - meta
    - name: robots
      content: 'index, follow'
  - - meta
    - property: 'og:title'
      content: 'OKR: [Objective]'
  - - meta
    - property: 'og:description'
      content: >-
        [Objective]. Breakdown of Key Results and Execution Plan.
  - - meta
    - property: 'og:image'
      content: '/images/blog/okr-[id-slug]-hero.png'
  - - meta
    - property: 'og:type'
      content: 'article'
---

Section 1: Hook — The Strategic Intent (150-200 words)

Purpose: Explain why this objective matters right now.

Template:

markdown
# OKR: [Objective]

**Owner:** [Owner Role]  
**Period:** [Period]

Strategy is useless without execution. This OKR (`[OKR ID]`) bridges the gap between the board's valuation targets and the daily work of the pods.

The goal is clear: **[Objective]**.

But "increasing ARR" isn't a task—it's an outcome. To achieve it, we must decompose it into measurable Key Results and specific execution workflows.

::: tip Strategy Stats
- **Key Results**: [Count]
- **Valuation Impact**: [List Valuation Layers]
- **Primary Process**: [Main Related Process]
:::

![OKR visualization](/images/blog/okr-[id-slug]-hero.png)

---

Section 2: Key Results Breakdown (300-400 words)

Purpose: Detail the specific metrics that define success.

Template:

markdown
## Key Results (The Scorecard)

We measure progress against this objective via [Count] Key Results:

[For each KR in `key_results[]`:]

### KR [N]: [Target Change] in [[KPI Name]](/blog/posts/[kpi-slug])
- **Metric:** [[KPI Name]](/blog/posts/[kpi-slug])
- **Target:** [Target Change]
- **Why:** [Brief explanation of why this metric matters for the objective]

---

Section 3: Execution Plan (The "How") (400-500 words)

Purpose: Link the OKR to the Processes and Tasks that will actually drive it.

Template:

markdown
## Execution Plan (The "How")

You cannot "manage" an OKR. You can only manage the work that drives it.

### Core Processes
This OKR is primarily delivered by the following workflows:

[For each related Process:]
- **[[Process Name]](/blog/posts/[process-slug])**: [Brief description of how this process moves the KRs]

### Critical Tasks
The following atomic tasks are the highest-leverage activities for this quarter:

[For each related Task (Top 3-5):]
- **[[Task Title]](/blog/posts/[task-slug])**: [Brief description]

---

Section 4: ValuationOps Impact (200-300 words)

Purpose: Tie the OKR to enterprise value.

Template:

markdown
## ValuationOps Impact

Achieving `[OKR ID]` directly strengthens the **[Valuation Layer]** of the business.

**The Value Chain:**
1. **Strategy**: We set the objective to [Objective].
2. **Execution**: Pods execute [Process Name].
3. **Result**: [KPI Name] moves by [Target Change].
4. **Valuation**: [Valuation Impact explanation].

::: warning Law 1: Time Is the First Balance Sheet
We are investing [Period] of time into this OKR. The return on that time *is* the valuation lift.
:::

---

Section 5: Traceability Chain

Template:

markdown
## Traceability Chain

**ValuationOps Layer:** [[Layer Name]](/blog/posts/[layer-slug]) *(coming soon)*  

**Related Processes:**
[For each Process:]
- [[Process ID]: [Process Name]](/blog/posts/[process-slug])

**Component KPIs:**
[For each KPI:]
- [[KPI ID]: [KPI Name]](/blog/posts/[kpi-slug])

---

Section 6: FAQ (3-5 Questions)

Template:

markdown
## FAQ

**Q: Who is accountable for this OKR?**  
A: The [Owner Role] is accountable for the outcome, but the execution is distributed across [Domains].

**Q: What happens if we miss a Key Result?**  
A: We analyze the *Process* failure. Did we execute the tasks but the tasks didn't move the needle (Strategy failure)? Or did we fail to execute the tasks (Execution failure)?

**Q: How often do we review progress?**  
A: Weekly during the [Process Name] alignment lab.

---

2. WRITING GUIDELINES

Tone Strategy

Strategic & Directive:

  • Focus on alignment and focus.
  • Use terms like "North Star," "Leverage," "Accountability," "Execution Gap."
  • Emphasize that OKRs are not a wish list; they are a contract for resource allocation.

Visuals:

  • Hero image should be abstract and aspirational (e.g., "North Star," "Mountain Peak," "Compass").

3. IMAGE GENERATION

Subject Formula:

  • "Abstract representation of [Objective] with upward momentum"
  • "Compass or North Star visualization"
  • "Strategic map with a clear destination"

Base Prompt:

Minimalist 3D relief illustration on off-white background. Muted teal (#1AA8A0) accent. Subject: [SUBJECT]. Composition: central focus, upward trend, clean lines, negative space. Typography: "[Short Objective]" in clean sans, dark slate. Lighting: soft top-front. 16:9 aspect ratio.

Save To: docs/public/images/blog/okr-[id-slug]-hero.png


4. FINAL CHECKLIST

  • [ ] OKR schema extracted
  • [ ] Key Results mapped to KPIs
  • [ ] Related Processes identified (Reverse Lookup)
  • [ ] Related Tasks identified (Reverse Lookup)
  • [ ] Valuation logic explained
  • [ ] Hero image generated

End of Template