# Strategy frameworks

> The eight framework presets Strategy Hub ships with, how the setup wizard recommends one, and how to tailor or build your own

Canonical: https://docs.caskcode.io/strategy-hub/strategy-frameworks/

Strategy Hub models your strategy as a hierarchy of **Strategic Items**, and a **framework** is a preset for that hierarchy. It defines the Types you can create—Objective, Key Result, Measure, and so on—how they nest, and the Statuses each level moves through. You pick a framework once, during the [setup wizard](https://docs.caskcode.io/strategy-hub/app-setup#run-the-setup-wizard), from eight presets that cover the common planning models. None of them is a ceiling: every preset is a starting point you can reshape, and you can build a fully custom hierarchy of your own.

## What a framework sets up

Choosing a framework seeds four things, so a new workspace is usable immediately:

- **Types** — the named levels of the hierarchy, each with its own icon, color, and key prefix.
- **Nesting rules** — which Types are allowed beneath which, so the structure stays valid as your team creates Items.
- **Status Sets** — the ordered Statuses each level moves through, split into a simpler set for high-level Items and a tighter one for execution-level Items.
- **Progress behavior** — how each level's value updates and rolls up, tuned to how that model actually works.

You choose from these presets on the wizard's first step. If you're not sure which fits, the step opens on a short conversation that recommends one for you — see [Choose a framework](https://docs.caskcode.io/strategy-hub/app-setup#choose-a-framework) in App setup.

## The eight presets

Each preset names its levels differently and nests them to match a planning model. The tree beside each one is the Type hierarchy it seeds, top to bottom—the same tree the setup wizard shows on its framework card. Find the closest fit; you can rename any level afterward.

### Simple OKR

![The Simple OKR Type tree: an Objective with a Key Result nested beneath it](media/strategy-frameworks-simple-okr.webp "w=272 float")

The lightest preset—two levels, with Key Results nested under the Objectives they measure. Each Objective's value rolls up from its Key Results, so progress on the measures moves the goal above them. It suits a small team putting structure on its goals for the first time.

### OKR

![The OKR Type tree: Strategy at the top, an Objective beneath it, and a Key Result below that](media/strategy-frameworks-okr.webp "w=272 float")

The full OKR model at three levels, adding a Strategy tier above Objectives. A Strategy holds one of the few priorities the organization is steering by; Objectives sit beneath it, and Key Results measure each Objective. Reach for it when you want day-to-day execution to ladder up to a handful of named strategic bets rather than a flat list of goals.

### OKR + KPI

![The OKR + KPI Type tree: Strategy, then Objective, with a Key Result and a KPI nested under the Objective](media/strategy-frameworks-okr-kpi.webp "w=272 float")

The three-level OKR hierarchy with one addition: a KPI sits alongside Key Results under an Objective. A Key Result is a time-boxed target for the quarter; a KPI is a standing metric you watch continuously, so pairing them lets an Objective carry both its push and its ongoing health signal. It fits data-driven teams that track operational numbers next to their outcome goals.

### OGSM

![The OGSM Type tree: Objective, then Goal, then Strategy, then Measure, each nested under the last](media/strategy-frameworks-ogsm.webp "w=272 float")

Objective, Goal, Strategy, and Measure captured as one cascading plan, four levels deep. The Objective states the ambition, Goals quantify it, Strategies are the chosen paths, and Measures track whether each path is working. Teams that like to see their whole strategy on a single page reach for OGSM.

### Hoshin Kanri

![The Hoshin Kanri Type tree: Breakthrough Objective, then Annual Objective, then Improvement Priority, then Target](media/strategy-frameworks-hoshin.webp "w=272 float")

A four-level cascade for long-horizon planning. Breakthrough Objectives set the multi-year ambition, Annual Objectives break it into the current year, Improvement Priorities name where to focus, and Targets make each priority measurable. The structure keeps every yearly plan tied back to the transformation it serves, which suits organizations driving a big, multi-year change through tightly aligned annual cycles.

### EOS (Traction)

![The EOS Type tree: 10-Year Target, then 3-Year Picture, then 1-Year Plan, then Rock](media/strategy-frameworks-eos.webp "w=272 float")

The Entrepreneurial Operating System's Vision-to-Traction ladder, from a 10-Year Target down through a 3-Year Picture and a 1-Year Plan to the quarterly Rocks a team commits to. Each level narrows the horizon, so long-range vision resolves into the few priorities that matter this quarter. It fits entrepreneurial teams that run on a short list of Rocks at a time.

### North Star

![The North Star Type tree: North Star Metric, then Input Metric, then Initiative](media/strategy-frameworks-north-star.webp "w=272 float")

A guiding North Star Metric, the Input Metrics that drive it, and the Initiatives that move those inputs. Unlike the OKR presets, North Star deliberately does not roll values up: an Input Metric drives the North Star Metric rather than summing into it, so each metric is tracked on its own. It suits product and growth teams steering by one leading number.

### 4DX (4 Disciplines of Execution)

![The 4DX Type tree: a Wildly Important Goal with a Lag Measure and a Lead Measure nested beneath it](media/strategy-frameworks-4dx.webp "w=272 float")

A single Wildly Important Goal with two kinds of measure beneath it. Lag Measures are the outcomes the goal is judged by; Lead Measures are the activities your team acts on each week to move them. The two are tracked separately—the Lead Measures don't pull the goal's value around—which keeps attention on the one or two goals that matter most.

## Make it your own

A preset is where you start, not where you're stuck. Everything a framework creates is editable under **Settings**, so most teams pick the closest preset and then reshape it:

- **Rename a level** to match your vocabulary—"Goal" instead of "Objective"—or change its icon and color.
- **Add or remove levels**, and set which Types are allowed beneath which, to deepen or flatten the hierarchy.
- **Edit the Statuses** and the sets they belong to, so the pills read in your reporting language.
- **Change how progress rolls up** at each level, from a value someone types in to one aggregated from nested Items or linked work.

You can also start from a preset and rework it into a hierarchy that matches no standard model at all—the presets are conveniences on top of a fully configurable structure, not a fixed menu. [Configure types and status sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets) walks through every one of these edits.

> **Tip** — pick the preset whose shape is closest to how you already plan, even if the names are off. Renaming levels is quick; rebuilding the nesting from an empty hierarchy is slower.

## Related

- [App setup](https://docs.caskcode.io/strategy-hub/app-setup) — where you choose a framework, get a recommendation, and run the rest of the setup wizard.
- [Configure types and status sets](https://docs.caskcode.io/strategy-hub/configure-types-and-status-sets) — reshape the Types, nesting, and Statuses a framework starts you with.
- [Statuses and progress](https://docs.caskcode.io/strategy-hub/statuses-and-progress) — what the Status Sets and progress behavior a framework sets up actually do.