Microsoft recently released Playbooks for Dynamics 365 for Sales and Customer Engagement. What are these, how might you use them, and what should you be careful about when working with them? Let's take a quick look at all of those items.
Spoiler Alert: I'm not a big fan.
When you read over the official documentation (click here) and play around a bit, the functionality is intriguing, but might be a bit disappointing once you put it into production.
In general, playbooks are a way that you can setup templated plans (a set of activities to follow) for following-up on specific situations that may arise regarding a Lead,Opportunity or other sales entity. Some examples that come to mind:
In the Sales Hub app, users with the right security role can create a playbook by navigating to the App Settings area, creating a new Playbook Template record, giving it a name, assigning a category, determining which entity(ies) it belongs to, and adding a set of activities to it. It's about that simple.
For detailed instructions on creating a playbook, here is that link to the official Playbook documentation again.
Personally, I'm not a big fan of creating a large series of activities for a user all at once. Too often this seems to result in an overwhelming list of activities to work through and users give up on activity management. But there may be scenarios in which this might work, so let's dive a little deeper.
Playbooks can be "called" from an entity that they're assigned to (Lead, Opportunity, Quote, Order or Invoice). For example, if one or more playbooks are assigned to the Opportunity entity, a user can open an opportunity, click the Launch Playbook button, select the playbook, and run it. Just like that, the playbook runs.
Now comes the not-so-intuitive part. Playbook activities don't appear under the entity that they've been assigned to. If you’ve applied a Playbook to an Opportunity, here’s the process for viewing the newly created activities:
That's a lot of navigation for most users to go through in order to work a task list.
But, you say, most users use the Activity entity to work their tasks. What is this experience like when it comes to playbooks? Unfortunately it’s worse!
In the nearby image you can see a task that was created as a part of a Dynamics 365 for Sales Playbook for an Opportunity. What don’t you see? Links or information about the Opportunity! As the user I would have no idea what to do with this task until I click the regarding link and then from the Playbook form, I’d probably also need to click the link to the opportunity to learn about it, then navigate back to the playbook to work the list of activites. Again – way too much navigation for most users.
Given the limitations listed above, I'm not sure that a good use-case exists for playbooks. At least not out-of-the-box. But here are a few ideas:
The bottom-line: I'm hard pressed to find a scenario that works. But this is new functionality - maybe I'm missing something or maybe Microsoft has a long-term plan to build something more useful on this foundation.
Microsoft has announced that documents and sales literature will soon be able to be aligned to playbooks. This is promising and hopefully these items will be made visible to users in a more intuitive format.
A number of other options exist for helping your sales team to work with CRM activities and to provide playbook type information in Dynamics 365. Contact C5 Insight for more information.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.