Same Old Song and Dance

One of the core functions of RevOps is to streamline processes and drive efficiency across all groups in the Revenue organization.  For early-stage companies, this means establishing a baseline of operations and more importantly, getting the steps on paper.  As unsexy as the idea of documenting processes is, you can’t wait a lifetime to do it.

If documenting processes seems like a foreign concept, you’re not alone: many revenue leaders of early-stage companies believe that processes are for big companies.  Putting processes in place now will slow things down, making the company less flexible.  It’s a common enough myth that it often prevents leaders from documenting even basic processes. 

Ironically, the truth is the opposite: not putting processes into place causes more problems than doing so.  For example, having recurring issues with key areas, like communicating across departments.  Until you establish a baseline process, you’ll repeat the same mistakes or reinvent the steps each time you do it.  For core processes—those activities across the business that must be done consistently for the business to succeed—having to come up with new ways daily, weekly, or monthly will exhaust your team.  It might also lead to preventable and potentially disastrous results with morale and customers.

A Change Would Do You Good

If it feels like the first time you’re doing it, here are some ways to approach documenting processes:

• Create a template: include the basics that will be a part of every process, regardless of how complicated it is or which department owns it.  General go-tos are Who, What, When, and How (the steps).  Include an example or two.  Share the template in an accessible place, and make sure everyone knows that it’s there and the expectations around using it.
• Create a repeatable process: yes, even processes need a basic process for doing correctly.  Outside of the basic template, offer a structure for making sure that the How section is simple to create.  This is especially important for those who are new to documenting processes.
• Document the first process: your first process should always be how to document processes.  This sets the tone for what right looks like and makes the exercise scalable across your teams.  RevOps can open up the door for Revenue and then assist others as needed. 
• Provide training and support: offer some initial training and support from your RevOps team to other departments.  While outside the scope of Revenue’s need to document its own processes, it’ll help create consistency across the company, including the processes that overlap with Revenue’s.  It’s also good for inter-departmental relations, meaning that it could help your company work together like it never did before if done right.
• Tip: The best process structures have a validation framework that verifies the process is complete.  Typically, these frameworks follow a “Do, Document, Communicate” loop format.  See if you can come up with one to validate your processes as you build them.