In her Propel23 session, Alisha Hardoon, Senior Manager, Customer Success & Onboarding at Robin, shared her experience with implementing a data-driven approach to onboarding.
In this session, Alisha talked about:
Here are key takeaways from the session.
Wherever possible when it comes to data driving your process, favor answers that are based on metrics like CSAT or TTO (Time to Onboarding) so you can track changes over time and see trends.
If you're just getting started, the best way is to define the questions for which you need answers and start from there.
The CS team at Robin identified three priority questions on which they based their data-driven approach. These questions were focused on using data to understand
The team conducted multiple in-depth discussions and feedback sessions with the team.
The team used Figjam to do this since it made it easy to work with in-office and remote employees.
The discussion focused on breaking down the onboarding milestones and discussing what needed to continue and what needed to change. At the end of the exercise, the team used the trends identified to prioritize the pain points they needed to solve.
The final result was an internal summary and project plan with designated owners, status, and timelines that detailed how the team was going to address the priority points.
To understand how the customer felt about the onboarding experience, the team sent out a survey (using Google Forms) at the Onboarding Review milestone.
The feedback form included scope for both quantitative and qualitative responses so that users could give their ratings and add any additional context. In addition, this survey exercise also sought/identified product advocates for further marketing about advocacy opportunities.
The survey findings gave the team raw data that they translated into internal documentation to
The team tracked the time taken from the partnership kickoff call to the onboarding review meeting to capture the TTO (Time to Onboard) metric.
They found that their actual TTO was several months beyond what they expected (and communicated to customers).
The team’s original onboarding journey was designed to onboard customers quickly. But the data showed that they had ended up doing too much too soon at the start, and overwhelming customers. Additionally, users ended up bypassing the optional training at the later stage of the journey, which caused downstream usage issues. Lastly, the team realized they’d overlooked a formal celebration of the success of the project.
With the insights from their data, the team made the following changes to their onboarding process:
The team put together a best practices guide for Onboarding Managers that detailed the activities, tasks, and behaviors expected from the onboarding team.
These best practices had an explicit focus on enabling and empowering the team to identify and flag risks.
The Robin team also used the insights and findings to develop playbooks and best practices to deal with stalled accounts.