Adoption starts when reps stop feeling alone. Why do reps resist the very tools and coaching that could help them win? On the latest SellMeThisPen Podcast, I had a great conversation with Venkat Nagaswamy, CRO at Splashtop about a challenge every leader runs into: how to drive adoption without force or bribery. "We need to create a space where coaching isn’t evaluative—it’s helpful." Venkat was working with a telco rolling out a new training program. The team? Resistant. The stakes? Their paychecks. The breakthrough? One-on-one conversations, sitting beside them on live calls, and making it safe to try. No dashboards. No mandates. Just trust. That same mindset now shapes how he leads sales enablement at scale—especially with AI. Here’s his 3-part playbook for adoption that sticks: 1️⃣ Start with coaching, not control. Don’t lead with features or deadlines. Show them how it makes their job easier—like saving 30 minutes on prep, or booking cleaner meetings. 2️⃣ Build a safe place to screw up. Reps aren’t lazy—they’re avoiding public failure. Adoption begins when they know you’ll catch them if it goes sideways. 3️⃣ Let the dominoes fall. Start with your curious, hungry reps. Help them succeed. Let them convince the rest. That social proof hits harder than any mandate. In the full episode we cover: ✅ How Venkat builds enablement models that actually move revenue ✅ Why “failure avoidance” beats ambition in shaping behavior ✅ His transition from IC to CRO—and what he misses most What’s your take on getting reps to adopt without force? P.S. Link to the full episode in the comments! — Names mentioned in the episode: – Graeme Pitches – referenced for sharing the “domino effect” adoption strategy with Michael – Lawrence Wayne O'Connor – upcoming guest & enablement leader 🎙 Venkat’s question for Lawrence: How should AI reshape modern sales enablement beyond static PDFs and playbooks? We’ll share his answer in the next episode. Stay tuned.

Building trust and creating a safe space for reps to learn can make a big difference Michael.

See more comments

To view or add a comment, sign in

Explore content categories