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 I am a customer in the financial sector, I want to use stock tickers in postings data, so I can map between my interests and Lightcast 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?

Customers in the financial sector are wanting to bridge the gap between our data and stock tickers. If we are able to do that then our data becomes immediately valuable to the context these customers work within and helps open up a market to Lightcast.

Value to Lightcast

Sometimes we do things for our own benefit. List those reasons here. 
Adding stock tickers to our data (perhaps just in the Company Taxonomy?) would help open up an additional market for our data.

Target User Role/Client/Client Category

Who are we building this for?

Customers in the financial sector.

Delivery Mechanism

How will users receive the value?

This would be best delivered in the Company Taxonomy as an additional field.

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 customer has a means of searching through our postings data via stock ticker.

Stock tickers are maintained alongside the other taxonomies.

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.

Accuracy and implementation of the main source (OpenFIGI). Some curation will be an inevitable lift, but that depends on how accurate (or inaccurate) the data is.

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.