Framework Glossary

Drift is the slow misalignment that builds up while everything still looks fine, and only shows itself when pressure arrives.

Architectural drift is the gradual, initially invisible misalignment of layers that precedes visible failure. Under normal conditions minor misalignments stay concealed, because time absorbs inefficiency and margins compensate. When pressure rises, tolerance reduces and what seemed manageable becomes unsustainable. Detecting drift early is what the Control System exists to do.

Beliefs are what you take to be possible, permitted or safe. They quietly decide what you will even attempt.

Beliefs are structural assumptions about what is possible, permissible or safe. They expand or restrict what you will attempt, at individual, leadership and collective scale. Within the Unchained Goals Framework, Beliefs are one of the four Structural Integrity Systems, designed after Ownership and before Plan. They are treated as structure rather than as motivation or attitude, which is why the framework addresses them by surfacing assumptions and generating evidence under manageable risk rather than by exhortation. In organisations, belief is formed less by what leaders say than by what leaders tolerate, reward and repeat.

Your control boundary is the line between what you have enough authority to govern and correct, and what you can only influence or want.

Within the Unchained Goals Framework, a control boundary is the line separating outcomes the owner possesses sufficient authority to govern from those the owner can only influence or desire. Control means sufficient authority over the primary causal inputs and corrective decisions required to govern an outcome. It does not mean certainty over every external factor, and no serious goal is ever free of external factors. A proposed Outcome inside the boundary, meeting the remaining SSMTC conditions, is a valid Outcome Goal. A proposed Outcome outside it is a dream until it is translated into one that sits within control. The control boundary is also the basis on which strategic outcomes are passed across organisational layers without losing executability.

When a goal is handed to someone else, it has to be rewritten as something that person can actually deliver.

Control Boundary Translation is the rule that an outcome passed to a lower level must be redesigned as an outcome within that level's control. Translate the outcome at every boundary. Never cascade it unchanged. It is the mechanism by which the Unchained Goals Framework scales across layers of authority without mutation. Breaking the rule produces a dream cascade: an Outcome passed across a boundary unchanged becomes a dream for the receiving owner, because it sits outside what that owner can govern. The result is accountability without authority, which produces defensive behaviour rather than disciplined execution.

Every serious goal costs something. There are six kinds of cost, and the one you have not named is usually the one that stops you.

The Cost Taxonomy is the six categories of cost any serious goal carries: time, emotional, social, financial, opportunity and identity. Why is tested against all six. A Why that has not been tested against the full cost, named across every category, weakens under pressure, and a goal stalls at its heaviest unnamed cost. At project or organisational scale, the cost is named in the same six categories for the layer that will carry it, and the record shows who accepts each category on that layer's behalf.

Design Mode is when you are building the system, in order, starting at Purpose.

Design Mode is the mode of the Unchained Goals Framework used when building the system in sequence: establishing a new goal, rebuilding after collapse, or scaling ambition. The eight design layers are constructed in order, Purpose first, and each layer feeds the next, so skipping one weakens everything after it. The Control System is installed once the eight are complete and before execution begins. Design Mode uses the same nine components as the other two modes. Only the activity changes.

Diagnose Mode starts when results fall below the agreed range by enough to meet the trigger you set in advance. You then work through the system from the most controllable layer upward, rather than simply trying harder.

Diagnose Mode is the mode of the Unchained Goals Framework entered when a below-range Performance signal meets the agreed diagnostic trigger. It is not entered because progress feels slow. Rather than escalate effort, the operator interrogates the architecture from the lowest controllable layer upward, in fixed order: habit consistency, then process validity, then Performance metric validity, then the Structural Integrity Systems in reverse design order (Plan, Beliefs, Ownership, Why), then the outcome control boundary. No layer is skipped and no layer is reviewed out of order. Because these four layers are designed in the order Why, Ownership, Beliefs, Plan, the layer designed first is diagnosed last. Diagnose Mode replaces blame with precision. It is one of three modes, alongside Design Mode and Operation Mode.

Direction is the part of the framework that answers where you are going. Vision is what fills it.

