Operating Playbook: Data-Driven Decisions and Analytics Cadence: cadence, instruments, and decisions for an operating program that runs after the consulting team leaves. Designed for the operating team rather than for the engagement.
What the playbook covers
The Stratenity operating playbook for embedding an analytics cadence into the operating system. How to move analytics from a service function to an operating discipline. The playbook is built for the operating team rather than for the consulting engagement. The engagement starts the program. The playbook keeps it running.
Operating programs that depend on consulting attention to keep functioning fade after the engagement closes. The Stratenity operating playbooks are designed to be operated by client teams without an embedded consulting presence, with a quarterly external review that catches drift before drift becomes failure.
The operating cadence
The cadence has three rhythms. The weekly operating review focuses on the leading indicators and the small operating decisions that the next week requires. The monthly portfolio review focuses on which initiatives are advancing, which are stalling, and what evidence the next month will produce. The quarterly capital gate focuses on retire-or-scale decisions and the reallocation of capital across the portfolio.
Each rhythm has a defined attendance list, a defined evidence pack, and a defined decision protocol. The protocols are not optional. Programs that allow the protocols to drift produce status meetings rather than operating reviews.
The instruments
The playbook is operated through a small number of instruments. A program scorecard captures the leading indicators that the program is organized around. A decision log captures the decisions made at each review with the evidence cited and the owner accountable. A risk and assumption log captures the program risks and the assumptions whose validation could turn into risks.
The instruments are deliberately spare. Operating programs accumulate dashboards faster than dashboards accumulate value. The discipline of keeping the instrument set small is what keeps the operating cadence focused on the decisions the program actually needs to make.
What the playbook produces
Across the first year of operation, the playbook produces the operational improvement the program was designed to deliver. Across the second year, it produces the institutional discipline that lets the operating team run the program without external support. Across the third year, it produces the platform components that subsequent programs can compose against, lowering the cost of the next program.
The compounding effect across years is the difference between a program that fades and a program that becomes how the firm operates. The playbook is designed for the compounding case.
How to use
Deploy the playbook in week one of the engagement, not at engagement close. The operating team runs the cadence from week one. The consulting team runs alongside, transferring the operating discipline as the program advances. By engagement close, the playbook is the way the program runs and the consulting team's withdrawal does not change the operating tempo.
Closing
Operating playbooks are the deliverable that distinguishes consulting that compounds from consulting that fades. The Stratenity playbooks are written for the operating team and tested against the realities of running a program at pace without an embedded consulting presence.