RevOps Unboxed

There are a handful of genuinely actionable tips - reframing 'why' questions, keeping a running Excel tracker of CRM observations, and the org chart/data/sales-process triage order - but they are widely spaced across 43 minutes dominated by casual banter, a long Zoom-vs-Teams tangent, and a hosting-handover announcement that consumes the final segment. The ratio of novel ideas to filler is low.

“when you get admin access to the CRM, do not go in and change anything. Like just sit and just wait”

“I'm keeping an Excel tracker. So every single thing that I'm finding, I'm making a note like, found this, see this, recognize this, notice this”

The reframe of 'why' into 'what/how' questions is the only mildly contrarian point; everything else - build relationships first, find quick wins, don't boil the ocean, always be learning - is standard career-advice canon. The episode leans on 'The First 90 Days' book by name and offers no counterintuitive or first-principles arguments.

“I learned very quickly not to always ask why, because some people get offended because they think you're questioning them”

“I'm doing ChatGPT data dumps out of my brain every day after these meetings”

Tana Jackson holds a legitimate Head of RevOps seat at a large global company (Motorola Solutions) and has real cross-functional practitioner history, which is credible. However, she is four weeks into the role being discussed, so she can only speak to observations rather than demonstrated outcomes, and the depth of strategic insight surfaced in the conversation undersells what her seniority might have yielded with sharper questioning.

“going into week four of my new role over at Motorola”

“I started in healthcare, so I was a nurse. Decided I did not want to be responsible for people's lives. But I really leaned into management”

There are occasional concrete details - MEDPIC methodology, EOS 'rocks,' a Zoho instance with 12 stages and deals sitting 400+ days in nurture - but no revenue figures, no before/after metrics, and no timelines with quantified outcomes. The Motorola data problems are described qualitatively ('multiple systems, M&A, none of it matches') without any numbers to anchor the scale.

“it is a lot of multiple systems, merger and acquisition, multiple products, um, broken in between different systems, different reporting tools, excels. None of it matches”

“The stages don't match the Med Pick. The probability and forecast categories are not being used in the CRM correctly”

The host asks mostly open-ended softballs and spends several minutes narrating her own Zoom-vs-Teams story rather than probing the guest; there is no pushback or challenge to any claim. The most interesting conversational moment occurs when the guest reverses a question back to the host, which is structurally unusual but underscores that the interview lacks direction. The episode effectively functions as a vehicle for a hosting-handover announcement.

“how did you get started in this kind of cool world of revops?”

“is there anything, uh, you'd like to, you know, words of wisdom, tana isms, things that you like to just operate by”