PART 1

Customer/User Job-to-be-Done or Problem

USER STORY

As a user, I would like to have the option to enter Global Occ. Snapshot without having to first go through Global Dashboard, so that I can save time, allowing me to be more efficient.

As a new user, I would like to understand what each report does, so that I don’t have to play around with these tool to learn what type of data I will be present. This will help eliminate any confusions for new team members.

Value to Customers & Users

In the JTBD framework, these are the “pains” and “gains” your solution will address. Other ways to think about it: What’s the rationale for doing this work? Why is it a high priority problem for your customers and how will our solution add value?

1. Decrease time spent going through dashboard in order to reach the Global Occ. Snapshot.

2. Decrease time spent playing around with reports in order to understand what exactly the information they’ll receive.

3. Bing able to view saved reports by having a new navigation bar, which is similar to TA.

Value to Lightcast

Sometimes we do things for our own benefit. List those reasons here. 

1. improved confidence in Global Analyst product.
   
   

Target User Role/Client/Client Category

Who are we building this for?

1. Current and new Global Analyst clients.

Delivery Mechanism

How will users receive the value?

1. Built directly into Global Analyst product.

Success Criteria & Metrics

How will you know you’ve completed the epic? How will you know if you’ve successfully addressed this problem? What usage goals do you have for these new features? How will you measure them?

1. Event clicks on Global Occ. Snapshot (Pendo Tracking)

2. Reduction in Global Dashboard Clicks (Pendo Tracking)

Aspects that are out of scope (of this phase)

What is explicitly not a part of this epic? List things that have been discussed but will not be included. Things you imagine in a phase 2, etc.

PART 2

Solution Description

Early UX (wireframes or mockups)

Lightcast Global

Lightcast Global

Dependencies

Is there any work that must precede this? Feature work? Ops work? 

None

Legal and Ethical Considerations

Just answer yes or no.

High-Level Rollout Strategies

• Initial rollout to [internal employees|sales demos|1-2 specific beta customers|all customers]

  • If specific beta customers, will it be for a specific survey launch date or report availability date 

• How will this guide the rollout of individual stories in the epic?

• The rollout strategy should be discussed with CS, Marketing, and Sales.

• How long we would tolerate having a “partial rollout” -- rolled out to some customers but not all

Risks

Focus on risks unique to this feature, not overall delivery/execution risks. 

None

Open Questions

What are you still looking to resolve?

Complete with Engineering Teams

Estimated Costs

Direct Financial Costs

Are there direct costs that this feature entails? Dataset acquisition, server purchasing, software licenses, etc.?

Team Effort

Each team involved should give a general t-shirt size estimate of their work involved. As the epic proceeds, they can add a link to the Jira epic/issue associated with their portion of this work.