PART 1

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

As an enterprise user, I want to understand the usage of my purchased product by my team members. This will allow me to justify the cost of the tool, properly allocate seats, and get the most of my subscription.

Value to Customers & Users

Customers do not know:

• Who their active users are

• How much their users are in the Analyst platform

• What parts of the Analyst platform they are using

The Admin User Portal Epic underway will take care of the first bullet here. It is not currently scoped to manage the 2nd or 3rd parts of this Epic.

Customers thus rely on Account Managers to pull these reports for them, when they have the time.

Value to Lightcast

From @Chayce Kowalski : “I'm sitting on a list of maybe 30+ accounts in talent which equates to more than 500 users (a few very large accounts, in revenue and seats, like allegis and allstate) that want usage reports on a Monthly, Weekly, Quarterly basis.”

Community estimate: every customer gets a report at least once/year, if not 2-3x per year

This is an expensive proposition for AMs to be pulling this manually on a regular basis.

Target User Role/Client/Client Category

Organization Admin role within our customer base

• Initial expected user is enterprise Talent users, expanding to others

Delivery Mechanism

• Via the Admin Portal in development, as a phase 2.

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?

• Customers will have access to the Admin Portal with a Usage Report option

• Adoption of the Usage Report by 30 Talent organizations within 3 months of delivery.

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.