This is a fictional prd that I wrote as part of my assignment for a PM internship at Bounce. All metrics are guesstimates. This was written based on a template that can be found here.
For the unitiated, a PRD is a Product Requirement document, a document that tells you what exactly you are building. It outlines the product's purpose, its features, functionalities, and behaviour.
This is my first attempt at writing a PRD so please feel free to dm me any suggestions/feedback on Twitter.
Swiggy is evaluating if it should start pickup from restaurants as a new feature on it’s app.
You are the PM on the project, what do you do next?
Please list down assumptions you have made
How would you plan to launch the project?
How will you evaluate success/failure of the launch
This spec discusses about (WHY), (WHAT), (WHEN) needs to be built for initiating self pickup from restaurants. It does not discuss the technical implementation (HOW) for it.
Author:Manan Agarwal, Fictional PM of Swiggy
Last updated: November 10th, 2020
OKRs (Vision: build better urban lifestyle)
After the pandemic people are apprehensive of using delivery partners because of their multiple interaction with various elements in the system.
Growth in gross volume of orders.
Increase in the retention, DAU and corresponding lagging metrics eg: less time spend for in app ordering
Major UX changes, on the customer side. (different swiggy pickup, like in blr airport)
Consumers willing to trade picking orders to save time.
Offering unparalleled convenience to urban consumers by eliminating the last mile time and introducing self pickup from restaurants allowing consumers to have maximum flexibility with respect to their order.
Framework Used: DHM (Delight, Hard to Copy, Margin Enhancement)
Orders done daily
Orders within distance
|Homepage to have a specific button which lists “Pickup your order”||MUST HAVE|
|Select the restaurant you wish to pick up your food from||MUST HAVE|
|Show the menu||MUST HAVE|
|Place the order, adding a cart feature||MUST HAVE|
|Create payment flow||MUST HAVE|
|Provided with an ETA||MUST HAVE|
|Alert user via email about order being placed||MUST HAVE|
|Alert via push notif, order is placed and ETA screen should pop up||MUST HAVE|
|Alert via push notif, when food is ready to be picked up||MUST HAVE|
|Alert via push notif, when order is delivered and give prompt for feedback in terms of 1-5 rating overall experience with a comment box.||MUST HAVE|
|Transaction is secured by a One time pin shared on both merchant and consumer end to authenticate during the pickup.||SHOULD HAVE|
|If customers choose to opt-in to share their location data when the app is running, merchants will be alerted when the customer is approaching the store so they can have their order ready upon arrival.||SHOULD HAVE|
|SMS ETA < 2mins, if the customer loses connectivity for the time being.||Delighter (Should have)|
|Call the customer, if the pickup has been waiting in the restaurant for >2mins, to reduce the wait time for the queue.||Delighter (Should have)|
|Marketing: Update Swiggy Blog on the new feature||Must Have||Marketing|
|Marketing: Announce feature through our social media accounts||Must Have||Marketing|
|Start PR for this feature||Must Have||PR|
|Build Marketing Collateral for partner restaurants in form of tents/ desk with Swiggy branding which will act as kiosks for orders placed on Swiggy||Must Have||Marketing|
This is how the screens would look
Shoutout to Shivang for helping me out with this.
|Testing should be done on design prototypes on both user/merchant end to see what kind of flow is suitable.||Done||15th Aug|
|Will start an internal rollout around Swiggy HQ/swiggy employees and restaurants to get clear actionable feedback..||Due||25th Aug|
|Post feedback and after iteration, launch to around 50 merchants in 3 populated hotspots, where restaurant to consumer distance is less and volume is high||Due||1st October|
|Gradually scale basis marketing events and other promotions keeping in mind #of restaurants > X AND # of consumers who've placed an order > Y in localities, where X & Y can be estimated after pilot run response||Due||1st November|