PART 1

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

As a client who appreciates the benefits that LOT brings to how I analyze Job Postings data - I want to also leverage this taxonomy in Lightcast’s various Government datasets

Value to Customers & Users

LOT in Postings and soon Profiles is great - but unless a client can slice Government datasets via LOT, it’s use will be limited for our clients. Bringing the granularity to our Government data will make it more relevant for our clients analysis involving LOT.

Value to Lightcast

Further drive adoption of LOT across more of our datasets. Significant differentiator with our various Government datasets.

Target User Role/Client/Client Category

Any clients who want to use LOT.

Delivery Mechanism

Core LMI

Occupation Benchmark API

Success Criteria & Metrics

For this PI - models team developments an effective approach to represent LOT in Government Occupation dataset. Could be - an approach is developed and we work it into products (like Occupation Benchmark API) in a following PI.

Aspects that are out of scope (of this phase)

• Not yet available in Analyst in this PI

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.