Operating playbooks
Playbooks for the operating decisions that come before the tooling.
Step-by-step operating guidance for connecting systems, governing automation, and proving a workflow before it scales — written to be executed rather than admired.
Sequenced
Ordered so each step is answerable when you reach it
Bounded
Scoped to one outcome, not a transformation programme
Free
No signup, Markdown download
Introduction
What a playbook covers that a template does not.
A template captures the decisions for one artifact. A playbook covers the sequence — what to do first, what has to be true before the next step is answerable, and where teams reliably get stuck.
The ordering is the substance. Most operating failures are not wrong answers; they are answers attempted in the wrong order, like setting an automation boundary before anyone has decided who owns the record.
These are written for the person doing the work rather than for the person approving it, which means they are specific about the awkward parts: what to do when two systems both claim a field, and when to stop and escalate rather than improvise.
- Format
- Sequenced operating guides
- Scope
- One outcome per playbook
- Cost
- Free, no signup
- Best paired with
- Implementation templates
Why this exists
Operating guidance usually describes the destination, not the route.
Most published guidance in this space states what good looks like. That is easy to agree with and hard to act on, because the difficulty is never in wanting the outcome — it is in the order of the twenty decisions between here and there.
The second failure is that guidance assumes a clean starting position. Real teams start mid-process, with existing systems, partial ownership, and automations somebody built two years ago and left.
These playbooks assume the messy starting point, and are explicit about which steps can be deferred and which cannot. Deferring the ownership decision, for instance, is what makes every later step ambiguous.
You're likely here because
- You know the outcome you want and not the first step
- A previous attempt stalled partway and nobody is sure why
- Steps are being done in parallel that depend on each other
How to choose
Which playbook to open first.
If
Nothing is automated yet and you are choosing where to start
If
Systems are connected but the data is not trusted
Start with
The connector and source-of-truth playbook
If
Automation exists and is producing disputed results
Start with
The measurement and baseline playbookIf
You are about to give a system autonomous scope
How it works
The order these playbooks assume.
Every playbook sits somewhere on this path. Knowing which stage you are actually at is usually more useful than reading further ahead.
Step 01
Find the constraint
Identify the workflow where the cost is real and recurring, rather than the one that is most visible or most often complained about.
Step 02
Establish ownership
Decide who owns each record and each exception before any automation is designed. Every later decision depends on this one being settled.
Step 03
Prove one path
Run a single bounded workflow end to end against real records, including the failure path, before widening scope.
Step 04
Measure against a baseline
Compare to the reading captured before the change, using the same population and definition.
Step 05
Expand deliberately
Add scope only once the first path completes reliably and the receiving team is using the result rather than working around it.
Playbooks
Published playbooks — 8 in total.
Operating playbook
30-Day AI Implementation Playbook
A bounded 30-day path from workflow selection to measured production evidence.
Read the playbook →
Operating playbook
60-Day AI Implementation Playbook
A 60-day operating plan for expanding a proven AI workflow without losing governance or observability.
Read the playbook →
Operating playbook
90-Day AI Implementation Playbook
A 90-day plan for scaling connected AI execution after the first outcome is proven.
Read the playbook →
Operating playbook
Replace Spreadsheets Playbook
A practical migration plan for replacing brittle spreadsheet workflows with explicit records, states, owners, and controls.
Read the playbook →
Operating playbook
AI CRM Implementation Playbook
A practical implementation plan for AI-assisted CRM workflows with authoritative data, governed actions, and measurable outcomes.
Read the playbook →
Operating playbook
Product Launch Playbook
A structured path from business intent to a tested product workflow with clear acceptance evidence.
Read the playbook →
Operating playbook
AI Sales Engine Playbook
A sales operating playbook covering source data, qualification, outreach, replies, scheduling, pipeline, and measurement.
Read the playbook →
Operating playbook
SMB AI Growth Playbook
A practical SMB playbook for choosing and improving the workflows most likely to affect revenue, customer value, and operating leverage.
Read the playbook →
Scope
What these playbooks assume and exclude.
- They assume the people who own the outcome are available to make decisions.
- They do not size engineering effort or produce a project plan.
- They do not cover organisational change management, which software cannot deliver.
- Sector-specific regulatory obligations take precedence over anything written here.
FAQ
Questions about this collection.
What is the difference between a playbook and a template?
A template is the artifact you fill in for one decision set. A playbook is the sequence — which template to reach for, when, and what has to be settled before the next one is answerable.
Do I need to follow the whole sequence?
No, but the ownership step is the one that cannot be deferred. Skipping it makes every subsequent decision ambiguous, which is the most common reason an implementation stalls.
Are these specific to UbiVibe?
No. The sequence applies regardless of which platform executes the workflow. Where a step is easier on a governed runtime we say so, but the ordering is not product-specific.
How long does a playbook take to work through?
The decisions take hours; the proving takes weeks. Most of the elapsed time is in running one bounded workflow against real records long enough to trust it.
What if we are already partway through?
Start at the stage you are actually at, then check backwards. Stalled implementations usually have an unsettled decision one or two stages earlier.
Is there a cost?
No. Playbooks are free and downloadable as Markdown with no signup.
Start with ARIA
Ask ARIA about playbooks.
You do not have to pick your way through this collection to get started. Describe the outcome you want and ARIA determines which capabilities, systems, and workflows the job needs.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Start at the constraint, not at step one.
Describe the outcome you are trying to reach. ARIA can resolve which systems are involved and where the actual constraint sits, which is usually not where the noise is.