Versions Compared

Old Version 21

changes.mady.by.user Jay Hill (Unlicensed)

Saved on

compared with

New Version 22

changes.mady.by.user Jay Hill (Unlicensed)

Saved on

Key

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

...

Expand
titleThe Problem

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

We currently rely on a team of expert mappers to meticulously add content into the UCF. The process works well but is slow. With the advent of automation and AI, Unified Compliance risks attacks from competitors who will use technology to accelerate content acquisition.

We risk losing customers to other platforms if we fall behind on the extent of coverage.

We will also find it difficult to take on new market segments without automation.

...

Expand
titleSection Explanation. Click to expand.

The intent of this section is for the following:

Monetization: Financial impact this product will introduce (if any)

Technical Risk Mitigation: Identifies potential technical risks and propose mitigation strategies.

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.

Identifies potential

What is the Unique Selling Proposition (USP)? Relay the key factors that separate our product from the competition and why we are the best possible solution for our prospects based on their unique needs.

Expand
Expand
titleRisk Mitigation
titleHigh-level Messaging
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?

Technical Risk Mitigation

If applicable, identifies potential technical risks and propose mitigation strategies.

Risk

Mitigation Strategy

The eCFR content volume could cause multiple challenges including impact on API responses, searches, dominate other content sources …

...

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.

 Yes

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)? 

 No

Talk to the Customer Success team.

Customer Success

Do we need a new or updated onboarding experience?

No

Talk to the Customer Success team.

Support

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

Yes

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?

Yes

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?

Yes

Review within our Product Team

Growth & Data

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

 Yes

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?

Everyone

Not applicable yet until feature flags are ready to go

Product

Are we running a Beta for this?

No

Review within our Product Team

Marketing

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

Yes

Talk with Marketing

...