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 I’m an organization in the UK, I want to leverage Lightcast’s Career Pathways model to help myself, my students or my employees explore career options so it can inform their next career move and learning opportunities. In order to do this I need to have this model speak the language of my market (Occupations, Certifications, Licensure requirements).

Value to Customers & Users

This work is required in order to unlock the Career Pathways model/API in UK markets. Value it brings is helping to shape career exploration and learning and development informed by skill similarity between occupations.

Value to Lightcast

Country specific input infrastructure for the Career Pathways API/model is already in place. Using this to provide career pathways data in the UK would enable price reviews and encourage renewals.

Target User Role/Client/Client Category

Worker looking to make a career move.

Educators helping students explore career possibilities

Employers looking to help upskill their people and build talent from within.

Delivery Mechanism

API - Career Pathways API, Occupation Benchmark API

Analyst

Success Criteria & Metrics

Minimum viable product would leverage LOT only in the UK.

PI 2 Delivery Definition of Done:

1. Model pipeline developed to enable Career Pathways using LOT to be added to UK

2. UK Career Pathways are available to clients using LOT in:

   1. Career Pathways and Occupation Benchmark API

   2. Analyst UK

   3. Licensure and Certifications are based on US for first biuld, them tweaked for UK specificity for MVP

Aspects that are out of scope (of this phase)

N/A

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.