I first set up a Marketo instance as a solo in-house user in a highly regulated industry (where everything must be documented, auditable and signed off). Now I'm agency side, helping clients build and follow best practice solutions. I keep coming back to the importance of a well documented instance - but I'm really curious to know how much documentation others do, and what tools you rely on.
Personally, I love:
What do you use? From process to business requirements, sign off to compliance... whether you hate it or love it:
Excel for naming conventions, channels, lead sources, and utm parameters.
One thing I've done that may be different - for some of the more complicated parts of our setup, I've recorded videos using Snagit by Techsmith, and highlight each part of the program - I find it is faster than creating a document with multiple screenshots and captions.
Thanks for your input!
I've had colleagues use Snagit & found it useful - neat to hear another person fond of it. How do you find handling the management of excel docs for these purposes across larger teams? I've always leaned towards online document platforms like google and confluence because they bypass the versioning issue.
On our main Marketing Department account, I use Google Docs to document my process.
I use the Google spreadsheet for the following:
A list of email templates to use for non scheduled promotional emails or announcements that are one-off when I'm on vacation.
- I list the names of the template, the location in Marketo and also provide the asset link.
- I provide a sample outbound campaign, the location in marketo and also provide the asset link. The smart lists are usually consistent by product so all they have to worry about is the flow and associating the correct approved email. Or how to clone a related email send program.
The most important ones that I document are:
- Data management, since I audit this every year, I have to update the process once a year.
- Document for the nurture programs that we have since some of the stream logic and contents are updated at the end of the year. For renewals it's September.
- Process for Archiving emails, forms and landing pages, and creating redirects. Archive of Old images and white papers. Hide unused tokens.
- A detailed how-to of the monthly subscription fulfillment emails maintained by our Marketing Associate.
- A detailed how-to of the daily news alerts that's maintained by our 2 editors.
- To complete: The process for auditing the behavior scoring and the lifecycle campaigns at the end of the year.
Great to hear a thumbs up for google sheets! Processes can be a hard thing to convey across the span of time and tenure. Moving agency side recently I've found myself relying on google sheets more and more for their ease of sharing and accessibility for my clients, but I'm missing the structure and organisation of having a single space on Confluence!
We find it very useful to document the implementation details and process. This serves as a master file to keep a detailed, consistent model. We create an Excel Workbook detailing the following information:
Hey Nick - that's a great list to see. I've seen a few clients go through significant staffing changes where none of these things are documented, and finding out what was done in the initial set up becomes really difficult. Do you keep the document regularly updated if you make changes to processes/settings?
Yes, we keep the master file updated. This helps with change management on both the client and internal team side. It's a great resource to show progress, specifically when implementing a new instance. It also provides an organized approach to keeping the instance structured and sustainable.
Just like you I started of on the client side, but for the last couple of years I've been active on the agency side. Marketing and technology are so intertwined with each other and as a marketer we use so many different tools, that documenting the actions we take became extremely important. I know, it is not sexy and as marketers we are not trained to document. Something we can learn a thing or two from IT ;-).
Anyway my quick thoughts on your questions concerning documenting your Marketo instance (or actually any Marketing Automation platform).
Thanks for your detailed reply, Jonas Verhaeghe ! Sounds like your preferences and challenges are pretty well aligned with mine. These will be helpful points to keep in mind