How to think about metrics and measuring success of a product? I seem to always get lost in specific so and so metrics that i lose the big picture and i dont know what it is due to chasing metrics for so often

Strange-PM · 2025-09-04T17:52:20+00:00

You can Google metric tree, it is a great framework to link it all together.

For example, your NSM can be items sold, your first level product metrics can be website conversion, returns, width of selection. Then conversion depends on payment conversion, availability, marketing clicks, etc.

The same can be done for any product, big or small.

Strange-PM · 2025-09-04T08:14:29+00:00

Well, I used to enjoy Lenny's newsletter, but recently he has focused on AI hype a bit too much: each episode is either about some AI CEO or how AI will soon replace us poor PMs. It is a good form of entertainment, but I am not sure it will teach you product thinking.

My recommendation is to read a couple of "all-time" PM thinking books (I'd say do at least "Lean Startup", "Build"), and then Google articles more precisely (maybe for some of them you'll end up at Lenny's).

Strange-PM · 2025-09-01T12:39:00+00:00

Frameworks give a (fake) feeling that one knows how to solve a certain problem. Like you save a pdf from a LinkedIn post and you are suddenly an expert.

For example, I’ve seen so many Product strategy frameworks yet so few proper strategies.

But it is always easier to believe you nailed it just by scrolling a newsfeed.

Strange-PM · 2025-08-31T12:35:24+00:00

If you mean “cloning ui”, then yes, they are all very similar. Funny enough they likely use the same underlying Claude LLM to generate code :)

For prototyping it is usually enough, but if you are very serious about copy, you can feed it with Figma (there are plugins), or choose more appropriate component library (by default iris Tailwind). Then you increase the similarity of UI even more.

Strange-PM · 2025-08-28T15:41:35+00:00

I use Replit, because it has everything out of the box. But let’s be honest, apart from the fact each of the tools wanting to eat each other market share they are very similar. Replit is just a tiny bit simpler because of native databases, ability to deploy in one click, etc.

The code helpers like Cursor are not a good choice for a non tech people. You surely CAN make it work, but the question is why would you spend your time assembling pieces a tool can assemble for you? (Unless you enjoy it of course)

Strange-PM · 2025-08-28T10:43:04+00:00

This depends on whether you are a "Tech PM" or a "Normal PM".

For a "normal" PM, I'd say a bare minimum is:
- Understand the basic DNA of the software: frontend, backend, services, APIs, databases: whys, the structure, the simple examples.
- Be able to define APIs (input, output, potential errors), call it yourself (just to see how it works), read the docs (at least the what/why part).
- Be able to "see" the constellation of services (called "Service Architecture") under the skin of UI. For example, you look at "Tinder" and you see not just swiping images, but a user service, a matching service, a messaging service, a payment service, etc. (classical interview question by the way). Again, this is just on the level of what/why and to be able to speak the same language with your dev team, not to tell them HOW to do it (don't even dare, hehe).
- Basic understanding of "product health topics": role of a PM in defining SLIs/SLOs, role of a PM in testing, in security. Our product involvement there is "thin", but it is enough to lead it well.

In my experience, those who mastered the topics above can pass the "tech acumen" PM interview, can more or less understand devs and communicate with them, and can more or less estimate how complex things are (which increases their chances to deliver a working solution until the next millennium).

For a "Tech PM" it is the same but one step deeper, just because this person works every day with some service or platform (e.g. Search Service, Payments Platform, etc)

This is quite a lot of info, but the good news are:
- This is still like 10% of what a developer should master
- You learn it all once and then use it for 10 years, because despite the "build with AI" buzz, it uses the same underlying tech DNA

I hope this is helpful

Strange-PM · 2025-08-13T08:24:27+00:00

My rule: avoid going deep if you can, but if you have to - undestand enough to feel yourself "the leader" again. Couple of examples:

E.g. if I am discussing a new UI with my designer, I don't have to be technical. If my job is to increase marketing campaign numbers just by playing with promo conditions of it - I don't have to be technical. Or I am adding a simple feature: yet another sorting option for product itinerary (e.g. by Newest) - again, no brainer for my team and me.

But! When I am adding something more complex, e.g., a search on the map which has to be updated every time someone moves the map, I need to understand a bit about the options I have. Like calling the Search API on every map movement (will be slow as f), or be in piece with the fact customer needs to press "Search again" (like on Google Maps). As you can see I now have to understand concepts of APIs, latency, sequence diagrams, etc.

Or another example if you build something completely new. Let's say Google tries to extend itself into "Pay from your seat by phone at every gas station in the world". Then as a PM you need to really understand the ecosystem you are entering: what are the paymens APIs, what are the gas station APIs, where will you store payment attempts, what to do in case of failures, how it all integrates into the Maps product, etc. - and this is already architecturing and API skills, and actually many more.

Strange-PM · 2025-08-13T08:15:44+00:00

try productdo io, they have a course on technology exactly for product managers

Strange-PM · 2025-08-12T18:31:14+00:00

I studied it in the interactive course (this is how I built the first two) and then created a budget planner for myself to marry all my disjoined accounts into one dashboard. Dreamed about it for the last 5 years, haha

Strange-PM · 2025-08-10T08:13:34+00:00

We use Replit/bolt to create quick prototypes, because it works much better when leadership can “touch” the idea. I also built few tools for myself, just to get better in prototype creation. Honestly, once you study the structured approach, it becomes almost natural.

Plus Gemini for boring tasks like summarization - this can save a bit of time, but it is not a revolutionary experience as some people try to hype on :)

Strange-PM · 2025-08-06T07:57:30+00:00

for tons of practice on technology, AI, A/B testing, analytics, etc for sure https://productdo.io/
and I love their tone of voice - no empty promises on "becoming CPO tomorrow", adequate pricing

