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.

When assessing regional openings/postings/conferrals/profiles, I want to easily understand which occupations are over and undersupplied, so I can develop the right programs, target correct initiatives, etc

 When preparing for a major economic development investment, I want to understand the projected supply of candidates to fill necessary roles so I can partner regionally to build the pipeline of talent needed to fulfill the goals. I want to assess current plans/educational pipeline to determine where I am likely short of the target so I can properly invest to build the correct workforce.

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?

We provide a lot of data but fewer insights to our customers. The most obvious is a clear recommended method on how to assess supply and demand for occupations and skills.

• For Community, this enables customers to advertise their strengths, prep reskilling for un- and underemployed workers, and advertise their strengths to potential organizations

• For Talent, this helps make better sense of the markets for site selection by understanding whether high employment means a good supply or simply high competition costs

• For education, this enables the creation of programs targeted toward available regional opportunity

Value to Lightcast

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

One of our top Talent competitors offers a S/D ratio that customers often point to as being available, not necessarily good. This would help with Competitive Advantage

Target User Role/Client/Client Category

Who are we building this for?

• Analyst customers (see above)

• API customers

Delivery Mechanism

How will users receive the value?

• APIs

• Snowflake

Future: Analyst

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?

• we are able to provide specialized occupation level supply/demand ratios at the countyor MSA level

• we are able to provide skill level supply/demand ratios at the county or MSA level

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.

Data out of scope:

This is not

• Supply/Demand by skill

• Region-specific career pathways

• Projected supply/demand in the future

• Supply/Demand of “entry-level roles”

Delivery out of scope:

We do not expect to have Supply/Demand in Analyst at the end of this but it will be available to research teams

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.