1. Understand. Before you dive in, gather the team and get to know the Customer Satisfaction Score. If needed, request an introduction from Product Analytics Hub.

2. Get commitment from Product Management and other stakeholders and run a CSAT introduction session.

3. Settle on set-up. Work with the Product Owner(s) to decide which processes to measure (survey points) as well as survey rules, such as survey questions, triggers and response rate. This can be done by running a 2h workshop for the Product Owner(s). Start with core processes (easy/important) for key user groups, and be mindful about not interrupting any userflows or tasks.

4. Test it! Before the launch you want to make sure everything works like intended. Catch mistakes by testing it with colleagues. Then, test everything in production, e.g. find out if you get answers correctly or if there are technical issues, as well as if you get enough responses. Make changes and iterate on findings.

5. Launch. Big moment! Decide on a launch date. Provide internal stakeholders with information about what CSAT is and why you are using it, as well as what the survey rules are. Share the survey data and how to best utilise it. If tests are successful, launch and remember to celebrate!

6. Design the follow-up process. Depending on what current channels and stakeholder groups exist around your product, the internal communication around the results will vary. Possible channels for communication may include Slack channels, stakeholder meetings and all-hands meetings.

7. Follow up and plan actions. Measuring and collecting data is only meaningful if it is followed up and leveraged. Keep the Product Owner(s) up to date and make sure everyone in the product team has access to the data. Showcase the results to Product Owner(s), stakeholders, product teams and the steering group, educating everyone on how you can leverage the results to inform priorities and make smarter product decisions together. Wait 2-4 weeks for results to be concrete. Make sure ownership is shared with the Product Owner(s). Decide together what you should investigate further.

8. Communicate the results. Make sure to communicate results from the previous month and the development over time (e.g. trend of the last twelve months), key feedback topics and planned actions based on the feedback to stakeholders.

9. Visualise and user test concepts. Once you have a better understanding of what you need to investigate further, conduct UX research and visualise concepts and test them with users. This way you will have an indication of if you are going in the right direction and if your solution might have a positive effect on the CSAT score.

‍

• Start with the most important processes and user groups
• Make sure to measure processes, not features
• Aim to measure at least three processes from the start, so that you can compare how the different processes are performing
• Metrics differ in terms of the insights they provide and the areas of customer satisfaction they focus on. CSAT captures satisfaction with specific interactions, pNPS evaluates loyalty and advocacy, and CES assesses the ease of the customer experience.

• Customer Satisfaction Score (CSAT) in Visma (Space page) – Product Analytics Hub
• What is Customer Satisfaction? (article) - InMoment
• CSAT vs NPS vs CES (article) - InMoment
• 7 steps to benchmark your product’s UX (article) - Nielsen Norman Group