Strategy Execution: Mission, Vision, Values, OKRs, and KPIs

Overview

Mission, envisioned future, and values can clarify purpose and behavioral commitments, but they are not strategy or a prerequisite taxonomy for every organization. Strategy still requires evidence, choices, trade-offs, resources, and coherent action. ^[3]

How to Apply

1. Define Your Mission (The "Why"): Your enduring purpose. It's not a goal to be achieved, but a pursuit.
   • Illustrative mission: "Make vital information easy for people to find and use."
2. Define Your Envisioned Future (The "What"): A clear, ambitious picture of a desired future state; it is not an operating target.
   • Illustrative vision: "A useful computer in every workplace and home."
3. Define Behavioral Commitments: Specify observable, job-related behaviors and how tensions among values will be resolved. Do not use values as stand-alone hiring, promotion, discipline, or termination criteria.
   • Illustrative values: "Judgment," "Communication," and "Curiosity," each paired with observable behaviors.

Figure 8.1. Strategy-to-learning operating system. Purpose, envisioned future, and values inform rather than mechanically cause strategy; choices and resources become a portfolio, while OKRs and KPIs supply evidence for review and adaptation. ^{[3] [2] [4]}

flowchart LR
    A[Purpose and Envisioned Future] --> D[Strategy: Diagnosis, Choices, and Coherent Action]
    B[Behavioral Commitments] --> D
    D --> E[Funded Initiative Portfolio]
    E --> F[OKRs: Periodic Outcome Hypotheses]
    E --> G[KPIs: Ongoing Measures and Guardrails]
    F --> H[Operating Review and Forecast]
    G --> H
    H --> I[Continue, Stop, Reallocate, or Adapt Strategy]
    I --> D

    style A fill:#4ecdc4
    style B fill:#ffd93d
    style E fill:#95e1d3
    style H fill:#95e1d3

Text equivalent: Purpose, envisioned future, and behavioral commitments inform strategy. A diagnosis and coherent choices allocate resources to an initiative portfolio. OKRs express periodic outcome hypotheses and KPIs monitor ongoing measures and guardrails. Operating reviews update forecasts and lead to continuation, stopping, reallocation, or strategic adaptation.

Source note: Original synthesis combining vision, strategy-kernel, OKR-practice, and metric-dysfunction sources; arrows are decision links, not proven causal effects. ^{[1] [3] [2] [4]}

So What for Managers

• Use purpose, an envisioned future, and behavioral commitments to clarify choices and trade-offs, not to substitute for strategy, resources, or decision rights.
• Translate each value into observable, job-related behavior and define how competing values, dissent, accessibility, and escalation will be handled.
• Review whether budgets, incentives, operating decisions, and observed behavior support the stated commitments before using them in people processes.

Limits and Critiques

• Mission, vision, and values are practitioner inputs; they do not establish strategy quality, employee commitment, or financial performance.
• A values statement can be vague, contested, inaccessible, or contradicted by systems and incentives; do not treat agreement or recall as proof of impact.
• Employment use requires job-related criteria, consistent documentation, due process, accessibility, and People/HR and legal review.

Connections

• Input: Use Chapter 3's diagnosis and choices to test whether purpose informs a real strategic trade-off.
• Output: Use OKRs only when a periodic goal system is appropriate; purpose does not require OKRs.

Overview

SMART is a widely used mnemonic, not a complete theory of goal effects. Its wording varies: the UF/IFAS account uses Specific, Measurable, Attainable, Relevant, and Time-bound and traces the approach to Doran's 1981 article. ^[5] This chapter uses “Achievable,” a common variant, while treating every letter as a design prompt rather than proof that a goal is valid.

Goal-setting research examines mechanisms and moderators rather than supporting a universal checklist, while a Harvard working paper documents risks including narrow focus, unethical behavior, distorted risk preferences, cultural effects, and reduced intrinsic motivation. ^{[6] [7]} The appropriate difficulty and review design therefore depend on commitment, ability, task complexity, feedback, incentives, controllability, learning, conflicting goals, potential harm, and the evidence available to the team.

• Specific, Measurable, Achievable, Relevant, Time-bound.

