Four strategies to improve product adoption

Tips from Preflight members on how to handle it when your customer's team is slow to adopt your product
June 29, 2021
Blog illustrator
Sivaprakash

The main goal of software companies is to build great products that create successful outcomes and value for their customers. Success occurs when customers experience that “aha” moment that transforms your product from a trial or POC to a core part of their day-to-day work.

But not all users experience these “aha” moments quickly. Sometimes your customers’ employees might resist this change which makes product adoption a change management challenge.

So how would you move your customer from POC to a daily user?

In our weekly topic teardowns, we asked Preflighters what change management measures they will take to convince their customer’s mid-level and low-level members to adopt your product during implementation. Preflighters shared the most sustainable product adoption strategies, and interestingly, they all had one thing in common - understanding your users.

TL;DR

  1. Empathize with your user
  2. Understand the “why” 
  3. Educate customers on benefits
  4. Find your product advocate

1. Focus on users

Gaurav Pansari, Customer Onboarding at Pando Corp

To improve product adoption, you can focus on:

  1. Retraining
  2. Mapping user benefits with product hook
  3. Top-down reviews through platform
  4. Team-KPI alignment
  5. Celebrating small wins
  6. Better/clear communication with team

You can also approach this tactically by:

  1. Doing a small-scale POC and from the results, building into a larger POC
  2. Empathizing with the user by observing them daily and bridging the small gaps in their experience which are most often the easiest fix to this problem.
  3. Sharing best practices from other successful clients 

2. Understand the “Why”

Sudheer Goda, Director of Professional Services at Gainsight

Firstly, CSMs need to check why the customer’s employees are not adopting the product during implementation. For instance, you need to gauge whether the product seems difficult for them to use or if they are comfortable with the current processes.

Once you get the accurate picture, you can strategize on the next steps. First, defining your customer base into three categories - high-touch, low-touch, and tech-touch, and understanding which category this customer falls under is crucial. From there, you can move with playbook strategies for product adoption.

3. Educate customers on benefits

Michael Rokos, Director of Customer Success at Stradigi.ai

Start from the ground up; you need to dig into the dissatisfaction with the status quo. Collect the pain points directly from the non-adopting users either through group or 1-1 conversations. They may be the same or different from those that led to the ultimate purchase decisions. Then, follow up with them by leveraging existing resources on how certain product features or attributes solve their problems. Share relevant content based on their feedback, and use this outreach with other users who haven't provided any feedback. Keep a record of this misalignment and bring it up in an upcoming strategic review with the customer because it is valuable information.

4. Find your product advocate

Srikrishnan G, Co-founder of Rocketlane

Firstly, it is crucial to find out why they are resisting the change. A few possible scenarios:

  1. They believe the change creates more work for them and focuses only on the benefits for the management.
  2. They believe the change will lead to more monitoring and measurement of their work.
  3. They are asked to continue their current process and also work on the new platform.
  4. They aren’t convinced with the “why”. 

Now, here are some measures you can take:

  1. Communicate the value of the product/platform to the mid and low-level team members. Explain why they should care, what the product does for them and their business, what they are learning, and how they can grow using it.
  1. Find a few of their team members who have a “growth mindset” and can influence to understand how to position the product to the rest of the team. Get them to share why the new platform is the way ahead, and let them lead adoption by example—by sharing what they love about your product with the team.
  1. Create some excitement around your product adoption. For instance, reward the best early adopters.
  1. Make the product adoption an OKR goal for some of the mid and low-level team members if possible (this Implementation Stories session with Pando dives deep into this subject).
  1. Take a look at your training material. It should talk about their problems and how your product will aid them in doing their job better and shouldn’t be an explanation or a walk-through of your product features.
  1. Having other company testimonials about how they got value from your product or how their customers benefited by adopting the solution can be a decisive, influential factor over non-adopting users.

Adoption is the ultimate test for your product. Regardless of the strategies you use, it’s important to prioritize your product adoption as one of the foundations of your business.

If you have any additional strategies you want to share, we’d love for you to join Preflight Community and share it with all our community members!

More resources

  1. Four customer onboarding strategies for happy end users 
  2. How pre- and post-sales interactions impact your business
  3. How to leverage customer onboarding to reduce churn
Subcribe to Our
Newsletter

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.

$99

per team member/month billed annually

*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.

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

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.