“Imagine you win the lottery today and quit your job tomorrow. Would someone be able to step right in and take over your Marketo instance?” This is the mindset Tori Forte, Marketo consultant extraordinaire, recommends as you’re thinking about documenting your Marketo instance. In fact, good documentation can be nearly as important as the actual implementation itself. Keeping track of changes and decisions you’ve made during your instance setup can help you:
There are a couple different types of documentation you can produce. A governance guide outlines your instance setup in detail with topics such as program/folder structures, communication limits, and more. This would be a living document that users would turn to in order to identify your specific best practices and governing standards for your Marketo instance, and would mainly be for your Marketo admin or main user. In addition to a governance guide, your team may need supplemental enablement documents or training materials to help them get up to speed with Marketo. These could include exercises to practice working with the platform, quizzes to pass before being granted access, or a list of what your users are allowed to do in Marketo. These would be aimed at all Marketo users in your organization.
Whether you’re putting together a full blown governance guide or are simply documenting the key aspects of your setup to start, writing down the decisions you make during onboarding will help you and your team be successful with Marketo.
Getting Started on Your Documentation
Having trouble getting started on your guide? Tori suggests first focusing on the most important aspect of your Marketo documentation: your Admin Setup. “Make sure you’re writing down all of your behind-the-scenes decisions so if anyone needs to take over your Marketo instance, they’ll be able to understand how and why your instance was set up the way it is.” It’s crucial, Tori points out, that you “don’t just document what was built, but why it was built that way.” This helps a future admin (or even future you) avoid repeating decisions that didn’t work out or wasting time going down dead ends.
Another recommendation from Tori to establish the success of your documentation is to “ensure every rule you make has an owner to enforce it down the line. Lack of enforcement makes writing those rules moot.” Check in with your team and put a process in place to make sure this documentation will continue to adapt and stay relevant, as well as stay top of mind for your users.
Tips and Tricks
Whether you’re documenting a new/existing instance or creating training resources for your organization’s Marketo users, consider these tips from one of our resident Marketo experts, Kylie Peters:
Marketo Documentation Sample Topics
Use these topics to guide your initial Marketo governance documentation plan. It may help to take it slow and start with a few topics that are important to your particular instance, then expand from there.
Check out an example of Channel Documentation here (or attached to this post).
Start documenting your instance today! Be sure to involve your whole team - whether that’s just you or a team of 10 - and revisit these docs every month to keep it up to date as your use of your Marketo instance grows.
To regularly receive content to help you through your Marketo onboarding and implementation, sign up for the Marketo Jumpstart series.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.