How to Apply

Use SMART and FAST as prompts for a goal conversation: define the decision, baseline, owner, time horizon, evidence, controllability, guardrails, and review rule before selecting letters, scoring, or transparency conventions.

Contrarian Thinking: The Problem with "Achievable"

Treat the "A" in SMART as an invitation to set a credible commitment rather than an automatic ceiling. Teams can use stretch goals when they are paired with clear learning loops and safeguards. The FAST framework offers one alternative for dynamic environments; Sull and Sull define it as Frequent discussions, Ambitious scope, Specific metrics, and Transparency. ^[8]

• Frequently Discussed: Choose a review rhythm that can change a decision; weekly is not universal.
• Ambitious: Stretch only when capacity, learning, safety, quality, and incentive effects are acceptable.
• Specific: They are quantified as metrics and milestones.
• Transparent: Make goals and progress visible to the people who need them, subject to privacy, confidentiality, labor, security, and legal constraints; transparency does not require universal public disclosure.

So What for Managers

• Define a goal's decision, baseline, owner, controllability, capacity, time horizon, and guardrails before debating whether it is SMART or FAST.
• Use stretch only when learning, quality, safety, workload, incentives, and affected-party risks are visible and reviewable.
• Treat goal progress as evidence for a decision, not as a standalone performance judgment or proof that the target caused an outcome.

Limits and Critiques

• SMART and FAST are practitioner mnemonics; neither guarantees valid targets, motivation, alignment, or performance.
• Goal effects depend on commitment, ability, task complexity, feedback, competing goals, incentives, culture, and potential harm.
• Transparency, ambition, and time bounds must respect privacy, confidentiality, labor, security, accessibility, and legal constraints.

Connections

• Input: Use the organization's purpose, strategy, evidence, and constraints to shape goals; vision is one input, not a prerequisite.
• Output: Use OKRs only after confirming that an outcome-based goal system fits the work.

Overview

Rumelt's strategy kernel distinguishes strategy from a list of aspirations and frames it around a diagnosis, a guiding policy, and coherent action. ^[2]

How to Apply

To use Rumelt's practitioner kernel, articulate three components while preserving evidence and uncertainty:

1. A Diagnosis: An interpretation of the challenge and causal structure. A strategy can address interacting constraints; do not force one “single biggest” problem when the system evidence does not support it.
2. A Guiding Policy: The overall approach to dealing with the challenge identified in the diagnosis. It's not a list of action steps; it's the strategic guardrails that will guide action. Constructed examples: (e.g., "We will compete on customer experience, not price," or "We will leverage our developer ecosystem to build a platform.").
3. Coherent Actions: A focused set of consistent actions and resource allocations that implement the guiding policy, with dependencies, owners, evidence, and adaptation. ^[2]

So What for Managers

• State the challenge, alternatives considered, guiding policy, coherent actions, owners, constraints, and evidence before turning strategy into goals.
• Treat the diagnosis as an interpretation to test; update it when new evidence, dependencies, or external conditions change.
• Fund and sequence only the actions the organization can support, with decision dates and stop, continue, or adapt rules.

Limits and Critiques

• The kernel is a practitioner framing, not a validated universal strategy process or causal model.
• A diagnosis can be wrong, incomplete, politically contested, or too narrow for interacting constraints; invite dissent and alternative explanations.
• Coherent action can still fail through insufficient capability, resources, execution, regulation, or changing conditions.

Connections

• Input: Use Chapter 3's external and internal analysis to test the diagnosis, while preserving alternative explanations and uncertainty.
• Output: Use the guiding policy and coherent actions to inform goals or other operating commitments when those mechanisms fit the work.

Overview

OKRs developed through Intel management practice and were later popularized more broadly. They pair qualitative objectives with measurable results, but cadence, number, scoring, alignment, and incentive treatment are design choices. An OKR can express an outcome hypothesis; it does not allocate resources or prove impact. ^[1]

How to Apply

