PART 1

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

When I want to understand an Occupation in the context of a region in Canada, I’d like to leverage Canadian data with the Occupation Benchmark API interface.

Value to Customers & Users

The value to clients here is the ease of use and interface benefits of pulling Canadian Occupation data in the Occupation Benchmark API.

Value to Lightcast

Enable clients using Canadian Occupation Profile API to transition to the Lightcast service. Create platform for further Canadian revenue expansion. This capability will also give us the mechanism to add further country support as the data becomes available.

Target User Role/Client/Client Category

Clients who want to understand the labor market through the lens of an Occupation in Canada.

Delivery Mechanism

Occupation Benchmark API - country input (CA)

Success Criteria & Metrics

Canada input is available in the Occupation Benchmark API - to start it will only be available for LOT

Aspects that are out of scope (of this phase)

• Canada version of the various models are not in scope and will be handled outside of this Epic.

• NOC can come later

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.