GIST Planning
Four-level planning from goals to daily tasks
GIST is a product planning framework with four levels: Goals (business and product outcomes), Ideas (hypotheses for achieving those goals), Steps (short validated experiments that test ideas), and Tasks (daily work). It replaces the traditional feature roadmap with an evidence-based planning stack where ideas must be tested before being committed to. The framework emphasises that most ideas are wrong — validation before investment is the core discipline.
Developed by Itamar Gilad, former product lead at Google and YouTube. Published on his blog in 2016 and expanded in his book 'Evidence-Guided' (2023). GIST was developed as a practical alternative to roadmap-centric product planning.
Use GIST Planning when
- ✓Teams wanting to move from a commitment-based roadmap to an evidence-based planning approach
- ✓Organisations where too many roadmap items ship without measurable impact
- ✓PMs wanting a structured connection from company strategy (Goals) down to daily work (Tasks)
- ✓Growth teams running many parallel experiments who need a framework for managing the pipeline
Avoid it when
- ✗Teams without measurement capability — GIST requires tracking outcome metrics per step
- ✗Fixed-scope projects or consulting engagements where the work is contractually defined
- ✗Very early-stage companies still discovering their goals — GIST assumes goals are clear
Key Concepts
Specific, measurable, time-bound company and product goals. Typically OKRs. Stable over 1–3 years at the company level; quarterly at the team level.
Hypotheses for ways to achieve the goals. Not commitments — most ideas will be tested and discarded. Ideas are held in an 'Idea Bank'.
Short (typically 1–10 week) experiments that test a specific idea with minimal investment. Each step validates or invalidates the idea.
The daily work required to execute the current step. Managed in sprint or Kanban boards.
A repository of all candidate ideas. Ideas are not scheduled until they pass minimum validation criteria.
Ideas in GIST are typically scored by Impact, Confidence, and Ease to prioritise which to test first.
How it works
Define company and team-level goals using OKRs or equivalent. Goals drive everything below them.
Collect ideas from customers, stakeholders, and the team. Score each with ICE. Prioritise the top ideas for step experiments.
For each prioritised idea, design the minimum experiment (step) that will provide enough evidence to decide whether to invest further.
Break each step into tasks. Use sprints or Kanban to manage daily work. Steps replace quarters as the unit of planning.
Tools that support GIST Planning
Industry standard for software development teams — most PMs will encounter Jira in their career
Exceptionally intuitive and visually clean interface — one of the lowest onboarding friction tools for non-technical teams
Highly visual and intuitive interface with color-coded boards — one of the easiest PM tools for non-technical teams to adopt
All-in-one platform replacing multiple tools — docs, whiteboards, goals, time tracking, chat, and project management in a single workspace
Unmatched flexibility as an all-in-one workspace — combines docs, wikis, databases, and project management in a single tool
Browser-based with no installation required — runs on any OS and enables instant sharing via URL, removing friction for cross-functional collaboration with PMs, engineers, and stakeholders
Best-in-class infinite canvas experience — the gold standard for collaborative whiteboarding with real-time multiplayer editing
De facto standard for workplace communication — most PMs will use Slack daily, and it appears constantly in job descriptions
Frequently Asked Questions
A traditional roadmap is a commitment: 'we will ship X in Q2.' GIST is an evidence pipeline: 'we have an idea, we will run a step experiment, and if it validates, we will invest further.' The roadmap tells stakeholders what you'll build; GIST tells them what you're learning. GIST requires a shift in stakeholder expectations from commitments to outcomes.
Goals in GIST map directly to OKRs. OKRs provide the Goals layer; Ideas are the hypotheses for achieving the Key Results; Steps are the experiments; Tasks are the sprint work. GIST operationalises OKRs by providing the planning structure below the goal level.
The key is shifting the conversation from 'what will you build?' to 'what will you learn?' Share the Idea Bank and Step results in quarterly reviews. Show which ideas were validated and invested in vs which were tested and discarded. Over time, the evidence trail builds stakeholder trust in the process.