1. Define an Objective: State the direction and decision horizon; quarterly and inspirational are options, not requirements.
2. Define Measurable Key Results: Choose a small number that tests the intended outcome, using baselines, definitions, owners, data lineage, guardrails, and controllability. Results do not “prove” the objective or causality.
   • Constructed output example: "Launch 5 new marketing campaigns."
   • Constructed outcome example: "Increase marketing-qualified leads (MQLs) from 500 to 1,000."
3. Negotiate Alignment: Connect enterprise and team commitments vertically and horizontally; resolve dependencies, capacity, shared measures, and decision rights rather than mechanically cascading.
4. Review and Reflect: Choose scoring and incentive treatment locally. Practitioner conventions such as decimal scores are not validated performance thresholds. Separate committed and stretch work, record why a result moved, and do not infer ambition or employee performance from one score. ^{[1] [4]}

Figure 8.2. Negotiated OKR alignment and learning loop. Enterprise priorities and team commitments meet through dependency, capacity, and guardrail negotiation rather than one-way cascade. ^{[1] [4]}

flowchart TD
    A[Enterprise Strategy and Constraints] --> B[Company Outcome Priorities]
    B --> C[Team Proposals]
    C --> D[Negotiate Dependencies, Capacity, and Guardrails]
    D --> E[Committed Team Outcomes and Work]
    E --> F[Operating Review: Evidence and Forecast]
    F --> G{Continue, Stop, or Reallocate?}
    G --> B
    C -.->|Local evidence and constraints| B

    style A fill:#4ecdc4
    style D fill:#ffd93d
    style E fill:#95e1d3
    style G fill:#95e1d3

Text equivalent: Enterprise strategy sets outcome priorities; teams propose contributions based on local evidence. Leaders and teams negotiate dependencies, capacity, and guardrails before committing. Reviews examine evidence and forecasts, then continue, stop, or reallocate work and update priorities.

Source note: Original synthesis of OKR practice with an incentive/gaming control; it does not claim one alignment design is superior. ^{[1] [4]}

So What for Managers

• Use OKRs to make a bounded outcome hypothesis visible after strategy, resources, dependencies, authority, and capacity are explicit.
• Negotiate vertical and horizontal commitments; record local constraints, guardrails, data lineage, and what will happen if the result moves.
• Review OKRs with forecasts, financials, operations, people, safety, and risk evidence; stop, continue, or reallocate rather than merely rescore.

Limits and Critiques

• OKRs are a practitioner goal system, not a universal operating model, causal test, resource-allocation method, or performance ranking.
• Cascading, quarterly cadence, decimal scoring, stretch goals, and compensation separation are conventions that can fail or create gaming.
• A result can move because of external conditions, measurement changes, dependencies, or unrelated work; do not infer ambition, causality, or employee value from one score.

Connections

• Input: OKRs should be reconciled with enterprise strategy, vision, local evidence, delegated authority, regulation, dependencies, and capacity; some operational or control objectives arise from obligations rather than top-down derivation.
• Output: OKR evidence is one input to a Quarterly Business Review (QBR) alongside financials, forecasts, customers, operations, people, safety, risk, controls, and external change.

Overview

KPIs and OKRs serve overlapping measurement purposes. Doerr's practitioner account supports the Objective/Key Result structure and distinguishes committed from stretch practice. ^[1] The comparison used here—KPIs as selected ongoing measures and OKRs as periodic objective/result commitments—is an author synthesis. A measure may serve both uses, and neither label establishes causal leverage, target validity, controllability, or data quality.

How to Apply

1. Establish Your Health Dashboard (KPIs): Define a manageable set of critical health metrics for each part of the business. These are your "business as usual" indicators; the appropriate number depends on the decision, work, and evidence.
2. Investigate a “Red” KPI: Deterioration can trigger diagnosis, but an OKR is only one response. First verify the definition, data, materiality, cause, controllability, urgency, existing owner, and whether incident response, corrective action, service management, risk control, or a project is more appropriate.
   • KPI: Customer Churn Rate (the lagging indicator of health).
   • Objective: "Dramatically improve customer loyalty and reduce churn."
   • Key Result: "Reduce monthly customer churn rate from 5% to 2.5% this quarter."
