TEAM: Yesoo Chae, Mengzi Liu, Quentin Magnett, Brandon WIlliams

Problem Statement

Users have problems finding the templates they need because they don’t receive enough visual information from the Template Picker. How might we make template picking a more intuitive experience?

User Pain Points

Pain Points were represented in three specific areas in the user's journey: on boarding, picking a template, edit or the diagram. Each stage as their own task the user must complete. At the three distinct points, there key problems the users mentioned in a survey that are represent by the circles below. 

From our data analysis, we chose to focus on picking a template due to the amount of users that had problems at this point.

We specifically focused on the need for better visual representation of templates in the Template Picker. Users have problems finding the templates they need because they don’t receive enough                                       VISUAL INFORMATION from the Template Picker. We believe the best way to go about making an MVP for our A/B testing purposes is to add a simple preview function inside the Template Picker. As a proposed implementation, this preview function allows for users to easily and quickly find the template they need.

A/B Testing

Success metrics for the preview implemented test:

• Higher subscription rate for preview group

• Higher rate of completing documents (exporting or sharing)

• Lower number of clicks on templates per view of Template Picker for preview group than control group

  • If preview is successful, users will not have to click on templates to look at what the template would look like.

Failure metrics for the preview implemented test:

• Lower subscription rate for preview group

• Higher rate of deleting document soon after creation

• Higher bounce rates for preview group

  • Bounce rates defined here as exiting out of Lucidchart during the Template Picker page, without progressing further.

Furthermore, A/B test can tell us following information:

• If we track the number of times a user will preview a template, we can measure how many templates a user considers before picking one to use, without using eye-tracking studies or other more involved methods. This can also tell us new information about how complex templates are or potential ways the Template Picker can confuse users.

• If our prediction that “users who have the preview function will click on fewer templates” is correct, we will know that the frequency of clicking on templates in one visit is likely an indicator of confusion about specific templates.

The Design