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 analysing ANZ/SGP labour markets, I want to have Core LMI data on employment by occupation/industry, so I can gain context on labour supply.

The final stage of LI integration is to migrate ANZ/SGP LI users to Spotlight. As with US/UK/CA migration, and aligned with our EU expansion, we want ANZ/SGP LI users to have Lightcast Core LMI as a migration benefit.

In common with EU LMI, the intention is not to replicate the full range of LMI data that we have in US/UK/CA but provide an employment layer which can provide valuable context to postings and profiles-based analysis. The requirement is:

• Employment by 4-digit ANZSCO 2021/SSOC 2020 occupation by admin geography (SA4, SA3, LGA in Aus, Regional Council and Territorial Authorities in NZ, not Singapore) and market, min 10 year history and 10 years projection

• Employment by 2-digit ANZSIC 2006/SSIC 2020 occupation by admin geography (SA4, SA3, LGA in Aus, Regional Council and Territorial Authorities in NZ, not Singapore) and market, min 10 year history and 10 years projection

As a follow-on, within the limits of mapping both sets would also be further mapped to ISCO-08 and NACE rev2 to allow for cross-country analysis.

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?

• As evidenced by our business across US/UK/CA, Core LMI provides substantial contextual value as a less noisy benchmark for labour supply and demand

• In conducting cross-country analysis, a layer of Core LMI across all US/UK/CA/EU/ANZ/SGP will allow for much richer investigation

Value to Lightcast

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

• As a migration benefit of moving from LI to Spotlight, producing APAC LMI will contribute to our efforts to conclude integration and allow the closure of ANZ/SGP LI resulting in substantial cost savings

Target User Role/Client/Client Category

Who are we building this for?

• All users of ANZ/SGP data - chiefly ANZ/SGP LI users but also those in other geographies analysing data for the region

Delivery Mechanism

How will users receive the value?

• Data will be produced and once QA’d will be transferred to Agnitio to serve API users and be accessed via Spotlight

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?

• ANZ/SGP LMI will be available to the specification described above, and meeting typical Lightcast quality standards

• ANZ/SGP LI users will report the availability of enhanced LMI within Spotlight to be a benefit facilitating their migration

• Spotlight users will use Core LMI packets to display the data in their dashboards (hopefully can quantify this)

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.

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.