A HUGE thank you to our newsletter sponsors for moving this newsletter to free for our readers. PAID subscribers will continue to receive access to the templates from this newsletter. If you're reading this but haven't subscribed, join our community of over 1,338 crazy smart Revenue leaders. If you’d like to sponsor the newsletter reply to this email to learn more.
Creating equitable territories is hard. Use BoogieBoard’s AI design copilot to generate them in seconds. Build trust with sales and customer success teams. Reclaim your time. Champion equity. Schedule your free AI-driven equity analysis with BoogieBoard today.
How much time do you spend finding answers to critical revenue questions? Want insights in seconds instead? SetSail’s GPT integration lets you ask questions like:
I think RevOps roadmaps work best as an extension of the RevOps backlog, as opposed to one of the items of the backlog itself! Some people think that a roadmap is just a fancy way of organizing the backlog, but I've found that it's helpful to keep them separate for two reasons. A checklist and a roadmap are two entirely different things altogether.
RevOps Impact Newsletter is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.
What's the difference between a checklist and a roadmap?
A checklist is a list of tasks or items that need to be completed, while a roadmap is a plan that outlines the steps that need to be taken to achieve a goal. A checklist is typically used to track progress on a specific task or project. It can be used to ensure that all of the necessary steps are completed, and that nothing is forgotten. Checklists can be simple or complex, depending on the task or project at hand.
A roadmap, on the other hand, is a more strategic document. It outlines the long-term goals of an organization or project, and the steps that need to be taken to achieve those goals. Roadmaps can be used to communicate the vision of an organization to its stakeholders, and to help ensure that everyone is working towards the same goals.
Here is a table that summarizes the key differences between checklists and roadmaps:
How large should the backlog be?
An actionable backlog should only include work for the next 3-4 sprints. This helps to keep it from getting too cluttered and makes it easier to focus on the most important tasks. Compare this to a roadmap covering 6-12 months, which is a much longer time frame.
Sample roadmap: powerslides.com; TBC - to be considered; BAU - business as usual. Big fan of this format
Second, it's important to get input from a broad range of stakeholders when developing a RevOps roadmap. This helps to create a shared understanding of the roadmap and ensures that everyone is on the same page. But attending sprint reviews can be challenging for stakeholders. The level of detail can be overwhelming, and it can be time-consuming.
Roadmaps start with first principles
So, a good compromise is to create a roadmap that is continuously inspected and adapted. This could happen every 6-12 weeks, depending on the RevOps team, the organization, and the target market. In my experience, this approach works well if you keep the following first principles in mind:
Have a vision. If you don't know where you're going, any roadmap will get you there. So, before you start planning, take some time to think about your vision for RevOps. What do you want to achieve? What problems do you want to solve?
Focus on themes, not features. A roadmap is a high-level plan, so don't get bogged down in the details. Instead, focus on the big picture and identify the themes that will help you achieve your vision.
Don't confuse a roadmap with a release plan. A roadmap is a strategic document, while a release plan is a more tactical document that outlines the specific steps you need to take to implement your roadmap.
Don't put dates on your roadmap. Dates are a moving target, so it's better to focus on the themes and priorities. If you absolutely need to put dates on your roadmap, make sure they are as broad as possible.
Review your roadmap regularly. The world is constantly changing, so it's important to review your roadmap on a regular basis to make sure it's still aligned with your vision.
Don't get hung up on the tool. You don't need a fancy tool to create a roadmap. A whiteboard and some index cards will do just fine. The most important thing is to create a roadmap that is clear, concise, and easy to understand.
What's a tactful way to balance competing priorities between multiple executive stakeholders?
It’s all well and good to have first principles for the roadmap but it’s another thing to balance the needs of several influential executive leaders who may or may not see eye to eye. So here’s where RevOps careers are made or broken in my opinion.
Understand the priorities of each stakeholder
The first step is to understand the priorities of each stakeholder.
What are their goals?
What are their concerns?
Once you understand their priorities, you can start to think about how to balance them.
Identify the common ground
Once you understand the priorities of each stakeholder, look for areas where there is common ground. What are the things that are important to all of the stakeholders? Once you identify the common ground, you can start to build a solution that addresses the needs of all stakeholders.
Be transparent and communicative
Be transparent and communicative with all stakeholders throughout the process. Keep them updated on your progress and let them know when you have made decisions. This will help to build trust and avoid surprises.
Be willing to compromise
In some cases, it may be necessary to compromise in order to balance the competing priorities. Be willing to give a little on one priority in order to get a little on another priority. Who says RevOps can’t be peacemakers and dealmakers?
Be prepared to walk away
If you are unable to find a solution that balances the competing priorities, be prepared to walk away. This may not be ideal, but it may be the best option for all involved.
Use data to support your decisions
When making decisions about how to balance competing priorities, use data to support your decisions. This will help to ensure that your decisions are based on facts and not on emotion.
Get buy-in from all stakeholders
Once you have made a decision, get buy-in from all stakeholders. This will help to ensure that everyone is on board and that there are no surprises down the road.
Be flexible and adaptable
Things change, so be prepared to be flexible and adaptable. If a situation changes, be willing to adjust your plans accordingly. Likely, the strategy and goals remain unchanged but the situation may call for a rapid change in tactics. If the change is around overall strategy I highly suggest slowing down and calling a War Council together.
Authentic conversations with paid subs
I will be hosting a monthly town hall with paid subscribers. I’m not exactly sure if I can thread the needle in terms of time zones that will work for everybody so I apologize in advance!
Loading...
Whenever you're ready, there are 2 ways I can help you:
1/ If you’re looking to further develop your Revenue Operations knowledge sign up for my courses in partnership with the RevOps Co-Op.
→ Unleashing ROI course. A ten-week virtual, live instruction RevOps course designed to level up your RevOps Impact (R.O.I.). Lessons from my career scaling from $10M to $100M+. Join 50+ alumni. https://www.revopscoop.com/learn/unleashing-roi-course
→ Sales Ops Masterclass. A six-week virtual, live instruction SalesOps course designed to take your sales operations skills to the next level. https://www.revopscoop.com/learn/salesops-masterclass
2/ Promote your Revenue focused startup to a newsletter with over 900 tenacious revenue leaders. My eventual goal is to shift this to a completely free newsletter for my readers through sponsored ads. Reply to this email if you’re interested in receiving a media kit to learn more.