Direction is one of the five structural groupings of the Unchained Goals Framework, and it is occupied by Vision. Purpose supplies the Foundational Constraint, which rules out what does not belong. Direction supplies the committed long-term position within what remains. The two are distinct and should not be merged: Purpose defines the domain, and Vision defines direction and magnitude within it. Without Direction, individual goals can each be sound on their own and still pull against one another, because nothing above them states which way the work is meant to travel. Where diagnosis becomes systemic, the sequence extends upward to Vision alignment before it reaches the Purpose constraint.

The spine is the chain that turns a result you want into something you can actually do on a given morning.

The Directional Execution Spine is the grouping of the Unchained Goals Framework that produces measurable movement. It runs in four stages: Outcome Goals, then Performance Goals, then Process Goals, then Habits. Outcome defines the destination. Performance defines the required operating standards. Process defines the controllable behaviour. Habits stabilise that behaviour so execution becomes progressively less dependent on conscious intention. The Spine is the only one of the five structural groupings that generates movement. The others constrain it, protect it, or govern it.

A dream cascade is what happens when a goal is handed down unchanged to someone who has no authority to deliver it.

A dream cascade is the failure that results from passing an Outcome across a boundary of authority unchanged. Because it lies outside the receiving owner's control boundary, it becomes a dream for that owner even where it remains a valid Goal for the level above. It produces accountability without authority. Exposure then creates pressure, pressure without sufficient authority creates defensiveness, defensiveness softens reporting and delays escalation, and governance weakens before the deviation becomes visible. The remedy is Control Boundary Translation: translate the outcome at every boundary, never cascade it unchanged.

A dream is an outcome you want but do not have enough authority to govern. A goal is one you can govern, and correct when it drifts. Naming which one you are holding decides how you should treat it.

The Unchained Goals Framework draws a structural distinction between dreams and goals. A dream is a proposed Outcome that sits outside the control boundary of whoever holds it. A valid Outcome Goal is one that passes SSMTC within that owner's control boundary. The test is not whether anything external is involved, since nothing is ever fully controlled. The test is whether the owner possesses sufficient authority over the primary causal inputs and corrective decisions required to govern the result. A dream is not discarded. Dreams may shape Vision, and a dream is translated into the largest governable result beneath it before execution begins. "Under your control" is the SSMTC condition that separates the two.

A long-term goal can sit too far off to shape what you do today. A 60 to 90 day window brings the next real result close enough to plan and govern.

The 60 to 90 day execution cycle is the framework's recommended operating window. Long-term Outcomes are translated into nearer-term Outcomes for the current cycle, then into the Performance standards that show whether the drivers are functioning, then into the Process behaviours that produce those standards, stabilised through Habits. The nearer-term Outcome must be a result complete in its own right. If it can be described only as part of the way there, it is a milestone rather than an Outcome.

False realism is treating low ambition as good sense. It is the reason the framework insists that a goal be Stretched.

False realism is the belief pattern that treats restraint as maturity and ambition as naivety, producing systematic under-commitment. It is the failure mode the "Stretched" condition of SSMTC exists to prevent: a goal set low enough to guarantee achievement produces no growth and is not a valid stretch, however well formed it looks in every other respect.

The Foundational Constraint is the part of the framework that rules things out. Purpose is what fills it.

Within the Execution Architecture of the Unchained Goals Framework, the Foundational Constraint is Purpose: the layer that constrains legitimate selection of goals. Purpose does not produce movement. It governs which directions are valid. When the Foundational Constraint is weak, direction becomes negotiable under pressure, and goals drift towards what is convenient rather than what matters. The Foundational Constraint is the most upstream component of the Execution Architecture.

Goals turn a long-term direction into something measurable. There are three kinds, and treating them as interchangeable is the most common mistake in goal setting.

Goals are the third design layer of the Unchained Goals Framework. They translate Vision into measurable form. Goals take three formal types, and the distinction between them carries weight: Outcome Goals, Performance Goals and Process Goals. Each is defined within the control boundary of whoever owns it. A standard is not a behaviour, and a behaviour is not a result. Mixing the three levels is the most common reason a goal system produces activity without trajectory.

A short diagnostic that scores each part of your goal separately and shows you which part is weakest, so you know where to start.

