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 [user situation/context/mindset], I want to [user need/goal], so I can [expected result/outcome].

 When I submit a title for normalization, I want the ability to include additional context such as a Job Description, Company, SOC, and/or Industry so that I can get a narrowed/better set of relevant titles returned.

When I submit a title and description in the Classification API, I want the ability for the requested response to be the sum of the parts so that I can have a response where the Titles, SOC, and other data requested are not unrelated to each other.

When I submit a title for normalization, I want it to return titles that contain the terms submitted so that I can pick from a list of suggestions (rather than nothing or non-related terms).

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?

• A more accurate set of Normalized Lightcast Job Titles returned will provide less need for Talent Transform clients to review changes, less need for Consulting to review and edit (true self-service), and more accurate skill suggestions (since these are driven first by the Title and other Title driven classifications)

• Improving title normalization will impact the entire Lightcast system from making sure we’re tagging job postings and profiles with accurate classifications

Value to Lightcast

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

• Reduce the time and effort for Consulting/AR to manually override Titles in products such as Talent Transform

• Improved client confidence in our ability to return the best information with our APIs

• Improved ability to sell Talent Transform as a true self-service product to achieve mass adoption

• Improved ability to classify job postings and profiles used throughout the system

Target User Role/Client/Client Category

Who are we building this for?

• Current and future Talent Transform clients/users

• Anyone looking for Title Normalization/Classification API services

Delivery Mechanism

How will users receive the value?

• Classification API

• Talent Transform

• Improved data in existing reports

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?

• A reduction in Consulting/AR edits to Title classifications in Talent Transform

• Reduction in “Unclassified” responses from Title Normalization API

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.