PART 1

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

See Platform Initiative: File Delivery Mechanism (HWOL, Consulting, AO 2.0, Report Downloader)) for overall customer JTBD.

For this Epic, the “customer” is internal consulting/research/other:

As a Lightcast employee who needs to deliver files to customers via the Analyst platform, I want a simple, clean interface that allows me to provide those files and necessary metadata that comes with those files, including:

• File name

• File Author

• Upload Date

• Target ‘space’ to limit to individual organizations

• Metadata indicating whether the file is encrypted (encryption to be handled outside the platform)

• Tags

• other

Value to Customers & Users

See See Platform Initiative: File Delivery Mechanism (HWOL, Consulting, AO 2.0, Report Downloader)) for overall customer value

Value to Lightcast

Internal value:

• Simpler, single interface means Lightcast staff know how to share files

• No need for sFTP credentials, other

• Lightcast can see who has seen the files, downloaded the files, shared the files from the platform rather than relying on email to the ether

Target User Role/Client/Client Category

Who are we building this for?

Delivery Mechanism

How will users receive the value?

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?

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)

Will be added here: https://www.figma.com/file/NNuqhcWctFCWsq6dubyT0w/File-Delivery?node-id=0-1&t=z3nHpQos52B130wd-0

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

Not complete → we need security involvement for PII files to ensure that we have the right procedures in place

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.