Skip to main content

Best practices for keeping your playbooks sharp

A well-configured playbook from the start loses effectiveness if not reviewed over time. Your team's process changes, priorities evolve, and the fields that were key six months ago may no longer be. These practices help you keep playbooks useful.

Review each active playbook quarterly

Reserve 30 minutes each quarter to review the active playbooks in your account. Ask yourself: are the fields we extract still relevant? Does the playbook objective reflect how the team works today? Are there fields that nobody looks at in the CRM that we could remove?

Limit the number of fields per playbook

A playbook with too many fields disperses diio's focus and generates more superficial analyses. The optimal range is between 6 and 12 active fields per playbook. Beyond that number, Key Notes become longer but less precise.

Specific fields should go to the CRM only if someone uses them

Specific fields that travel to the CRM have value only if the sales, post-sales, or recruiting team actually consults them to make decisions. If a field has been in the CRM for months and nobody looks at it, remove it from the playbook. It reduces noise without losing useful information.

Keep the Objective updated

The playbook Objective is what tells diio what to look for in each conversation. If the objective changed (for example, the renewals team now also does upsell), update the Objective field in the playbook configuration so the analysis reflects the new reality.

Deactivate playbooks you no longer use

A playbook without assigned teams for more than one quarter is a candidate for deactivation. Inactive playbooks don't generate noise in the analysis, but they do in the configuration list and can confuse new Admin team members.

Did this answer your question?