Explore

PRD

Team

PM:

Design:

Eng:

Problem

Showcasing and distribution : Application needs provisions for publishing & sharing to social media, store and broadcast the assets.

Solution

Sharing and publishing the assets to social media can be made easy and can be broadcasted through normal and scheduled emails.

Goals & Success Metrics

Metrics

Goal

Increase daily active users

30%

Reduce churn rate

Penetration market rate

30%

Increase paid users

20%

There are no rows in this table

⁠

Core Features

Content calendar helps to draft posts and plan the social media feeds. Designing, drafting and scheduling of social media posts can be done in just a few clicks natively. Users can set various timeline, checklist, social media scheduling and content publish workflows

Workflow status : The below statuses are assigned for every design work at different stages to monitor/track the workflow.

Draft

Pending Approval

Requires Edits

Approved

Scheduled

Published

3. Timeline helps campaign managers to plan and assign tasks to the team and follow the campaign

4. Manage publish schedule helps to plan, schedule and publish posts, images, to multiple social networks simultaneously by content calendar. Users can visualize the content on a shared publishing calendar.

6. Account Management helps to manage multiple account of user and multiple account of social media account

7. Post Analytics helps to see your posts reach & engagement across multiple social networks from the same spot and get the top performing ones delivered at your mailbox.

Requirements

Requirement

User Story

Importance

Jira Issue

Notes

There are no rows in this table

⁠

Core Flows

Post creation flows

Link yourSocial account to Picmaker account manager

Click Create Post

Upload your visuals from project

Craft your post (write your caption, add mentions and hashtags)

Click the Publish button, and select Schedule

Miro Diagram Embed:

XD Prototype Embed:

Launch Readiness

Key Milestones

Date

Milestone

Audience

Description

Fri, May 15

POC

Internal employees only

Testing internally

Fri, Jul 31

Beta

Early cohort of 100 customers

Getting user feedback

Fri, Sep 11

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)

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

Do you need additional tracking?

Are we running a Beta for this?

Talk to the Marketing team.

Do we need an popup new features

Talk to the Marketing team.

Email to all user about the features

Talk to the Marketing team.

Do you need a GTM plan? (packaging, positioning, etc)

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.

Do you need sales enablement materials?

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

Make sure the Stakeholder 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 sales team.

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

Talk to the Development team, Raghav and Arjun.

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 social media integration)?

Talk to the APP 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 user ?

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.

All Security Check before lanuch

Talk with the Security team.

⁠

Stakeholders

Reviewer Signoffs

Reviewer Signoffs

Reviewer

Team/Role

Status

Raghav

CEO

Signed off

Arjun

Needs revisions

Ganesh

Design Lead

Signed off

Karthik

Marketing Lead

Not read

Devi

Team Lead

Not read

There are no rows in this table

⁠

Thoughts / Questions

Thoughts / Questions

Done

Questions

Author

Reaction

I don’t think we are considering the user here.

What happens if our competitor designs the same thing?

There are no rows in this table

⁠

Decision Log

Asked by

Question

Status

Decision

Decided On

Navaneetha Krishnan K

What color should we make the logo?

Of the options, green is the closest to our branding.

3/10/2021

Navaneetha Krishnan K

When should we launch?

After reviewing all options, we should launch next Thursday.

2/18/2021

Raghav

Who is our target audience?

There are no rows in this table

⁠

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.