All related (6)
Nico Rattazzi
VP of Product at Zumper
My CS degree itself was not that important but my CS background and experience as a software engineer was critical to my success. Learning to code, understanding web frameworks, knowing the process for software development, and making tradeoffs between complexity and impact really help provide effective solutions for the organization. Granted, you can have an incredible tech lead but that won't always be the case. I believe that if you're working on a digital product, it helps to have some technical understanding to ensure you're working with the development team responsibly. Also, really h...more
Virgilia Kaur Pruthi (she/her)
Principal PM & Product Coach at Microsoft | Formerly Amazon

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.

Tasha Alfano
Staff Product Manager, Libraries and SDKs at Twilio

The worst KPIs to commit to are the ones you can’t commit to at all. We can set targets and metrics and make dashboards, but that’s exactly what they are - targets. I recommend looking at past performance and trends within the data and setting a realistic yet aspirational target to work towards. After that, begin iterating on your target. Revisit the KPI, analyze, adjust, and communicate your findings.

Nico Rattazzi
VP of Product at Zumper
Product, Engineering (and even design!) should ensure the majority of the user's experience is measured (engagement, conversion), the platform is functional (speed, etc), and that the company's key metrics are preserved.  A big miss that comes up between product and engineering is when there is confusion around a product experience. Product Perspective: "This is not working as expected. This is a bug" Engineering: "This is what I was asked to build. It's working as specified" This will happen from time to time based on how mocks, specifications, or flows are interpreted. The best KPI her...more
Farheen Noorie
Director of Product Management, Growth and Monetization at Zendesk
Product Management is a bit hard to list skills for because product managers wear so many different hats and each company has a different way on how they think of product management. But I do think there are some broad skills that PMs should have or build as they think of their career.  1. Hustle - This is the number 1 skill that I look for. If you have this everything else follows or can be built. 2. Empathy - Understanding your customer and being able to put yourselves in their shoes 3. Storytelling - Communication is key for product managers but I think its super importan...more
Paresh Vakhariya
Director of Product Management at Atlassian
Some of the worst KPI's in my opinion are: * KPI's that cannot be measured correctly * KPI's that do not give a sense for the goal you are tracking. You can use the AARRR (Acquisition, Activation, Retention, Revenue, Referral) framework to understand the best metrics you can choose to align with your outcome/goal. * KPI's that are not achievable in a desired timeframe. Yes there could be exceptions here but generally these are not the best ones in my opinion. * Any KPI's that do not really tell you the health of the business unless a holistic picture is presented. e.g. numb...more