The product design process could be overwhelming for some designers. Questions such as did I miss any important information, did I explain the process well, or who are the people who will be viewing the project design process? In this blog, our mentor Chelsea Zhou, the Product Design Lead at ThoughtSpot will share the 7 steps that are essential for you to go through when planning a structure for your product design process.
Sharing and invitation are fundamental building blocks to drive user growth, because sharing and inviting directly impacts ThoughtSpots’s creation and consumption loops, which directly affects the core business metrics like net retention.
What is the product design process all about?
Clearly explain your action process. Example:
Over the next 4 to 6 weeks, ThoughtSpot will create detailed design flows and screens to show how updated Sharing and Invitation flows. This update includes:
a) increased entry points to invite and share b) simplified invite and share dialog boxes c)improved post-invitation experiences
Who is the product design process for?
Identify the viewers or collaborators of the product design project. Example:
This feature is for data analysts who are evaluating ThoughtSpot for their company team and business users who want to share Liveboards. Currently, there are limited ways to invite users during a free trial for ThoughtSpot customers on Cloud.
Highlights the product design process strategy and rationale
Show details of underlying data sources clearly to enable users to make decisions regarding data access.
Reduce clicks and typing to add a group/user.
Default to more open data access.
Provide functionality to nudge multiple users to join the team.
c) Explain the Why Describe the reason to grant access to Liveboards and underlying data sources so invited users can fully experience ThoughtSpot.
Define audience needs
A clear understanding of what Liveboards and underlying data are being granted for the security-conscious analysts.
Smooth experience to invite others and remind users to accept invitations
Ample entry points to invite others throughout the product.
Provide an estimated timeline For example for ThoughtSpot Project it is 4 to 6 weeks | 2-3-2 week sprints
Describe the Audience Narrative
Activity This feature is for data analysts who are evaluating ThoughtSpot and setting up for that company. This feature is also for business users who want to share Liveboards with other users.
Outcomes Improved Share and invite experience increases the virality of the product. It is proven that inviting others is a strong indicator of users understanding the value of the product.
The 3 Types of Product Design Structure
The UERD structure User Experience Requirements Documents is a partner to the Product Requirements Document. It comes before the designing of screens and will be developed throughout the life of the project. Benefits:
Helps to clearly define the problem in a way that clearly shows the requirements for any designed solution.
Establishes design strategies that help them design, and product team to evaluate the designs which are being developed with a common set of criteria.
Rules for UERD:
Never try to complete a UERD alone as a designer, always collaborate with your team, manager, and product team.
Never wait until the end of the project to complete the UERD. It is made as a tool to help evaluate the project. Always add to your overall work plan time to complete the elements of the UERD.
When working on rough ideas, please use the scratch space page. Then copy more complete screens into the UERD or screen specification pages. Set all UERD screens as 1920x 1080.
UI screens should follow Radiant guidelines.
Practice, the UERD requires skill to complete. The more you practice the better the requirements you will get and this will help your designs.
The Feature-level UERD template Use the Feature-level template when you have a project that uses a single user story and requires you to update one part of the application.
The EPIC/S UERD Template Use the EPIC template when you have a project that uses multiple user stories and requires you to rethink a section/s of the overall application.
Clearly define the business impact in your product design process
What are the goals that your company is trying to achieve from the product design process or design project? Below are examples of ThoughtSpot goals that you can use as a reference for your product design process.
ThoughtSpot Goals are to:
Deliver a great first impression for business users
Allow analysts to invite business users to a content-rich experience
Lower Customer Acquisition Cost (CAC) for ThoughtSpot
Customers can invite product specialists on a free trial
ThoughtSpot Sales team can run trials in a multi-tenant environment for all customers
Create virality in the product for organic growth of Thoughtspot inside an organization
Drive user adoption
ThoughtSpot Product Design process goals:
Enable collaborative Analysis setup by allowing users to invite others to a team
Enable friction-free sharing with anyone, including people who are not yet in the systems as ThoughtSpot users.