The Worksona Leadership Runbook: Turning Principles into Commands

We built the Worksona Leadership Runbook to solve a specific problem with how leadership is usually taught: it is descriptive, not executable. Books and workshops explain what good leadership looks like. They rarely specify how to run it.

The runbook reformats leadership as a set of seven CLI-style commands. Each command is a named principle with typed flags, expected inputs, and concrete output deliverables. There is no narrative to interpret — only a procedure to run.

The seven commands are:

• /demonstrate-not-decorate — ship proof, not polish
• /map-before-make — draw the terrain before marching
• /drive-through-documentation — treat docs as a control surface
• /orchestrate-by-theme — fewer, bigger bets that compound
• /enforce-measurement — evidence or it didn't happen
• /champion-adoptability — adoption is the product
• /mandate-interoperability — open by default, prevent silos

Every command runs the same five-phase loop: advise → critique → build → analyze → learn. You learn the loop once and apply it to all seven commands, in all contexts.

Why format leadership as executable commands?

Leadership principles fail in practice for a predictable reason: the gap between "be transparent" and knowing what to do in a Tuesday standup is unbridgeable by principle alone. The command format closes that gap.

When a team lead is about to kick off a new initiative, they open /map-before-make and follow the flags: produce user journey and workflow diagrams (advise), flag missing interfaces or ownership gaps (critique), break the map into thin backlog slices (build), validate integration contracts (analyze), and update maps with what was learned (learn). The output of each phase is the input to the next.

/map-before-make --advise   "Produce user journey + workflow diagrams"
                 --critique "Flag missing interfaces or ownership gaps"
                 --build    "Break map into thin backlog slices"
                 --analyze  "Validate integration contracts"
                 --learn    "Update maps with discovered gaps"

This is what Worksona first principles call "intelligence residing in structure." The five-phase loop is the smart part. The content is secondary.

The format also makes leadership teachable and auditable. A decision log template captures the decision, the evidence, alternatives considered, the owner, and the next review date. Leadership actions leave artifacts — not just intentions.

How the seven commands work in practice

The Startup Pathfinding component applies the same logic to opportunity decisions. Before committing to any initiative, apply the Focus Filter — four yes/no questions: primary objective alignment, testable in two weeks, value regardless of outcome, and capacity reality. Four yes answers: proceed. Zero to one: automatic no.

The entire system is distributed as zero-dependency static HTML files. No server, no account, no installation. Open a file and run a command. The runbook generator accepts any organization's existing principles and produces a custom runbook in the same format — the framework is generative, not fixed.

Where it applies

The runbook is the meta-layer of the Worksona portfolio — the leadership philosophy made executable. All seven commands are visible throughout the portfolio's architecture: /map-before-make shows up in the diagram-first design of Merman; /champion-adoptability drives the zero-registration design of the AI Compass; /mandate-interoperability shapes the MCP-first API design.

Any organization that wants to move from leadership storytelling to leadership procedures can generate their own runbook from their own principles using the included generator — and apply the same five-phase execution loop to each one.