3. Choose the Mechanism: Use OKRs only when a periodic objective/result system improves focus and learning. Initiatives, forecasts, service levels, risk controls, or project milestones may be more appropriate for some work.

So What for Managers

• Define each measure's decision, denominator, owner, lineage, latency, uncertainty, controllability, and guardrail before calling it a KPI or Key Result.
• Investigate a deteriorating KPI before choosing an OKR; an incident response, service level, risk control, forecast, or project may fit better.
• Use countermetrics and affected-party evidence so improvement in one measure does not conceal quality, safety, customer, workforce, or equity harm.

Limits and Critiques

• KPI and OKR labels are overlapping management conventions, not an ontology of health versus change or proof of causal leverage.
• A target can be invalid, gamed, uncontrollable, or based on poor data; a visible score can narrow attention rather than improve the underlying work.
• Some obligations require ongoing controls or professional judgment and should not be converted into periodic goals merely for comparability.

Connections

• Input: Use key drivers from your business model, Financial Analysis (Chapter 4), Operations (Chapter 6), customer evidence, and risk or control obligations as inputs to KPI selection.
• Output: A deteriorating KPI may become a QBR discussion item, but the appropriate response may instead be an incident, control, service-level action, forecast, or project.

Overview

Balanced Scorecard was developed by Kaplan and Norton as a strategic performance-management framework that broadens attention beyond lagging financial indicators across four perspectives. It can expose neglected dimensions and strategy hypotheses, but it does not ensure long-term health, causal balance, good targets, or resistance to gaming. ^[9]

How to Apply

For your strategy, define goals, metrics, and initiatives for each of the four perspectives:

1. Financial: "To succeed financially, how should we appear to our shareholders?" (e.g., Revenue Growth, Profitability, ROIC).
2. Customer: "To achieve our vision, how should we appear to our customers?" (e.g., Customer Satisfaction, NPS, Market Share).
3. Internal Business Processes: "To satisfy our shareholders and customers, what business processes must we excel at?" (e.g., Operational Efficiency, Quality, Cycle Time).
4. Learning and Growth: "To achieve our vision, how will we sustain our ability to change and improve?" (e.g., Employee Skills, Technology Infrastructure, Culture).

Figure 8.3. Balanced Scorecard strategy hypotheses. The arrows are relationships to test, not established causal chains or guaranteed financial outcomes. ^[9]

flowchart LR
    A[Learning and Growth] --> B[Internal Processes]
    B --> C[Customer Outcomes]
    C --> D[Financial Results]
    D --> E[Strategic Feedback]
    E --> A

    style A fill:#4ecdc4
    style B fill:#ffd93d
    style C fill:#95e1d3
    style D fill:#95e1d3

Text equivalent: Learning-and-growth, internal-process, customer, and financial perspectives are connected as hypothesized strategy logic. Review evidence for each link, adverse effects, missing measures, and whether the proposed driver is controllable before reallocating resources.

Source note: Original redraw of the four Balanced Scorecard perspectives; strategy-map arrows are hypotheses. ^[9]

Contrarian Thinking: BSC vs. OKRs

The Balanced Scorecard and OKRs serve distinct purposes: the BSC emphasizes a balanced performance system, while OKRs provide a periodic goal-setting cadence. One possible design is to use the four BSC perspectives when testing whether company-level OKRs are balanced rather than focused only on financial results; local evidence should determine whether that design helps. ^{[1] [9]}

So What for Managers

• Use the four perspectives to test whether a strategy review is ignoring customer, process, capability, or financial consequences.
• Define measures, owners, baselines, data lineage, targets, guardrails, and review decisions for each perspective rather than filling a template.
• Treat arrows and driver relationships as hypotheses; update or remove them when evidence, trade-offs, or unintended effects do not support the proposed logic.

Limits and Critiques

• The Balanced Scorecard is a practitioner framework; the perspectives do not guarantee balance, performance, causality, or long-term health.
• Strategy maps can imply causal certainty, overproduce measures, or hide weak definitions, external drivers, and uncontrollable outcomes.
• A scorecard can be gamed or used as an employment or incentive instrument without adequate job-related criteria, safeguards, and review.

Connections