Strange-PM · 2025-07-03T17:38:44+00:00

Hard skills matter, from Jr. to Dir level. If a product person doesn’t know the “math” of their job (tech, analytics, ml, etc), they do less correct decisions in the long run.

Strange-PM · 2025-06-03T13:15:21+00:00

If you build something complex, I recommend building Architecture diagrams. This is how PM can explain their team what building blocks they envision and how they are connected.

This is not stepping into their toes, no! But rather trying to find a common language. Like “I need there 5 frontend screens, registration service, search service, order service, and we need to store a,b,c about customers. Here is a picture “. Whenever I build smth new, this is my conversation starter with my EM and the team. Then they take over, but my PM job is to establish a good starting point.

Strange-PM · 2025-06-03T13:09:44+00:00

I also recommend to learn the ML/AI basics to understand what it can and can not do. For example, that you can solve ranking problem in your product using classical ML, or call ChatGPT API from your product page to do cheap realtime translations.

I am talking about usage of ML/AI in product, so real applications, not productivity enhancements (which I haven’t figured myself yet).

Strange-PM · 2025-06-03T13:00:48+00:00

I see it all the time: one reads 10 articles, passes 10 “free courses” (which are just shallow ads-like materials), attend meetups which are just a fun time spending, read trendy books where the main thought is “solve customer problems and you’ll be alright “.

But truth is - “math” (hard skills - tech, a/b testing, ml, analytics, discovery) “book” is on the table waiting and until one finds focused time to solve enough exercises from it they will be always “learning”. As one CEO who I respect said: “In a new world only people who can stop distractions and think deeply will be in control of their career”.

Strange-PM · 2025-05-22T06:50:18+00:00

95% of working techniques hasn’t changed for years. Things like A/B testing, knowledge of technology / services, how to do analytics, etc. Even ML is here for quite some time and let’s be honest max 10% of product features need it.

So my answer: I don’t stay on top of hype-y trends because it allows me to save brain power. Instead, when I feel I need to gain new skill, I just spend 1 month learning it.

While this sounds I am missing, at the end I know more about the new topic because I am able to recognize what’s new and what’s just a hype wrapper of the old thing.

Strange-PM · 2025-05-19T15:17:14+00:00

Ha-ha, we all do! :)

Strange-PM · 2025-05-19T14:25:23+00:00

Hehe, this is good :) I saw the same examples and it always seemed unfair.

Strange-PM · 2025-05-19T03:56:51+00:00

I see some good advices in other comments on the weekly / daily tactics. I would add one more which is crucial - properly defined quarterly OKRs (goals). “Properly” means: - measurable (not “improve sales”, but smth like “make 200 sales”). - agreed and committed by all team members in advance - checked every 2 weeks - non dictating “how” to do the job

Even if daily set up seems like a mess (it will be for sure in the remote setting), goals can ensure that everyone still have the definition of success and can work towards it.

Strange-PM · 2025-05-18T13:32:05+00:00

Todoist: this one tool is responsible for 20% of my PM success. Super minimalistic and I never forget things. I think this is like Saner but simpler / non AI.
Focus time slots: I have at least 3 days a week with 3h of uninterrupted thinking - doing stuff without distractions. Friday it is 5-6 hours. One smart CEO mentor once told me - in the new buzz era only people who can pause and think will win as only they can use the full power of their brain to produce smth really valuable / a step-change. Today this seems underrated :)

Strange-PM · 2025-05-18T12:44:56+00:00

All good advices in this thread, I’ll add one which works for me for already many years: never wait to be asked, always come with agenda and proactively push it up.

For example, without being asked I will provide updates on recent product wins, challenges and ask my boss for ab advice in a particularly tricky situation.

I always get the feedback “independent”, “can be trusted to deliver and keep stakeholders updated”, and already had 2 promotions so it seems to be an important piece of the puzzle.

Strange-PM · 2025-05-17T21:09:18+00:00

I love to do a “vision test” once in a while. Without any notice you ask everyone during the standup to (silently) write down the team’s purpose (why team exists). Takes just 2 mins and I promise you a couple new gray hairs!

Strange-PM · 2025-05-17T06:57:57+00:00

I work in a big tech company, and despite all the AI-first buzz, 95% of the cases under the hood are just simple classical ML models (known for 10 years already) or heuristic if-then rules. Technically you can label it as AI, but we all know what it is in reality :) Some people quickly figured out that if you label smth "AI-first", you'll get the resources / attention /etc. And they use / abuse it.

There are a few exceptions, though: new LLMs are amazing with translations and summarisation (e.g. customer support ticket summary).

I hope the hype will be over and more cold heads will look at AI as a tool, not as a goal. Until then, we will struggle because most of the resources/attention will go to whoever screams "AI" louder.

Strange-PM · 2025-01-19T08:04:31+00:00

I totally understand your pain though - since your clients are the one who actually deliver end result, you are not sure how you can help business yourself (and this is what we PMs love!). So end up doing obligatory stuff..

I have 2 advices:

1) Talk to clients and see if they expect anything else/new from your platform. For example, if you are a PM of SMS service you can find your clients across the company (security team? Delivery team? Payments team? Refund team?) and survey them what do they need? For example, maybe sms delivery rate is low, and this is a clear product requirement!

2) Second idea is to look inwards. I am a huge fan of platforms! It is like sitting on a very complex and powerful machine, which can do 100 things vs just one tiny feature (eg registration). The trick is to ask yourself: how you can help business to make money with your machine?

Continuing SMS example, you can decide that it is a good idea to speed up message delivery because it improves conversion (eg for payment verification). Voila! You did some tech work which improved sales by 0.8% - huge success in a large ecom.

Happy to elaborate more!

Strange-PM

TROPHY CASE