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

The Occupation Snapshot is our most used report and comprised (almost 25% of our revenue by page view for Talent Analyst). However, the Occupation Snapshot has some key pain points noted by users 1) valuable items are hidden by scroll depth 2) It’s difficult to understand which datasets are being used for information throughout the report 3) some items in the report are not relevant 4) basic users would benefit from a simple top level summary of the data. We will synthesize and restyle the content in the Occupation Snapshot in order to highlight the most valuable information for easy consumption.

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?

Value to Lightcast

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

Target User Role/Client/Client Category

Who are we building this for?

• The majority of all Talent clients

Delivery Mechanism

How will users receive the value?

• Occupation Snapshot

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?

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.

Solution Description

Early UX (wireframes or mockups)

Non-Functional Attributes & Usage Projections

Consider performance characteristics, privacy/security implications, required copy translations (mostly surveys), mobile requirements, accessibility requirements

Dependencies

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

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. 

Open Questions

What are you still looking to resolve?