• Input: Use the organization's overall Strategy (Chapter 3), stakeholder outcomes, operating risks, and financial constraints to decide which quadrants or perspectives matter.
• Output: BSC measures can supply candidate KPIs and review questions; they do not automatically belong on a health dashboard.

Overview

The Hedgehog Concept is Collins's practitioner model of deep understanding at the intersection of three circles: what the organization is passionate about, what it can be best in the world at, and what drives its economic or resource engine. ^[10] The account derives the concept from retrospective comparison of selected companies. Denrell's peer-reviewed analysis shows why samples focused on survivors and successful organizations can produce misleading beliefs about management practices. ^[11] Use the concept as a reflection and hypothesis-building model, not evidence that the intersection causes performance.

How to Apply

The three prompts below are an author adaptation of Collins's circles that adds feasibility, customer, risk, and externality checks.

1. What you are deeply passionate about: What is your core purpose and motivation? What work do you love?
2. Where could capabilities create differentiated value: Test the customer, competitor, capability, complementary-asset, and imitation evidence; “best in the world” is not a required or always feasible claim.
3. What drives the economics: Identify several value and cost drivers with cash, risk, externality, and guardrail measures rather than forcing one denominator.

Treat the intersection as a strategic hypothesis to compare with alternatives, not a transformation guarantee.

So What for Managers

• Use the three prompts to compare strategic alternatives with customer, capability, economic, risk, externality, and implementation evidence.
• Separate passion, differentiated capability, and economic logic; do not force one denominator or treat “best in the world” as a feasible requirement.
• Record rejected alternatives, uncertainty, resource needs, and review dates before converting a Hedgehog hypothesis into policy or goals.

Limits and Critiques

• The Hedgehog Concept is a retrospective practitioner model, not proof that an intersection causes durable performance.
• Survivor and success-sample bias can make selected management practices look more general or effective than they are.
• A compelling focus can become tunnel vision if it ignores customer harm, regulation, capability gaps, externalities, or changing conditions.

Connections

• Input: Use purpose and behavioral commitments, capabilities from a VRIO Analysis (Chapter 3), financial drivers from Financial Analysis (Chapter 4), and customer evidence as inputs to a focus hypothesis.
• Output: A provisional Hedgehog hypothesis can inform candidate guiding policies in "Good Strategy" (Framework 3) and questions for company-level OKRs (Framework 4); it does not supply either automatically.

Overview

VSEM is used here as an author synthesis connecting vision, strategy, execution, and metrics. It is a mnemonic, not a canonical complete management system; linearity can conceal diagnosis, resources, dependencies, incentives, risk, and adaptation.

How to Apply

Use these four prompts iteratively, not as a required sequence:

1. Vision: Where are we going? (The desired future state).
2. Strategy: What's our plan to get there? (The guiding policy and coherent actions).
3. Execution: What funded work, operating commitments, controls, or initiatives are implementing the strategy?
4. Metrics: What evidence and measures will show progress, health, risk, and unintended effects?

Use the four questions as a traceability check, then add budget/capacity, owners, dependencies, decision rights, forecasts, guardrails, and review.

So What for Managers

• Use VSEM as a traceability check: can the team connect the intended future to choices, funded work, measures, owners, and review decisions?
• Add diagnosis, budget, capacity, dependencies, decision rights, forecasts, guardrails, and adaptation rather than treating the four labels as a complete process.
• Use missing links to ask a bounded question and assign an owner; do not infer execution quality from a completed mnemonic.

Limits and Critiques

• VSEM is an author synthesis, not a canonical or empirically validated management system.
• A linear vision-to-metrics sequence can hide trade-offs, resources, incentives, obligations, power, risk, and learning.
• The mnemonic does not establish that a metric is valid, that execution caused an outcome, or that one operating design fits every organization.

Connections

• Input: This framework synthesizes the purpose inputs in Mission, Vision, and Values (Framework 1) and Good Strategy (Framework 3).
• Output: It can expose missing links; it does not replace the execution operating system above.

Overview

Goal alignment is an author-created coordination aid. Once enterprise priorities are set, teams need vertical and horizontal coordination. Strict cascade and alignment networks are two stylized options; matrix, product, regulated, and professional organizations may need different designs.

