PART 1

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

When using Gazelle Web Application I need to have access to continuously refreshed and frequently updated companies-related data points to identify the most relevant targets, as well as other related data (people, g-scores, industry information, trade shows, featured lists, projects etc.)

Value to Customers & Users

Data updated from the latest providers’ datasets regularly, increased quality of dataset including deduplication, removing invalid information, better company trees matching, reliable working of all the main functionality of the Web Application, making a significantly improved data available via familiar means.

Value to Lightcast

Scalable solution which allows adding additional data points, providers and further data enhancement in future (NeoETL) and the corresponding new-generation Web Application.

Target User Role/Client/Client Category

Gazelle clients

Delivery Mechanism

Gazelle Web Application, Snowflake

Success Criteria & Metrics

NeoETL pipelines are completed and allow reliable frequent reruns in semi-automated way; Gazelle Web Application is deployed with the new data produced via NeoETL and client facing.

Aspects that are out of scope (of this phase)

No new UX (that’ll be in Gazelle 2.0).

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.

• Have you thought through these considerations (e.g. data privacy) and raised any potential concerns with the Legal team?

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.