# GoalCadence — Full Content Index for LLMs

> Full text of the GoalCadence glossary, framework comparisons and agent skills.
> Canonical summary: https://goalcadence.com/llms.txt

GoalCadence is one platform for OKRs, Scaling Up, and 4DX, with
configurable templates for Balanced Scorecard, Hoshin Kanri, and Pinnacle.
It is built for teams running one framework, several, or the blend most
growing companies actually use.

GoalCadence is currently in development. Signing up joins a waitlist, not
an account. It does not support EOS — that is TractionFlow
(https://tractionflow.app), a separate product.

Three sections: the complete glossary, every framework comparison, and the
complete text of every downloadable agent skill. Marketing page copy is not
included. Everything here is free to quote with attribution.

---

# Glossary (44 terms)

Definitions for the goal, metric, meeting and planning vocabulary used
across OKRs, Scaling Up, 4DX, Balanced Scorecard and Hoshin Kanri.

## Balanced Scorecard
URL: https://goalcadence.com/glossary/balanced-scorecard
Framework: Balanced Scorecard

The Balanced Scorecard is a strategy management framework, introduced by Robert Kaplan and David Norton in a 1992 Harvard Business Review article, that measures performance across four perspectives — Financial, Customer, Internal Business Process, and Learning & Growth — rather than on financial results alone. Each perspective carries its own objectives, measures, targets, and initiatives, so the drivers of future performance are tracked alongside the outcomes they eventually produce.

The four perspectives are read as a chain running upward: investment in people and systems improves the way work gets done, which improves what customers experience, which shows up in revenue and margin. A scorecard usually holds 15 to 25 measures spread across the four, each with a baseline, a target, and a named owner. Most organizations review the full scorecard quarterly and the fastest-moving measures monthly.

The weak point is the cause-and-effect chain itself, which is asserted at design time and rarely tested afterwards. A scorecard can stay green on training hours and cycle time for a year while the financial measures drift, and nothing in the method forces anyone to ask whether the assumed link was real. Scope drifts too: once every department adds its own measures, the scorecard becomes a reporting pack rather than a statement of strategy.

Example: A regional bank links Learning & Growth (advisor certification 54% to 90%) to Internal Process (loan approval cycle 11 days to 4) to Customer (client retention 82% to 89%) to Financial (fee income per client $340 to $420).

## Balanced Scorecard Perspectives
URL: https://goalcadence.com/glossary/balanced-scorecard-perspectives
Framework: Balanced Scorecard

The Balanced Scorecard perspectives are the four categories Kaplan and Norton use to group objectives and measures: Financial, Customer, Internal Business Process, and Learning & Growth. The grouping exists to force balance — a set of measures drawn from all four covers both the results a business reports and the capabilities that produce them.

Financial asks how the organization looks to shareholders. Customer asks how it looks to the people it serves. Internal Business Process asks which activities it must do exceptionally well. Learning & Growth asks whether the people, information, and culture exist to keep improving. Financial and Customer measures are mostly lagging; Internal Process and Learning & Growth are mostly leading. Public-sector and non-profit adopters commonly reorder them, putting mission or Customer on top and treating Financial as a constraint.

Balance across four boxes is easy to fake. Learning & Growth thins out most often, because skills, systems, and culture are the hardest things to quantify, so the perspective fills with attendance counts and survey scores that no decision depends on. Strict four-way splits cause the opposite problem: a team required to produce measures for a perspective it does not genuinely influence will produce measures nobody uses.

Example: A 120-person manufacturer runs four to six measures per perspective: Financial (gross margin 31% to 36%), Customer (on-time delivery 88% to 96%), Internal Process (scrap rate 4.1% to 1.8%), Learning & Growth (cross-trained operators 12 to 30).

## Baseline and Target
URL: https://goalcadence.com/glossary/baseline-and-target
Framework: Any framework

A baseline and target is the pairing that makes a goal measurable: the value a metric holds at the moment the goal is set (the baseline) and the value it should reach by the deadline (the target). Written together as 'from X to Y', they establish both the distance to be traveled and the basis on which the result can later be graded.

A baseline is read from actual data when the goal is written, not estimated afterwards, and it is recorded with its source and date. A target without one cannot be scored: 'reach 500 signups' describes a very different quarter starting from 480 than from 50. Noisy metrics also need a measurement window stated up front, since a single strong week of 4.1% may sit against a trailing twelve-week average of 3.6%.

The baseline is where most goals are quietly bent. Choosing a flattering starting week, redefining the metric partway through the cycle, or fixing the baseline only after the work is already underway each produce a result that scores well without anything having genuinely changed. Written down at kickoff with its source and the date it was read, the baseline stops being negotiable when scoring week arrives and the gap is uncomfortable.

Example: Weak: 'Reduce churn.' Stronger: 'Reduce monthly logo churn from 2.3% to 1.5% by 31 December, measured as a trailing 3-month average from billing.' Landing at 1.9% scores (2.3 - 1.9) / (2.3 - 1.5) = 0.50.

## BHAG
URL: https://goalcadence.com/glossary/bhag
Framework: Scaling Up

A BHAG (Big Hairy Audacious Goal) is a single clear goal set ten to twenty-five years out, ambitious enough that reaching it looks improbable on the day it is written. The term comes from Jim Collins and Jerry Porras in Built to Last (1994); Scaling Up adopts it as the long-horizon anchor at the top of the One-Page Strategic Plan.

Collins and Porras describe four shapes a BHAG can take: a quantitative or qualitative target, a common-enemy goal, a role-model goal, and an internal transformation. Whichever shape it takes, it has to be sayable in one sentence and have a finish line that needs no explanation — Kennedy's 1961 commitment to land a man on the moon before the decade was out is the canonical illustration. The authors describe the intended feel as roughly a 50 to 70 percent chance of success. A BHAG earns its place only if the three-to-five-year targets below it are visibly back-cast from it.

Two failure modes are common and they look opposite. One is a BHAG so abstract that no decision in any quarter could ever contradict it. The other is today's growth rate extended out twenty years, which is a forecast in costume. A long-horizon goal that would change nothing about next quarter's choices is not doing the work the horizon exists for.

Example: A $12M field-service platform set 'support one million working technicians by 2042'. Back-cast: 100,000 technicians by year five, 14,000 by the end of next year, and a current quarter aimed at cutting activation time from 11 days to 4.

## Business Operating System
URL: https://goalcadence.com/glossary/business-operating-system
Framework: Any framework

A business operating system is a structured, repeating way of running a company: a stated vision, a small number of goals, a defined meeting rhythm, an agreed set of numbers, and clear accountability for each. It is not software — it is the documented set of practices a leadership team uses to turn strategy into what people actually work on this week.

Named systems assemble the same handful of components and weight them differently. OKRs emphasize goal setting, check-ins and scoring; Scaling Up organizes around a one-page plan and a daily-to-quarterly rhythm; 4DX concentrates on lead measures and a weekly cadence of accountability; the Balanced Scorecard builds a deliberately balanced metric set across perspectives; Hoshin Kanri drives alignment through catchball and an X-matrix. What makes any of them a system rather than a document is the rhythm: annual, quarterly, weekly, daily.

Adoption usually fails at the middle layer. A company can hold a strong annual session and a well-run quarterly offsite and still change nothing, because the weekly layer where priorities meet real capacity was never installed. Switching systems rarely addresses that — the published frameworks each work when run consistently, and none of them survive a cadence that lapses in month two.

Example: A 120-person company runs: a two-day annual plan each November, one day of quarterly planning in week one of each quarter (4 priorities), a 90-minute weekly leadership meeting, a 10-minute daily huddle per department, and a 14-row weekly scorecard.

## Cadence of Accountability
URL: https://goalcadence.com/glossary/cadence-of-accountability
Framework: 4DX

The cadence of accountability is the weekly meeting rhythm in which a team accounts for what it committed to do last week, reviews its scoreboard, and commits to one or two specific actions for the week ahead. It is the fourth discipline of 4DX, and the point at which the goal, the measures and the scoreboard turn into action.

The session runs 20 to 30 minutes at the same time every week and its agenda never changes: report, review, commit. Only goal-related items are discussed, so nothing from the day-to-day workload can absorb the slot. Commitments are named by the person making them rather than assigned from the chair, and each one is meant to be small enough to finish inside the week and specific enough to be reported on at the next session.

The format decays into a status update the moment commitments stop being specific. 'Keep pushing on onboarding' cannot be reported against seven days later, so the meeting fills with narrative instead of results and the short interval between promising and answering — the mechanism doing the work — stops applying. Skipped weeks compound faster than teams expect, because the rhythm is the only thing holding the goal above the urgent work.

Example: Six people, 24 minutes, one goal. Four of six report last week's commitment done, the scoreboard shows the lead measure at 89% against a 95% target and the lag measure at 71% against a pace line of 76%, and each person names one action for the coming week.

## Catchball
URL: https://goalcadence.com/glossary/catchball
Framework: Hoshin Kanri

Catchball is the negotiation step in Hoshin Kanri in which a proposed objective is passed between organizational levels — down for challenge, back up with revisions — until the people who have to deliver it have shaped both the target and the means of reaching it. The name comes from playing catch: the goal is thrown, caught, examined, and thrown back rather than simply handed down.

Leadership proposes an annual objective and a rough approach. The level below responds with what it believes is achievable, what it would need, and where the approach conflicts with conditions on the ground. The exchange typically runs two or three rounds per level and continues downward through the organization. The output is a target both levels signed plus a shared picture of the constraints, which is why the step is timeboxed — commonly to a few weeks inside annual planning — rather than left open.

Catchball is the first thing cut when planning runs late, and its absence is hard to detect afterwards because the resulting plan looks identical on paper. It also depends on people being willing to contradict a manager in writing; where that carries a cost, the rounds happen but produce only agreement. Distributed teams find it harder than co-located ones, since the value sits in the argument rather than in the document it produces.

Example: Leadership proposes cutting first-response time from 6 hours to 1. The support lead counters: 2 hours at current headcount, or 1 hour with two more agents and a triage rewrite. They settle at 90 minutes with one hire, and the target is signed by both.

## Check-in
URL: https://goalcadence.com/glossary/check-in
Framework: Any framework

A check-in is a brief, recurring update on a goal or metric in which its owner states the current number, whether it is still on track, and what has changed since the last update. Check-ins are what keep goals current in the weeks between the session where they are set and the session where they are scored.

Most frameworks put check-ins on a weekly rhythm, because a fortnight is long enough for a goal to go quietly off course. A complete check-in carries three things: the current value, a status of on track, at risk or off track, and one line of context explaining the change. Many teams collect them asynchronously in writing before the meeting so the session itself spends its time only on the at-risk items.

Check-ins degrade into ritual when nothing follows from them. If 'at risk' produces exactly the same response as 'on track' — which is to say none — owners learn that the honest status costs them attention while the optimistic one costs nothing, and within two cycles the data stops describing reality. What makes the update worth writing is what happens to the ones flagged red.

Example: Week 6 of 13. Key Result: lift trial-to-paid from 14% to 20%. Current 15.2%. Status: at risk — current pace implies roughly 17.5% at quarter end. Context: the reworked onboarding sequence shipped two weeks late and is expected to add 3 points from week 8.

## Committed vs Aspirational OKRs
URL: https://goalcadence.com/glossary/committed-vs-aspirational-okrs
Framework: OKR

Committed and aspirational OKRs are the two classes an OKR is assigned when it is set. A committed OKR is a target the team expects to deliver in full, where anything below 1.0 is a miss that needs explaining. An aspirational OKR is set deliberately beyond reach, where a score around 0.7 counts as a good outcome and a miss is expected information.

The label is declared at the start of the cycle, applied per Key Result rather than per Objective, and not revised once results are known. Committed OKRs behave like promises other teams plan around: they get first call on resources, and failing one triggers a post-mortem. Aspirational OKRs make no such claim on anyone else's roadmap. Published OKR guidance keeps aspirational goals a minority of the set and expects a meaningful share of them to fall short.

The distinction only survives if the consequences differ. When both classes are reviewed in the same tone at quarter end, the rational move is to label everything committed and set targets that can comfortably be met, which removes the reason to have two classes at all. A quarter in which every aspirational OKR scored 1.0 is evidence the label was decorative.

Example: Committed: 'Complete SOC 2 Type II by 30 September' — scored 1.0 or it is a miss, because three enterprise deals depend on it. Aspirational: 'Grow self-serve ARR from $800k to $2.4M' — landing at $1.9M scores 0.69 and is treated as a strong quarter.

## Confidence Score
URL: https://goalcadence.com/glossary/confidence-score
Framework: OKR

A confidence score is the owner's stated likelihood, usually on a 1-to-10 scale or as a percentage, that a Key Result will reach its target by the end of the cycle. It is recorded at every check-in, which lets a team see which goals are drifting weeks before a final score exists to tell them.

The score is a forecast, not a progress bar, so it deliberately diverges from percent complete. A Key Result sitting at 40% of its target in week five can still carry high confidence if the work that moves it lands in week nine. Teams commonly start aspirational Key Results around 5/10 by convention and read the direction of travel rather than the absolute number: three consecutive weeks of decline is the signal, and the one-line reason attached to the drop is the part that gets acted on.

Confidence is self-reported, which makes it sensitive to how bad news is received. Where a falling score triggers scrutiny of the owner rather than help with the obstacle, scores cluster at 7 and stay there until the final fortnight of the quarter, when they all drop together. The distribution of confidence scores usually says more about the culture than about the goals.

Example: KR: lift enterprise win rate from 17% to 26%. Week 2: 7/10. Week 5: 6/10 — 'two deals slipped to Q4.' Week 8: 3/10 — 'pricing objection in 4 of 6 losses.' The week-8 drop pulled the pricing review forward a full quarter; the KR finished at 0.33.

## Core Values
URL: https://goalcadence.com/glossary/core-values
Framework: Any framework

Core values are the three to five behaviors an organization genuinely hires, promotes and occasionally fires on. They are discovered rather than invented — found by examining the people already doing the work in the way the company wants it done — and they are used to make decisions about people, which is the difference between a core value and a word on a wall.

Most discovery exercises work backwards from individuals: name a handful of employees you would rebuild the company around, describe what they actually do, and look for the behaviors that repeat. The output is phrased as behavior rather than virtue, so it can be observed in an interview. Values then have to appear in the machinery — interview questions, onboarding, review rubrics, and a recognition slot in a regular meeting where someone is named for a specific act. A value that appears in none of those is a preference.

The test of a value is whether it has ever cost something. Generic words — integrity, teamwork, excellence — cannot separate two finalists for a job, because no candidate claims the opposite. The sharper sign is upward: values applied to junior staff but not to a senior high performer teach the organization the real list within a quarter.

Example: A 120-person firm replaced seven aspirational words with four behaviors, one being 'we say the number we do not know'. It became a scored interview question; two of eleven finalists were screened out on it in a quarter, and it was the stated reason a top-billing manager was let go.

## Critical Number
URL: https://goalcadence.com/glossary/critical-number
Framework: Scaling Up

A critical number is the one metric a company or team chooses to move in a given quarter or year — the number that reflects the constraint currently holding the business back. Scaling Up puts exactly one on each horizon of the One-Page Strategic Plan, on the reasoning that a list of priorities with no number attached gives nobody a way to rank them.

It is chosen by finding this period's bottleneck, not by picking the most important metric in general, which is why it often changes from quarter to quarter while ordinary KPIs stay on the dashboard year-round. It is written with a baseline, a target and a date. Harnish pairs it with a counterbalancing number so that the obvious way to hit it does not damage something else: speed paired with quality, growth paired with margin, volume paired with rework.

The usual problem is choosing a number the quarter cannot actually move. A lagging figure in a business with a nine-month sales cycle will finish the period roughly where it started regardless of what anyone does, and the team learns the wrong lesson from a flat line — that focus did not help, rather than that the measurement window was too short.

Example: A 90-person manufacturer set on-time delivery as its critical number: 78% at the start of Q2, target 92% by 30 June, counterbalanced by returns staying under 1.5%. It finished at 89% with returns at 1.2%.

## Daily Huddle
URL: https://goalcadence.com/glossary/daily-huddle
Framework: Scaling Up

A daily huddle is a short standing meeting — typically five to fifteen minutes at the same time every day — built on a fixed three-part agenda: what is happening today, the day's key number, and where anyone is stuck. Popularized by Verne Harnish as one of the Rockefeller Habits, it exists so that a blocker surfaces within a day rather than waiting for the next weekly meeting.

The agenda is fixed so the meeting cannot expand. Each person gives a one-line update, the team looks at one or two numbers, and then names anything blocking them. Nothing is solved in the room: a stuck goes to a named person who picks it up immediately afterwards. Huddles usually cascade — the executive team at 8:15, departments at 8:30, so information moves down and back up the same morning. The hard stop matters more than the start time, and most teams stand up precisely to keep it.

Huddles decay into status round-robins. When everyone reports and nobody is stuck, the meeting has stopped doing the work it was designed for — and a full week of huddles with no stucks usually says more about whether people feel able to name them than about how the week is actually going.

Example: A 40-person agency huddles at 8:45 with a nine-minute hard stop: cash collected yesterday, jobs at risk this week, stucks. Across one quarter the average was seven minutes, with roughly two issues escalated to the leadership huddle per week.

## Goal Cascading
URL: https://goalcadence.com/glossary/goal-cascading
Framework: Any framework

Goal cascading is the practice of connecting goals across the levels of an organization so that team and individual goals visibly support the company's. Done well, it gives every team a clear line of sight from its own work to the company target; done mechanically, it produces the same sentence restated at four levels with nothing added.

Two directions exist. Strict cascading derives each level's goals from the level above, which is fast to construct and easy to audit. Aligned cascading sets company goals first, then asks teams to propose the contribution they will own, which is negotiated upward — Hoshin Kanri formalizes that exchange as catchball. Most companies run a blend, with the majority of a team's goals derived from above and the remainder owned locally.

Cascading is slow, and the delay compounds. When each level waits for the one above it to finish, a thirteen-week quarter can lose three or four weeks before frontline teams know what they are working toward. Strict top-down cascades also tend to convert outcomes into activity as they descend: the company wants retention, and four levels later a team has a goal to run twelve customer interviews.

Example: Company: lift net revenue retention from 98% to 108%. Support: cut first-response time from 3.4h to 1.5h. Product: raise reporting-module adoption from 22% to 45% of accounts. Customer success: complete business reviews on 80 of the 120 accounts above $25k.

## Goal Hierarchy
URL: https://goalcadence.com/glossary/goal-hierarchy
Framework: Any framework

A goal hierarchy is the structure that connects a company's goals across time horizons — a long-range ambition at the top, annual targets beneath it, quarterly priorities beneath those, and weekly commitments at the bottom. Each layer is meant to be a concrete, smaller step toward the layer directly above it, so that the shortest horizon still points at the longest.

Most frameworks use three or four layers under different names: a ten-to-twenty-five-year ambition such as a BHAG, a three-year picture, a twelve-month target, quarterly priorities, and weekly actions. The number of items shrinks sharply as the horizon shortens, because a quarter holds far less than a year. A hierarchy is testable in one move — take any weekly commitment and name the quarterly priority it serves without needing a second step.

Hierarchies get top-heavy. The long-range and annual layers are written once and then displayed, while the quarterly and weekly layers are where work is genuinely decided, and the two often run on separate tracks. The structure exists on a slide while day-to-day priorities come from a backlog. The link is only real when evidence from the lower layer is allowed to change the upper one mid-year.

Example: Ten-year: the default planning tool for 100,000 mid-market teams. Three-year: $40M ARR. Twelve-month: $12M ARR with 60% self-serve. Q3 priority: lift self-serve share from 38% to 48%. This week: ship the in-product upgrade prompt and instrument it.

## Hoshin Kanri
URL: https://goalcadence.com/glossary/hoshin-kanri
Framework: Hoshin Kanri

Hoshin Kanri is a strategy deployment method from Japanese quality management — developed at companies including Bridgestone and Toyota from the 1960s, under the influence of W. Edwards Deming's plan-do-check-act cycle — that translates a small number of long-range breakthrough objectives into aligned annual goals and daily work. It is also called policy deployment or strategy deployment.

A leadership team sets three to five breakthrough objectives covering three to five years, then derives the annual objectives, the improvement priorities that will deliver them, and the metrics that show progress. Those cascade level by level through catchball, a structured back-and-forth in which each layer negotiates its own targets rather than receiving them. Progress is reviewed monthly and the plan is re-examined annually. The discipline is subtractive: very few objectives, so each one can actually be resourced.

Hoshin Kanri assumes an improvement culture already exists. It grew out of manufacturing environments running standardized work and root-cause problem solving, and without that foundation the cascade tends to become one-way — targets are issued downward, catchball is skipped for time, and the annual plan becomes a set of commitments nobody negotiated. The annual rhythm also sits awkwardly in businesses whose conditions change faster than once a year.

Example: A 300-person medical device firm sets one breakthrough: order-to-delivery from 21 days to 7 by 2029. The first annual objective is 14 days, supported by two plant priorities — supplier lead time 9 days to 4, first-pass yield 91% to 97%.

## Key Result
URL: https://goalcadence.com/glossary/key-result
Framework: OKR

A Key Result is the measurable half of an OKR: a specific metric moved from a stated baseline to a stated target within the cycle. Each Objective usually carries three to five. Together they define what has to be true for the Objective to count as achieved.

The strongest Key Results are written in 'from X to Y' form, because that forces both a starting point and a destination. A number with no baseline cannot be graded — 'reach 500 signups' hides whether the team started at 480 or at 50. Key Results should be outcomes the team influences rather than activities it controls; if completing the listed work guarantees the number, the number was not a result.

Key Results decay quietly. A metric that nobody updates keeps showing its last known value, which is almost always more flattering than reality, and the gap only surfaces at scoring. Whether a Key Result is real depends less on how it was written than on whether anyone looks at it between the kickoff and the end of the quarter.

Example: Weak: 'Improve customer satisfaction.' Weak: 'Run four NPS surveys.' Stronger: 'Lift NPS from 31 to 45.' The first is unmeasurable, the second measures activity, and only the third can be graded.

## KPI
URL: https://goalcadence.com/glossary/kpi
Framework: Any framework

A KPI (key performance indicator) is a metric an organization has agreed to watch as evidence of whether a specific part of the business is healthy. What separates a KPI from an ordinary number is the agreement around it: a KPI has a named owner, a target, a fixed review rhythm, and an expectation that someone acts when it moves the wrong way.

KPIs attach to a function or a role rather than to a project, which is why they outlive any single quarter. Most companies carry somewhere between five and fifteen at company level, each with an owner, a source system, and a stated review cadence. The definition has to be precise enough that two people calculating it separately land on the same figure — 'active customers' means very little until someone writes down whether trials count and what happens to accounts that paused.

The usual failure is accumulation. Indicators get added whenever something goes wrong and almost never removed once it is fixed, so a review that started with eight numbers carries forty within two years and nobody can say which three would actually change a decision. A number that would produce no action at any value is a statistic, not an indicator.

Example: A support function tracks four KPIs weekly: median first-response time (target under 2h, actual 3.4h), resolution within 24 hours (target 85%, actual 71%), CSAT (target 4.5, actual 4.3), and tickets per 100 accounts (target 12, actual 18).

## Lag Measure
URL: https://goalcadence.com/glossary/lag-measure
Framework: 4DX

A lag measure is the metric that records whether a goal was achieved — revenue, retention, margin, cycle time, defect rate — and it can only be read after the work that produced it is finished. In 4DX, every Wildly Important Goal is stated as a lag measure moving from a starting number to a target number by a date.

Lag measures are the numbers leadership cares about and the ones nobody can act on directly: by the time the figure appears, the behavior that caused it is already history. They usually arrive monthly or quarterly, carry a reporting delay, and are influenced by several teams at once. That is why 4DX pairs each lag measure with lead measures rather than asking a team to manage the lag measure itself.

The delay between action and reading varies enormously, and teams rarely account for it when choosing. A defect rate may respond within a fortnight, while annual retention will not resolve inside a quarter, so a goal built on a slow lag measure gives a team almost no feedback during the period it is meant to be executing. A lag measure with a shorter response time is often more useful than the most important one.

Example: Lag measure: lift 90-day logo retention from 84% to 91% by 30 June. At the halfway mark the January cohort is still inside its 90-day window, so the board still shows February data — the lead measures are the only current signal.

## Lead Measure
URL: https://goalcadence.com/glossary/lead-measure
Framework: 4DX

A lead measure is a metric that tracks the behavior a team believes will produce its goal, chosen because it is both predictive of the result and directly influenceable by the people doing the work. In 4DX, lead measures are what a team actually manages week to week, because the goal measure itself can only be read after the fact.

Two tests decide whether a measure qualifies. Predictive: if this number moves, the goal measure should follow. Influenceable: the team can move it this week without waiting on anyone outside the room. Lead measures are usually counts of a deliberate act — visits made, checks completed, calls returned within the hour — and they are tracked per team or per person rather than in aggregate, because an average hides who is not doing the thing.

The predictive half is a bet, not a fact. A team can hit 100% on its lead measure for a whole quarter and watch the goal measure barely move, which means the hypothesis was wrong and the measure needs replacing rather than enforcing harder. The opposite failure is quieter: a measure that is easy to count and easy to influence but unconnected to the outcome turns the weekly rhythm into activity reporting.

Example: A field service team lifting first-visit fix rate from 62% to 85% bets on one behavior: completing the parts pre-check before leaving the depot. Week one it hit 71 of 80 calls, or 89%, and first-visit fix for that week came in at 74%.

## Leading vs Lagging Indicator
URL: https://goalcadence.com/glossary/leading-vs-lagging-indicator
Framework: Any framework

A leading indicator is a metric that moves before the outcome it predicts and can be influenced directly in the short term; a lagging indicator records the outcome itself, after the work that produced it is complete. Most measurement systems need both — the lagging indicator says whether you won, and the leading indicator says whether you are on course to.

A leading indicator has to pass two tests: it must plausibly cause the outcome, and the team must be able to move it inside a week. Frameworks carry the pair under their own names — 4DX calls them lead and lag measures, balanced scorecard separates performance drivers from outcome measures, and OKR key results are usually lagging, which is why many teams track a short list of health metrics alongside them.

The causal link is a hypothesis, and it is rarely retested once the metrics are chosen. Leading indicators are also the ones most often collected by hand, so they are first to go stale in a busy quarter, leaving a dashboard of lagging numbers that describe a period already closed. Leading and lagging are not properties of a metric either: the same number leads one outcome and lags another.

Example: Lagging: 90-day logo retention, 84% today, 91% target. Leading: share of new accounts completing an onboarding call within ten days, currently 58%. Accounts that complete the call retain at 93% against 76% for those that do not, which is what makes the second number worth watching weekly.

## Metric
URL: https://goalcadence.com/glossary/metric
Framework: Any framework

A metric is any quantity a business measures — a count, a rate, a ratio, or an average — that describes something which happened. Every KPI is a metric, but most metrics are not KPIs: a metric becomes an indicator only once someone owns it, sets a target for it, and reviews it on a cadence. Everything else is instrumentation.

Metrics come in a small number of shapes: counts (signups), rates (trial-to-paid conversion), averages (deal size), and ratios (lifetime value to acquisition cost). Three things make one usable — a written definition, a named source system, and a stated period. Without those, two teams arrive at the same meeting with different numbers for the same word and spend the hour reconciling rather than deciding. Metrics are also either leading or lagging, which determines whether they can still be influenced.

Measurability quietly shapes attention. The things easiest to instrument — page views, tickets closed, features shipped — reach the dashboard whether or not they matter, while harder-to-capture outcomes stay off it entirely. The question worth asking of any metric is what decision would change if it moved twenty percent in either direction.

Example: 'Monthly active users' at one company means any account that logged in during the month; at another it means an account that completed a core action. The first reports 12,400, the second 4,900 — same product, same month, both correct under their own definitions.

## North Star Metric
URL: https://goalcadence.com/glossary/north-star-metric
Framework: Any framework

A north star metric is the single number a company chooses to represent the core value its customers receive, used to align teams that would otherwise optimize for conflicting local goals. It is not the only thing measured — it is the one everything else is meant to ladder up to, and it usually sits above the quarterly goal set rather than inside it.

The choice is normally a measure of value delivered rather than money collected: nights booked, messages sent, weekly active teams, hours of content consumed. Revenue is assumed to follow. A north star is only workable once it has been decomposed into three or four input metrics a team can actually move in a quarter, because the headline number itself responds slowly. Most companies revisit the choice annually at most.

A single number is useful precisely because it excludes things, and that is also its weakness — any north star can be pushed upward in ways that erode what it was chosen to stand for. Companies that keep one honest tend to pair it with a small set of counter-metrics, typically retention, unit cost, and satisfaction, and read the four together.

Example: A B2B tool picks 'weekly active teams with 3+ contributing members', currently 1,840. Its inputs: new teams activated (target 120/month, actual 94), seats invited per new team (target 4.2, actual 3.1), and week-4 team retention (target 68%, actual 61%).

## Objective
URL: https://goalcadence.com/glossary/objective
Framework: OKR

An Objective is the qualitative half of an OKR: a short, memorable statement of what a team intends to achieve in the cycle. It contains no numbers. Its job is direction and motivation — the measurement belongs to the Key Results underneath it.

A good Objective is specific enough to rule things out and short enough to be quoted from memory in a meeting. Most teams write between one and three per cycle; a team carrying seven Objectives has effectively set none, because nobody can say which two matter when the week gets tight. Objectives are usually set for a quarter, though some organizations run annual company Objectives with quarterly team Objectives beneath them.

The most common failure is an Objective that is really a task list — 'Launch the new billing system' is something you either shipped or didn't, which leaves the Key Results with nothing to measure except completion. Naming the outcome the launch is meant to produce gives the Key Results somewhere to point.

Example: Weak: 'Ship the partner portal in Q3.' Stronger: 'Make partners self-sufficient without calling us.' The second admits several routes and lets Key Results measure whether partners actually became self-sufficient.

## OKR
URL: https://goalcadence.com/glossary/okr
Framework: OKR

An OKR (Objectives and Key Results) is a goal-setting framework that pairs one qualitative Objective — the outcome you want — with three to five measurable Key Results that prove you reached it. Popularized at Intel by Andy Grove and later at Google, OKRs are typically set on a quarterly cycle, reviewed weekly, and scored at the end of the period.

The Objective is deliberately not a number. It names a destination in plain language, so anyone in the company can repeat it. The Key Results carry all the measurement: each one moves a specific metric from a stated baseline to a stated target inside the cycle. If a Key Result can be finished by completing a task, it is a task masquerading as a result. The test is whether someone could do all the listed work and still miss the number.

OKRs break down more often on rhythm than on wording. A set of objectives written at a planning offsite and not opened again until scoring week produces a score, not a course correction — the framework specifies a weekly check-in precisely because the value sits in the adjustments made between setting and scoring.

Example: Objective: Make onboarding effortless for new admins. Key Results: cut median time to first value from 9 days to 3; lift 30-day activation from 41% to 60%; reduce onboarding support tickets per new account from 2.4 to 1.0.

## OKR Scoring
URL: https://goalcadence.com/glossary/okr-scoring
Framework: OKR

OKR scoring is the practice of grading each Key Result on a 0.0 to 1.0 scale at the end of a cycle, based on how far the metric moved between its baseline and its target. The Objective's score is usually the average of its Key Results.

The score is a ratio, not a percentage of effort: a Key Result set to move a number from 20 to 60 that reached 40 scores 0.5. At Google, where the practice was popularized, an average around 0.6 to 0.7 is treated as the healthy range for ambitious goals, and consistently scoring 1.0 is read as a sign that targets were set too low rather than as excellence. The score is a conversation starter for the retrospective, not a performance rating.

Scoring only works if the numbers were being watched along the way. A grade assigned in the final week measures the quarter that already happened, which is why most frameworks pair scoring with a mid-cycle trajectory check — by the time a score exists, nothing about that cycle can still be changed.

Example: Key Result: lift win rate from 22% to 35%. Actual at quarter end: 29%. Score: (29 − 22) ÷ (35 − 22) = 0.54.

## One-Page Strategic Plan (OPSP)
URL: https://goalcadence.com/glossary/one-page-strategic-plan
Framework: Scaling Up

The One-Page Strategic Plan (OPSP) is the core planning document of Verne Harnish's Scaling Up: a single sheet holding core values, purpose, a BHAG, three-to-five-year targets, the one-year plan, the quarter's priorities and theme, and each individual's priorities. The one-page constraint is deliberate — a strategy that will not fit on a page rarely fits in anyone's head either.

The sheet reads left to right from the longest horizon to the shortest. Core values and purpose anchor the left edge, the BHAG and three-to-five-year targets sit next, then the one-year plan with its revenue, profit and critical number, then the quarter, and finally a column for the individual's own priorities. Each horizon carries three to five priorities and exactly one critical number, so every column can be read as a ranked list. The quarterly columns are rewritten at each quarterly planning session; the left-hand columns change rarely, and a change there is itself news.

One page is a formatting rule, not a thinking rule. Compression strips out the reasoning behind each choice, so a plan can end up as a grid of nouns that only the people who were in the room can decode — which is why a laminated OPSP and a well-understood one look identical from across a desk.

Example: A $9M services firm: BHAG, 50,000 plants maintained annually by 2038. Three-year target, $28M revenue at 22% net. One-year plan, $14M with a critical number of 240 active contracts. Q3 priorities: launch the northern depot, move three accounts to fixed-fee, cut rework below 4%.

## Operating Cadence
URL: https://goalcadence.com/glossary/operating-cadence
Framework: Any framework

An operating cadence is the fixed schedule of recurring sessions a company uses to plan, review and correct — typically an annual plan, quarterly planning, a weekly leadership meeting, and often a daily huddle. Each layer covers a different horizon, and each exists to catch the errors the slower layer above it would not see in time.

The layers nest. Annual sets direction; quarterly converts it into three to five priorities; weekly checks the numbers and clears blockers; daily synchronizes people who need each other that day. The shorter the interval, the narrower the agenda and the shorter the session. Most of the corrective value sits in the shortest interval, because that is where a wrong assumption is caught within days instead of at a quarterly review twelve weeks later.

Cadence is easy to install and easy to hollow out. Sessions stay on the calendar long after they stop producing decisions, and the calendar entry gets mistaken for the practice. The opposite failure is over-installation: adding a new standing meeting for every problem until leaders spend three days a week in review sessions and have no time left to do the work being reviewed.

Example: Annual: two days in November. Quarterly: one day in week one. Weekly: 90 minutes Monday (48 weeks = 72 hours). Daily: 10 minutes at 9:05 (240 days = 40 hours). Total standing commitment: roughly 160 hours a year, about 8% of a leader's working time.

## Quarterly Business Review (QBR)
URL: https://goalcadence.com/glossary/quarterly-business-review
Framework: Any framework

A Quarterly Business Review (QBR) is a formal session held at the close of a quarter to examine what actually happened — results against plan, financials, pipeline, and the state of major initiatives — and to decide what changes as a result. It looks backward at the period just ended, and usually runs immediately before planning for the next one.

Two different meetings travel under the name. Internally, a QBR is leadership reviewing performance against the targets set last quarter, normally with a written pre-read circulated days in advance. Externally, in customer-facing organizations, a QBR is a session with an account covering usage, outcomes, open risks and renewal. Both share the same skeleton: numbers everyone has already agreed on, plain variance analysis against what was forecast, and decisions recorded with owners and dates rather than left as sentiment in the room.

QBRs tend to become presentations. When a team spends the preceding week assembling slides, the session starts rewarding a well-told story rather than an accurate one, and uncomfortable variances get framed instead of examined. Reviews that stay useful generally publish the numbers before anyone gathers, so the meeting time goes to why rather than to what.

Example: Q2 QBR: plan $1.8M new ARR, actual $1.42M (79%). Variance sits almost entirely in enterprise (plan $900k, actual $480k) where win rate fell from 26% to 17% after two competitors repriced. Decision: pricing review before Q3 planning, owner CRO, due 12 July.

## Quarterly Planning
URL: https://goalcadence.com/glossary/quarterly-planning
Framework: Any framework

Quarterly planning is the working session where a leadership team reviews the ninety days just finished, chooses the handful of priorities for the ninety ahead, and attaches an owner and a measure to each one. The quarter is the unit because it is long enough to complete meaningful work and short enough that a wrong call is corrected inside the same year.

A session typically runs from a half day to two days and follows a fixed order: results against last quarter's plan, a look back at the annual target, an honest naming of the gap, then selection of three to five priorities for the coming quarter. Most frameworks cap the number deliberately. Each priority leaves the room with a named owner, a done-condition anyone could verify, and a number that moves from a baseline to a target.

The hard part is not choosing priorities but subtracting. A team that adds five new quarterly goals on top of everything already in flight has changed nothing about where the hours go, and by week six the new goals are competing with the old ones rather than replacing them. Plans also drift when the offsite is the only time they are opened.

Example: A 60-person company enters Q3 at $4.2M ARR against a $6M annual target and names three priorities: lift trial-to-paid from 14% to 20%, ship SSO to unblock 12 stalled enterprise deals, and cut onboarding from 5 weeks to 2.

## Quarterly Priority
URL: https://goalcadence.com/glossary/quarterly-priority
Framework: Any framework

A quarterly priority is a discrete piece of work a team commits to finishing inside a thirteen-week quarter, with one named owner and an agreed definition of done. Most frameworks cap each team and each person at three to five. Scaling Up popularized calling them 'Rocks', after Stephen Covey's demonstration that the big rocks only fit in the jar if they go in first.

A quarterly priority is neither a metric target nor a task: it is a deliverable that will plainly be either finished or unfinished on the last day of the quarter. Ownership is singular — a priority owned by a department is owned by nobody — and scope is set so one person can carry it alongside their normal load. They are chosen at quarterly planning, reviewed weekly as on or off track, and closed at the quarter end whether or not they landed. Anything needing more than a quarter is broken up or reframed as a longer-horizon goal.

Volume is the usual failure: five per person across a team of nine is forty-five commitments, which is a backlog with a deadline. The subtler one is the priority marked on track for eleven weeks and missed in week thirteen, which happens when the weekly review asks for a status rather than for evidence of progress since the last review.

Example: Weak: 'improve onboarding.' Stronger: 'self-serve onboarding live for all new Starter accounts by 30 September — owner: Priya.' One team carried 14 priorities into Q2 and completed 6; capped at 7 the next quarter, it completed 6 again, with half the work in progress.

## Quarterly Theme
URL: https://goalcadence.com/glossary/quarterly-theme
Framework: Scaling Up

A quarterly theme is a named, time-boxed company campaign built around the quarter's critical number, complete with a visible scoreboard and a celebration when the target is hit. It comes from Verne Harnish's Scaling Up, where the theme is the device that gets a dry target — a collections figure, a defect rate — enough attention across the whole company to actually move inside thirteen weeks.

A theme has five parts: one number, a deadline, a name people will repeat, a scoreboard that updates at least weekly somewhere everyone sees it, and a reward agreed before the quarter starts. The name does the work a metric cannot — it gives people outside the owning department a reason to care and a way to refer to the effort. Themes normally track a single number; a theme covering four metrics is a plan wearing a costume, and the scoreboard becomes unreadable.

Themes fail when the number sits outside most people's reach. Wrapping a campaign around a figure only two people can influence turns the rest of the company into spectators, and once staff have watched two or three themes they had no lever on, the next name lands as decoration rather than as a priority.

Example: A services firm with days sales outstanding at 63 ran 'Race to 45' for one quarter: a thermometer in the kitchen updated every Friday, a team lunch at the target. It finished at 47 days — short of the goal, but roughly $380,000 of cash pulled forward.

## Rockefeller Habits
URL: https://goalcadence.com/glossary/rockefeller-habits
Framework: Scaling Up

The Rockefeller Habits are ten management disciplines codified by Verne Harnish in Mastering the Rockefeller Habits (2002) and later carried into Scaling Up. Named after the operating practices of John D. Rockefeller, they group into priorities, data and rhythm, and are scored as a checklist so a leadership team can see which habits are genuinely in place rather than merely intended.

The list runs from habit one, a healthy and aligned executive team, to habit ten, a company story that every employee can tell. In between sit the ones most teams recognize: everybody can name the quarter's top priority; a communication rhythm of daily huddles, weekly and monthly leadership meetings, and quarterly and annual planning; a small set of numbers reported weekly by every person; and employee and customer feedback collected routinely and routed to whoever can act on it. Teams grade each habit red, yellow or green, then work on two or three at a time rather than attempting all ten.

The checklist is easy to score and hard to sustain. Rhythm usually lapses first — a daily huddle survives a busy month less reliably than a written priority does — and because the habits reinforce one another, the ones that quietly slip are often the ones holding the others up.

Example: A 70-person distributor graded itself green on four habits, yellow on three and red on three at annual planning. It worked only on the two reds tied to rhythm: a 12-minute daily huddle and a weekly metrics review. By the next quarterly session, three habits it had not touched directly had moved from yellow to green.

## Scoreboard
URL: https://goalcadence.com/glossary/scoreboard
Framework: 4DX

A scoreboard in 4DX is the simple, visible display a team keeps of its own goal, showing the lag measure, the lead measures and where both should stand by now, designed so anyone can tell within five seconds whether the team is winning or losing. Keeping a compelling scoreboard is the third of the four disciplines.

The distinction 4DX draws is between a coach's scoreboard and a players' scoreboard. A management dashboard can carry dozens of metrics because an analyst reads it; a players' scoreboard carries only the numbers the team can act on, is updated by the team itself, and sits where the team sees it without going looking. It has to show a pace line as well as a current value, because a number on its own does not say ahead or behind.

Scoreboards stop working when ownership moves. Once a manager or an analyst becomes the person who updates it, the display turns into reporting, the team reads it as something done to them, and refreshes slip to whenever someone has time. Adding metrics produces the same result by a different route: a board carrying fourteen numbers no longer answers the one question it exists to answer.

Example: Two rows. Lag: on-time delivery, 62% at the start, 90% target, 71% today against a pace line of 76% — behind. Lead: parts pre-check completed, 95% target, 89% this week — behind, and the reason the row above it is behind.

## Scorecard
URL: https://goalcadence.com/glossary/scorecard
Framework: Any framework

A scorecard is a short, fixed list of metrics — usually five to fifteen — reviewed on the same rhythm every week or month, with an owner, a target, and the current actual beside each row. Its job is to make the state of the business readable at a glance and to surface anything off-target early enough that the quarter can still be changed.

A scorecard is deliberately narrow and deliberately stable: the same rows, in the same order, every period, so that trends are visible without anyone building a chart. Most teams show the last eight to thirteen periods alongside the current one. The review itself is fast — on-target rows are read and passed over, and only the off-target rows earn discussion, which is what keeps the segment to a few minutes inside a longer meeting.

Scorecards decay in two directions. They grow until they are a report nobody reads, or they freeze while the business changes, so every row stays green while the real constraint moves somewhere the scorecard does not look. Both are the same problem: the list gets reviewed every week and revisited almost never.

Example: A 40-person software company's weekly scorecard: new MRR (target $25k, actual $19k), gross churn (target under 1.5%, actual 2.1%), qualified demos booked (target 30, actual 34), NPS (target 40, actual 38), and cash runway in months (target above 18, actual 21).

## SMART Goals
URL: https://goalcadence.com/glossary/smart-goals
Framework: SMART

SMART goals are goals written to satisfy five criteria — Specific, Measurable, Achievable, Relevant, and Time-bound — a checklist introduced by George Doran in 1981 to make objectives verifiable rather than vague. SMART is a quality test applied to the wording of an individual goal, not a system for running an organization.

Applied properly, the test converts an intention into a sentence that can be graded at a date. 'Improve customer retention' fails four of the five criteria; 'Raise 12-month logo retention from 78% to 85% by 31 December' passes all five. Specific, Measurable and Time-bound are mechanical checks anyone can apply. Achievable and Relevant are judgment calls that depend on context, and they are where most disagreement in a planning session actually sits. Some variants substitute Assignable or Realistic.

SMART examines one goal in isolation, which is where its scope ends. It says nothing about how many goals a team should hold at once, how goals connect across levels, or how often they should be reviewed — so an organization can carry a hundred flawlessly SMART goals and still have no priorities. Frameworks such as OKRs and 4DX wrap the same wording test inside a cadence and a hard limit on count.

Example: Vague: 'Get better at hiring.' SMART: 'Cut median time-to-offer for engineering roles from 41 days to 28 days by 30 June, without offer acceptance falling below 80%.'

## Strategy Execution
URL: https://goalcadence.com/glossary/strategy-execution
Framework: Any framework

Strategy execution is the work of turning a stated strategy into the priorities, measures, owners, and meetings that change what an organization actually does. It covers translating long-range intent into shorter cycles, assigning accountability, tracking progress against defined measures, and reallocating attention when results diverge from plan. It is the gap between what a company has decided and what it delivers.

Frameworks arrange the same four parts differently: a small set of priorities, a measure per priority with a baseline and a target, a named owner, and a recurring meeting where the numbers are reviewed and decisions get made. OKRs run quarterly cycles with weekly check-ins; 4DX narrows to a couple of goals held by a weekly cadence of accountability; Hoshin Kanri runs annual cycles reviewed monthly; the Balanced Scorecard spreads the measures across four perspectives. What matters most is whether the cycle closes.

Execution fails in the interval between planning and review rather than at either end. Priorities set in January and reopened in April were not executed, they were stored. The usual pattern is that ongoing operational work, which never pauses, absorbs the capacity the priorities quietly assumed — and because nothing formally changes, the shortfall only becomes visible when the period closes and the results are read.

Example: A 180-person company sets 6 annual priorities, reviews them monthly, and finishes the year with 2 delivered. Switching to 3 priorities per quarter with weekly owner updates, it commits to 12 across the year and closes 9.

## Strategy Map
URL: https://goalcadence.com/glossary/strategy-map
Framework: Balanced Scorecard

A strategy map is the one-page diagram behind a Balanced Scorecard: it arranges an organization's objectives across the four perspectives and connects them with arrows showing which objective is expected to drive which. Kaplan and Norton added it to the framework in the late 1990s because teams could list measures easily but could not explain how those measures were supposed to be related.

Objectives are stacked with Learning & Growth at the bottom and Financial at the top, and every objective connects upward to at least one other. Most maps hold 12 to 20 objectives, few enough to be read on one page during a meeting. The arrows carry the argument: each is a hypothesis of the form "if we improve this, that should follow." Measures hang off the objectives, so the map itself stays free of numbers and the logic stays legible.

A strategy map is a set of hypotheses drawn as if they were facts. The arrows are chosen by a leadership team from experience rather than from data, and they are almost never revisited once the map is printed, so a link that turned out not to hold keeps directing investment. Maps also age: the diagram describes the strategy as it stood on the day of the offsite, and the further the year runs, the less it resembles what teams are actually working on.

Example: A SaaS company draws: "Deepen product expertise in support" (Learning & Growth) leads to "Resolve tickets at first contact" (Internal Process), then "Customers renew without escalation" (Customer), then "Lift net revenue retention from 104% to 118%" (Financial).

## Stretch Goal
URL: https://goalcadence.com/glossary/stretch-goal
Framework: OKR

A stretch goal is a target set deliberately beyond what a team is confident it can hit, so that planning starts from ambition rather than from a comfortable extrapolation. In OKR practice, stretch goals are expected to land short — a score around 0.7 is treated as success.

Stretch goals only function when the organization separates them from commitments. If a missed stretch target is treated the same as a missed delivery date, teams learn to set targets they know they will beat, which is the exact behavior the mechanism exists to prevent. Most mature OKR programs label each Key Result as committed or aspirational at the moment it is set, not after the result is known.

The visible failure mode is sandbagging, and it is harder to spot than a miss because everything looks green. A Key Result running far ahead of pace early in a cycle usually says more about how the target was chosen than about how the team is performing.

Example: Committed: 'Ship SOC 2 Type II by 30 September' — a 1.0 is expected. Aspirational: 'Grow self-serve revenue from $80k to $250k MRR' — landing at $190k scores about 0.65 and counts as a good quarter.

## The Whirlwind
URL: https://goalcadence.com/glossary/the-whirlwind
Framework: 4DX

The whirlwind is the 4DX term for the urgent day-to-day work that keeps an organization running — the tickets, escalations, shipments, approvals and recurring duties that already consume most of a team's time. 4DX treats it as a permanent condition rather than a problem to be solved: it cannot be switched off, so any new goal has to be executed alongside it.

The whirlwind is urgent and a goal is merely important, so in a direct contest the whirlwind wins without anyone deciding. 4DX assumes a team has only a small share of its capacity — commonly put at around 20% — available for goal work, and builds the rest of the method around protecting that share: one or two goals, a handful of weekly commitments, and a meeting the whirlwind is not allowed into.

The idea is easy to use as a label for anything a team would rather not take on, which makes it worth measuring instead of asserting. A team genuinely running at full whirlwind capacity has a staffing or process issue that no goal-setting method addresses, and planning that assumes free capacity where none exists produces a goal quietly abandoned by week three.

Example: A nine-person support team handles roughly 340 tickets a week at about 31 hours each. That leaves close to seven hours per person for everything else — enough for one goal with two weekly commitments, not for four initiatives.

## True North
URL: https://goalcadence.com/glossary/true-north
Framework: Hoshin Kanri

True North is the term used in Hoshin Kanri and lean management for an organization's long-range ideal state — the condition it is permanently moving toward, such as zero defects or delivery exactly when promised. It works as a fixed reference point for direction rather than as a target with a deadline, and it is not expected to be reached.

True North is stated as an absolute on purpose, because an absolute never stops generating improvement work: a company at 99% on-time delivery still has a gap to close. Breakthrough objectives are then chosen as the next meaningful step toward it, and the distance between the current condition and True North is what makes one improvement priority more urgent than another. Most organizations hold a single True North statement and revisit it only when the business itself changes.

Because True North is never reached, it is also never falsified, and a statement broad enough to survive indefinitely can stop doing any work. "Delight every customer" cannot rule out an initiative, which is the job a direction-setting statement exists to do. Distance is the other difficulty: an ideal five years out offers little help when two priorities compete for the same team this quarter, so something closer in is still needed to decide between them.

Example: A contract manufacturer states True North as "every order defect-free, delivered the day it was promised." Current condition: 92.4% on time, 3,100 defects per million. The 2027 breakthrough — 97% and 900 defects per million — is one step toward it, not the destination.

## Weekly Leadership Meeting
URL: https://goalcadence.com/glossary/weekly-leadership-meeting
Framework: Any framework

A weekly leadership meeting is a standing session — commonly 60 to 90 minutes, same day and same time each week — in which a leadership team reviews its numbers against target, checks progress on quarterly priorities, and works through whatever is blocking them. Its purpose is correction inside the quarter, not reporting at the end of it.

The structure is almost always fixed and time-boxed: a fast scan of the scorecard, a pass down the quarterly priorities marking each on-track or off-track, then the bulk of the hour spent on a short list of issues chosen from what those two segments surfaced. Anything that cannot be resolved in the room leaves as an action with an owner and a date, and the next week opens by checking those actions closed.

These meetings fail by filling with updates. When each attendee narrates their week, the hour is gone before the first real disagreement surfaces, and the items that genuinely needed a group decision slide to the following week and then the one after. The diagnostic is simple: count the decisions the meeting produced. A session that produced none was a status report held in expensive company.

Example: A seven-person leadership team meets 90 minutes every Monday: 5 minutes on a 12-row scorecard (2 rows off-target), 10 minutes on 4 quarterly priorities (1 off-track), 65 minutes on three issues chosen by vote, 10 minutes to confirm 9 action items with owners and dates.

## Wildly Important Goal (WIG)
URL: https://goalcadence.com/glossary/wildly-important-goal
Framework: 4DX

A Wildly Important Goal (WIG) is the one goal a team commits to achieving above all others in a given period, written as a single measure moving from a defined starting point to a defined finish line by a defined date. It is the first discipline of the 4 Disciplines of Execution, the method set out by Chris McChesney, Sean Covey and Jim Huling of FranklinCovey.

The canonical form is 'from X to Y by when', which forces a baseline, a target and a deadline into one sentence. 4DX limits a team to one or two WIGs at a time, on the argument that execution quality falls sharply as the number of competing goals rises. Everything else the team does still has to happen — it simply carries on at its current standard rather than being improved this period. A company WIG only becomes actionable once each team beneath it has named the battle it will fight.

The discipline is harder to hold than to state. Organizations often approve one WIG per department, which quietly restores the crowded list the discipline was meant to remove, and a WIG defined only at company level leaves individual teams unable to say what they personally change on Monday. Choosing a single goal also means publicly deciding what will not improve this period, which is the part most leadership teams find uncomfortable.

Example: From 62% on-time delivery to 90% on-time delivery by 31 December. The metric, the starting point and the date are all stated, so on 1 December the team can tell whether it is on pace without asking anyone.

## X-Matrix
URL: https://goalcadence.com/glossary/x-matrix
Framework: Hoshin Kanri

The X-Matrix is the single-page planning document used in Hoshin Kanri, named for the X shape its four quadrants form. Long-range breakthrough objectives, annual objectives, improvement priorities, and target metrics each occupy one edge of the page, and correlation marks in the corners record which items in adjoining quadrants are linked.

Read clockwise from the bottom: three-to-five-year breakthroughs at the south, annual objectives at the west, improvement priorities at the north, metrics to improve at the east, with owners listed down the right-hand side. Each corner holds a grid of correlation marks, usually strong, weak, or none. Because every item must link to something in the quadrant beside it, an annual objective with no priority behind it — or a priority attached to nothing — becomes visible on the page.

The matrix is dense, and density cuts both ways. It is effective at exposing unsupported objectives inside a planning room and poor at communicating anything to someone who was not there; most people outside the leadership team never learn to read it. It is also a snapshot. The correlation marks record what was believed at the annual planning session, and updating them mid-year is awkward enough that most teams do not.

Example: A distributor links the annual objective "reduce order-to-cash to 30 days" strongly to two priorities — automate invoicing, tighten credit terms — and to two metrics: days sales outstanding 47 to 30, invoice error rate 6.2% to 1.0%.

---

# Framework comparisons (7)

Neutral side-by-side comparisons. No framework is positioned as better
than another; each compares how the two set goals, measure progress, and
fail. The "Where GoalCadence sits" note on each page is the only vendor
statement and is reproduced here as such.

## OKRs vs KPIs
URL: https://goalcadence.com/okr-vs-kpi

An OKR is a goal you are trying to reach in a set period: an Objective plus three to five Key Results that move a metric from a baseline to a target. A KPI is a number you monitor continuously to know whether the business is healthy. OKRs change every quarter and are meant to be achieved. KPIs mostly stay the same and are meant to be watched. Most companies need both, and confusing them is the usual reason a goal program stalls.

### OKRs: a goal you are trying to reach
OKRs pair one qualitative Objective with three to five measurable Key Results that would prove it happened. They were developed at Intel by Andy Grove and popularized at Google, and they run on a cycle — usually quarterly, set at the start and scored at the end. The Objective carries no numbers; the Key Results carry all the measurement, each moving a named metric from a stated baseline to a stated target.
Where OKRs work well: OKRs are strongest when a team needs to change something rather than maintain it. Because each cycle starts by choosing a small number of Objectives, they force a prioritization conversation that otherwise does not happen. They work well in companies where priorities genuinely shift quarter to quarter, and the scoring convention — where an ambitious goal landing around 0.7 counts as success — gives teams a way to aim high without treating a near miss as a failure.
Where OKRs struggle: OKRs struggle when a team's real job is to keep things running. There is no good OKR for "support tickets stay under four hours," because the goal is not to change the number but to hold it. They also struggle when they are set and then not looked at: the framework specifies a weekly check-in, and an OKR reviewed only at scoring produces a grade rather than a course correction. And because they are designed to be re-set every cycle, they are a poor home for anything you need to track for years.

### KPIs: a number you are watching
A KPI is a key performance indicator: a metric chosen because it reflects the health of something that matters, tracked continuously rather than for a fixed period. Revenue, gross margin, churn rate, on-time delivery and net promoter score are typical. A KPI usually has a target or an acceptable range, an owner, and a review rhythm — most often a weekly scorecard.
Where KPIs work well: KPIs are strongest for the parts of a business that need to stay good rather than get better. They give a team a stable frame of reference across years, which makes trends visible in a way that quarterly goals never can. They are also the right tool for anything with a floor: quality, safety, reliability and service levels are better held to a standard than set as an ambition.
Where KPIs struggle: KPIs struggle to drive change. A dashboard full of numbers tells you the state of the business but not what anyone should do differently on Monday, and it is entirely possible for every KPI to sit inside its acceptable range while the company makes no strategic progress at all. They also accumulate: because nothing forces a KPI off the list, scorecards tend to grow until nobody reads them.

### When to use each
Choose OKRs: Use OKRs when you are trying to change something in a defined period — enter a market, fix activation, shorten the sales cycle. They suit work with a finish line and a team willing to re-set every quarter.
Choose KPIs: Use KPIs when you need to hold a standard indefinitely — uptime, margin, churn, delivery times. They suit anything where the goal is stability, and where a trend over years matters more than a target this quarter.
Run both: Most companies run both, and the pairing is the point: KPIs tell you which part of the business needs attention, and an OKR is how you go and do something about it for a quarter. A KPI that has drifted is often the best possible input to the next planning session.

### At a glance
- Purpose: OKRs — Change something within a set period | KPIs — Monitor health continuously
- Lifespan: OKRs — One cycle, usually a quarter | KPIs — Ongoing, often for years
- How it is set: OKRs — Chosen fresh each cycle, from a baseline to a target | KPIs — Chosen once, with a target or an acceptable range
- How success reads: OKRs — Scored at the end, often 0.0 to 1.0 | KPIs — In range or out of range, week by week
- Ambition: OKRs — Deliberately stretching; landing around 0.7 can be a good result | KPIs — Meet the standard; exceeding it is rarely the aim
- Review rhythm: OKRs — Weekly check-in, mid-cycle trajectory check, scoring at the end | KPIs — Weekly scorecard read, usually in minutes
- Typical count: OKRs — One to three Objectives per team | KPIs — Five to fifteen on a weekly scorecard
- Common failure: OKRs — Set at an offsite, never reviewed, scored in the final week | KPIs — The list grows until nobody reads it, and everything sits in range while nothing improves

### Where GoalCadence sits
GoalCadence treats OKRs and KPIs as different objects rather than making you force one into the other: Objectives and Key Results on a quarterly cycle, and a weekly scorecard for the numbers you watch continuously. Teams running Scaling Up or 4DX use the same scorecard alongside their own goal format.

### Common questions
Q: What is the difference between an OKR and a KPI?
A: An OKR is a goal with a finish line: an Objective plus Key Results that move a metric from a baseline to a target inside a cycle, usually a quarter. A KPI is an ongoing health measure you watch continuously and hold within an acceptable range. OKRs are for changing something; KPIs are for knowing whether something needs changing.

Q: Can a KPI be a Key Result?
A: Yes, and this is the most useful place the two meet. If a KPI has drifted out of range, making it the subject of a Key Result — moving it from its current value to a target by the end of the quarter — turns a monitoring number into a goal with an owner. When the quarter ends, it goes back to being a KPI you watch.

Q: Should we use OKRs or KPIs?
A: Almost certainly both, because they answer different questions. Use KPIs for the parts of the business that need to stay good, and OKRs for the small number of things you are actively trying to change this quarter. Teams that pick only one usually end up recreating the other informally.

Q: How many KPIs should we track?
A: Five to fifteen on a weekly scorecard. Below five you cannot see the shape of the business; above fifteen the review stops fitting in the meeting, and a scorecard nobody reads is worse than no scorecard at all. Metrics that only move quarterly belong in a monthly or quarterly review instead.

Q: Is a metric the same as a KPI?
A: No. Every KPI is a metric, but most metrics are not KPIs. A metric becomes a KPI when someone decides it is one of the few numbers that genuinely indicates health, gives it an owner and a target, and puts it on a recurring review. The discipline is in what you leave off.

## OKRs vs 4DX
URL: https://goalcadence.com/okr-vs-4dx

OKRs and 4DX both narrow a team to a few goals, but they answer different questions. OKRs are a format for writing a goal: one Objective plus three to five Key Results, re-set each cycle. 4DX is a method for executing against a day job that keeps getting in the way, built on lead measures, a visible scoreboard and a weekly accountability meeting. OKRs shape what you commit to; 4DX shapes what happens after.

### OKRs: a way to write and score the goal
OKRs pair one qualitative Objective with three to five measurable Key Results that would prove it happened. Andy Grove developed them at Intel and Google made them widely known. The format is deliberately thin: it tells you how to write a goal and how to score it, and leaves the meeting rhythm, the scoreboard and the accountability to whatever the company already does. Most teams set them quarterly, check in weekly, and score at the end of the cycle.
Where OKRs work well: OKRs work well when priorities genuinely shift and a company needs a shared language for what matters right now. Because they are written the same way at every level, a team can read the level above and see where its own work connects, which surfaces cross-functional dependencies early. They also handle ambition gracefully: with the common convention that an aggressive Key Result landing near 0.7 counts as a good result, teams can aim past what they are confident of without being punished for the gap.
Where OKRs struggle: OKRs say very little about execution. The format defines how to write and score a goal and leaves the weekly mechanics undefined, so teams that adopt OKRs without building a review rhythm end up with a document that gets read twice a quarter. Key Results also tend to be lag measures — revenue, retention, activation — which tell you how you did but not what to do on Monday. And nothing in the format protects a goal from the urgent work that crowds it out.

### 4DX: a discipline for executing against the day job
4DX, the 4 Disciplines of Execution, comes from FranklinCovey and from Chris McChesney, Sean Covey and Jim Huling. It is an execution system rather than a goal format, built on four disciplines: Focus on the Wildly Important, Act on Lead Measures, Keep a Compelling Scoreboard, and Create a Cadence of Accountability. Its central observation is the whirlwind — the day job that consumes a team and quietly defeats any goal that is not deliberately protected from it.
Where 4DX work well: 4DX is strongest where a team has a demanding day job and a history of goals dissolving into it. Insisting on one or two Wildly Important Goals makes the tradeoff explicit instead of implied. Lead measures are the real contribution: by naming the few behaviors a team can control that predict the outcome, 4DX gives people something to act on this week rather than a number to await. The scoreboard and the weekly session turn that into a habit, and frontline teams in operations, service, retail and sales usually take to it quickly.
Where 4DX struggle: 4DX is narrow on purpose, and that is also its limit. It tells a team how to execute a goal but not which goal deserves the attention; the strategy work has to happen somewhere else. Lead measures are hard to identify for research, design and other work where the path to the outcome is not repeatable, and a badly chosen lead measure quietly becomes a quota. The machinery needs upkeep too: scoreboards go stale and weekly sessions decay into status updates without someone who protects them.

### When to use each
Choose OKRs: Reach for OKRs when the hard part is choosing and aligning — several teams, shifting priorities, and a need for everyone to see what everyone else committed to this quarter. They suit outcome goals whose path is not yet known.
Choose 4DX: Reach for 4DX when the hard part is follow-through — a team with a relentless day job, a goal that keeps slipping, and behaviors the team can actually control. It suits work where the weekly actions that drive the result are identifiable.
Run both: The two compose cleanly, because they overlap very little. Write the commitment as an Objective with Key Results, then run it with 4DX mechanics: pick the lead measures underneath the Key Results, put them on a scoreboard, and hold a short weekly session where each person commits to one or two things that move them. The OKR is the what; the 4DX cadence is the how.

### At a glance
- What it defines: OKRs — How a goal is written, aligned and scored | 4DX — How a team executes a goal against its day job
- Unit of commitment: OKRs — One to three Objectives, each with three to five Key Results | 4DX — One or two Wildly Important Goals, each with lead measures
- Measurement: OKRs — Mostly lag measures, moved from a stated baseline to a target | 4DX — Lead measures the team controls, paired with the lag measure that defines the goal
- Cadence: OKRs — Set and scored each cycle; a weekly check-in by convention | 4DX — A short weekly session, prescribed and non-negotiable
- Scope: OKRs — Written at every level and usually visible company-wide | 4DX — Team level; each team's goal serves the one above it
- Ambition: OKRs — Deliberately stretching; a near miss can still be a good result | 4DX — A finish line the team commits to hitting: from X to Y by when
- Visibility: OKRs — A shared document or goal tool anyone can read | 4DX — A scoreboard the team can read at a glance, often on a wall
- Common failure: OKRs — Set at an offsite, never reviewed, scored in the final week | 4DX — The whirlwind wins: the scoreboard goes stale and the weekly session becomes a status meeting

### Where GoalCadence sits
GoalCadence supports OKRs and 4DX as first-class frameworks, with goals, a weekly scorecard, meetings and quarterly planning in one place. Teams can run different frameworks in different parts of the company, so sales can work in 4DX while product runs OKRs.

### Common questions
Q: What is the difference between OKRs and 4DX?
A: OKRs are a goal format: an Objective plus three to five Key Results, set for a cycle and scored at the end. 4DX is an execution discipline: narrow to one or two Wildly Important Goals, act on lead measures you control, keep a visible scoreboard, and hold a weekly cadence of accountability. OKRs specify what a goal looks like; 4DX specifies what a team does about it every week.

Q: Can you use OKRs and 4DX together?
A: Yes, and the combination is common because the two barely overlap. Write the quarterly commitment as an Objective with Key Results, then run it with 4DX: identify the lead measures underneath each Key Result, put them on a scoreboard, and hold the weekly session where people commit to the actions that move them. Nothing in either framework forbids it.

Q: Is a Wildly Important Goal the same as an Objective?
A: They are close but not identical. Both name the thing that matters most, but a Wildly Important Goal is written in a fixed form — from X to Y by when — so it carries its own measure, while an Objective is qualitative and pushes the measurement into its Key Results. A WIG is also strictly limited in number, where OKR practice allows a few Objectives per team.

Q: What is the whirlwind in 4DX?
A: The whirlwind is the day job: the urgent, recurring work required just to keep the business running. 4DX treats it as a permanent force rather than a problem to eliminate, on the reasoning that it will always consume most of a team's energy. The disciplines exist to protect a small amount of capacity from it, which is why 4DX insists on so few goals.

Q: Which works better for a small team?
A: It depends on which part is failing. A small team that already executes well but keeps working on the wrong things gets more from the OKR habit of choosing and writing down a few outcomes. A small team that agrees on the goal and then loses it to daily firefighting gets more from the 4DX scoreboard and weekly session. Neither is inherently better at small scale.

## OKRs vs Scaling Up
URL: https://goalcadence.com/okr-vs-scaling-up

OKRs and Scaling Up overlap, but they operate at different sizes. OKRs are a goal format — one Objective, three to five Key Results, re-set each cycle — and nothing more. Scaling Up is Verne Harnish's full operating system: a One-Page Strategic Plan, quarterly priorities with owners and metrics, a meeting rhythm from daily huddle to annual, and explicit attention to cash and people. OKRs can sit inside Scaling Up; Scaling Up would not fit inside OKRs.

### OKRs: a portable format for the goal itself
OKRs pair one qualitative Objective with three to five measurable Key Results, each moving a named metric from a baseline to a target. Andy Grove developed them at Intel and Google popularized them. The format is intentionally small: it standardizes what a goal looks like and how it is scored, and says nothing about strategy documents, meeting rhythms, hiring or cash. Whatever else a company does, OKRs slot in next to it.
Where OKRs work well: OKRs travel well precisely because they ask for so little. A single team can adopt them next Monday without the rest of the company agreeing to anything, which makes them realistic in organizations where each function works differently enough that one prescribed rhythm would chafe. They are also well suited to environments where the priorities really do change every quarter, and the shared format makes it easy to read another team's commitments without a translation layer.
Where OKRs struggle: OKRs leave out everything that is not the goal: no strategic plan, no meeting rhythm, no scorecard, no place for values, people or cash. That is a feature when a company already has those things and a problem when it does not, and plenty of companies adopt OKRs hoping for an operating system and receive a goal template. The cycle length is a constraint too — anything with a three-year arc has no natural home in a quarterly format, so long-horizon work gets sliced into quarterly pieces that lose the thread.

### Scaling Up: a complete operating system for a growing company
Scaling Up is Verne Harnish's growth methodology, built on the Rockefeller Habits and organized around four decisions: People, Strategy, Execution and Cash. Its central artifact is the One-Page Strategic Plan, which holds core values, purpose, a long-range target, three-to-five-year thrusts, annual goals and the quarterly priorities beneath them. Around that runs a meeting rhythm — daily huddle, weekly, monthly, quarterly and annual — plus a scorecard with a named owner for every line.
Where Scaling Up work well: Scaling Up fits companies where the founding team can no longer hold the plan in their heads and the gap between strategy and the working week is where things break. Because it prescribes the artifacts and the rhythm together, far less is left to invent than with a goal format alone. It is also unusually complete: cash, people and strategy each get an explicit place, so the plan does not quietly collapse into a revenue plan, and the One-Page Strategic Plan gives everyone the same picture of where the company is heading.
Where Scaling Up struggle: Scaling Up asks for a great deal at once. The plan, the full meeting rhythm, the scorecard and the habits amount to a real implementation project, and companies that adopt half of it usually keep the meetings and lose the strategy behind them. It is also opinionated about shape: the plan assumes one company with one coherent strategy, which sits awkwardly over a portfolio or a large matrixed organization. The daily huddle in particular is the first thing to fall over in distributed teams, and once one layer of the rhythm lapses the rest tends to follow.

### When to use each
Choose OKRs: Choose OKRs when the goal-setting is the missing piece and the rest of the operating cadence already exists, or when adoption has to be incremental — one team, one function, one quarter at a time, without asking the whole company to change how it meets.
Choose Scaling Up: Choose Scaling Up when the company needs the whole system: a written strategy, a rhythm that connects the year to the day, and explicit discipline around cash and people. It suits leadership teams ready to adopt something together rather than team by team.
Run both: Running both is normal and not a compromise. Scaling Up supplies the plan, the rhythm and the scorecard; OKRs supply the format for the quarterly priorities that plan produces, so each priority arrives with an owner, a baseline and a target instead of a phrase. The risk to watch is duplication — one set of quarterly commitments, written once, reviewed in the meetings the rhythm already provides.

### At a glance
- Scope: OKRs — A goal format and nothing else | Scaling Up — A full operating system: strategy, execution, cash and people
- Core artifact: OKRs — An Objective with three to five Key Results, per team | Scaling Up — The One-Page Strategic Plan
- Planning horizon: OKRs — A quarter at a time, with annual goals above it by convention | Scaling Up — Long-range target, three-to-five-year thrusts, annual, then quarterly
- Meeting rhythm: OKRs — Not prescribed; a weekly check-in is common practice | Scaling Up — Prescribed: daily huddle, weekly, monthly, quarterly, annual
- Metrics: OKRs — Key Results carry all the measurement | Scaling Up — A weekly scorecard plus a critical number for the quarter
- Cash and people: OKRs — Out of scope | Scaling Up — Explicit: two of the four decisions the method is organized around
- How adoption starts: OKRs — One team can start on its own | Scaling Up — Works when the leadership team adopts it together
- Common failure: OKRs — Adopted in the hope of an operating system, then used as a goal template nobody revisits mid-cycle | Scaling Up — The rhythm is adopted without the plan, so the meetings run on schedule while the strategy never changes

### Where GoalCadence sits
GoalCadence supports OKRs and Scaling Up as first-class frameworks, with goals, a weekly scorecard, meetings and quarterly planning in one place. Different parts of the company can run different frameworks without moving to a second tool.

### Common questions
Q: What is the difference between OKRs and Scaling Up?
A: OKRs are a way to write a goal: an Objective plus three to five Key Results, set for a cycle and scored at the end. Scaling Up is Verne Harnish's complete operating system, covering strategy on a One-Page Strategic Plan, quarterly priorities, a meeting rhythm from daily huddle to annual, and the four decisions of People, Strategy, Execution and Cash. One is a format; the other is the system that surrounds it.

Q: Can you use OKRs inside Scaling Up?
A: Yes. Scaling Up says a quarter should have a small number of priorities with owners and measures, but it does not dictate how each one is phrased. Writing them as Objectives with Key Results gives every priority a baseline, a target and a scoring convention, and the meeting rhythm already provides the review points those goals need.

Q: Are quarterly priorities the same as OKRs?
A: They serve the same purpose — the few things that must move this quarter — but they differ in form. A quarterly priority in Scaling Up sits on the One-Page Strategic Plan with an owner and a success measure, connected upward to the annual goal. An OKR splits that into a qualitative Objective and separately measured Key Results. Many teams write their quarterly priorities in OKR form for exactly that reason.

Q: Does Scaling Up replace OKRs?
A: It can, but it does not have to. Scaling Up already includes a place for quarterly commitments, so a company that implements it fully may never need a separate goal format. Companies that already have OKRs working usually keep the format and adopt the parts of Scaling Up they lack — the strategic plan, the rhythm and the scorecard.

Q: Which should a 50-person company start with?
A: It depends on what is missing rather than headcount. If the leadership team cannot state the strategy the same way twice and meetings are ad hoc, the complete system gives more structure than a goal format would. If the strategy is clear and the rhythm exists but commitments stay vague, starting with OKRs is the smaller, faster change.

## Scaling Up vs 4DX
URL: https://goalcadence.com/scaling-up-vs-4dx

Scaling Up and 4DX sit at different layers. Scaling Up is Verne Harnish's company-wide operating system: a One-Page Strategic Plan, quarterly priorities, a weekly scorecard and a meeting rhythm from daily huddle to annual. 4DX is FranklinCovey's team-level execution discipline: one or two Wildly Important Goals, lead measures, a visible scoreboard and a weekly cadence of accountability. Scaling Up decides what the company works on; 4DX is how a team protects one goal from the whirlwind.

### Scaling Up: the operating system for the whole company
Scaling Up is Verne Harnish's growth methodology, rooted in the Rockefeller Habits and organized around four decisions: People, Strategy, Execution and Cash. The One-Page Strategic Plan holds core values, purpose, a long-range target, three-to-five-year thrusts, annual goals and quarterly priorities on a single sheet. A prescribed meeting rhythm — daily huddle, weekly, monthly, quarterly and annual — plus a scorecard with an owner for every number keeps the plan connected to the working week.
Where Scaling Up work well: Scaling Up is strong at the layer 4DX deliberately leaves alone: deciding what the company should be doing at all. It forces the leadership team to write down strategy in a form everyone can read, and it links a five-year target down through the year to this quarter, so a priority can be traced to the thing it serves. Because cash and people get their own decisions, the plan stays honest about what growth actually requires rather than becoming a wish list of revenue.
Where Scaling Up struggle: Scaling Up is heavy to implement and easy to implement partially. The plan, the rhythm, the scorecard and the habits arrive together, and companies that take only the meetings end up with a well-run calendar and an unchanged strategy. It is also stronger on setting priorities than on driving them: the rhythm gives a priority regular airtime, but nothing in the method insists on the lead-indicator behaviors that would move it, so quarterly priorities can be reviewed all quarter and still be reported red at the end.

### 4DX: a discipline for finishing one goal that matters
4DX, the 4 Disciplines of Execution, comes from FranklinCovey and from Chris McChesney, Sean Covey and Jim Huling. Its four disciplines are Focus on the Wildly Important, Act on Lead Measures, Keep a Compelling Scoreboard, and Create a Cadence of Accountability. Underlying them is the whirlwind: the day job that consumes nearly all of a team's energy and will absorb any goal that is not deliberately protected. 4DX is an execution method, not a planning method.
Where 4DX work well: 4DX is strongest at the point where good plans usually die. Limiting a team to one or two Wildly Important Goals makes the tradeoff explicit, and lead measures give people something they can act on this week instead of a lagging number they can only watch. The scoreboard makes the game legible at a glance, and the weekly session — where each person commits to one or two actions and reports on the last ones — converts intent into a habit. Frontline teams in operations, service and sales tend to adopt it fast.
Where 4DX struggle: 4DX assumes the goal has already been chosen well, and provides no way to choose it. There is no strategy artifact, no place for cash or hiring, and no model of how the company fits together, so a team can execute a mediocre goal flawlessly. Lead measures are also hard to find for research, design and other work where the route to the result is not repeatable, and a poorly chosen one turns into a quota people game. The cadence needs an owner, or it drifts back into a status meeting.

### When to use each
Choose Scaling Up: Reach for Scaling Up when the open question is what the company should be doing and how the year connects to the week — strategy is unwritten, meetings are ad hoc, and priorities differ depending on which leader you ask.
Choose 4DX: Reach for 4DX when the priorities are already clear and the problem is that they never get finished. It is the right tool for a specific team with a relentless day job and one outcome that has slipped for two quarters running.
Run both: They stack rather than compete, because each is weakest where the other is strongest. Scaling Up produces the plan, the quarterly priorities and the scorecard; 4DX takes the one or two priorities that matter most for a given team and adds the lead measures and weekly session that actually move them. The thing to avoid is two parallel scoreboards and two weekly meetings — the 4DX session works best folded into the rhythm that already exists.

### At a glance
- Layer: Scaling Up — Company-wide, starting with the leadership team | 4DX — Team level, one team at a time
- Core artifact: Scaling Up — The One-Page Strategic Plan | 4DX — A visible scoreboard behind one or two Wildly Important Goals
- Strategy: Scaling Up — Explicit: values, purpose, long-range target, thrusts, annual goals | 4DX — Out of scope; the goal is assumed to be chosen already
- Goal count: Scaling Up — Three to five quarterly priorities, plus a critical number | 4DX — One or two goals per team, fewer as you move up
- Measurement: Scaling Up — A weekly scorecard of ongoing numbers, one owner per line | 4DX — Lead measures the team controls, plus the lag measure that defines the goal
- Meeting rhythm: Scaling Up — Daily huddle, weekly, monthly, quarterly and annual | 4DX — One short weekly session, held separately from the day-job meetings
- What it asks of you: Scaling Up — Leadership adopts the whole system together | 4DX — A single team can start without company-wide agreement
- Common failure: Scaling Up — The rhythm is adopted without the plan, so the meetings run while the strategy never changes | 4DX — The whirlwind wins: the scoreboard goes stale and the weekly session turns into a status update

### Where GoalCadence sits
GoalCadence supports Scaling Up and 4DX as first-class frameworks, with goals, a weekly scorecard, meetings and quarterly planning in one place. Different parts of the company can run different frameworks, so a frontline team can work in 4DX while the leadership team runs the Scaling Up rhythm.

### Common questions
Q: What is the difference between Scaling Up and 4DX?
A: Scaling Up is a company-wide operating system from Verne Harnish: a One-Page Strategic Plan, quarterly priorities, a weekly scorecard and a meeting rhythm running from daily huddle to annual. 4DX is FranklinCovey's team-level execution discipline: narrow to one or two Wildly Important Goals, act on lead measures, keep a compelling scoreboard, and hold a weekly cadence of accountability. Scaling Up chooses the priorities; 4DX finishes them.

Q: Can you run Scaling Up and 4DX together?
A: Yes, and they combine naturally because they cover different ground. Scaling Up sets the quarterly priorities and the scorecard; 4DX supplies the lead measures and weekly discipline for the priority a given team must not miss. The practical caution is overhead: fold the 4DX session into the existing weekly meeting rather than adding a second one.

Q: Is a quarterly priority the same as a Wildly Important Goal?
A: They are related but not interchangeable. A quarterly priority sits on the One-Page Strategic Plan with an owner and a measure, connected upward to the annual goal, and a company typically has three to five. A Wildly Important Goal is written as from X to Y by when, a team holds only one or two, and it comes with lead measures and a scoreboard attached. A priority can become a WIG; it is not automatically one.

Q: Does 4DX include a scorecard like Scaling Up?
A: Both use a visible board, but for different jobs. The Scaling Up scorecard tracks ongoing weekly numbers across the business, each with an owner, so the leadership team can see health. A 4DX scoreboard is built for one goal and is designed for the team playing the game: it shows the lead and lag measures for that goal and whether the team is winning right now. Many companies keep both.

Q: Which should a company adopt first?
A: It depends on where the breakdown is. If leaders disagree about what the company is trying to do, the strategic plan and rhythm address that first, and 4DX would only make a team faster at the wrong goal. If the plan is clear and it is execution that keeps slipping, starting 4DX with one team is far less disruptive than a full operating-system rollout.

## OKRs vs SMART Goals
URL: https://goalcadence.com/okr-vs-smart-goals

OKRs and SMART goals solve different problems. SMART is a quality test applied to a single goal: Specific, Measurable, Achievable, Relevant, Time-bound. OKRs are a structure for a whole organization's priorities, pairing one Objective with three to five Key Results and re-setting the set each cycle. A SMART goal makes one goal well written. OKRs decide which goals exist, connect them across teams, and give them a review rhythm. Many teams write their Key Results to the SMART test.

### OKRs: a system for choosing and connecting goals
OKRs pair one qualitative Objective with three to five measurable Key Results that would prove it happened. Andy Grove developed the format at Intel, and Google popularized it. The unit is not a single goal but a set: a team commits to a small number of Objectives for a cycle, usually a quarter, and the Key Results underneath each one carry all of the measurement. Because every team publishes its set, OKRs are as much a coordination device as a goal format.
Where OKRs work well: OKRs are strongest when several teams have to pull in the same direction and someone needs to see whether they are. Publishing a small set each quarter forces the prioritization argument to happen out loud, at a specific time, rather than being settled quietly by whoever is busiest. The cycle also gives goals an expiry date, so stale commitments fall away instead of accumulating. And the scoring convention, where an ambitious goal landing around 0.7 counts as success, lets a team aim past what it is confident of.
Where OKRs struggle: OKRs carry real overhead. Drafting, aligning and scoring a set every quarter costs meeting time, and in a company of fewer than about twenty people that cost can exceed the coordination it buys. They also invite gaming: when Key Results are tied to compensation, teams write targets they already know they will hit. And OKRs are a poor home for maintenance work, because there is no useful Objective for keeping the lights on, so teams whose job is exactly that end up inventing goals to have something to submit.

### SMART Goals: a quality test for one goal
SMART is a checklist for testing whether a goal is written well enough to act on: Specific, Measurable, Achievable, Relevant and Time-bound. The acronym is commonly traced to a 1981 article by George T. Doran, and the wording behind the letters has drifted since. It says nothing about how many goals you should have, who sets them, or how often they are reviewed. Applied to any goal in any framework, it catches the most common defect of all: a goal nobody can tell they have met.
Where SMART Goals work well: SMART is quick to teach and works at any scale. A manager can apply it in a one-to-one, to one person's goal, with no rollout, no software and no quarterly ceremony, which is why it survives in performance reviews, development plans and project charters decades after more elaborate systems came and went. It is also framework-agnostic: a Key Result, a 4DX lead measure and a personal objective all benefit from the same five questions, so a team that uses nothing else still gets most of the value of clear goal writing.
Where SMART Goals struggle: SMART tests one goal at a time and has nothing to say about the set. Ten SMART goals can be individually flawless and collectively incoherent, contradictory, or simply too many, and the checklist will not notice. Achievable also pulls against ambition, so teams under pressure write targets they are sure of, which is a known reason SMART goals cluster just above what would have happened anyway. And it stops at the writing: with no cadence, no owner convention and no scoring, a SMART goal can be perfectly formed and never looked at again.

### When to use each
Choose OKRs: Use OKRs when the problem is which goals exist and how they connect across teams. They suit organizations with shifting priorities that need the whole picture visible in one place, and re-decided, every quarter.
Choose SMART Goals: Use SMART when the problem is a single goal that is too vague to act on. It is the right tool for individual objectives, development plans, project charters and small teams that need clarity without adopting a planning system.
Run both: They stack rather than compete. OKRs decide what the small set of goals is and when it gets reviewed; SMART is the test you run on each Key Result before committing to it. A Key Result that fails the Measurable or Time-bound question is worth rewriting no matter which framework it lives in.

### At a glance
- What it is: OKRs — A goal-setting and alignment system | SMART Goals — A quality test for a single goal statement
- Unit: OKRs — A set of Objectives, each with three to five Key Results | SMART Goals — One goal, written one at a time
- Origin: OKRs — Andy Grove at Intel; popularized at Google | SMART Goals — Commonly traced to George T. Doran, 1981
- Ambition: OKRs — Deliberately stretching; around 0.7 can be a good result | SMART Goals — Achievable by design; targets are meant to be met
- Cadence: OKRs — Set each cycle, checked weekly, scored at the end | SMART Goals — None specified; inherited from whatever process surrounds it
- Alignment: OKRs — Published across teams so dependencies are visible | SMART Goals — No alignment mechanism; works for one person or one project
- Learning curve: OKRs — A couple of cycles of practice before it settles | SMART Goals — Explained in a single meeting
- Common failure: OKRs — Set at an offsite, never reviewed, or padded until every score is a 1.0 | SMART Goals — Individually flawless goals that add up to nothing, with Achievable used to justify a soft target

### Where GoalCadence sits
GoalCadence has first-class support for OKRs: Objectives, Key Results, weekly check-ins and scoring on a quarterly cycle. SMART is not a separate mode, because it is a way of writing a goal rather than a system to run: the Key Result format already asks for the metric, baseline, target and date that the SMART test looks for.

### Common questions
Q: What is the difference between OKRs and SMART goals?
A: SMART is a five-part test for whether one goal is written well: Specific, Measurable, Achievable, Relevant, Time-bound. OKRs are a system for the whole set of goals, pairing an Objective with three to five Key Results, re-chosen each quarter and published so teams can see each other's commitments. SMART improves a goal you already have. OKRs decide which goals you have at all.

Q: Can a Key Result be a SMART goal?
A: Yes, and it is the most useful place the two meet. A well-formed Key Result names a metric, a baseline, a target and an end date, which satisfies Specific, Measurable and Time-bound directly. Relevant is answered by the Objective it sits under. Achievable is the only letter that needs care, since OKRs are often set to be a stretch rather than a certainty.

Q: Are SMART goals outdated?
A: No. The criticism is usually aimed at something SMART never claimed to do: it tests one goal, so it cannot tell you whether you chose the right goals or too many of them. As a writing test it is as useful as it was in 1981, and it is still the fastest way to fix the most common problem in goal setting, which is a goal nobody can measure.

Q: Should a small team use OKRs or SMART goals?
A: Under roughly ten people, SMART goals plus a regular review often deliver most of the benefit, because alignment happens in conversation and the quarterly OKR process is overhead you do not need yet. OKRs start to earn their cost when there are enough teams that nobody can hold the full picture in their head, or when priorities visibly conflict.

Q: Does the A in SMART mean achievable or ambitious?
A: Achievable, in the original formulation, and that is the real tension with OKRs. SMART asks whether a goal can realistically be reached; OKRs often ask a team to aim past that point and treat roughly 70 percent as a win. Teams that use both usually apply SMART to the wording and let the OKR cycle set the level of ambition.

## OKRs vs Balanced Scorecard
URL: https://goalcadence.com/okr-vs-balanced-scorecard

OKRs are a quarterly goal format: one Objective with three to five Key Results, re-set each cycle. The Balanced Scorecard is a strategy management system that measures performance across four perspectives — Financial, Customer, Internal Business Process, and Learning and Growth — so financial results are read alongside their causes. OKRs ask what a team will change this quarter. The Balanced Scorecard asks whether the whole strategy is in balance, and it usually runs on an annual frame.

### OKRs: a quarterly commitment to change something
OKRs pair a qualitative Objective with three to five Key Results that would prove it happened, and the whole set is re-chosen at the start of each cycle. The format came out of Intel under Andy Grove and spread from Google. What it standardizes is deliberately small: a shape for a goal, a baseline, a target and a date. Everything else — which Objectives matter, what a strategy should cover, how the pieces connect — is left to the team that writes them.
Where OKRs work well: OKRs suit companies whose strategy is still moving. Choosing a fresh set every ninety days makes a change of direction cheap, and the list stays short by construction, because nobody can carry twenty Objectives through a quarterly review. The weekly check-in means a drifting goal surfaces in week three rather than week twelve. And the format is simple enough to explain in one meeting, so it reaches the level where the work is actually done instead of staying with the leadership team.
Where OKRs struggle: OKRs have no opinion about coverage. Nothing in the format stops a company from setting four Objectives that are all revenue and none that concern the customers, the processes or the people who deliver it, and quarterly cycling makes that easier to miss. They are also awkward for multi-year strategy: a two-year platform migration has to be sliced into quarters that individually look unremarkable. And they do not model cause and effect — the link between one team's goal and another's is asserted in a planning meeting, not drawn.

### Balanced Scorecard: a strategy measured from four sides
Robert Kaplan and David Norton introduced the Balanced Scorecard in Harvard Business Review in 1992, as an answer to managing by financial results alone. It sorts objectives, measures, targets and initiatives into four perspectives: Financial, Customer, Internal Business Process, and Learning and Growth. The strategy map came later in their work, drawing the cause-and-effect links between the perspectives and turning the scorecard from a measurement framework into a way of describing what a strategy actually claims.
Where Balanced Scorecard work well: The Balanced Scorecard is strongest when a company has to defend a strategy to people who would otherwise read only the financials. The four perspectives make the argument explicit: investment in people and processes shows up as customer outcomes first and revenue later, which protects long-horizon work from being cut in a bad quarter. It is well established in regulated industries, public sector bodies and large enterprises, and a strategy map gives a board one page that shows the whole logic.
Where Balanced Scorecard struggle: The Balanced Scorecard is heavy. Building a full map with measures and targets across all four perspectives is a months-long exercise, often with outside help, and the market can move while it is being built. Its natural rhythm is annual with quarterly reviews, which is slow for a company changing direction. It also tends to stay near the top: unless real effort goes into cascading it, frontline teams see a corporate scorecard they had no hand in and cannot act on directly.

### When to use each
Choose OKRs: Use OKRs when priorities change faster than a year and the work has to reach team level quickly. They suit companies where the live question is what to do next quarter rather than how to describe the strategy.
Choose Balanced Scorecard: Use the Balanced Scorecard when the strategy is stable enough to be worth mapping and the problem is that it is being judged on financial results alone. It suits larger, regulated or public organizations, and anyone who must show a board why non-financial investment matters.
Run both: The pairing is common and it works. The scorecard says what the strategy is and how the four perspectives connect; OKRs are how a team moves one part of it in a given quarter. A scorecard measure that is off target is the natural input to the next set of Objectives, and the perspectives are a useful check on whether those Objectives cover more than revenue.

### At a glance
- Purpose: OKRs — Change a few specific things this cycle | Balanced Scorecard — Describe and measure a whole strategy
- Origin: OKRs — Andy Grove at Intel; popularized at Google | Balanced Scorecard — Kaplan and Norton, Harvard Business Review, 1992
- Structure: OKRs — An Objective plus three to five Key Results | Balanced Scorecard — Objectives, measures, targets and initiatives in four perspectives
- Required coverage: OKRs — None; the team chooses what to work on | Balanced Scorecard — Financial, Customer, Internal Business Process, Learning and Growth
- Time horizon: OKRs — A quarter, re-set each cycle | Balanced Scorecard — Annual strategy, reviewed quarterly, against a multi-year map
- Cause and effect: OKRs — Implied, argued in a planning session | Balanced Scorecard — Made explicit on a strategy map
- Where it lives: OKRs — Every level, frequently drafted by the team itself | Balanced Scorecard — Executive and board level, then cascaded downward
- Common failure: OKRs — Objectives that are all revenue, set once and never reviewed | Balanced Scorecard — A map built over months, then hung on a wall while the business keeps running on the financials

### Where GoalCadence sits
GoalCadence has first-class support for OKRs: Objectives, Key Results, weekly check-ins and quarterly scoring. Balanced Scorecard is offered as a configurable template rather than a first-class framework, so it can be set up around the four perspectives without the depth of tooling the OKR workflow has.

### Common questions
Q: What is the difference between OKRs and the Balanced Scorecard?
A: OKRs are a quarterly goal format: an Objective with three to five Key Results, re-chosen every cycle. The Balanced Scorecard is a strategy management system that requires performance to be measured across four perspectives — Financial, Customer, Internal Business Process, and Learning and Growth — usually on an annual frame. OKRs are built to change things; the scorecard is built to describe a strategy and keep it in balance.

Q: Can you use OKRs and a Balanced Scorecard together?
A: Yes, and it is one of the more natural combinations. The scorecard supplies the strategy and the measures, including the non-financial ones that tend to get dropped, and OKRs become the quarterly mechanism for moving whichever measures need attention. The main caution is process weight: run the scorecard annually and let the OKR cycle do the quarterly work, rather than rebuilding both.

Q: What are the four perspectives of the Balanced Scorecard?
A: Financial, Customer, Internal Business Process, and Learning and Growth. The order is a causal argument rather than a ranking: investing in Learning and Growth improves internal processes, better processes improve customer outcomes, and customer outcomes eventually show up in financial results. A strategy map draws those links so the assumption behind the strategy can be tested against what actually happens.

Q: Is the Balanced Scorecard still relevant?
A: It remains widely used in large enterprises, government and regulated industries, where a strategy has to be explained and defended outside the operating team. What has changed is the pace around it: a framework designed for annual planning sits awkwardly with companies that reconsider direction every quarter, which is why many of them keep the four perspectives as a coverage check and run a faster goal cycle underneath.

Q: Does a small company need a Balanced Scorecard?
A: Usually not as a full implementation. Under a few hundred people, the mapping exercise costs more than the clarity it returns, and the same coverage discipline can be borrowed cheaply by asking whether this quarter's goals touch customers, processes and people as well as revenue. The full framework earns its cost when there are enough layers that the strategy has to be written down to travel.

## Balanced Scorecard vs Hoshin Kanri
URL: https://goalcadence.com/balanced-scorecard-vs-hoshin-kanri

The Balanced Scorecard is a measurement system: Kaplan and Norton's four perspectives — Financial, Customer, Internal Business Process, and Learning and Growth — force a strategy to be described with its causes, not only its results. Hoshin Kanri is a deployment system from Japanese quality management: a few breakthrough objectives are negotiated down through every level by catchball and tracked on an X-matrix. One answers whether the strategy is balanced; the other answers whether it reached the floor.

### Balanced Scorecard: a strategy described from four sides
Robert Kaplan and David Norton published the Balanced Scorecard in Harvard Business Review in 1992, arguing that financial measures report on decisions already made and need to be read next to the things that produce them. The framework sorts objectives, measures, targets and initiatives into four perspectives: Financial, Customer, Internal Business Process, and Learning and Growth. The strategy map arrived later in their work and made the cause-and-effect chain between the perspectives explicit rather than assumed.
Where Balanced Scorecard work well: The Balanced Scorecard is unusually good at making a strategy legible. One map states what the organization believes: that these capabilities produce these processes, which produce these customer outcomes, which produce these numbers — a claim that can then be tested against results. That suits boards, regulators and public sector bodies, where a strategy has to be explained and defended outside the operating team, and it gives non-financial investment a defensible place in the reporting pack.
Where Balanced Scorecard struggle: The Balanced Scorecard tells you what to measure, not who does what on Monday. Its unit is the measure, and an organization can populate all four perspectives thoroughly and still have no mechanism for turning them into assignments. Building it takes months and is often outsourced, which weakens ownership of the result. And because it was designed as a way to describe and report a strategy, the link between a corporate scorecard and a frontline team's week has to be built separately.

### Hoshin Kanri: a strategy pushed down until someone owns it
Hoshin Kanri — policy deployment, or strategy deployment, in English — grew out of Japanese quality management in the 1960s and 1970s at companies including Bridgestone and Toyota, shaped by the plan-do-check-act thinking Deming brought to Japan. An organization picks a very small number of breakthrough objectives, often three to five for the year, then deploys them: each level negotiates its own contribution with the level above through catchball, and the X-matrix records how objectives, strategies, measures and owners line up.
Where Hoshin Kanri work well: Hoshin Kanri is strongest at getting a strategy out of the boardroom. Catchball is a genuine negotiation rather than a cascade — a plant manager pushes back on a target and the conversation changes the plan, which produces commitment that assigned goals rarely do. The insistence on very few objectives makes trade-offs unavoidable at the top, where they belong. And because it comes from a quality tradition, the annual review asks what the process taught you, not only whether the number was hit.
Where Hoshin Kanri struggle: Hoshin Kanri assumes stability. It runs on an annual planning cycle against a three to five year breakthrough horizon, and catchball through several levels takes weeks, which is expensive in a company whose strategy could change by March. The X-matrix is genuinely hard to read without training and is easily reduced to a template filled in once. It is also thin on everything outside the breakthrough objectives: daily management is assumed to exist alongside it, and organizations without that discipline find hoshin silent about the rest of the work.

### When to use each
Choose Balanced Scorecard: Use the Balanced Scorecard when the problem is describing and reporting a strategy — showing a board or a regulator how investment in people and processes turns into results, and keeping the whole picture in view rather than the financials alone.
Choose Hoshin Kanri: Use Hoshin Kanri when the strategy is already clear and the problem is executing it at every level. It suits operations-heavy organizations with a stable annual rhythm and enough management layers that alignment will not happen on its own.
Run both: They are complementary and organizations do combine them. The scorecard supplies the measures and the cause-and-effect logic; hoshin supplies the deployment mechanism that turns a few of those objectives into negotiated commitments at each level. The practical caution is weight — running both in full is a great deal of planning process, so most companies take the map from one and the catchball from the other.

### At a glance
- Origin: Balanced Scorecard — Kaplan and Norton, Harvard Business Review, 1992 | Hoshin Kanri — Japanese quality management at Bridgestone and Toyota, with Deming's influence
- Core question: Balanced Scorecard — Is the strategy balanced across the things that drive results? | Hoshin Kanri — Has the strategy reached every level as a real commitment?
- Organizing structure: Balanced Scorecard — Four perspectives and a strategy map | Hoshin Kanri — A few breakthrough objectives and the X-matrix
- How it spreads: Balanced Scorecard — Cascaded downward as measures and targets | Hoshin Kanri — Negotiated level by level through catchball
- Number of objectives: Balanced Scorecard — Typically a dozen or more, spread across four perspectives | Hoshin Kanri — Three to five breakthrough objectives for the year
- Planning horizon: Balanced Scorecard — Annual, reviewed quarterly, against a multi-year map | Hoshin Kanri — Annual, against a three to five year breakthrough
- Review emphasis: Balanced Scorecard — Performance against the measures | Hoshin Kanri — Process learning through plan-do-check-act
- Common failure: Balanced Scorecard — A map built over months and reported against, with nobody accountable for any single line on it | Hoshin Kanri — Catchball collapses into a cascade, and the X-matrix becomes a template filled in once a year

### Where GoalCadence sits
GoalCadence supports Balanced Scorecard and Hoshin Kanri as configurable templates rather than first-class frameworks; its deepest tooling is built for OKRs, Scaling Up and 4DX. Teams running either framework here should expect to configure a template rather than find purpose-built strategy map or X-matrix tooling.

### Common questions
Q: What is the difference between the Balanced Scorecard and Hoshin Kanri?
A: The Balanced Scorecard is about measurement: it requires a strategy to be expressed across four perspectives — Financial, Customer, Internal Business Process, and Learning and Growth — so results are read with their causes. Hoshin Kanri is about deployment: a handful of breakthrough objectives are negotiated down through every level by catchball and tracked on an X-matrix. One makes a strategy legible, the other makes it owned.

Q: What is catchball in Hoshin Kanri?
A: Catchball is the back-and-forth by which an objective is agreed between levels. Leadership proposes a breakthrough objective, the next level down responds with what it can commit to and what would have to change, and the objective is revised before it is accepted. The point is that targets are negotiated rather than assigned, so the people who have to deliver a goal have already shaped it.

Q: What is an X-matrix?
A: The X-matrix is the single-page grid used in Hoshin Kanri to show how the pieces of a plan relate. Long-term breakthroughs, annual objectives, improvement priorities and measures sit along the four edges, with owners in a column at the side, and marks in the corners show which items connect. It is dense by design, and it usually needs an explanation before a new reader can follow it.

Q: Can you use a Balanced Scorecard with Hoshin Kanri?
A: Yes. A common arrangement uses the scorecard's four perspectives to choose and measure the strategy, then uses hoshin catchball to deploy the two or three objectives that matter most into level-by-level commitments. The risk is process overload, so teams that combine them usually take the coverage discipline from one and the deployment mechanism from the other rather than running both frameworks in full.

Q: Is Hoshin Kanri only for manufacturing?
A: No, though its roots are there and that shows. The method assumes a relatively stable annual plan and several management layers to negotiate through, which is common in manufacturing, healthcare, logistics and large service organizations. Software and other fast-moving companies often keep catchball and the discipline of very few objectives while running a shorter cycle than the annual one hoshin assumes.

# Agent skills (9)

Markdown instruction files for Claude, Cursor, ChatGPT and Copilot. Each
one is reproduced below in full, exactly as it downloads from
https://goalcadence.com/skills/files/<slug>.md

## OKR Writer
URL: https://goalcadence.com/skills/okr-writer
File: https://goalcadence.com/skills/files/okr-writer.md
Framework: OKR

A Markdown skill that turns a vague intention into a well-formed OKR: one Objective with no numbers in it, and three to five Key Results written from a real baseline to a real target. Copy it or download the .md — no signup.

--- begin skill file ---
# OKR Writer

You help a team turn a vague intention into a well-formed OKR: one qualitative
Objective, and three to five Key Results that would prove it happened.

## What you do

Given a goal, a team, a time period, or just a rough sentence about what someone
wants, you produce a draft OKR and explain the choices you made. You ask for the
minimum you need and get on with it — one round of questions at most.

## What you need before drafting

Ask only for what is missing, in one message, and never more than four questions:

1. **Who owns this** — a team or a person, not a department in the abstract.
2. **The cycle** — usually a quarter. You need the end date to write targets.
3. **The current numbers** — a Key Result without a baseline cannot be graded.
   If the person does not know a baseline, say so in the draft and mark it
   `[baseline needed]` rather than inventing one.
4. **What "better" means here** — the outcome they want, not the work they plan.

If they give you enough to draft something useful, draft it. Do not interrogate.

## Rules for the Objective

- No numbers. The Objective is direction; the Key Results carry measurement.
- Short enough to quote from memory. If it needs a comma and a subclause, cut it.
- It must be an outcome, not a deliverable. "Launch the partner portal" is a
  project. "Make partners self-sufficient without calling us" is an Objective.
- One to three per team per cycle. If asked for seven, push back once and
  explain that a team with seven Objectives has effectively set none.

## Rules for Key Results

- Three to five per Objective.
- Write every one in **from X to Y** form: `Lift win rate from 22% to 35%`.
  The baseline is not decoration — without it the result cannot be scored.
- Measure outcomes the team influences, not activities it controls. Apply the
  test: *could someone complete all the planned work and still miss this
  number?* If no, it is a task wearing a Key Result's clothes.
- Prefer numbers the team already collects. A Key Result that needs new
  instrumentation before it can be read will go unmeasured for six weeks.
- Include at least one counter-metric when the Objective could be gamed. If the
  Objective pushes volume, add a quality or cost guardrail.
- Mark each as **committed** (expected to reach 1.0) or **aspirational**
  (0.7 is a good outcome). Say which and why.

## What you output

```
Objective: <one line, no numbers>

Key Results:
1. <metric> from <baseline> to <target>   [committed | aspirational]
2. ...
3. ...

Notes:
- Why these Key Results and not others
- What this OKR deliberately does not cover
- Any baseline the team still needs to find
```

Then add one short paragraph: **how this could be gamed**, and what the team
should watch for. Be specific. This is the most useful thing you produce.

## Things to refuse politely

- Writing Key Results with no baseline, when a baseline is knowable. Say what
  you need instead.
- More than five Key Results per Objective. Offer the strongest five and
  explain what you dropped.
- Turning a task list into an OKR. If everything they describe is work rather
  than outcome, say so plainly and ask what the work is supposed to change.

## Tone

Direct and concrete. No preamble, no encouragement, no restating the request.
Give the draft, then the reasoning. Where you are uncertain, name the
uncertainty rather than smoothing over it.

---

Built by GoalCadence (https://goalcadence.com) — one platform for OKRs, Scaling Up, and 4DX.
--- end skill file ---

## OKR Grader
URL: https://goalcadence.com/skills/okr-grader
File: https://goalcadence.com/skills/files/okr-grader.md
Framework: OKR

A Markdown skill that grades a draft OKR out of 100 before the quarter starts, with line-by-line PASS / TIP / FIX feedback. It scores whether the OKR is gradeable at all, not whether it is ambitious. Copy it or download the .md — no signup.

--- begin skill file ---
# OKR Grader

You grade a draft OKR before the quarter starts, so the problems get fixed
while fixing them is still cheap.

You are not scoring achievement at quarter end. You are judging whether this
OKR is *gradeable at all* — whether, ninety days from now, anyone could settle
what happened without an argument.

## What you output

A score out of 100, then line-by-line feedback. Always in this order.

```
Score: 68/100

Objective — 18/25
<one line on what works, one on what does not>

Key Results
1. "Lift win rate from 22% to 35%"          PASS
   Baseline and target both present.
2. "Improve onboarding"                      FIX
   No metric, no baseline, no target. Not gradeable.
3. "Run four customer workshops"              TIP
   Measures activity. What is the workshop supposed to change?

Biggest risk: <the single thing most likely to go wrong>
```

## How to score

**Objective — 25 points**

- Start at 25.
- Contains a number: −8. The Objective is direction; measurement belongs to the
  Key Results.
- Reads as a task rather than an outcome: −10. Task verbs to watch for — ship,
  launch, build, implement, complete, deliver, release, run, hold, publish,
  migrate, roll out, set up.
- Longer than about fourteen words: −5. If it cannot be quoted from memory in a
  meeting, it will not be.

**Key Results — 75 points**

Rate each one, then average and scale:

- **1.0** — moves a named metric from an explicit baseline to an explicit
  target, in *from X to Y* form.
- **0.7** — measurable, but no baseline. Gradeable only by argument.
- **0.6** — measures an activity the team fully controls rather than an outcome.
- **0.0** — no number at all. Not gradeable.

Then apply a count factor: one Key Result ×0.6, two ×0.85, more than five ×0.85.
A single Key Result is usually a metric with an Objective bolted on; more than
five means nothing was prioritized.

`Total = objectiveScore + 75 × averageKeyResult × countFactor`

## Bands

- **80–100** — gradeable. Ship it.
- **55–79** — will produce an argument at quarter end. Name exactly which Key
  Result causes it.
- **Below 55** — this is a plan, not an OKR. Say so directly.

## The checks that matter most

Run these regardless of score, and report any that fire:

1. **The completion test.** Could the team finish every piece of planned work
   and still miss this number? If no, it is a task.
2. **The sandbag test.** Is any target within ~10% of the baseline? Flag it.
   A target the team is certain to hit tells you about the target, not the team.
3. **The instrumentation test.** Does reading any of these numbers require
   tooling that does not exist yet? Those go unmeasured for six weeks.
4. **The gaming test.** Name the cheapest dishonest way to hit each Key Result.
   If it is easy, recommend a counter-metric.
5. **The ownership test.** Is there one name against the Objective? "The team"
   is not an owner.

## Things to be firm about

- Do not soften a 0.0. A Key Result with no number is not "a good start" — it
  is not a Key Result, and saying so now saves the quarter.
- Do not invent baselines to make a draft look better. Mark them
  `[baseline needed]`.
- Do not grade on ambition. A modest, gradeable OKR scores higher than an
  inspiring, ungradeable one. That is the point.

## Tone

Blunt and specific. Quote the exact text you are criticising. Never give a
score without saying what would raise it.

---

Built by GoalCadence (https://goalcadence.com) — one platform for OKRs, Scaling Up, and 4DX.
--- end skill file ---

## WIG Definer
URL: https://goalcadence.com/skills/wig-definer
File: https://goalcadence.com/skills/files/wig-definer.md
Framework: 4DX

A Markdown skill that narrows a long list of goals down to one or two Wildly Important Goals, written in 4DX's from-X-to-Y-by-when form, and checks the team can actually move them. Copy it or download the .md — no signup.

--- begin skill file ---
# WIG Definer

You help a team cut a list of goals down to one Wildly Important Goal — two at
the absolute outside — written in 4DX form: **From X to Y by WHEN**.

This is Discipline 1 (McChesney, Covey and Huling). Your job is the cutting,
not the collecting. Teams arrive with eight things they care about, wanting
help ranking them. Ranking is not the work. Choosing one is.

## What you need before starting

Ask only for what is missing, in one message, and never more than four questions:

1. **Whose WIG is this** — a team with a shared calendar, not a division. A WIG
   spanning four teams belongs to none of them.
2. **The company WIG above it**, if one exists. A team WIG that does not
   visibly move it is a side project with good lighting.
3. **The current number and the deadline.** "From X" needs a real X; "by WHEN"
   needs a calendar date, six to twelve months out.
4. **What the whirlwind looks like** — the day job that already fills the week:
   tickets, month-end close, shipping the roadmap.

If they have given you enough to draft, draft it. Do not interrogate.

## One WIG. Two if you must.

Quote the arithmetic back: a team pursuing two or three goals beyond the
whirlwind typically achieves two or three; four to ten, it achieves one or two;
eleven or more, none. A team with eleven priorities has a to-do list. Allow a
second WIG only when the team is genuinely two crews with separate work and
separate numbers. Never a third.

## The whirlwind test

The whirlwind is not the enemy — it is the urgent work that keeps the business
alive, and it wins any fair fight against something merely important. So: can
this WIG advance on the two hours per person per week the whirlwind will
concede? If it needs twenty, it is a staffed project, and should be named one.

## Line of sight to the company WIG

The company WIG is the war; each team WIG is a battle you must win to win it.
Never cascade it downward verbatim — a support team handed "grow revenue from
$40M to $60M" cannot move that, and will quietly return to the whirlwind. Test
each candidate by finishing the sentence out loud: *"If we hit this, the
company WIG moves because ___."* If the "because" takes three hops, cut it.

## The movability test

The team must move the number without new budget, new headcount, or another
team's roadmap. Ask for three things someone could do differently on Monday
morning; if all three need an outsider to say yes, this is somebody else's WIG.
Influence is enough; control is not.

## Writing the line

- **X** is today's measured number, not an estimate.
- **Y** is far enough that hitting it would be noticed. Within about 10% of X
  is the whirlwind's normal drift.
- **WHEN** is a date on a calendar.
- No compound WIGs. "…by June, while also reducing churn" is two WIGs joined
  by a comma.
- No verbs like improve, optimize, drive. The measure carries the meaning.

## What you output

```
WIG: From <X, today's number> to <Y> by <date>

Owner: <one name>
Serves: <company WIG, or "none stated">

Why this one:
- <what winning it buys that the others do not>

Cut, and why:
- <goal> — <whirlwind work | not movable by this team | no line of sight>

Consciously not improving this period:
- <what the team is letting sit>

Movability check: <three things someone could do differently on Monday>
```

Then add one short paragraph: **what will pull this team back into the
whirlwind by week three**, and the earliest observable sign of it. Be specific.
This is the most useful thing you produce.

## Things to refuse politely

- Writing three or more WIGs. Give the strongest one and rank the rest as
  "next".
- A WIG stated as a project — "Launch the new onboarding flow". Ask what number
  the launch is meant to move, and write that instead.
- A WIG whose X is unknown but knowable. Mark it `[baseline needed]`; with no X
  there is nothing to put on a scoreboard.
- Cascading a company WIG unchanged to every team.

## Tone

Direct. Do the cutting out loud — name every goal you dropped and the reason,
because that list is what the team will argue about. No preamble, no
encouragement. Where you are guessing at a baseline or a line of sight, name
the guess.

---

Built by GoalCadence (https://goalcadence.com) — one platform for OKRs, Scaling Up, and 4DX.
--- end skill file ---

## Lead Measure Finder
URL: https://goalcadence.com/skills/lead-measure-finder
File: https://goalcadence.com/skills/files/lead-measure-finder.md
Framework: 4DX

A Markdown skill that takes a lag measure and finds the two or three lead measures that are both predictive of it and influenceable by the team — the pairing 4DX is built on. Copy it or download the .md — no signup.

--- begin skill file ---
# Lead Measure Finder

You take a lag measure — the result a team has already committed to — and find
the two or three lead measures that will actually move it.

A lag measure tells you whether you won, too late to do anything about it. A
lead measure is what the team does this week that makes next month's lag
measure move. Discipline 2 of 4DX (McChesney, Covey and Huling) is the
difference between watching your number and moving it.

## What you need before starting

Ask only for what is missing, in one message, and never more than four questions:

1. **The lag measure**, with its baseline and its date.
2. **The team and its size.** Commitments are per person per week, so headcount
   changes the arithmetic.
3. **What the team already tracks weekly.** A lead measure needing new
   instrumentation goes uncounted for six weeks.
4. **The team's own theory** of what drives the lag measure. Start there and
   test it; do not silently swap in yours.

## The two tests. Both, every time.

**Predictive.** If this number goes up and nothing else changes, the lag
measure moves. Test it backwards: *"If we did forty of these a week for eight
weeks and the result did not budge, what would that tell us?"* If the honest
answer is "nothing, they are unrelated", it is not predictive. A correlation
the team has watched happen beats a plausible story.

**Influenceable.** A named person can change this number this week, alone, with
no budget request, no hiring, no other team's roadmap. Test it forwards:
*"What does someone do differently on Monday morning?"* If the answer is
"marketing sends us more leads", the measure is influenceable by marketing —
their lead measure, not this team's.

The pairing is the whole idea. Predictive but not influenceable is a forecast.
Influenceable but not predictive is busywork with a spreadsheet.

## Lead measure or activity metric?

Activity metrics are what you get when only the second test is applied. Tells:

- **It counts what the team already does at that rate.** A lead measure demands
  a behavior change. If today's number is already the target, nothing moves.
- **Nobody can say what number is enough.** "More customer calls" is a
  direction. "Eight discovery calls per rep per week" is a lead measure.
- **It is a team total.** Team-level counts hide the two people carrying it.
  Commitments belong to individuals.
- **It can be hit without the quality that made it predictive.** Put the
  standard inside the definition: not "twelve site visits" but "twelve with the
  checklist completed on site".

Prefer behaviors where the team is currently *inconsistent*. The gap between
best and worst performer is where the lag measure hides.

## Setting the weekly commitment

- Per person, per week. Never per quarter, never per team.
- Sized to survive a bad week in the whirlwind — the team's good week today,
  not an ideal one. Missed three weeks running, a commitment is dead.
- Countable by Friday, by its owner, in under two minutes. If counting needs a
  report someone else runs, it will not happen.
- Two or three per goal in total, not per person.
- Show the arithmetic, and say plainly if it does not reach the target.

## What you output

```
Lag measure: From <X> to <Y> by <date>

Lead measure 1: <behavior + quality standard>, <n> per person per week
  Predictive:    <why — observed evidence, or mark [assumption]>
  Influenceable: <what someone does differently on Monday>
  Counted by:    <who, where, by Friday>
  Arithmetic:    <n x people x weeks -> expected movement in the lag measure>

Lead measure 2: <same shape>

Rejected:
- <candidate> — fails <predictive | influenceable>: <reason>

Weakest assumption: <the link most likely to be wrong, and the week by which
the team will know>
```

Then add one short paragraph: **how each commitment could be hit without the
result moving**, and the standard that closes the loophole.

## Things to refuse politely

- More than three lead measures. Two well-counted beat five half-counted.
- A project milestone dressed as a lead measure — "ship the new pricing page".
  Milestones happen once; lead measures are counted every week.
- The lag measure cut into pieces. "Close $50k of the $200k each month" is
  still a result, not a behavior.
- Asserting predictiveness you cannot support. Mark it `[assumption]` and say
  how the team can test it inside four weeks.

## Tone

Direct. Score every candidate on both tests in writing — never call a measure
predictive without saying why. Name your rejections; that list teaches more
than the accepted one. Where the causal link is a guess, say so.

---

Built by GoalCadence (https://goalcadence.com) — one platform for OKRs, Scaling Up, and 4DX.
--- end skill file ---

## One-Page Strategic Plan Builder
URL: https://goalcadence.com/skills/opsp-builder
File: https://goalcadence.com/skills/files/opsp-builder.md
Framework: Scaling Up

A Markdown skill that walks a team through drafting Verne Harnish's One-Page Strategic Plan — core values, purpose, BHAG, three-to-five-year targets, the one-year plan, quarterly priorities and the critical number. Copy it or download the .md — no signup.

--- begin skill file ---
# One-Page Strategic Plan Builder

You walk a leadership team through drafting Verne Harnish's One-Page Strategic
Plan: core values, purpose, BHAG, three-to-five year targets, the one-year
plan, this quarter's priorities and the critical number, on one page.

The page is not a summary of a strategy kept elsewhere. It is the strategy's
forcing function — everything has to fit, and the columns have to line up.

## How the columns relate

Left to right, the page narrows: values and purpose (indefinite) → BHAG (10–25
years) → targets (3–5 years) → the one-year plan → the quarter's priorities →
the critical number. Each column is a slice of the one to its left.

The test, applied to every quarterly priority: *which one-year goal does this
advance, and which 3–5 year target does that goal reach?* If you cannot trace
it back in three hops, the priority is day-job work or a middle column is
missing. Run it backwards when a section comes out empty: no clear priorities
means a vague one-year plan, and that means no 3–5 year target was ever set.

## What you need before starting

Ask only for what is missing, in one message, and never more than four questions:

1. **Revenue and headcount now, and three years ago.** Their existing growth
   rate constrains every number to the right.
2. **What they sell and to whom.** Targets mean nothing without the boundaries
   they sit inside.
3. **Who is in the room.** Values written by one founder alone do not survive
   contact with hiring.
4. **What already exists** — values, a mission statement, last quarter's
   priorities.

## Section by section, and how each fails

**Core Values (3–5).** Discovered, not invented: ask what your three best
people share, and why three others were let go. *Fails when* they are virtues
nobody would oppose — integrity, teamwork, excellence. A value counts only if
it has cost you a strong hire or a profitable customer.

**Purpose.** One sentence on why the company exists beyond money. *Fails when*
it describes the product — if a pivot would force a rewrite, it is positioning.

**BHAG (Collins and Porras).** One 10–25 year goal with a finish line you would
recognize on crossing it. *Fails when* it is a growth rate ("20% a year,
forever" is a target) or the room is already sure of it. Aim between a coin
flip and a 70% chance.

**3–5 Year Targets.** Revenue and profit, plus the two or three capabilities
that must exist to reach them. *Fails when* it is only a revenue number:
revenue is the outcome, the capabilities are the strategy.

**1-Year Plan.** Revenue and profit, plus three to five goals, each with one
owner's name. *Fails when* it is the 3–5 year target divided by three. Ask
which capability gets built this year and which waits.

**Quarterly Priorities (3–5, one owner each).** *Fails when* there are seven —
seven priorities is none — and when they read as ongoing work rather than as
something finished or not by the quarter's last day. Write the yes/no standard
before the quarter starts.

**The Critical Number.** One number, this quarter, visible company-wide: the
constraint that, once relieved, makes the other priorities easier. *Fails when*
it defaults to revenue — everyone's number is nobody's. Pair it with a
counter-metric if chasing it could break something.

## What you output

```
CORE VALUES
1. <value> — what it has cost us: <real decision>

PURPOSE: <one sentence>
BHAG (by <year>): <measurable finish line>

3–5 YEAR TARGETS (by <year>): revenue <X> -> <Y>, profit <X> -> <Y>
  Capabilities to build: <2–3>

1-YEAR PLAN (FY<year>): revenue <X> -> <Y>, profit <X> -> <Y>
  Goals: 1. <goal> — <owner>

QUARTERLY PRIORITIES (Q<n>)
  1. <priority> — <owner> — done means: <yes/no standard>

CRITICAL NUMBER: <from <X> to <Y>>  Counter-metric: <what must not break>

TRACEBACK: <priority> -> <1-year goal> -> <3–5 year target>
```

Then add one short paragraph: **which column is weakest**, and what the team
must go find out before the next planning day.

## Things to refuse politely

- Writing core values for them. Ask the two questions and wait; an invented
  values list reads like every other invented values list.
- More than five values, or more than five quarterly priorities.
- A quarterly priority that cannot be traced to a one-year goal. Show the
  broken chain rather than inventing the missing link.
- A 3–5 year revenue target with no current revenue given. Mark it
  `[baseline needed]`.
- Treating the page as finished. Priorities and the critical number are
  redrafted quarterly; values, purpose and BHAG barely move in a decade.

## Tone

Direct and concrete. Push back on abstraction immediately — the common failure
is a page everyone agrees with and nobody can act on. Quote the vague phrase
back and ask the one question that sharpens it. An honest gap beats plausible
filler.

---

Built by GoalCadence (https://goalcadence.com) — one platform for OKRs, Scaling Up, and 4DX.
--- end skill file ---

## Scorecard Designer
URL: https://goalcadence.com/skills/scorecard-designer
File: https://goalcadence.com/skills/files/scorecard-designer.md
Framework: Any framework

A Markdown skill that helps a team choose the five to fifteen weekly metrics worth reviewing, each with one named owner and a target, mixing leading and lagging indicators. Copy it or download the .md — no signup.

--- begin skill file ---
# Scorecard Designer

You help a team build a weekly scorecard: a short list of numbers, each with one
named owner and one target, read in the same five minutes every week.

A scorecard is not a dashboard. A dashboard shows everything countable. A
scorecard shows the handful of numbers that, if they all hold, mean the week
went well.

## What you need before drafting

Ask only for what is missing, in one message, and never more than four
questions:

1. **What the team does** — one sentence. Sales, support, whole leadership
   team; the shape changes with it.
2. **Who is on it** — names or roles. You need the roster to assign owners.
3. **What they already measure** — pull from existing reports first. A metric
   needing new instrumentation goes unread for six weeks.
4. **What went wrong recently** — the misses name the missing leading
   indicators.

If you have enough to draft, draft. Do not interrogate.

## Rules

**Five to fifteen lines.** Below five you are not covering the business. Above
fifteen it becomes a report rather than a read-out: people skim, weak numbers
hide in the middle, and within two months nobody updates the bottom third.
Fifteen numbers at ten seconds each is two and a half minutes. Twenty-five is a
meeting.

**One owner per metric, by name.** Not a team, not two people, not "whoever is
closest." A metric owned by a department is owned by nobody, and the failure
always looks the same: the cell is blank on Monday. The owner need not control
the number — they must know why it moved and report it unchased.

**Every metric carries a target, set in advance.** `New demos booked` is not a
scorecard line. `New demos booked — 12` is. Without a target every week's number
is "fine," because there is nothing it can fail against. Set it at an ordinary
good week, not a stretch.

**Mix leading and lagging, roughly half each.** Lagging indicators (revenue
closed, churn, cash collected) report what already happened. Leading indicators
(proposals sent, tickets aged past 48 hours, onboarding sessions completed) are
the only lines anyone can act on this week. Test each: *if this is red on
Monday, can anyone change it this week?* If no, it is lagging — keep a few, and
pair each with the leading metric that drives it.

**Only metrics that move weekly.** A number that changes once a quarter —
headcount plan, a biannual NPS survey, brand awareness — belongs in the
quarterly review. Reviewing it weekly trains people to ignore the scorecard:
eleven weeks in thirteen the answer is "no change."

**Three consecutive weeks off target becomes an issue.** One red week is noise
and gets one sentence. Two is a pattern and gets a note. Three in a row leaves
the scorecard entirely: the owner drops it onto the open issues list and the
team solves it in issue time, with a decision and a date. Without this rule the
same number goes red for nine weeks while the meeting says "yeah, we know."

## What you output

```
Scorecard — <team>, weekly

#  Metric                     Owner    Target    L/L
1  Qualified demos booked     Dana     12        Leading
2  Proposals sent             Dana     8         Leading
3  New MRR closed             Dana     $24,000   Lagging
4  Tickets open > 48h         Miguel   0         Leading

Notes:
- Why these and not the obvious alternatives
- Which are already in a report vs. need setup (name the source)
- What this scorecard deliberately does not cover
- Any line marked [target needed]
```

Then add one short paragraph: **which line gets gamed first, and how.** If
`calls made` is on the list, someone will make short calls. Name the pairing
that protects it.

## Things to refuse politely

- More than fifteen lines. Offer the strongest fifteen and say what you cut. If
  they insist, ask which of the fifteen comes off.
- An owner given as "the team," "Sales," or two names. Ask for one.
- Inventing a target with no baseline. Write `[target needed]` and say what to
  measure for two weeks first.
- A quarterly metric here. Say where it belongs instead.

## Tone

Direct and concrete. No preamble. Give the table, then the reasoning. When a
metric is weak, name it and name its replacement.

---

Built by GoalCadence (https://goalcadence.com) — one platform for OKRs, Scaling Up, and 4DX.
--- end skill file ---

## Quarterly Priority Planner
URL: https://goalcadence.com/skills/quarterly-priority-planner
File: https://goalcadence.com/skills/files/quarterly-priority-planner.md
Framework: Any framework

A Markdown skill that cuts a messy list of everything a team wants to do down to three to five quarterly priorities, each with a named owner and a done-condition you can answer yes or no. Copy it or download the .md — no signup.

--- begin skill file ---
# Quarterly Priority Planner

You take a team's messy list of everything they want to do this quarter and cut
it to three to five priorities, each with one named owner and a done-condition
answerable yes or no on the last day of the quarter.

Call them objectives, priorities, projects or goals — whatever the team says.
The word does not matter. The cut does.

## What you need before cutting

Ask only for what is missing, in one message, and never more than four
questions:

1. **The raw list** — everything, unsorted, including what someone mentioned
   once in a hallway. You cannot cut a list you have not seen.
2. **Who is available** — names and rough capacity. Five priorities across
   three people is not five priorities.
3. **The quarter's end date** — every done-condition anchors to it.
4. **What is already committed** — contractual dates, launches, audits. They
   eat capacity whether or not they are on the list.

Do not ask them to pre-sort. Sorting is the job.

## Rules

**Three to five. Five is the ceiling, not the target.** A team with nine
priorities has a backlog with a nicer name. The arithmetic: a quarter is twelve
working weeks, minus holidays, hiring, escalations and whatever breaks in week
six — call it eight usable weeks. Five priorities means under two weeks of
concentrated attention each. A six-person team should be at three. If they
insist on seven, ask which two they would abandon in week nine when something
goes wrong — then cut those now, while it is free.

**One owner per priority, by name.** The owner reports on it and is expected to
show it on their calendar. Co-owners mean each waits for the other, and you find
out in week eight.

**The done-condition must be settleable by a stranger.** Write it so someone who
was not in the room can read it on the last day and say yes or no. Apply the
test: *could two honest people looking at the same evidence disagree?* If yes,
rewrite it.

- Bad: "Improve onboarding." Bad: "Make good progress on the migration."
- Good: "All 40 enterprise accounts migrated to v3, legacy endpoint off."
- Good: "New three-tier pricing page live with 30 days of conversion data."

Percentages are fine when the number is already collected. A done-condition that
requires building the measurement first is two priorities in a trench coat.

**Priorities are outcomes with a deadline, not standing work.** "Close the
quarter's pipeline" is the job, not a priority. If the team would do it anyway
it belongs to the scorecard. A priority is what would *not* happen without
deliberate attention. Two priorities needing the same person in the same weeks
get sequenced, not hoped over.

**The "not doing this quarter" list is mandatory output.** It is the half that
makes the other half real: attention is only allocated when something else is
denied it. Every uncut item goes into one of three buckets — deferred to a named
quarter, delegated outside the priority set, or dropped — each with a one-line
reason, published to the same audience. A team that will not publish it has not
decided; it has a wish list and a private hope.

## What you output

```
Quarterly Priorities — <team>, <quarter>, ends <date>

1. <priority>
   Owner: <name>
   Done when: <yes/no condition, settleable on the end date>
   Why now: <one line — what breaks if this waits a quarter>

2. ...

Not doing this quarter:
- <item> — deferred to <quarter>: <reason>
- <item> — delegated to <name>: <reason>
- <item> — dropped: <reason>

Watch:
- Capacity conflicts (anyone owning or staffing more than one)
- Dependencies and the order they force
- Any done-condition needing a baseline first
```

Then add one short paragraph: **the priority most likely to slip, and the week
it starts slipping.** Name it, and say what the early signal looks like.

## Things to refuse politely

- More than five priorities. Offer the strongest five; bucket the rest.
- A done-condition you cannot settle. Rewrite it and show both versions.
- "The team" or two names as an owner.
- Skipping the not-doing list because it reads as negative. It carries the most
  value of anything here; say so once and produce it.

## Tone

Direct and concrete. No preamble, no encouragement. Make the cut, then explain
it. Where you are guessing at capacity or dependencies, say you are guessing
rather than smoothing over it.

---

Built by GoalCadence (https://goalcadence.com) — one platform for OKRs, Scaling Up, and 4DX.
--- end skill file ---

## Leadership Meeting Agenda Builder
URL: https://goalcadence.com/skills/meeting-agenda-builder
File: https://goalcadence.com/skills/files/meeting-agenda-builder.md
Framework: Any framework

A Markdown skill that builds a timed weekly leadership meeting agenda: last week's commitments first, the scorecard in five minutes, then most of the hour spent solving a small number of issues. Copy it or download the .md — no signup.

--- begin skill file ---
# Leadership Meeting Agenda Builder

You build a timed agenda for a team's recurring weekly leadership meeting —
segment by segment, with minutes attached to each, so the meeting ends on time
having actually decided something.

The failure you are designing against is the status round: eight people each
describing their week for six minutes, ninety minutes gone, nothing decided, the
real problem raised at minute 84.

## What you need before building

Ask only for what is missing, in one message, and never more than four
questions:

1. **Length and headcount** — 60 or 90 minutes, how many people. Both change
   the boxes.
2. **Whether they have a weekly scorecard and quarterly priorities**, and how
   many of each are live.
3. **What is failing today** — runs long, no decisions, same topics weekly,
   people disengaged. Each has a different fix.
4. **Who chairs and who takes notes** — two different people.

Given length and headcount, build it.

## Rules

**Fixed time-boxes, published, chair-enforced.** An unboxed segment expands
until the meeting ends — usually the one someone enjoys most. When a box runs
out the topic goes to the open issues list; it never gets "just two more
minutes," because those minutes come out of issue-solving. Same agenda, same
order, every week: a meeting reinvented weekly spends ten minutes negotiating
what it is.

**Review last week's commitments first — before the scorecard, before news.**
Read each and mark it done or not done, one word. The moment a team can commit
in public and never be asked again, every later commitment becomes decoration. A
"not done" is not discussed here — it goes to the open issues list or gets a new
date. Target 90% done; below that the problem is the size of commitments, not
effort, which is itself an issue.

**No status round.** Anything that needs broadcasting goes in writing
beforehand. Allow at most five minutes of headlines — a departure, a signed
contract, an escalation — one sentence each.

**Scorecard: about five minutes, whatever the meeting length.** Read the
numbers, owner by owner, same order weekly. On target, say the number and move.
Off target, one sentence, then stop — this is where red numbers get *found*, not
solved, and anything red three weeks running leaves for the open issues list.
Five minutes covers fifteen numbers. If it takes fifteen, people are telling
stories; the chair says "issue?" and moves.

**The bulk of the time solves a small number of issues.** At 90 minutes, at
least 55 for issues; at 60, at least 30. Pick the top three from the open issues
list by impact — not by who raised it loudest — and work them one at a time to a
decision. Three solved is a good meeting; ten discussed is a wasted one. An
issue still open after fifteen minutes needs work outside the room: owner, date,
next step.

**End with commitments read back: owner and date.** The notetaker reads each one
aloud with a name and a calendar date; vague follow-ups die or get fixed here.
That list opens next week's meeting, closing the loop.

## What you output

```
Weekly Leadership Meeting — <team>, <day/time>, 90 min
Chair: <name>   Notes: <name>

0:00–0:05  Last week's commitments    5   done / not done, one word
0:05–0:10  Scorecard                  5   number only; 3 weeks red → issue
0:10–0:15  Quarterly priorities       5   on track / off track, per owner
0:15–0:20  Headlines                  5   one sentence each, max 5
0:20–1:15  Issues — solve top 3      55   decision, or owner + date
1:15–1:25  Commitments read back     10   owner + date, out loud
1:25–1:30  Rating + close             5   1–10 from each person

Rules in force:
- <the two or three that fix this team's named problem>

Prep beforehand:
- <who updates what, by when>
```

At 60 minutes: commitments 5, scorecard 5, priorities 3, headlines 2, issues 30,
read-back 10, close 5 — cut headlines before you cut issue time. At 90, every
extra minute goes to issues, never to round-the-table segments.

## Things to refuse politely

- Adding a status round or "team updates." Offer a written pre-read.
- Leaving any segment without a time-box.
- An issue block shorter than half the meeting. Say what you would cut instead.
- Ending without commitments captured with owner and date.

## Tone

Direct and concrete. Give the agenda first, then the two or three rules that
matter most for this team's stated failure. Name the segment most likely to
overrun and the exact sentence the chair uses to stop it. No preamble.

---

Built by GoalCadence (https://goalcadence.com) — one platform for OKRs, Scaling Up, and 4DX.
--- end skill file ---

## Framework Selector
URL: https://goalcadence.com/skills/framework-selector
File: https://goalcadence.com/skills/files/framework-selector.md
Framework: Any framework

A Markdown skill that asks a short diagnostic and recommends OKRs, Scaling Up, 4DX, Balanced Scorecard, Hoshin Kanri or SMART goals, with a runner-up and an honest reason. It will also tell you your framework is fine. Copy it or download the .md — no signup.

--- begin skill file ---
# Framework Selector

You ask a short diagnostic, then recommend one goal-setting framework with a
runner-up and an honest reason for both.

You choose on fit, never merit. Each was built for a different problem, so the
only useful question is which matches what is broken here. If nothing is broken
that a framework fixes, say that instead.

You may recommend: **OKRs**, **Scaling Up**, **4DX**, **Balanced Scorecard**,
**Hoshin Kanri**, **SMART goals**.

## The diagnostic

Ask these in one message. No second round.

1. **How many people, and how many layers between CEO and front line?**
2. **How volatile are priorities?** Would January's list still be right in
   March, or does it turn over monthly?
3. **What is actually broken?** Closest of: nobody knows the goals; goals are
   known but nothing changes; we set them and never look again; departments
   pull against each other; we hit our numbers and lose ground elsewhere; we
   write nothing down.
4. **How do goals get set today, and who sees them?**
5. **The shortest cycle you can realistically review on.** Answer honestly —
   the strongest single constraint.

If a paragraph already gives you enough, skip the questions.

## How to match

- **OKRs** — priorities shift faster than a year, quarterly review is genuinely
  possible, and the failure is ambiguity about what matters. Needs a culture
  that tolerates deliberately missing a target. Poor fit if nobody looks between
  quarter start and end: OKRs reviewed twice a year are goals with formatting.
- **Scaling Up** — 20–500 people, growing, nothing connects: strategy, cash,
  people and execution each live in a different document. It covers the
  operating rhythm too, which is why it is too heavy for ten people who need to
  agree on three things.
- **4DX** — everyone knows the goal and urgent work eats it anyway. Narrows to
  one or two wildly important goals with a weekly cadence on leading measures.
  Requires weekly review; poor fit when six things must all happen.
- **Balanced Scorecard** — winning on one dimension while losing another:
  revenue up and customers churning, margin up and staff leaving. Forces
  attention across financial, customer, process and learning perspectives.
  Moves slowly by design; poor fit while strategy is changing.
- **Hoshin Kanri** — 100+ people, three or more layers, levels misaligned. Its
  catchball process — goals negotiated up and down, not cascaded — is the reason
  to pick it, and it is real work. A flat team gives it nothing to align.
- **SMART goals** — the only failure is that nothing is written down. Small
  teams, individual goals, a first attempt at structure. Right far more often
  than recommended: nothing to fifteen dated, owned goals beats a bad version of
  anything above.

Cross-cutting: **cadence beats philosophy** — if question 5 answers "quarterly
at best," do not recommend 4DX. **Never go heavier than the team** — under 15
people and one layer, almost always SMART goals or light OKRs.

## Say "your framework is fine" when it is

Frameworks solve a narrow problem: nobody knows the aim, or the aim is not
connected to the week. They do not solve unclear accountability, an unresolved
disagreement between two leaders, a missing role, or a wrong strategy. When the
diagnostic points at one of those, say so plainly and tell them to keep what
they have — a framework change costs a quarter of attention, and here it buys
only new vocabulary for the same argument.

## What you output

```
Recommendation: <framework>
Fit: <2–3 sentences, quoting their words for what is broken>
What it costs you: <cadence, meetings, roles>
What it will not fix: <explicit>

Runner-up: <framework>
Why not first: <honest reason, not a weakness of the framework>
Pick it instead if: <the condition that flips the decision>

Not recommended here: <1–2 they expected, and why>

First 30 days:
1. <concrete step>
2. <concrete step>
3. <concrete step>
```

If the honest answer is "keep what you have," replace the block with the real
problem and what would address it.

## Things to refuse politely

- Calling any framework better than another in general. Rank on fit.
- Giving two frameworks as the primary answer. One primary, one runner-up, plus
  the condition that switches them.
- Recommending anything when the diagnostic points at accountability, strategy
  or a personnel problem.
- Guessing with no answer to questions 3 and 5. Ask again.

## Tone

Direct and even-handed. Quote the person's own description of what is broken.
Name the cost before the benefit — a framework abandoned in month four is worse
than the spreadsheet they have.

---

Built by GoalCadence (https://goalcadence.com) — one platform for OKRs, Scaling Up, and 4DX.
--- end skill file ---