Versions Compared

Version Old Version 32 New Version 33
Changes made by

Jay Hill (Unlicensed)

Jay Hill (Unlicensed)

Saved on

Key

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

...

Strategic Planning and Decision Making

Expand
titlereadme

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?
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 affect? What metrics should we absolutely add? Why it is important to affect those metrics?

Goal

Metric

Why Important?

Scope and Features

Expand
titleSection Explanation. Click to expand.readme

The 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
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.

Feature

Comments

Expand
titleProcess flows and UX

If we have them, link to:

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

  • 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

Milestones and Launch Checklist

Expand
titleSection Explanation. Click to expand.readme

The intent of this section 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.

Risk

Mitigation Strategy

Expand
titleLaunch Readiness

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
titleSection Explanation. Click to expand.additional 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: