/
CA Expansion of Career Pathways Model/API

CA Expansion of Career Pathways Model/API

Β 

Target PI

PI 2

Created Date

Jan 25, 2023

Target Release

Apr 14, 2023

Jira Epic

Document Status

Draft

Epic Owner

@Nick Studt (Deactivated)

Stakeholder

@Ben Bradley

Engineering Team(s) Involved

Documents Micro C&E Taxonomy Models ANALYST

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, 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 Canada markets. Value it brings is helping to shape career exploration and learning and development informed by skill similarity between occupations.

Β 

Value to Lightcast

This work will put in place the levers for the Career Pathways 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 project will enable us to deliver this model into brand new markets and therefore drive additional ARR in Q1 2023.

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 v6 only in Canada.

Stretch goal would be include Canada NOC and UK LOT v6 + UK SOC in the model.

Expose in the Career Pathways and Occupation Benchmark API and Analyst as a part of this PI.

Β 

PI 2 Delivery Definition of Done:

  1. Canada Career Pathways are available to clients using LOT v6 in:

    1. Career Pathways and Occupation Benchmark API

    2. Analyst Canada

    3. Licensure and Certifications are based on US for MVP

  2. Model pipeline developed to enable Career Pathways using LOT to be added to UK within 2 weeks of release of LOTv6 in UK data

    1. Model is prepared to accept national licensure and certifications but US

  3. Model pipeline developed to enable Career Pathways using national occupation taxonomies but will re-evaluate if this is required based on success of LOT v6.

Β 

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.

Have you thought through these considerations (e.g. data privacy) and raised any potential concerns with the Legal team?

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

Β 

Effort Size Estimate

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.

Team

Effort Estimate (T-shirt sizes)

Jira Link

Team

Effort Estimate (T-shirt sizes)

Jira Link

Micro

M

https://economicmodeling.atlassian.net/browse/MIC-1697

Β 

Β 

Β 

Β 

Β 

Related content