The Goals Readiness Score™ is an 18-question diagnostic built directly from the architecture of the Unchained Goals Framework. It reviews how well a stated goal is designed, executed and governed across the nine components: Purpose, Vision, Goals, Why, Ownership, Beliefs, Plan, Habits and the Control System. Each component is scored in its own right, and the scores are not added together. An aggregate would conceal the weakness the assessment exists to find. The result names the weakest component and counts those falling below threshold, with next steps for the reader's context. Weakness propagates downstream, so the lowest-scoring component is where structural design review begins. It identifies the first candidate for attention rather than proving where a particular failure began, and it does not replace the fixed diagnostic sequence when a below-range signal has met its trigger. It takes about ten minutes and works at individual, team and organisational scale, because the framework itself scales without mutation.

Three situations the Control System recognises: on track, below the range, and above it. Each has its own response, and being above the range is not automatically good news.

The Control System operates three governance states. Performing within range, where measured Performance sits within the defined and accepted range and the response is optimisation rather than redesign. Underperforming, activated when a below-range deviation signal meets its pre-agreed trigger, which opens Diagnose. Overperforming, activated when an above-range signal meets its trigger, which opens Validate: favourable deviation is confirmed as genuine, repeatable and sustainable before standards are raised. A result outside range is first a deviation signal. While it remains below the agreed response threshold, monitoring continues and no state is activated. A signal under observation is not a fourth state.

Habit Conversion is the work of repeating a behaviour until starting it takes less and less deciding.

Habit Conversion is the activity of designing and repeating Process behaviours until they become increasingly automatic and reliable. It produces Habits, which are the terminal stage of the Directional Execution Spine and one of the nine components. The conversion is not optional. It makes execution progressively less dependent on conscious intention and fluctuating motivation, reducing what has to be decided rather than removing the decision. Habits reduce cognitive load and protect consistency under pressure. Habit consistency is the first checkpoint in the fixed diagnostic sequence when a below-range signal meets its trigger.

A Habit is a Process Goal you have repeated often enough that starting it no longer takes much deciding.

Habits are the eighth design layer of the Unchained Goals Framework and the terminal stage of the Directional Execution Spine. They are Process Goals and Plan disciplines stabilised through repetition, so that execution becomes progressively less dependent on conscious intention and fluctuating motivation. Habits are designed with a behaviour, a cue and a cadence, where the cue may be a time, a place, a preceding event or a defined condition. They reduce what has to be decided each time rather than removing the decision. Habit consistency is the first checkpoint in the fixed diagnostic sequence.

A range is what counts as normal for a measure. A trigger is the point at which you stop watching and start investigating.

An operating range is the band of acceptable values defined for a Performance indicator, agreed before pressure rather than during it. An indicator without a range cannot trigger anything. A trigger is the pre-agreed threshold at which a deviation signal activates a governance state and its fixed response. Triggers are set on significance, persistence, recurrence or consequence, proportionate to the scale, risk and behaviour of the indicator, and defined before execution begins. The framework sets no universal number of misses. A critical deviation may require immediate diagnosis, and where delay would cause irreversible harm, containment takes priority without replacing ordered diagnosis.

Operation Mode is when the designed system is running and Performance is being monitored against its agreed ranges.

Operation Mode is the mode of the Unchained Goals Framework in which the designed system runs. The nine components function together as a structured operating system through the five structural groupings. The Control System monitors Performance against defined operating ranges and confirms Outcome at a lower frequency. Operation Mode uses the same nine components as Design Mode and Diagnose Mode. Only the activity changes.

When something is not working, check the simplest and most controllable thing first, then work upward. Do not skip a step because you think you already know the answer.

Ordered Diagnosis is the fixed diagnostic sequence of the Unchained Control System. A result outside the defined operating range is a deviation signal. When a below-range signal meets its pre-agreed trigger, diagnosis begins at the lowest executable layer and escalates upward in fixed sequence: habit consistency, then process validity, then Performance metric validity, then the Structural Integrity Systems in reverse design order (Plan, Beliefs, Ownership, Why), then the outcome control boundary. No layer is skipped and escalation occurs only when the preceding layer is confirmed sound. Ordered Diagnosis prevents the most common failure mode in goal pursuit: escalating effort or redefining the outcome before checking whether the behaviour is intact. Where a breakdown is systemic, repeated or part of formal recovery, the sequence extends upward to Vision alignment and then the Purpose constraint.