How to Apply

1. The "Strict Cascade" (Traditional): The CEO's Key Result becomes a direct manager's Objective, which is then cascaded down to their team.
   • Potential benefit: Can make an intended hierarchy of contributions visible when metric definitions, controllability, dependencies, and decision rights are explicit; it does not ensure mathematical or behavioral alignment.
   • Con: Can feel very top-down and disempowering. A strict cascade can leave teams with measures they cannot fully control.
2. Alignment Network: The company sets high-level priorities and teams propose contributions based on local evidence and dependencies.
   • Potential benefit: Can use local knowledge and improve ownership when decision rights, capacity, and conflict resolution are clear.
   • Con: An alignment network can increase negotiation cost or ambiguity when decision rights, conflict resolution, and strategic context are unclear.

So What for Managers

• Choose cascade, network, portfolio, service-level, control, or professional-judgment mechanisms based on work dependencies, authority, capacity, and risk.
• Make cross-team commitments negotiable and explicit: define owners, interfaces, shared measures, conflict routes, decision rights, and review dates.
• Test whether local contributions improve the enterprise decision without forcing teams to inherit measures they cannot control.

Limits and Critiques

• Cascade and alignment networks are stylized operating designs, not universal solutions or proof of ownership, trust, or performance.
• Strict cascade can create top-down goals, metric distortion, and accountability without control; networks can create negotiation cost and ambiguity.
• Some work requires service levels, safety controls, regulatory duties, cases, portfolios, or professional judgment rather than OKRs.

Connections

• Input: Use company-level OKRs (Framework 4) only where a periodic outcome system fits the work.
• Output: A proposed set of team-level contributions, dependencies, and conflicts for review. Some teams may require service levels, controls, cases, portfolios, or professional judgment, and no cascade is assumed to drive every team's daily work.

Overview

Mission and values can be stress-tested with this author-created diagnostic; it is not evidence that mission statements generally fail. Mission and values statements can be vague, contradicted, or unused, but the available chapter sources do not justify broad claims that they fail or lack impact. Evaluate a statement by clarity, credibility, decision use, stakeholder legitimacy, and alignment with actual systems.

How to Apply

Use the questions below with affected people and decision owners. Record what would change in decisions, systems, resources, incentives, and behaviors; then review the evidence rather than treating agreement with a statement as proof of value.

The Critique

• Is it understood? Test whether relevant people can explain the statement's meaning; verbatim recall is not the only validity test.
• Does it inform action? Ask what a manager or employee would do differently because of the statement.
• Is it credible? Compare it with actual incentives, resource choices, controls, and observed behavior.

The Alternative: A Measurable Vision and Behavioral Values

1. Clarify the role: A mission can express enduring purpose; an envisioned future can express direction. Neither must be reduced to a measurable target, and neither substitutes for strategy.
2. Make Values Behavioral: Don't just state a value; describe the specific, observable behaviors that represent it.
   • Vague Value: "We value communication."
   • Constructed behavioral example: “Share relevant information in accessible form, seek understanding before reacting, and raise material concerns through protected channels.” Validate job relevance, culture/accessibility, conflicts, adverse patterns, and employee rights before using a behavior in people decisions.

So What for Managers

• Ask what a mission or value changes in a real decision, resource choice, control, or behavior; remove language that cannot guide action.
• Validate clarity, credibility, legitimacy, accessibility, conflicts, and adverse patterns across affected roles before adoption or revision.
• Keep the statement subordinate to strategy, evidence, capacity, professional duties, and approved people-process criteria.

Limits and Critiques

• This is an author-created diagnostic, not a validated mission-quality scale or proof that statements cause performance.
• A statement may be meaningful to some groups and contested or harmful to others; recall and agreement are incomplete evidence.
• Values used in employment or incentive decisions require job-related criteria, consistency, documentation, due process, accessibility, and HR/legal review.

Connections

• Input: This critique forces a more rigorous approach to defining Mission, Vision, and Values (Framework 1).
• Output: It can inform a candidate set of guiding principles for further review across the organization.