Explore

PRD: [Halodoc App]

Figma's Product Requirements Doc

Miftah Faroq

Project:

⁠

EDIT INFO

⁠

Team:

@Editor

⁠

Contributors:

⁠

TL;DR:

Create feature simplifyed the registration form

⁠

Status:

@Not started

⁠

Shipping:

Apr 30, 2020

⁠

Problem Alignment

The Problem

The current registration form is too long and complex, leading to user frustration and potential drop-offs during the onboarding process.

The objective is to simplify and streamline the registration form to improve the user experience and increase conversion rates.

High-level Approach

Simplify the registration form by reducing the number of fields and steps required.

Optimize the user interface and user flow to make the registration process more efficient and user-friendly.

Goals & Success

Goals:

Improve user satisfaction and reduce abandonment rates during the registration process.

Increase the conversion rate of new users completing the registration and successfully onboarding onto the platform.

Success Metrics:

Decreased registration abandonment rate.

Increased conversion rate from registration to active users.

Improved user satisfaction ratings related to the registration process.

⁠

Solution Alignment

Key Features

Give an overview of what we’re building. Provide an organized list of features, with priorities if relevant. Discuss what you’re not building (or saving for a future release) if relevant.

Key Flows

Show some mocks/embeds of the experience. Link to any other documentation as necessary. In general, it’s helpful to organize these around certain user journeys / use cases. Show enough of a clickthrough where people can walk away with a reasonable understanding of how the product works.

Embed example:

⁠

⭐️ Now you can embed private Figma files, too!

Open Issues & Key Decisions

Keep track of open issues / key decisions here. Sometimes, certain decisions are made that might feel controversial; document these here so people know that the discussions have happened and there’s strong awareness of the tradeoffs.

⁠

Launch Readiness

Key Milestones

Identify any relevant milestones (e.g., a Dogfood or Beta milestone) that people should know about. Make sure to show when you’re expecting to publicly launch, too.

Date

Milestone

Audience

Description

Mon, May 4

Dogfood 🐶

Internal employees only

Testing internally

Mon, May 11

Beta 👥

Early cohort of 100 customers

Getting user feedback

Tue, May 19

Launch! 🚀

Gradual ramp over the day to 100% of all users

It's the big day!

There are no rows in this table

⁠

Launch Checklist

Make sure you answer all of the questions below and involve necessary stakeholders.

Area

Question

Answer

Instructions if "Yes” (or unsure)

Will new learning material be needed (or updates to existing documentation)? Help Center articles? Images/GIFs? YouTube videos? Plugin documentation?

Talk to the Product Education team.

Will this feature require new support processes, like saved replies, new tags to track feature changes, or training the support team on new products/changes?

Talk to the Support team.

Have you implemented sufficient tracking in order to measure success, risks and impact on user behavior for the new feature?

Involve your data counterpart to make sure feature is well instrumented.

Could this impact Growth numbers? (E.g., impact to NUX, UI changes to CTAs.)

Let the Growth team know. Consider running this as an A/B if you haven’t already.

Are we turning this feature on for everyone immediately (versus a gradual rollout)

Defend in this section why you’re opting for an instant ramp to 100%.

Are we running a Beta for this?

Talk to the PMM team.

Do we need an onboarding experience?

Talk to the PMM team.

Will this be available only in certain tiers (Pro or Org)?

Make sure the Enterprise team is in the loop and have good reasoning for your packaging decisions. In addition, if this is to be included in sales enablement material, talk to your PMM.

Is this a new action that should be included in the Activity Logs?

Talk to the Enterprise team.

Are you introducing new functionality that we’d want to add to our Web or Plugin APIs?

The general expectation is that the feature team builds these capabilities into these APIs. Talk to the Platform team if you have questions.

Could this break any existing integrations (e.g., with Zeplin, JIRA)?

Talk to the Platform team.

Will this introduce new work on mobile or mobile web?

Talk to the Prototyping team.

Are you introducing new data models, or exposing new API end points? Or are you changing anything to do with Authentication, Sign in, or Sign up? Is data flowing to a new vendor or outside of Figma prod ?

Talk with the Security team.

Are we collecting any data that we did not already, or are we using any data in a manner that we did not already use it in?

Talk with the Legal team.

⁠