Complete firstOKR
Strategic outcome goals at company or team level are defined so that Goals in GIST align to them.
Without: Without a higher-level outcome anchor, Goals become locally optimized and GIST loses its strategic anchor.
RunsheetProduct Strategy
GIST Planning
ComplexityMedium
TimeWochen bis Monate je Goal
Participants3-10
FormatWorkshop + async
MaturityEstablished
01
Prerequisite
What needs to be finished first
02
Preparation
What needs to be ready before start
Materials
GIST board with four levels (Goals, Ideas, Step-Projects, Tasks) in a tool or on a wall; idea bank database (Notion, Airtable, or a custom table); prioritization framework (for example ICE); sprint board for tasks; cadence calendar (quarterly Goals, rolling Ideas, monthly Step-Projects, weekly Tasks).
People / roles
One owner per Goal (typically PM or Product Lead); team from PM, engineering, design; sponsor with outcome mandate; researcher (optional) for idea validation.
Pre-read
Strategic outcomes from the level above; existing roadmap or backlog items as conversion material; lessons learned from last quarter; outcome measurement infrastructure; team capacity.
Time needed
Initial setup 1-2 days, ongoing updates at different cadences per level
Setup
Set up four level boards. Keep Idea Bank columns for idea, hypothesis, goal link, ICE score, status. Fix cadences: Goal review quarterly, idea triage every two weeks, Step-Project monthly, Tasks weekly.
03
Core question
The one question this method answers
Which Goals will the team achieve in 12 months, which prioritized Ideas should it test next, and how do these move into deliverable Step-Projects?
04
Flow
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Goals (quarterly) | Half day per Goal review | Maximum 5 goals per team. Per Goal: outcome statement, measurable metric, baseline, target value, time horizon (typically 12 months). Derive from company OKR. Sponsor signs off. | Goals are not feature lists. If someone uses "launch X" as a goal, they are describing output. A goal is "activate 22% more users in 14 days," not "launch app." |
2Phase 2: Idea bank (continuously maintained) | 1-2 h weekly | Collect ideas per goal: hypotheses for how to achieve each goal. Each Idea includes hypothesis, expected effect, goal link, ICE score (Impact, Confidence, Ease). Target at least 20 Ideas per goal. | Teams with only 5 ideas per goal have too little optionality. Prefer 30 mediocre ideas and top selection over selecting 5 seemingly best ideas if three fail. |
3Phase 3: Step-Projects (monthly planning) | 1-2 h per Step-Project planning | Define top Ideas (by ICE or sponsor decision) as Step-Projects: deliverable in 2-6 weeks, with clear hypothesis, success criterion, and team allocation. One owner per Step-Project. | A Step-Project is an experiment, not a mini-release. If delivery takes 8 weeks, scope is too large. Split or drop it. |
4Phase 4: Tasks (weekly) | Sprint planning | Break Step-Projects into tasks. Keep sprint backlog as usual, but each task references a Step-Project and therefore a Goal. Keep tasks without Goal connection in a separate "Maintenance" category. | Tasks without goal connection quickly drift into maintenance and goal work gets crowded out. Set quarterly maintenance cap (for example 30%) and keep the separation visible. |
5Phase 5: Learning and idea update | 1 h after each Step-Project | Each Step-Project produces a learning report: confirm or disprove hypothesis, impact on Goal metric. Feed results back into Idea Bank: reprioritize ideas, promote validated ideas into larger projects, retire rejected ideas with rationale. | Without idea updates the Idea Bank becomes static and learning disappears. Expect 2-3 idea status updates per Step-Project. |
05
Artifact
What comes out at the end
Form
Four-level board or database with Goals (5), rolling idea bank, Step-Projects (monthly), and Tasks (weekly); visible links between levels; learning reports per Step-Project; outcome dashboard per Goal with baseline and trend.
Versioning / ownership
Create separate entry per quarter for each Goal with end score. Idea bank grows continuously with idea-level status history. Archive Step-Projects with learning report. Track tasks in normal sprint tracking.
Tool alternatives
- Notion with linked databases per level
- Airtable with table relationships
- Jira with custom issue types (Goal, Idea, StepProject, Task)
- Linear with projects as Step-Projects and cycles as tasks
gist-planning-working-template.md
Compact working template for GIST Planning with context, input, output artifacts, and next step.
GIST Planning Canvas
Context
What is this method used for?
Core question
Which question should be answered at the end?
Input
Which data, observations, or materials are available?
Working area
- Area 1:
- Area 2:
- Area 3:
- Relationships / patterns:
Output artifacts
- Goals:
- Idea bank:
- Step-project list:
- Tasks:
- Learning reports:
Open questions
- ...
Next step
Owner, date, success signal.
06
Example output
Concrete filled scenario, fictional example
gist-planning-beispiel.md
Concrete filled scenario, fictional example
GIST — Product team "Activation" Q3-2026 (18.05.2026)
Goals (3):
- G1: Activation rate for first-time installers from 22% to 38% in week 1. Baseline 22%, Owner @lisa.
- G2: Time-to-first-value from 7:40 to 3:00 minutes. Baseline 7:40, Owner @ben.
- G3: NPS day 7 from 14 to 30. Owner @anna.
Idea bank G1 (excerpt of 31 ideas):
- I-12: Wizard instead of slideshow for step 3. ICE 8/9/7 = 504. Status: Step-Project SP-7.
- I-19: Sample data at first use. ICE 7/6/8 = 336. Status: queued.
- I-23: Onboarding quiz instead of tutorial. ICE 6/5/4 = 120. Status: low.
- I-28: Inline support bubble after step 2. ICE 7/7/8 = 392. Status: Step-Project SP-8.
Running Step-Projects:
- SP-7 (Wizard Step 3): Hypothesis confirmed, 5/5 tests successful. Goal effect: 27% (+5pp). Learning report @anna 16.05.
- SP-8 (Inline support): Running, A/B test since 15.05, evaluation on 29.05.
- SP-9 (Tenant context templates): Setup, start 26.05.
Sprint 24 tasks: 4 tasks for SP-8, 2 for SP-9, 3 maintenance.
Idea update week 20: I-12 validated, I-19 in "queued" due to free capacity starting sprint 26. I-23 archived with low ICE.
Cadence: Goal review Q3 on 30.09., idea triage every second Wednesday, Step-Project planning at start of each month.
07
Pitfalls
Recognize symptoms and steer against them
Trap
Goals as outputs
Symptom
Goals state "launch feature X" or "three releases per quarter," and outcome linkage is missing.
What to do
Goal test: can I measure it without naming the output? If not, it is output; define the outcome underneath.
Trap
Idea bank is stagnant
Symptom
Idea bank has only 8 entries; new ideas are moved directly to Step-Projects or tasks.
What to do
Make it mandatory that every idea first goes into Idea Bank with hypothesis and ICE. Run triage weekly. Direct promotion is not allowed.
Trap
Step-Projects are mini-releases
Symptom
Step-Project delivers feature without hypothesis or learning report.
What to do
Definition: Step-Project must have a hypothesis and success criterion. A learning report is a mandatory artifact.
Trap
Tasks without goal link
Symptom
70% of sprint tasks are maintenance without visible goal connection.
What to do
Keep clear separation between goal work and maintenance. Set a quarterly cap for maintenance, for example 30%. If exceeded, escalate: what is consuming goal capacity?
Trap
ICE score becomes pseudo-science
Symptom
ICE scores are changed by gut feeling and no one documents confidence.
What to do
Treat ICE as rough orientation, not truth. Add confidence evidence (data points, research quotes) per idea. If confidence has no evidence, lower it.
Trap
Learning is lost
Symptom
Step-Project ends without a learning report and idea status stays open, knowledge dissipates.
What to do
Make learning report mandatory before Step-Project close. Reference Idea Bank updates. Sponsor reviews learning reports monthly, otherwise no next Step-Project.
08
Stop criteria
Done signals checkable in under a minute
No measurable outcome metric exists for goals, so GIST loses its measurement anchor.
Team is heavily output-driven with fixed delivery commitments; hypothesis-driven work is not possible.
No strategy exists one level above, so goals cannot be anchored.
Sponsor requires a fixed roadmap and does not accept GIST flexibility.
Capacity is not available for four cadences (quarterly/biweekly/monthly/weekly).
Team is primarily in maintenance, and goals and Step-Projects have no capacity.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.