Overview

Background

Content providers such as CSA, PCI, and GRI need a meean

Objective

Provide additional context and explain how this product fits into UC’s strategic goals and initiatives and why we are building it.

Personas

Link to UC’s personas for the user, buyer, influencer.

Success Metrics

List project goals and the metrics we’ll use to judge success

Goal	Metric

Current Challenges / Limitations

Describe the challenges that users face using the current product, alternative solutions, or performing tasks manually.

Benefits

Highlight the main benefits the customer/user will gain by this product

Subscription / Pricing / Billing Impacts

Describe any financial impact this product will introduce (if any)

Beta and Early Access

Describe if beta customers and/or early access is essential for success. If betas are required, there could be a substantial recruitment process required which needs to be anticipated and planned for.

Risks and Assumptions

List any risk or assumptions you have about the users, technical constraints, business goals …

Milestones and Phases

List the project milestones along with how that milestone can be successfully measured.

Number	Description	Success Measurement

Product Requirements

Describe the product requirements that will fulfill the underserved need(s) starting off with the use cases, then specific functionality

Use Cases

Happy Day Scenarios

This is the “happy path” that includes the beginning to end steps the customer/user takes to be successful.

Rainy Day Scenarios

Here is where you describe what to do when things go wrong (e.g., user closes the browser, API doesn’t return results …)

Requirements

Requirement	Description	User Story	Importance	Jira Issue	Comments
Following reports all pertain to shared lists which infers the organization is using the API.
Authority Document usage per organization.	List of companies that have placed specific ADs in at least one shared list.
Authority Document count per organization.	Cumulative count of all ADs used per organization.
Authority Document distinct / unique count per organization.	Distinct count of all ADs used per organization.
Authority Document usage per Industry.	Count of Authority Documents used in at least one shared list by Industry.
Authority Document revenue tracking.
Authority document per country.	Count of Authority Document used in at least one shared list by Country.
Authority Document usage by Job Title and Job Function.	Count of Authority Document used in at least one shared list by Job Title and Job Function.
Authority Document usage by user.	Count of Authority Document used in at least one shared list by user.
Following reports all pertain to organizations who have created builds.
Build usage per organization.
Build usage by industry.
Build usage by annual revenue.
Build usage by country.
Build usage by user.
Compare build usage by organization.

Open Questions

List any open questions that come to mind throughout the lifecycle of this project

Question	Answer	Date Answered

Out of Scope / Future Functionality

List the known features that are out of scope for this project or might be revisited at a later time.

As is case with the assumptions, it is important to list these out so that architects and engineers can plan accordingly for these later updates.

Impacted Product Components

If this project is a component to other areas or an update to an existing product, specifically call out where this product will interact with other areas.

User Interaction and Design

Link to mockups, prototypes, or screenshots related to the requirements.

Process Flow Diagrams

Links to user journeys, process flow, or other diagrams related to the requirements.

Guides

If there are UI components to this requirement, list the main areas where interactive user guides would be needed.

Additional References

List and link to any other reference sites, documents … that might be important to the reader.

PRD - Authority Document Reporting