An Outcome Goal is the result you are going for, written so that delivering it is genuinely yours to do.

An Outcome Goal is the result to be achieved, defined within the control boundary of whoever owns it. It is the first stage of the Directional Execution Spine and confirms delivery rather than driving it. A proposed Outcome becomes a valid Outcome Goal only when it passes all five SSMTC conditions for its named owner. An Outcome that sits outside the owner's control boundary is a dream until it is translated. The Outcome Goal provides lagging confirmation and is normally reviewed less frequently than Performance.

Ownership means accepting in advance, with your eyes open, the cost of pursuing this goal and the consequences that come with it.

Within the Unchained Goals Framework, Ownership is a distinct structural layer, separate from Why, from motivation and from enthusiasm. Ownership is the conscious acceptance of the cost and consequences of pursuing a Goal within the owner's control boundary. Why justifies the cost; Ownership accepts it. The two are routinely conflated, and that conflation is one of the most common reasons commitment collapses under pressure. Ownership requires that authority, responsibility and cost acceptance are aligned. Where responsibility is assigned without matching authority, exposure replaces ownership and defensive behaviour follows. Ownership is one of the four Structural Integrity Systems, designed after Why and before Beliefs.

A Performance Goal is the standard that tells you whether you are on track, before the result itself arrives.

A Performance Goal is a measurable operating standard that indicates whether progress towards the Outcome is on track. It is the second stage of the Directional Execution Spine and the level the Control System monitors at a defined cadence. A Performance Goal must state a level that could be met or missed within the cycle, and movement in it should appear before the Outcome moves. An indicator that moves only when the Outcome moves is lagging confirmation, not a Performance standard. Every Performance indicator needs an operating range, agreed before pressure arrives rather than during it. An indicator without a range cannot trigger anything.

The Plan is how the work fits into the time, money and attention you actually have, alongside everything else you have already promised.

Plan is the seventh design layer of the Unchained Goals Framework and one of the four Structural Integrity Systems. It is the structure of coordinated movement under constraint: it sequences action, resolves trade-offs and protects the constraining resource first. The constraining resource is whatever is most likely to run out and stop progress, which may be time, money, skilled people or decision-making capacity, and protecting it means not spending it on work that something else could carry. SSMTC establishes that an Outcome is a valid Goal within the owner's control boundary; Plan then tests whether there is a credible path to carry it within sustainable capacity, assessed against every other commitment drawing on the same capacity over the same period. If no credible path exists, execution must not proceed in that form. Plan is the first of the four Structural Integrity Systems to be interrogated during diagnosis, because it is the last to be designed.

A Process Goal is the behaviour you will actually carry out. It is something you could put in a diary.

A Process Goal is the repeatable, directly controllable behaviour within the responsible actor's control boundary that produces the required Performance standard. It is the third stage of the Directional Execution Spine. Two tests apply: it must sit wholly within the owner's control, and it must serve a named standard above it. A Process Goal that serves no standard is activity. A Process Goal may carry a number, a duration or a cadence without becoming a Performance Goal, because the number there specifies the behaviour rather than setting the target being measured. Process Goals are stabilised into Habits through Habit Conversion.

Purpose is the problem you have decided to take responsibility for. It tells you which goals are yours and which are distractions.

Purpose is the first of the eight design layers of the Unchained Goals Framework and its Foundational Constraint. It is the problem you accept responsibility for addressing, and it determines which goals are legitimate and which are distractions. Purpose is not a motivational statement. It is a constraint, which means its job is to rule things out, and a constraint that rules nothing out is not yet a Purpose. It does not produce movement; it governs selection. When Purpose is weak, direction becomes negotiable under pressure and goals drift towards what is convenient. Purpose defines what you are responsible for. It does not define what you are.

Recovery Architecture is the order of work for rescuing something that has already gone wrong, so the repair does not make it worse.

