PART 1

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 Canada or the UK, I want to leverage Lightcast’s DDN model to help myself, my students or my employees better understand the dimensions of Defining, Distinguishing and Necessary Skills of a given occupation. In order to do this I need to have this model speak the language of my market, including:

• Function in national (CA/UK) Occupation Taxonomies

• Localized demand (at least for national taxonomies)

Value to Customers & Users

DDN skills are valuable to cutting through the noise in job postings and illuminate the skills that are most crucial to an occupation. They serve as the basis for significant further opportunity in understanding occupations, credentials, skills gaps, etc., and are closely related to the career pathways models.

This work is required in order to unlock the DDN model/API in Canada and UK markets. Value it brings is helping to shape how clients in these markets can look at the key skills which shape a specific occupation.

Value to Lightcast

This work will put in place the levers for the DDN API/model to take country specific inputs. The value is that this product would be made more broadly available in these markets and we’d be able to offer this feature across our Analyst platform as well as API offerings.

This:

1. Reflects that we are a global company with global data assets

2. Opens up new opportunities, as DDN has never been available in these markets
   
   

Target User Role/Client/Client Category

• Educators helping students explore occupations and shape their own programs.

• Employers looking to develop relevant job postings or help upskill their people and build talent from within.

• Workers looking to better understand how to develop their learning and development plan.

Delivery Mechanism

• DDN API

• Analyst

Success Criteria & Metrics

1. DDN are available using NOC in:

   1. APIs Canada

   2. Analyst Canada

2. Model pipeline developed to enable DDN using UK SOC to be added to UK in PI 3.

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)

<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.