The RevOps Show

Marketing attribution has Doug feeling a little salty today. He and Jess dig into whether or not marketing attribution is a waste of time.

Questions/Topics Addressed: 

• What is marketing attribution? 
• Where does attribution marketing work? 
• Attribution Models
• How do you measure marketing attribution?

If you like the show, please subscribe and share the episode. For updates on new episodes follow us on:
Twitter/X: @dougdavidoff, @JessDCardenas & @demandcreator
LinkedIn: Lift Enablement, Doug Davidoff
You can also watch the video version of the show on our page. 
Thanks for listening and remember to just say no to shitty RevOps!

Sales and sales strategy is where Doug comes from. It will always hold a special place in his heart. It's also "the last mile" for organizations. Doug sees, too often, companies that are getting 80-90% of it right only to falter when it comes to implementing their sales approach and methodology.

If you want to scale growth, you must master a methodology, and in this episode we're resharing, Doug does one of his favorite things - dispels popular myths to provide a no-BS perspective on what works.

If you like the show, please subscribe and share the episode. For updates on new episodes follow us on:
Twitter/X: @dougdavidoff, @JessDCardenas & @demandcreator
LinkedIn: Lift Enablement, Doug Davidoff
You can also watch the video version of the show on our page. 
Thanks for listening and remember you can't solve your upstream problems, downstream.

The four most dangerous and damaging words in any tech implementation: "All we need is." People want outcomes that come from low effort, cost, and things associated with a simple CRM build. If it were that easy, everyone would be doing it.

Jess picked this episode because "we cover some key things everyone should have in mind when implementing a CRM and what the real cost is. Doug and I also dig into how the status quo can impact the implementation." This episode is part of a series we put on. We'd highly recommend listening to the rest of the series.

If you like the show, please subscribe and share the episode. For updates on new episodes follow us on:
Twitter/X: @dougdavidoff, @JessDCardenas & @demandcreator
LinkedIn: Lift Enablement, Doug Davidoff
You can also watch the video version of the show on our page. 
Thanks for listening and remember you can't solve your upstream problems, downstream.

Technology is not a solution. A solution is built around the jobs that need to be done, which at Lift, grows out of our prime directive: the business process should always drive the technology; the technology should never dictate the business process. This directive guides us in everything we do, especially in our view of solutions.

A strong solutions architect can be your competitive advantage, but as the role of RevOps has grown, the focus on "solution" and "architects" has multiplied in a confusing way. This episode guides listeners about the most important considerations (when something), which is why Doug chose to reshare this episode in this week of our Best of series.

If you like the show, please subscribe and share the episode. For updates on new episodes follow us on:
Twitter/X: @dougdavidoff, @JessDCardenas & @demandcreator
LinkedIn: Lift Enablement, Doug Davidoff
You can also watch the video version of the show on our page. 
Thanks for watching and remember you can't solve your upstream problems, downstream.

The phrases "Let's keep it simple" or "all we need is" are things we hear quite often when implementing CRMs, but simple isn't enough. Your CRM also has to serve your needs; otherwise, people won't see the point in using the new system. To get there you must ask yourself, "What's the problem we're solving for?" The goal with this question should not be simple, it should be complete. Jess chose this episode for our Best of RevOps Show series because her and Doug dive into how you define what complete is, what the real problems are with your CRM, and how your problems impact your CRM configuration.

If you like the show, please subscribe and share the episode. For updates on new episodes follow us on:
Twitter/X: @dougdavidoff, @JessDCardenas & @demandcreator
LinkedIn: Lift Enablement, Doug Davidoff
You can also watch the video version of the show on our page. 
Thanks for watching and remember you can't solve your upstream problems, downstream.

System design can either make you a winner or let you fall to the game of your competition. The choice is yours. We're continuing our RevOps Show "Best of" series with a pick from Doug on system design because RevOps is only as good as the design of its operating system. Put another way - your system is perfectly designed to get the results you're currently getting, so if you want to change your results, you need to change your system. But the problem is that you can't judge/assess your system from within it. This episode digs into what the critical discipline of system design means.

Questions discussed in this episode: 

•  What is system design? 
• Why is system design important? 
•  Why do we always go back to system design? 
•  Where do you start with system design? 
•  What are some of the biggest challenges that you run into? Where are places where people get stuck? 

