Project/Feature Name

Subtitle Explaining the project

Context/Key Problem Areas

Readers should be able to understand the need for solving the problem. This section should cover:

1. What? - The problem you are trying to solve

2. Who? - The users it will impact and how the problem impacts them
3. Why? - This should help justify the reason the problem needs to be solved (typically backed with
some kind of analytical support)

Success Criteria
Reader should be able to understand what exact metrics would be impacted by the solution:

1. Provide details of objective metrics which are expected to be moved

2. Provide starting point and attach Jarvis Queries/Spreadsheets for the same where applicable
3. Quantify expected impact owing to the release

There are two type of metrics

1. Health Metrics - These will measure the key milestones which will help in achieving your main
metrics. (Example - % PROs attaching to product subscription on PRO App)
2. Outcome Metrics - These will measure the main business metric which corresponds to the
impact you are creating. (Example - % increase in revenue/product adoption owing to subs)

Type Definition Targets

Metric 1... ˜X%

Health Metric 2…. ˜Y%

Metrics
Metric N... ˜Z%

Metric 1…. ˜P
 Outcome Metric N…. ˜Q
Metrics

Non-Goals
The section should explain the items which are not being solved for in the proposed build

Product Flow
The section should walk through the solution through either of the two lenses:

1. Capability Diagram - What kind of systems will interact with each other and the information flow
which will happen among them? This is primarily to understand the interactions between
capabilities/systems. Example - Capability view for Airtight system on Partner side:
 2. Flow Diagram - This can highlight user journey (PRO, Customer, Biz), highlighting how the user
moves through the product journey. This is primarily to highlight user journeys and navigation.
Example - The below diagram represents the user journey for the revisit flow:

User Stories
1. Provide a consolidated view of user stories which need to be developed along with their priorities
2. Key Tenets:
a. Concise, Simple, and comprehensive
b. Written from the perspective of the user
c. Should highlight the value addition from the feature in the life of the user
d. Should contain the Acceptance Criteria
3. Components:
a. Actions
b. Reasons
c. Acceptance Criteria
 d. Events
4. Examples:
1. As a user, I should be able to discover facials grouped by the outcomes (or any other
prominent axis), so that I can deepdive into variants suitable for my need
2. As a PRO, I should be able to submit my claims for receipt of damaged products, so that I
can get a refund
3. As a Business Owner, I should be able to define products which need to be enabled for
barcode scanning, so that I can drive adoption for such products

As a user, I should be able to discover facials grouped by the outcomes (or any other
prominent axis), so that I can easily select a facial suitable for my need

Acceptance Criteria:

Users should see the grouped facials with the relevant details of the group on the various
interaction points.

Details

Group details -
● Name based on the decided axis (e.g - if outcome as an axis, then glow facials or anti
aging facials)
● Number of facials inside the group
● Starting price of the facial (price of facial with min. price inside the group)
● Brief info about the group in bullet points. Included brands, outcome etc
● More details in view details - This will be a separate page for the group level details
where users can see the comparison, benefits and reviews of facials within a group.
This page is currently available but the different components of it will need a revamp
based on the design
Interaction points -
● Selectable SP - Rich group details and variant details in V1
● Tweakable SP (MYOP and other packages) - Muted group details and variant details in
V1, will solve for rich tweakable SP journey in V2z

Designs
● Figma Link(s)
● Wireframes
Open Pointers
● Any problem area which is not answered in the document
● Any assumptions which are pertinent and need agreement
● Alternative Approaches

Appendix
● Discovery Docs
● User Research