SaaS Playbooks

Create and implement repeatble processes that will allow your team to hit their metrics and goals.

Problem: Your team is working hard but they are wasting time reinventing the wheel, working on ineffective strategies, or too busy to document what is working.

Solution: Playbooks allow you to create a repository of coordinated processes so your team can execute multiple strategies across multiple business functions.

SaaS Playbook Definitions

Playbook: There should be a single playbook for each team, department or business function. Example: Marketing Playbook

Game Plan: There are multiple game plans within a playbook. These game plans can be shared across multiple playbooks. Be careful not to duplicate game plans across different playbooks. Example: Promotions (shared amongst product, marketing, sales, and customer support)

Plays: There are multiple plays within a game plan. These plays, often referred to as processes are the repeatable steps a team member takes to execute a game plan. Again, plays should be shared across game plans and you should not have duplicate plays. Example: How to create a landing page.

SaaS Playbook Hierarchy Diagram

SaaS Playbook Requirements

Playbooks should include

  1. An owner for the playbook, game plan, and plays
  2. When the game plan and play was last updated
  3. Where the game plan or play is shared
  4. Concise writing and simple examples

Playbook Pitfalls

Teams should not duplicate plays to include them in their game plan. A single play must exist for the topic and be included in other game plans.