The influence playbook: Smart conversations that drive system adoption

Published in June
06 June 2025
Published in June

06 June 2025

Summarize blog with

System implementations are about reshaping behavior, bridging silos, and shifting mindsets.

In her Propel25 session, "The influence playbook: Driving system adoption through smart conversations," Jenn Brantmier, Principal Consultant at CLV Consultants, shared a refreshingly candid take on the art and science of internal adoption. 

Drawing from her hands-on experience in professional services and operations across hospitality, healthcare, and real estate, Jenn unpacked how influence, not authority, drives meaningful adoption.

This recap draws on the strategies discussed to present a broader thought-leadership perspective on how implementation and professional services leaders can embed change more effectively.

In this article

  • Common objections to change: Understanding the hidden barriers
  • Change conversations: The power of repetition, empathy, and presence
  • Understanding objections: Emotional costs > Technical barriers
  • A blueprint for change: Lessons from implementation leaders
  • Continuous iteration: What comes after go-live
  • Key takeaways for implementation leaders

Common objections to change: Understanding the hidden barriers

In any implementation initiative, recurring objections emerge time and again. Recognizing them is the first step toward overcoming them:

Change is hard

Emotional resistance is real. People aren’t just reluctant. They're protective of what they know. Leaders must treat resistance as a source of insight instead of viewing it as an annoyance.

Adoption is hard

Tools may be intuitive, but change is not. Success hinges on scaffolding adoption with training, reinforcement, and cross-functional clarity.

Change is expensive

It’s not just budget lines; it’s also time, morale, and perceived risk. Highlighting the long-term ROI and opportunity cost of stagnation is essential.

Integrations are hard

Complexity may stem from differing processes, data formats, and ownership. Bridging teams becomes as crucial as APIs.

Conflicting interests

When KPIs clash, alignment dies. Bringing departments into the design process helps surface and negotiate these trade-offs early.

Collaboration isn’t valued

If the culture doesn't reward cross-functional wins, adoption suffers. Leaders must reinforce shared success stories.

These objections aren’t blockers; they’re diagnostic signals. The role of an implementation leader is to decode and address them with empathy and precision.

Change conversations: The power of repetition, empathy, and presence

Effective system adoption is less about one-time alignment and more about consistent influence. Four conversation tactics stand out:

Talk a lot

Visibility is everything. Implementation leaders must normalize open dialogue around objections and progress across all channels.

Be a broken record

Repetition creates familiarity. Reinforce key benefits and workflows frequently so they embed into daily habits.

Find your friends

Champions within teams multiply your influence. Identify them early, equip them with context, and celebrate their wins.

Unfamiliar to familiar

Analogies and anchors help reduce cognitive friction. Frame new features in terms of familiar tasks or legacy tools.

Above all, listen. Not passively, but actively and inquisitively. The small frustrations people voice often point to deeper misalignments or missed opportunities.

Conversations are the currency of change. The more intentional and widespread they are, the smoother the path to adoption.

Understanding objections: Emotional costs > Technical barriers

Objections to new systems usually wear rational disguises but stem from emotional realities:

Sunk cost

People feel personally invested in legacy processes. Change feels like invalidation. Leaders must honor past work while advocating for evolution.

Comfort

Familiarity breeds speed and confidence. Replacing it without sufficient support triggers defensiveness and delays.

Disruption

Even rare outages or reconfigurations can create fear. Transparent communication and contingency planning help build resilience.

Time

Everyone’s overloaded. Asking for time without clarifying the purpose and benefit breeds resentment.

Ego

Systems reset power dynamics. Going from expert to novice hurts pride. Training that builds confidence, not just competence, is critical.

Tactical takeaway

Map objections back to emotions. When implementation leaders validate feelings while removing friction, they earn trust and accelerate adoption.

A blueprint for change: Lessons from implementation leaders

