Search the library
Keyword search across the published essays. It points you to the closest piece — it does not answer for me.
Playbook 01

The Orchestration Playbook

The Ladder tells you which rung a capability belongs on. This playbook is how you actually move it up one — the baseline, the gate, the review, and the evidence you need before you trust it further.

The problem this solves. Most teams adopt AI at the wrong altitude: either they let it draft a tweet and call it transformation, or they hand it a decision it should never have owned. Both fail, and both fail expensively.

What you will have at the end. A written inventory of every marketing task, each one assigned a rung, each rung with an explicit gate and an owner. In practice this takes a leadership team about two weeks.

Who runs it. One accountable owner plus whoever currently does the work. This does not work as a delegated exercise — the person who owns the outcome must be in the room.

01Inventory the work before you automate any of it
02Assigning a rung: the four-question test
03Designing a gate that people actually respect
04Baselines — measuring before, so after means something
05Promotion criteria: earning the next rung

The module outline for this playbook. Recorded walkthroughs are planned but not yet published — the written playbook stands on its own without them.

XLSTask inventory & rung assignment sheet
In preparation
DOCGate definition template (one per irreversible action)
In preparation
SOPSOP — weekly orchestration review
In preparation
DOCBaseline measurement worksheet
In preparation
TXTPrompt library — drafting, review, and escalation
In preparation

These templates are still being written — nothing here is downloadable yet. Each one is deliberately tool-agnostic, so the Implementation checklist can be run in whatever you already use in the meantime.

Implementation checklist
Every task written down before any tool is chosen
Each task assigned exactly one rung, with a named owner
Every irreversible action has a written gate
A baseline exists for each task you intend to move
Promotion criteria agreed in advance, not after the fact
A review cadence in the calendar, with a person attached
Common mistakes
01Starting at Rung 03+

Teams skip Observe because it feels slow. Observe is where the capability earns trust cheaply. Skipping it means your first real failure is also your first public one.

02Gating by category, not by action+

"Social posts need approval" is not a gate. "Any post naming a client is approved by the account owner" is. Vague gates get ignored within a fortnight.

03Automating a process nobody had written down+

If it only worked because a specific person knew the exceptions, automation does not scale it — it scales the gaps.

04Measuring activity instead of outcome+

Drafts produced is not a result. Time-to-publish and rework rate are.

Where LevelUp Growth shortens this
Task inventory

LevelUp Growth can import your existing task list and pre-assign rungs from historical data — the same output as the spreadsheet, without the fortnight.

Gates

Approval gates are native, with an audit trail per action. In the manual version this is a shared doc and discipline.

Baselines

Instrumented automatically. Manually, this is the honest but tedious part of week one.

The playbook does not require it. Each shortcut removes manual work from a process that already runs without it. If you cannot run this playbook by hand, buying software will not fix that.

Recommended reading