The Recovery Architecture is the structured intervention sequence within the Unchained Goals Framework used to recover programmes, teams or individuals from execution failure. It introduces no new components. It is the disciplined reapplication of the ordered design sequence. Its four phases are: Stabilise, which prevents secondary damage before analysis begins; Diagnose from Execution Upward, following the fixed diagnostic order from the lowest controllable layer; Structural Decision, which converts diagnosis into an explicit choice; and Architectural Rebuild, which returns to Design Mode and rebuilds in design order without skipping layers. The Three Governing Fractures are frequently what diagnosis surfaces, but they are observed patterns rather than a competing diagnostic model, and they do not replace the fixed sequence.

These are the four things that keep a goal standing when the work gets hard: your reason for pursuing it, your acceptance of its cost, what you believe is possible, and a Plan that fits the capacity and resources you actually have.

The Structural Integrity Systems are the four components of the Unchained Goals Framework that protect the Directional Execution Spine from collapse under pressure: Why (cost justification), Ownership (cost acceptance), Beliefs (interpretive stability) and Plan (coordinated movement under constraint). Each addresses a specific failure mode. Without them, even a well-designed Execution Spine fails when sustained pressure is applied. They are protective rather than generative: they do not produce movement, they keep movement coherent. They are designed in the order Why, Ownership, Beliefs, Plan, and interrogated in the reverse of that order, so the layer designed first is diagnosed last.

Three failure patterns that keep recurring: taking on what you cannot control, losing belief that it can work, and running out of willingness to keep paying the cost.

The Three Governing Fractures are three recurring failure patterns the Unchained Goals Framework observes in practice. They are: Misjudged Control, where an outcome contains material elements outside the owner's authority, so exposure is mistaken for commitment; Eroded Conviction, where belief weakens under sustained friction; and Exhausted Ownership, where cost tolerance is depleted without reaffirmation of Why. They often reinforce one another, and by the time outcome failure is visible the pattern is usually well established. They are not an exhaustive list and they do not replace the fixed diagnostic sequence. Formal diagnosis still proceeds in order. They are worked through within the Recovery Architecture.

The Control System is how you keep watch. It checks performance against agreed ranges and tells you when to look deeper, when to raise the bar, and when to leave things alone.

The Unchained Control System, referred to throughout the framework simply as the Control System, is the ninth component of the Unchained Goals Framework and its governance component. It is installed once the eight design layers are complete, which makes it the ninth component without being a ninth design layer. Its rules remain continuously in force across the architecture, but governing the whole architecture does not mean measuring every component continuously. The operating rule is: monitor Performance, confirm Outcome, and respond when an out-of-range signal meets its agreed trigger. It reviews measured Performance indicators against the operating ranges defined by Performance Goals, at a defined cadence. The Outcome Goal provides lagging confirmation and is reviewed less often. Plan, Beliefs, Ownership, Why and the outcome control boundary are interrogated through Diagnose Mode when the underperformance trigger is met. It operates three governance states: Performing within range, which supports Optimise; Underperforming, which opens Diagnose; and Overperforming, which opens Validate.

Vision is the position you intend to hold in the long run, inside the area your Purpose has defined.

Vision is the second design layer of the Unchained Goals Framework and its Direction. It is the long-term position or operating condition you commit to building within the domain that Purpose defines. Purpose asks what problem you are responsible for; Vision asks what enduring position you will build within it. Vision is not aspiration. It is committed positioning, and it is confirmed by refusal rather than by ambition: you know a Vision is real when it makes you turn down opportunities that are genuinely attractive but point somewhere else. A declared position that rejects no otherwise attractive future is a direction of travel, not yet a Vision. Horizon is set by function rather than by a number of years. What makes a statement Vision is whether it continues to give direction to the Goals designed beneath it.

Your Why is the reason this goal is worth what it will cost you. It is tested before you start, not after.

The justification for the cost. The reason a specific goal is worth its specific price, strong enough to hold when the cost becomes real. Why is one of the four Structural Integrity Systems. It is designed after the Goal and before Ownership, and the two are distinct: Why justifies cost, Ownership accepts it. A Why that has not been tested against the full cost, named across all six categories of time, emotional, social, financial, opportunity and identity, weakens under pressure. A goal stalls at its heaviest unnamed cost.