Versions Compared

Version Old Version 17 New Version Current
Changes made by

Jay Hill (Unlicensed)

Jay Hill (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

Expand
titleSection Explanation. Click to expand.readme

The product requirements document (PRD) is a central document used to align all stakeholders (product management, engineering, QA, designers, and leadership) on the overall objective and vision of the proposed product and is used as a decision-making toolhow we will solve a specific problem with the proposed solution.

When creating the PRD, provide just as much information as needed and nothing more. If the document is too long and complex, it will quickly become outdated, and readers will lose interest.

PRD content and structure vary by organization. Depending upon the product line, company culture, and processes, PRDs could have quite a different look and feel.

In this latest iteration of the Unified Compliance PRD template, we changed the template to help raise visibility of how the proposed product (or feature set) adheres to Unified Compliance’s strategic plan including details on why this product proposal is important to Unified Compliance.

Strategic Planning and Decision Making

How does this proposal fit into our overall vision and which specific initiative does this proposal align with and how?
Expand
Expand
titleVision and Initiative Alignment
titleSection Explanation. Click to expand.

  • Vision and Goal Setting: articulates the vision alignment, problem being addressed, and goals of the product proposal describing what the product is, who it is for, and how it will benefit the users and the organization.

  • Decision-Making Framework: helps in making informed decisions throughout the product development process acting as a reference point for evaluating progress and making changes.

  • Performance Measurement: sets the criteria for measuring the success of the product through specified metrics and key performance indicators (KPIs) including potential financial impact.

  • Basis for Prioritization: helps in prioritizing features based on the product strategy, market needs, and resource constraints.

readme

Describe the problem we are solving, the high-level approach, and goals so that before we get too far into the details, readers will have a good understand of where we are headed.

Expand
titleThe Problem

What problem are we trying to solve? and why it important to our customers and/or to Unified Compliance?

Start writing here:
Expand
titleHigh-level Approach

Briefly describe the approach you’re taking to solve this problem. Provide enough information for the reader to imagine possible solution directions and get a rough sense of the scope of this proposal.

Start writing here:
Expand
titleGoals

What does success look like? What metrics do we measure today that we can we effect and why affect? What metrics should we absolutely add? Why it is important to affect those metrics?

Goal

Metric

Why Important?

Scope and

...

Features

Comments

section focusses on the details of the solution including what is in scope, what is out of scope and additional information to help in the product and engineering collaboration process.

Expand
titlereadme

The intent of this section is for the following:

Scope Definition: defines the scope of the proposed product (or features), including what will and will not be included helping manage expectations and focus development efforts.

Guideline for Development: provides detailed information on the product’s features, functionalities, user flow, and interface to guide the development team in building the product.

Framework: provides high-level evaluation criteria for alternative solutions (build, buy, partner) to evaluate different routes to success.

Expand
titleRequirements

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

Requirement

Importance

Expand
titleFeatures

Describe the product features that will bring value to customers and fulfill underserved need(s).

Feature

Use Case / Problem Solved

Expand
titleOut 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.

RequirementFeature

Comments

Link to mockups, prototypes, or screenshots
Expand
titleUser Interaction Process flows and Design
UX

If we have them, link to:

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

Expand
titleProcess Flow Diagrams
Links to user journeys, process flow, or other diagrams

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

Link here:
Expand
titleImpacted 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.

Start writing here:
Expand
titleOpen Questions

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

Question

Answer

Date Answered

Expand
titleAlternative Solutions
Provide a high-level evaluation criteria for alternative solutions (build, buy, partner) to evaluate different routes to success.

Milestones and Launch Checklist

Expand
titlereadme

The intent of this section is for the following:

Launch Readiness: launch checklist including high-level go-to-market plan to ensure cross-departmental alignment.

High-level Messaging: Includes Unique Selling Proposition (USP) raising visibility of the proposed solution’s value proposition.

Risk Mitigation: Identifies potential is mostly focused on getting the solution “out the door” and who else is affected outside the product and engineering teams.

Expand
titleTechnical Risk Mitigation

If applicable, identifies potential technical risks and propose mitigation strategies.Subscription / Pricing / Billing Impacts: Financial impact this product will introduce (if any)

Risk

Mitigation Strategy

Expand
titleLaunch Readiness

Milestones and launch checklist including high-level go-to-market plan to ensure cross-departmental alignment.

Expand
titleHigh-level Messaging

Includes Unique Selling Proposition (USP) raising visibility of the proposed solution’s value proposition.

Expand
titleRisk Mitigation

Identifies potential risks and propose mitigation strategies.

Expand
titleMonetization

Will this product be part of an existing subscription or an add-on?

Will this product be usage based or part of a subscription?

Additional References

Expand

Identify any relevant milestones that people should know about. Will we “eat it” ourselves first? Will this require a beta? and what is the target launch date?

Date

Milestone

Audience

Description

TBD

Dogfood 🐶

Internal employees only.

Testing internally

TBD

Beta 🎈

Early cohort of X customers.

Getting user feedback

TBD

Public Launch 🚀

Roll-out to all users.

Let’s do it!

Expand
titleLaunch Checklist

This section is a reminder to the product team to make sure all relevant stakeholders are involved as necessary.

Area

Question

Answer (yes/no)

Instructions if "Yes” (or unsure)

Product

Are we introducing new functionality that requires changes to the pricing implementation.

 

The expectation is that these changes are part of the features in the PRD.

Customer Success

Will new training material be needed (or updates to existing classes)? 

 

Talk to the Customer Success team.

Customer Success

Do we need a new or updated onboarding experience?

 

Talk to the Customer Success team.

Support

Will new FAQs be required (or updates to existing ones)? API documentation?

 

Talk to the Customer Support team.

Support

Will this functionality require new support processes like new HubSpot workflows or saved replies? Or training the support team on the product?

 

Talk to the Support team.

Growth & Data

Do we need additional tracking in order to measure success and impact on user behavior for the new feature? Will UserFlow be used? Do we need a new Power BI report?

 

Review within our Product Team

Growth & Data

Could this impact CTAs? Or new-user-experience (NUX)?

 

Review within our Product Team

Growth & Data

Are we turning this product or feature on for everyone immediately or are we going to use feature flags for a slow roll-out?

 

Not applicable yet until feature flags are ready to go

Product

Are we running a Beta for this?

 

Review within our Product Team

Marketing

Are we introducing functionality where we will want to update or create new web pages? New/updated CTAs?

 

Talk with Marketing

Additional References

Expand
titleadditional references

List and link to any other reference sites, documents … that might be important to the reader including the business model canvas (BMC).

Start writing or linking here: