Before defining Rundown's vision, positioning, products, or sales strategy, it is essential to establish the rules that govern this document. This chapter defines how the Strategy Manual should be read, interpreted, maintained, and improved over time.

The objective is to ensure that the manual remains a living strategic system rather than a static document.

0.0 How to Read This Manual

Objective

Establish a common language, structure, and decision-making framework for everyone who contributes to or references this manual.

Why This Section Exists

As Rundown grows, multiple people will contribute to strategic discussions and business decisions. Without a shared framework, the manual risks becoming inconsistent, opinion-driven, or outdated.

This chapter ensures that every future addition follows the same standards of reasoning and documentation.

Information Classification

Every statement within this manual must belong to one of the following categories.

No statement should exist outside one of these categories.

Decision Hierarchy

Not every decision has the same importance.

All strategic decisions should respect the following hierarchy.

Vision
    ↓
Identity
    ↓
Principles
    ↓
Strategy
    ↓
Execution

Higher levels govern lower levels.

Execution should never contradict Strategy.

Strategy should never contradict Principles.

Principles should never contradict Identity.

Identity should always support the Vision.

The Three-Layer Strategy Model

Every major chapter in this manual should answer three questions.

Layer 1 — Identity

Who are we?

Defines:

• Why Rundown exists.

• What we believe.

• What we refuse to become.

• What characteristics should remain true regardless of market conditions.

Identity changes very rarely.

Layer 2 — Strategy

How do we compete?

Defines:

• Positioning.

• Target market.

• Product architecture.

• Pricing philosophy.

• Sales approach.

• Outreach strategy.

• Competitive differentiation.

Strategy may evolve as the market evolves, but it should always remain consistent with Rundown's identity.

Layer 3 — Execution

How do we deliver?

Defines:

• Processes.

• SOPs.

• Systems.

• Templates.

• Automation.

• Quality assurance.

• Project delivery.

Execution is documented primarily within Rundown OS and exists to support the strategy defined in this manual.

Strategy Validation System

Every significant strategic decision should move through the following lifecycle.

Research
      ↓
Assumption
      ↓
Decision
      ↓
Experiment
      ↓
Validation
      ↓
Insight

Ideas do not become facts until they have been tested.

The objective is to create a culture of evidence-based decision making rather than intuition-based decision making.

Strategic Registers

The following registers should be maintained throughout the Strategy Manual.

Decision Register

Records every major strategic decision, including the rationale, alternatives considered, risks, owner, review date, and current status.

Assumption Register

Captures beliefs that have not yet been validated, assigns a confidence level, and defines how they will be tested.

Experiment Register

Documents structured experiments, including the hypothesis, success metrics, duration, results, and conclusions.

Insight Register

Captures lessons learned from client engagements, sales conversations, projects, and internal experimentation.

Only validated learning should be recorded here.

Opportunity Register

Maintains ideas that are intentionally deferred rather than forgotten.

Every opportunity should include a reason for deferral and a review date.

Strategic Debt Register

Tracks weaknesses within Rundown's business model, positioning, messaging, systems, or execution that require future improvement.

Strategic debt should be reviewed periodically alongside technical and operational debt.

Confidence Framework

Every assumption and major strategic decision should include a confidence score.

Confidence scores should increase only through experimentation and real-world validation.

Decision Filters

Before approving a significant strategic decision, evaluate it against the following questions.

• Does this align with Rundown's vision?

• Does this strengthen our identity?

• Does this improve our strategic positioning?

• Does this increase perceived client value?

• Can this be productized?

• Can this be systemized?

• Is it operationally sustainable?

• Does it simplify the business?

• Does it improve profitability?

• Will it still make sense three years from now?

A decision that fails multiple filters should be challenged before implementation.

Red Team Review

At the conclusion of every major phase, conduct a structured challenge of the proposed strategy.

The objective is not to defend the work but to identify weaknesses before implementation.

Key questions include:

• What assumptions could be incorrect?

• What evidence would change our decision?

• Where is the strategy most vulnerable?

• How might a competitor exploit these weaknesses?

• What conditions would cause this strategy to fail?

Every major phase should conclude with a documented Red Team Review.

Change Management

Whenever a strategic decision changes, the following questions must be answered.

• What is changing?

• Why is it changing?

• What evidence supports the change?

• Which assumptions have been validated or disproven?

• Which other sections of the manual are affected?

• Who approved the change?

• When should this decision be reviewed again?

No strategic decision should be changed without documenting its reasoning.

Guiding Principle

This manual exists to preserve Rundown's strategic thinking.

Its purpose is not merely to record decisions but to ensure that every future decision is intentional, evidence-based, aligned with Rundown's identity, and capable of scaling with the business over time.