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 using Spotlight, I want to be able to use the data in my language and currency, so I can find and report the data I want.

Spotlight is designed to be globally usable, and is initially focused on customers in western European countries. While initially designed as an English language tool, sales feedback is that the ability to search geographies in their native names would improve usability significantly. At the same time, we would like to ensure that users can select the currency that monetary values (specifically, job posting advertised salaries) can be displayed in.

To this end, the ambition of this epic has two elements:

• Allow the searching of geography names in native form - this depends upon successful completion of the PI-2 epic https://economicmodeling.atlassian.net/wiki/spaces/DPM/pages/2563245078/Spotlight+Multi-language+taxonomy+search - the definition of done will be the completion of this search capability and not its integration within Spotlight, which will be for PI-4

• Allow users to select currencies for the display of monetary values - this builds on work in Global data

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?

European customers will be able to display data in Euro or Pounds across countries, and will be able to search for places in their local name - so searching for Koln will get Cologne and Roma will get Rome.

Value to Lightcast

Sometimes we do things for our own benefit. List those reasons here. 
If Lightcast is to succeed as a global authority in the labour market, it needs to be able to meet non-English language use cases in their own terms. These are targeted user supports to aid that development.

Target User Role/Client/Client Category

Who are we building this for?

All users who work in non-USD and may use local terms to describe places.

Delivery Mechanism

How will users receive the value?

Currency selection in the Spotlight tool.

Geography search in the Spotlight tool in PI-4, given the capability developed in this PI.

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?

When a user can see Job Postings salary data in Euro, and Spotlight development can depend on integrating search for European regions in their native names during PI-4.

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.