0% found this document useful (0 votes)
56 views8 pages

Last Min Prod Man Notes: App Design

The document provides information on product design and metrics for different types of digital products and services. It discusses frameworks for understanding customer needs and defining solutions. It also lists common metrics used to measure acquisition, activation, retention, and monetization for various categories including ecommerce sites, mobile apps, and enterprise software. Specific examples of metrics are provided for each category.

Uploaded by

vineeth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
56 views8 pages

Last Min Prod Man Notes: App Design

The document provides information on product design and metrics for different types of digital products and services. It discusses frameworks for understanding customer needs and defining solutions. It also lists common metrics used to measure acquisition, activation, retention, and monetization for various categories including ecommerce sites, mobile apps, and enterprise software. Specific examples of metrics are provided for each category.

Uploaded by

vineeth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Vineeth M R

LAST MIN PROD MAN NOTES

App Design
Start with some basic questions and understand the problem better. Use 5W-1H framework for
this.

Then try to state the objective: If it is user acquisition, user retention etc.

Now start with customer segment and stakeholder analysis for the problem.

Don’t Ask the interviewer to choose the segments, rather you only propose one, based on
highest impact or reach etc.

Once you have chosen that, ask the interviewer if he is fine with this segment or does he have
anything else in his mind.

Now to define the customer needs, start analyzing the situation using customer journey approach

Try to identify up to 5 needs and prioritize top 3 of them based on highest impact, reach or
importance etc.

Once you have chosen that, ask the interviewer if he is fine with these needs or does he have
anything else in his mind.

Solutioning phase can be new feature additions or existing feature improvements based on the
needs chose. Typically suggest 1-2 solutions per need -> so it would be 3-5 solutions.

Prioritize the solution again to top 3 based on reach or impact and try to quantify reach or
impact using “low” “medium” “high”.

Now at this point the interviewer might ask u to go with summary or he might ask u to choose
the metrics.

For summary go with: Objective -> customer segment chosen -> needs -> solution

For Metrics use AARM framework as defined below:

• Acquisition: Tracking customer signups for a service. The bar for signing up for a service
has gotten lower and lower, thanks to the popularity of free signup and pay later “freemium”
models. The typical acquisition metric to track is lazy registrations or app downloads.
• Activation: Getting users that have completed a lazy registration to register fully. For a social
networking site like Google+, this may include uploading a photo or completing their profile
page.
• Retention: Getting users to use the service often and behave in a way that helps the user or
business. Key metrics include adding more information to their profile page, checking the
news feed frequently or inviting friends to try the service.
• Monetization: Collecting revenue from users. It could include the number of people who are
paying for the service or the average revenue per user (ARPU).

Common Metrics for Ecommerce Sites


Acquisition

Daily sessions
Cost per acquisition (CPA)
Cost per click (CPC)
Cost per impression (CPM)
Top search engine terms leading to the website Mailing list click-through rate
Mailing list open rate
Mailing list conversion rate
Mobile app downloads

Activation

New registered users


Mobile app opens
Number of searches on website or app
New cart started
User information given (address, credit card, etc.) New customers with a successful purchase

Conversion rate
Recommendation engine conversion rate

Shopping cart abandonment Shopping cart size


Visits from activated users per month

Monetization

Revenue per customer


Lapsed customers
Purchases per year
Revenue per click
Cost of sale (ad spend / revenue) Customer lifetime value (CLV) Cost of shipping

Other

Average listing position on the Google search results page for the most important keywords

Cost of goods sold Shipping time Stockouts


Returns

Checkout errors
Number of reviews left by customers

Viral coefficient (number of users that each customer refers)

Market share
Customer engagement on social media Net or gross margin

Common Metrics for Mobile Applications Category Example


Activation

Number of accounts created, after mobile download

Acquisition
Number of mobile installs

Cost per install

Retention

Daily and monthly active usage Time in-app


Star rating
Session length

Percentage of users who rate the app

Monetization

Percentage who are paid users Lifetime value


Average revenue per user Churn

Common Metrics for Enterprise Software


Activation

New registered users

Acquisition

Leads Virality

Retention

Daily active usage Time on-site


Interval between logins Churn

Monetization

Conversions
Deal size
Renewal rate
Monthly recurring revenue Revenue per user

Revenue per lead LTV

Other

Uptime
Fav App Question

Okay, there are a few key design principles I use to evaluate products. These are
usefulness, understandability, efficiency, good user experience, and communication with
the user. To be more precise, let me explain what each principle means to me.

Usefulness. The product is useful if it solves the problem it purports to solve.


Understandability. The product is easy to use and is intuitive.
Efficiency. The product solves a problem efficiently or minimizes work for the user.
User experience. The product delights the user.
Communication. The product provides the necessary feedback to a user to dispel
confusion or avoid mistakes.

Whatsapp

2 billion MAU, 200 million DAU

◦ Pros
User-Friendly
Share Live Location
Listen To Audio Messages Discreetly
End-to-End Encryption
Reduce Data Usage For Calls
Ads Free
Free Of Cost
Starred Messages
Broadcast Messages
Delivery Status
Delete Sent Messages

◦ Cons
No Virtual Assistant – hike has it
Self-Destructing Messages - insta /FB has it
File Size limit 50mb
Video limit
Contact Number Required
No Sign-Out Option

◦ Suggestions
thread kind of feature like MS teams
old messages
mention everyone
pinning messages
sticker search
reminder/alert service
whatsapp api

Google pay

◦ Features
User-Friendly
Send and Receive Money via Audio ( Google Pay has introduced a new feature called as
Audio based QR system for sending and receiving money. In order to transfer money using
this feature one need to scan QR code appearing on screen while sliding the circle for
payment and receipt. It is claimed that ultrasonic wave is used to create one-time code for
digital payment. )

REWARDS DURING DIWALI GAMES

Google Pay has recently tied up with ICICI Bank, HDFC Bank and Kotak Bank for
offering loan on the move. If you are eligible you will directly receive loan offer on the app.

Ref : https://medium.com/stellarpeers/how-would-you-critique-a-products-design-
9b5b0092c355

https://docs.google.com/presentation/d/1zX0vUYaSGU5d52_Q-
BWVqWAZn50imLY5/edit#slide=id.g7d78c46301_1_0

You might also like