Virgilia Kaur Pruthi (she/her)

Virgilia Kaur Pruthi (she/her)Share

Principal PM Manager / Product Leader, Microsoft
My goal is to help you grow as a product leader, whether you're trying to get a job, level up, build an effective team, or figure out how to work towards that north star vision.
Content
Virgilia Kaur Pruthi (she/her)
Principal PM Manager / Product Leader, Microsoft | Formerly AmazonJanuary 31

Creating the right mechanisms to manage your stakeholders is critical to managing up and across. Allowing your stakeholders to stay on the pulse of your product while having access to updates really helps in building trust. Creating mechanisms like brownbag/learning sessions on a frequent basis (weekly or biweekly basis) also helps in creating an open forum. Then you can focus on protecting your engineering/design team and enabling yourself to scale.

Virgilia Kaur Pruthi (she/her)
Principal PM Manager / Product Leader, Microsoft | Formerly AmazonJanuary 31

I'd love to learn more about what you mean by this. In reality they shouldn't change, your customers would just be internal that's all. You could still measure activation, activation, retention, engagement, resolution time, etc. On the other hand, you could measure self help vs. those who still asked for support or metrics lik elatency.

Virgilia Kaur Pruthi (she/her)
Principal PM Manager / Product Leader, Microsoft | Formerly AmazonJanuary 31

It really depends on what type of business it is. For instance, a product feature or product should be so frictionless that it allows users to onboard (adopt) easily once they are in the experience. Product marketing is responsible for bringing users to that experience. So it is almost eyeballs vs. activation. In reality these metrics should be shared, and over time broken up where the tech is meant to solve for the customer's need.

Virgilia Kaur Pruthi (she/her)
Principal PM Manager / Product Leader, Microsoft | Formerly AmazonJanuary 31

This is a hard one as I am sure there are a ton of layers to unpack here. Whenever there is a question around metrics, I would first look to the customer and understand what customer pain points your product area is solving for. Then see how those needs and your business goals align, and how your specific area can help solve for that. If it is a matter of stakeholder management that is a different story, but engineering, product and design should really have shared KPIs.

Virgilia Kaur Pruthi (she/her)
Principal PM Manager / Product Leader, Microsoft | Formerly AmazonJanuary 31

Wonderful, congrats!

Get into a rhythm by understanding the business/company goals. Then understand how the tech works (look at the customer/user interface first and then make sure you understand how the system behind the UI works). Begin collecting data in a transparent way and share your learnings with your stakeholders and leadership.

Conduct user research (both qualitative and quantitative) to help illustrate what product areas (epics/themes) you want to focus on and how these connect back to the business/company goals.

Virgilia Kaur Pruthi (she/her)
Principal PM Manager / Product Leader, Microsoft | Formerly AmazonJanuary 31

Such a great question! When you first set a KPI especially if you are in a new market and/or in a new product/customer space, it can feel uneasy. The best way I have learned is by setting something and tracking it over time, seeing if there is any measurable change. If not start by marking out the customer's journey (no matter who they are) and see if you can collect data on their interactions along the way. This may reveal some hidden trends you weren't yet measuring.

Virgilia Kaur Pruthi (she/her)
Principal PM Manager / Product Leader, Microsoft | Formerly AmazonJanuary 31

Don't think of it of what you should and should not own. Think about what makes sense to the customers you are focusing on. Then think about where you are in the customer/product lifecycle and product/market fit. What does the overall business care about at this time (e.g. retention vs. acquisition) and start seeing how your product area could contribute back to that overall goal.

Virgilia Kaur Pruthi (she/her)
Principal PM Manager / Product Leader, Microsoft | Formerly AmazonJanuary 31

Product teams in my opinion consist of product, engineering, and design (at a minimum). With that said, product KPIs should always be shared with engineering since what they are building essentially impacts the KPIs of the product in question. All the work that product teams do should always build up back to the overall company/business unit objectives (even if those metrics are more technical).

Virgilia Kaur Pruthi (she/her)
Principal PM Manager / Product Leader, Microsoft | Formerly AmazonJanuary 31

This could really range based upon the company, your users, your target goals, where you are in your business lifecyle, etc.

The most basic ones are: acquisition, activation, retention, revenue, referral

You could also be measuring customer lifetime value. 

Again this will really depend upon what type of business you are in.

Virgilia Kaur Pruthi (she/her)
Principal PM Manager / Product Leader, Microsoft | Formerly AmazonJanuary 31

This could really range based upon the company, your users, your target goals, where you are in your business lifecyle, etc.

The most basic ones are: acquisition, activation, retention, revenue, referral

You could also be measuring customer lifetime value

In regards to the worst KPIs, honestly those that cannot be discretely measured and tracked over a specific time period. Vanity metrics (e.g. the number of views from a marketing article or number of shares of a post) really add no value.

Credentials & Highlights
Principal PM Manager / Product Leader at Microsoft
Formerly Amazon
Product Management AMA Contributor
Lives In Seattle, WA
Knows About Building 0-1 Products, AI Product Management, B2B Product Management KPI's, Building ...more