Smart system adoption begins long before the first login. A proven playbook includes:

  • Start by listening: Early immersion in team dynamics and processes builds empathy and credibility.
  • Plant strategic seeds: Use micro-moments to propose helpful shifts from documentation to processes to role clarity.
  • Engage external voices: Customer insights and expectations can reframe internal resistance and elevate urgency.
  • Reframe language: Swap rigid answers for expansive ones. "Yes, and…" opens doors. "No, but…" shuts them.
  • Quantify value: Metrics speak louder than assumptions. Usage data, reduced workload, and improved visibility make the ROI case tangible.
  • Empower your teams: The most effective system rollouts happen when the people using the tool every day are given the agency to shape and evolve it. Distributed ownership unlocks creativity and sustainability.

Continuous iteration: What comes after go-live

Implementation success doesn’t stop at launch. Sustained value requires iteration:

Plan for v2 from day one

Setting expectations for continuous improvement builds patience and reduces pressure.

Track outcomes, not just activities

Adoption metrics, time saved, and customer satisfaction scores tell a compelling story.

Find off-label opportunities

A well-implemented system often solves more problems than expected. Be open to those use cases.

Rocketlane, when fully embedded, becomes more than a PSA platform. It evolves into an operational command center from CRM and billing to project planning and customer engagement.

Key takeaways for implementation leaders

Adoption isn’t a process problem. It’s a people problem. 

Understand the human side of objections. Technical solutions only work when emotional barriers are addressed.

Talk more, not less. 

Be the broken record. Relationships and repetition build trust and normalize change.

Start with influence, not authority. 

Win over allies and skeptics through empathy and strategic listening. Mandates rarely stick.

Use metrics to make your case. 

Data changes the conversation from opinion to evidence. Make insights visible.

Plan for v2. 

System adoption is a journey, not a single milestone. Iteration invites ongoing engagement.

Smart, empathetic conversations are the real drivers of system adoption. Want more insights like this? Check out the Propel25 sessions here.

FAQs

What I appreciated most about Rocketlane is its seamless approach to onboarding and project management. The ability to collaborate in real-time, set clear timelines, and track progress across multiple teams makes it incredibly efficient. The built-in document-sharing and communication tools reduce the need to switch between platforms. It’s especially useful for client-facing projects, where transparency and accountability are key

Sebastian
Intercom

AI that executes your delivery work (Add to any plan)

Most popular

Standard

Ideal for expanding organizations needing more in-depth capabilities and integration for scaling.

$49

per team member/
month billed annually

*minimum of 5 team members

  • Full partner ecosystem support
  • Dynamic templates for any project
  • Milestone CSAT for customer pulse
  • Docs, forms, projects in one place
  • Docs, forms, projects in one place
  • Approval-governed time tracking
  • 200 Automations/user/month
  • Native HubSpot, Jira, Slack Integration

Most popular

Premium

Great for teams desiring tailored workflows with comprehensive reporting capabilities.

$69

per team member/month billed annually

*minimum of 5 team members

  • Real-time project profitability
  • AI resourcing and capacity planning
  • All revenue recognition models
  • Centralized rate cards and budgets
  • Portfolio reporting for leaders
  • Bill faster & improve cash flow
  • Native Salesforce integration

Most popular

Enterprise

Tailored for large enterprises requiring a fully customizable, comprehensive delivery engine.

Custom Pricing

*minimum of 5 team members

  • SAML SSO and role-based access
  • Unlimited, hands-off automations
  • Soft-allocate pipeline deals early
  • Skills matrix for smarter staffing
  • Staff global teams ahead of demand
  • Multi-currency global delivery
  • Snowflake data + custom reports

Full reviews for all 11 tools below

<TL;DR>

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.

<TL;DR>

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.

Trusted by top companies

One platform does what the entire table above tries
to split across tools.

One platform does what the entire table above tries
to split across tools.

One platform does what the entire table above tries
to split across tools.

Myth

Enterprise implementations fail because customers don’t follow the process or provide clean data on time. Most delays are purely “customer-side” issues.

Fact

Implementations fail because complex environments need real-time technical problem-solving. FDEs unblock workflows, integrations, and unknown constraints that traditional onboarding teams can’t resolve on their own.

Get a better all-in-one PSA

Get a better all-in-one PSA

Did you Know?

Companies that embed engineers directly with customers see significantly higher enterprise retention compared to traditional post-sales models — because embedded engineers uncover “unknowns” that never surface in ticket queues.

Sebastian mathew

VP Sales, Intercom

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.