Playbooks vs. One-Off Projects

Not sure whether to launch from a Playbook or build a project from scratch? Here’s how to think about it — and when each approach pays off.

Playbooks: For Repeatable Processes

Playbooks are reusable blueprints for project types you run often.

• Come pre-loaded with tasks, stages, roles, and logic
• Ensure every new project follows the same structure
• Update centrally — future projects use the new version automatically
• Save time by eliminating repetitive setup

Example: If every new customer goes through the same 4-stage onboarding, always launch from your Customer Onboarding Playbook.

One-Off Projects: For Unique Work

One-off projects are created manually without a Playbook as a starting point.

• Best for non-repeatable, ad-hoc work
• Tasks and stages are built from scratch each time
• More flexible, but more setup effort
• Changes don’t carry over — nothing gets saved for reuse

Example: A customer requests a custom pilot with unique milestones — that’s a one-off project.

How to Decide

• Will I run this project type again? Yes → Playbook. No → One-off.
• Do I need consistency across customers or teams? Yes → Playbook. No → One-off.
• Do I want to save setup time? Yes → Playbook. No → One-off.

Tips

• Test a new workflow as a one-off project first. If it works well, save it as a Playbook.
• Can’t launch from a Playbook? Check that it’s published in the Library and that you have permission to access it.