Skip to content

CS Product Testing

Customer Success Product Testing

The customer success team plays a vital role in the deployment and adoption of the DoubleGDP application across partner cities.

Through this process the team will ensure product knowledge is internally embedded and passed on to DoubleGDP city partners with an aim of helping them reach their growth goals through the app.

Overall Responsibilities

Members of the CS team have a responsibility of having an overall appreciation of the product.

Each member has been assigned product areas of focus. For which they will personally schedule time to understand the product area. They can also connect with the engineer responsible for their product area as detailed in engineering's module experts.

Assignments of the Product Areas:

  1. Mutale:
  • Payments, Invoices and Collections
  • Maps and Property Registry
  1. Penny:
  • Campaign Management System (Sales)
  • Content Management System (News)
  • Community Engagement and Support
  1. Doreen:
  • CRM, Customer Journey and Pipeline
  • Forms, contracts, and workflows
  1. Gabriel
  • Business Registry

Changes to Product

DoubleGDP releases several product changes in a sprint.

The CS team member will take note of the changes in their product area at the end of each sprint as communicated through the engineer sprint updates. They will personally schedule time to test the functionality on the and give feedback during the Thursday retrospective meeting.

User Guide

The CS team member will keep the user guide up to date with instructions on how to use the functionality and updates to the functionality as they are released.

User Guide Update Tips

  1. Consider the audience: An end-user and administrator's view are different. The guide should taken into account all user types.

  2. Text or video: Depending on the functionality using a video guide would be better than text or vice versa. Videos should be no longer than 2 minutes while text should be no more than 10 steps.

  3. When text is used, screenshots are required for visualizations:

    • The screenshot should be taken from the demo or staging environments and not display any Personal Identifiable Information (PII)

    • All screenshots annotations and markings (arrows, text, etc) shall be in orange color.

    • One screenshot can be used to demonstrate several steps by using numbering to denote each step.