GIST Planning Cadence: Managing Multi-Cadence Cycles

Set the GIST planning cadence for each layer: yearly goals reviewed quarterly, an always-open idea bank, steps reprioritized each sprint, daily tasks.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

The GIST planning cadence is what makes the GIST Planning Framework agile at every level. Itamar Gilad designed the four layers to change at different speeds, and in the original article he gives each one its own planning horizon (HackerNoon copy). Goals are set for a horizon of a year or more, defined at the start of the year, and evaluated and adjusted every quarter. Ideas are constantly collected and prioritized. Step-projects are defined at the start of the quarter, and the quarterly list is reprioritized every 1-2 weeks in sync with task iterations. Tasks are planned in 1-2 week iterations, such as Scrum sprints, and adjusted daily.

Multi-cadence product planning solves a problem most teams feel but rarely name. When every layer is planned at the same time, usually in a big quarterly planning event, the plan is either too rigid to absorb what the team learns or so unstable that goals change every sprint. Gilad's diagnosis of classic roadmaps is that changes at the top cause huge ripple effects of replanning and cancelled projects (GIST Framework). Separate cadences keep the slow layers stable and let the fast layers move.

The cadences are linked through one artifact, the GIST board. Gilad uses it in weekly or bi-weekly team meetings, working left to right from goals to ideas to steps, and changes happen on the spot: ICE scores are updated from experiment results, failed ideas are removed with their steps, and new ideas take their place (The GIST Board). That meeting is the heartbeat of the system.

The output of this skill is a cadence calendar for the team: which review happens when, who attends, what each review decides, and how decisions flow between layers. It replaces the single quarterly planning marathon with a set of short, regular rhythms.

How It Works

Each layer has a natural speed set by how quickly its information changes. Goals depend on strategy and on metrics that move over months, so reviewing them weekly only adds noise. The OKR practice GIST borrows from also runs on quarterly cycles, as the What Matters guide notes. Tasks depend on what the team discovered yesterday, so they need daily attention. Ideas and steps sit in between.

The idea layer is continuous but still needs set moments. New ideas can arrive at any time, and Gilad's ICE guide lists the moments to calculate or update scores: when triaging a new idea, when choosing ideas to work on, when new evidence arrives, and during periodic reviews of the bank. He also suggests going through the parked ideas every few months. In practice that means a short weekly intake plus a deeper review around each quarterly goal cycle.

The step layer runs on the weekly or bi-weekly board review. Steps are chosen at the start of the quarter, but the list is reprioritized every one or two weeks as results come in. Aligning this review with sprint planning keeps the tasks in each sprint pointed at the current steps.

The task layer runs on whatever the team already does. The Scrum Guide sets sprints at one month or less and the Daily Scrum at a 15-minute event. GIST adds nothing here except the link from each task to its step.

Changes flow between layers at set points. A task-level surprise goes to the step owner the same day. A step result changes the idea's score at the next board review. A pattern of results that questions a goal goes to the quarterly goal review, unless it is serious enough to call an unscheduled one. That rule keeps the fast layers from constantly reopening the slow ones, while making sure important evidence still reaches the top.

Step-by-Step Guide

Step 1: Map your current planning meetings

List every planning meeting the team has now: quarterly planning, roadmap reviews, sprint planning, standups, backlog grooming. For each, note which GIST layer it actually serves. Most teams find several meetings mixing layers and no regular meeting for ideas or steps.

Step 2: Set the goal cadence

Schedule the yearly goal-setting session and a quarterly goal review. At each quarterly review, check progress on every goal, adjust targets, retire goals that no longer fit and add new ones from strategy. Keep goals fixed between reviews unless strategy changes.

Step 3: Set the idea cadence

Set up a short weekly intake where new ideas are triaged, scored roughly and given a status. Add a deeper idea review before each quarter, where candidates are re-scored against the goals and a working set is chosen. Put a recurring reminder to review the parked list every few months.

Step 4: Set the step review

Hold a GIST board review every week or two, timed to fit just before sprint planning. Walk the board left to right, update ICE scores from step results, drop failed ideas, bring in new ones and plan the next steps. Keep it short and focused on decisions.

Step 5: Keep the task rhythm

Leave the team's sprint planning, standup and retrospective as they are. The only changes are that sprint planning pulls tasks from the current steps and that each task is tagged with its step. Surprises at standup that affect a step go to the step's owner.

Step 6: Build the cadence calendar

Put all the reviews on one calendar with owners, attendees and the decision each one makes. Share it with stakeholders so they know when goals and plans can change. A shared calendar prevents the old habit of reopening goals in any meeting.

Step 7: Agree how changes cross layers

Write down the rules: what triggers an unscheduled goal review, how step results update the idea bank, and who can add or remove a step between board reviews. Keep the rules short. Their purpose is to make changes predictable.

Step 8: Pilot and adjust

Run the new cadence for one quarter and check at the end whether each review made real decisions. Merge or drop reviews that never decide anything, and shorten ones that run long. Adjust the rhythm to how fast your market and your evidence actually change.

Best Practices

• Match each cadence to how fast its information changes. Goals move slowly, tasks daily, and ideas and steps in between.
• Tie the board review to sprint planning, as Gilad's original article does by reprioritizing steps in sync with task iterations.
• Make each review decide something. A review that only reports status can be replaced by a written update.
• Keep goals stable between quarterly reviews. Frequent goal changes make every step's evidence harder to interpret.
• Show the board to stakeholders on a regular rhythm. Gilad suggests they see it regularly, even if that means sending photos weekly (The GIST Board).
• Protect the idea intake in busy weeks. When it stops, untriaged ideas pile up and people stop submitting.

Common Mistakes

• Planning every layer in one quarterly event: A single planning marathon fixes steps and tasks for months and ignores what the team learns. Spread decisions across the layer cadences.
• Reviewing goals too often: Monthly goal debates make the plan unstable. Hold them quarterly, with a clear trigger for exceptions.
• No regular step review: Without a board review every week or two, failed ideas keep consuming sprints. Put the review on the calendar before sprint planning.
• Letting tasks drive goals: A single surprise in a sprint should not reopen a goal. Route it through the step and idea layers first.
• Adding meetings without removing old ones: GIST reviews replace roadmap reviews and grooming sessions that mixed layers. Retire the old meetings or the team will resent the new ones.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: GIST Planning Framework

Related Skills

• Defining Measurable Product Goals in GIST
• Building a Product Idea Bank for the GIST Ideas Layer
• Breaking Step-Projects into Daily Tasks
• Replacing Your Product Roadmap with GIST

Sources

• HackerNoon: the original GIST Planning article
• Itamar Gilad: GIST Framework
• Itamar Gilad: The GIST Board and Other GIST Tools
• Itamar Gilad: ICE Scores, All You Need to Know
• What Matters: OKR meaning and definition
• The 2020 Scrum Guide

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.