If you like the show, please subscribe and share the episode. For updates on new episodes follow us on:
Twitter/X: @dougdavidoff, @JessDCardenas & @demandcreator
LinkedIn: Lift Enablement, Doug Davidoff
You can also watch the video version of the show on our page. 
Thanks for watching and remember you can't solve your upstream problems, downstream.

So many are striving for the "perfect database, but what does "perfect" actually mean? A database shouldn't be judged by its perfection - it should be judged by its impact on your velocity, by throughput optimization, and by successfully achieving your revenue objectives. Getting to that database is half the battle, which is why we're resharing this episode. Over the next six weeks, we'll be sharing the Best of RevOps Show. Doug and Jess have selected their favorite episodes and can't wait to share them with you. 

From Jess: The pursuit or the perfect database is something that I really believed in for a long time. As I have worked in a myriad of databases over the better part of a decade, I have realized that the "perfect" database is a myth. I chose this episode because Doug really challenged me on this idea in this episode and we had an interesting discussion that might just change the way you look at your database, what to focus on and what a "perfect" or clean database really means.

Questions/Topics Discussed: 

•  What’s the perfect database?  
•  Why do you think focusing on the perfect database is a problem? 
•  What’s the key to having a priority? 
•  How do you know what the problems are? Where should you start in the journey if you want to be successful? 

If you like the show, please subscribe and share the episode. For updates on new episodes follow us on:
Twitter/X: @dougdavidoff, @JessDCardenas & @demandcreator
LinkedIn: Lift Enablement, Doug Davidoff
You can also watch the video version of the show on our page. 
Thanks for watching and remember you can't solve your upstream problems, downstream.

Source of truth vs system of record
Disclaimer: If you are a data scientist, please skip this episode because it'll be painful for you.

Questions/Topics discussed in this episode: 

• What is a source of truth?
• What is truth?
• What is sales and marketing alignment?
• What drives productivity when it comes to data? 
• The danger of source of truth

If you like the show, please subscribe and share the episode. For updates on new episodes follow us on:
Twitter/X: @dougdavidoff, @JessDCardenas & @demandcreator
LinkedIn: Lift Enablement, Doug Davidoff
You can also watch the video version of the show on our page. 
Thanks for watching and remember you can't solve your upstream problems, downstream.

The focus of this episode is on the three core sales pipelines of any business. To be clear, this episode is more about why there are three pipelines. Doug will be covering the structural problem from a go-to-market standpoint in terms of managing the functions.

Questions addressed in this episode: 

•  What’s the problem we’re trying to solve with pipelines?  
•  Why multiple pipelines?  
•  What are the three pipelines?  
•  What are the things you should think about as you put pipelines together?  
•  Why do you want to reduce the dependence on salespeople?  

If you like the show, please subscribe and share it with your friends and/or coworkers. Follow us on Twitter: @dougdavidoff, @JessDCardenas & @demandcreator to receive updates on when new episodes publish or to get other great insights. You can also watch the video version of the show on our page. Thanks for watching and remember you can't solve your upstream problems, downstream.

In this episode Doug and Jess talk through the RevOps role and growth strategy. What they get into in this episode is the core of what it means for RevOps to be strategic. 

Doug’s Thesis: Whether companies are referring to what they’re doing as RevOps or not. 

Tactical RevOps has taken hold and it’s enabled companies to get better at what they’re doing. As a result, they’re getting weaker. Those companies that are at the leading edge of this phenomenon are the ones that are taking it on the chin the hardest. The proof: the environment that they’re finding themselves in today.

Questions/Topics addressed in this episode:

• What is strategy?
• Where do we play? Where do we win?
• Once you have a policy and strategy outlined/your hypothesis outlined, what are the things you need to consider?
• Intent dynamics
• What are the other dangers as you build out a strategy? 
• What do you need to get strategy right? 

If you like the show, please subscribe and share it with your friends and/or coworkers. Follow us on Twitter: @dougdavidoff, @JessDCardenas & @demandcreator to receive updates on when new episodes publish or to get other great insights. You can also watch the video version of the show on our page. Thanks for watching and remember you can't solve your upstream problems, downstream.