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 creating Spotlight user dashboards, I want to have a UI which is more flexible and intuitive and has improved data access and visualisation, so I can create more compelling narratives with Lightcast data.

During the first half of 2023 we have launched Spotlight to the European and global market, as well as adding a Deep Dive for US customers. In the second half of 2023 our next goal is to prepare Spotlight to be a go-forward too in place of Labour Insight for APAC customers. While this transition process may create demands for more ambitious requirements for APAC customers, we have early feedback from Spotlight users already which allows us to anticipate improvements in the wider UI which will aid transition customers as well as making Spotlight a more compelling product for sales in all geos.

This epic will create capacity to work through prioritised feature improvements emerging from that early feedback which will tackle known challenges including:

• Improved user support through templates and tooltips

• A more fluid UI allowing users to add packets more flexibly and better manage the workspace of a dashboard

• Improved options for packet visualisations and data display and export

• Addition of section dimension to allow user annotations and organisation

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?

Value to customers and users will be to make Spotlight a more complete user experience. Early testing suggests users value the free-flowing nature of dashboard creation but are inhibited by the current ‘empty page’ of first use, a wish to be able to keep adding and improving their dashboards, and to better be able to display and explore data.

Value to Lightcast

Sometimes we do things for our own benefit. List those reasons here. 
Spotlight represents two gains to Lightcast: creating a new type of research tool for the business, of use to customers in all verticals, and a scalable research tool for global data, which is essential if we are to realise our vision of being a global provider of labor market analytics.

Target User Role/Client/Client Category

Who are we building this for?

Primary users are current subscription customers of Labour Insight ANZ and Labour Insight SGP. A separate initiative (https://economicmodeling.atlassian.net/wiki/spaces/DPM/pages/2712436831 ) will add Australia, New Zealand and Singapore to Spotlight Global, with the intention of opening it up to them as their go-forward tool. We anticipate there will be feedback on requirements to achieve value parity, and this epic seeks to anticipate obvious limitations of Spotlight Global to allow work in PI 6 and PI 7 to focus on more specific problems to allow us to achieve a successful transition.

Delivery Mechanism

How will users receive the value?

UI and feature improvements will be made to Spotlight Global and Spotlight US.

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?

Progress will be made in delivering prioritised features for Spotlight improvement. From these we anticipate success will be measured by:

• Positive initial reception of Spotlight Global in the hands of existing Labour Insight ANZ and SGP subscription customers, measured by product feedback planned for the transition process

• Early customers of Spotlight Global reporting improved experience, measured by product follow-ups and return to testing customers where necessary

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? 

The work focuses primarily on improvements to software and so is not anticipated to create dependencies.

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.