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

The Scope of the user problem should be narrowed to the scope you are planning to solve in this phase of work. There may be other aspects you are aware of and plan to solve in the future. For now, put those in the Out of Scope section.

As an HWOL subscriber, I want to be able to access job_postings_reports using the HWOL Universe of Jobs. I also want to be able see the Index and Publication Series

I want to do this on Developer, with taxonomies not available to me on Labor Insight 

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?

• users require this as part of their contract with Lightcast and The Conference Board

• users on Labor Insight are not being upgraded to the newest taxonomies (SOC 2018, O*Net 2019, NAICS 2017)

Value to Lightcast

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

• Final major feature that enables us to turn off Labor Insight US

• This is a contractual requirement with The Conference Board

Target User Role/Client/Client Category

Who are we building this for?

• $1.5m book of business HWOL users

Delivery Mechanism

How will users receive the value?

• Via the HWOL section of Developer

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?

• 100% of HWOLcustomers transitioned off of Labor Insight and onto Developer by March 1, 2023

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.

No enhancements to the platform or new series, etc. This is lift and shift from Labor Insight

Solution Description

Early UX (wireframes or mockups)

<FigmaLink>

Non-Functional Attributes & Usage Projections

Consider performance characteristics, privacy/security implications, localization requirements, 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?

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.