Worksona Leadership Runbook: Seven Commands That Make Leadership Executable

The Worksona Leadership Runbook is a set of seven named commands that convert leadership principles into repeatable, executable procedures. It ships as zero-dependency HTML files — no server, no accounts, no build toolchain. You open the file and run it.

Each command follows the same five-phase execution loop: Advise, Critique, Build, Analyze, Learn. That loop applies regardless of which command you invoke. The seven commands are: /demonstrate-not-decorate, /map-before-make, /drive-through-documentation, /orchestrate-by-theme, /enforce-measurement, /champion-adoptability, and /mandate-interoperability.

The runbook ships with four companion tools. An interactive viewer lets you browse commands and read full phase-by-phase descriptions. An AI chatbot accepts a leadership situation as input and returns guidance grounded strictly in runbook content — it does not produce generic advice. A Runbook Generator accepts custom organizational principles and produces a runbook in the same format. A Startup Pathfinding Playbook includes a four-question Focus Filter, a 90-day thesis template, risk-sharing partnership guidance, and milestone checklists.

Why is it useful?

Leadership literature is descriptive. It explains what good leadership looks like and why it matters. It rarely specifies what to do next Tuesday. The gap between principle and action is where most leadership development stalls — not for lack of understanding, but for lack of procedure.

The runbook closes that gap by treating leadership as a discipline that can be proceduralized. Each command has a name, a purpose, a set of phases, and expected outputs. When a team member asks what /enforce-measurement requires, the answer is not an essay — it is a checklist. That specificity is the point.

The AI chatbot reinforces this by staying within the runbook's scope. A domain-constrained advisor is more useful than a general-purpose one in high-stakes situations, because the advice stays anchored to the organization's own declared principles rather than drifting toward generic management frameworks.

How and where does it apply?

The runbook applies at the moment a principle needs to become an action. A team is starting a new initiative — /map-before-make specifies that diagrams precede implementation. A project is missing a success criterion — /enforce-measurement specifies how to define and attach one. A new team member is onboarding — /champion-adoptability specifies what the onboarding experience must provide.

The Runbook Generator extends this to other organizations. Any team can input their own principles and receive a structurally identical runbook — same format, same loop, their content. The format itself is the transferable artifact.

The Decision Log format, included as a standalone template, captures decisions, tradeoffs considered, alternatives rejected, and scheduled review dates. It operationalizes /drive-through-documentation at the individual decision level.

The following snippet shows the structure of a single runbook command as a data object. The Runbook Generator uses this schema to produce custom runbooks from user-supplied principles.

{
  "command": "/enforce-measurement",
  "purpose": "Every initiative requires a defined metric before work begins.",
  "phases": [
    {
      "name": "Advise",
      "action": "Identify the initiative and propose two to three candidate metrics.",
      "output": "Candidate metric list with rationale for each."
    },
    {
      "name": "Critique",
      "action": "Evaluate each candidate for observability, baseline availability, and gaming risk.",
      "output": "Ranked metric shortlist with critique notes."
    },
    {
      "name": "Build",
      "action": "Instrument the selected metric and confirm data is flowing before launch.",
      "output": "Live metric dashboard or report with confirmed baseline."
    },
    {
      "name": "Analyze",
      "action": "Review metric movement at defined intervals against the initiative hypothesis.",
      "output": "Interval analysis report with variance commentary."
    },
    {
      "name": "Learn",
      "action": "At initiative close, document what the metric revealed and what it missed.",
      "output": "Measurement retrospective logged to Decision Log."
    }
  ]
}

The runbook does not prescribe management style. It prescribes structure. Teams apply their own judgment within each phase. The procedure holds; the content varies by context.