Product Sense/Design Interview: PAIN POINTS (Part 3)

แชร์
ฝัง
  • เผยแพร่เมื่อ 26 ส.ค. 2024
  • 👩‍🎓 Book 1:1 Coaching With Me! 🧑‍🎓 @ calendly.com/d...
    Most PM interview candidates STRUGGLE to come up with good user pain points in the product sense PM interviews. Here are the best practices on coming up with outstanding painpoints.
    👋 Connect With Me 👋
    ► LinkedIn: / diannayau
    ► Blog: diannayau.subs...
    ► Discord: / discord
    ► Linktree: linktr.ee/dian...
    🎓 Interview Questions, Company Guides, Mock Partners 🎓
    www.tryexponen...
    📚 Books to Prep for Product Interviews & Careers 📚
    www.amazon.com...

ความคิดเห็น • 43

  • @diannayau
    @diannayau  ปีที่แล้ว +1

    🤩Comment below: ✍what pain points do you suffer from when trying to find doctors?
    🥴Struggling with product interviews? 🚀Book 1:1 COACHING @ superpeer.com/dyau

  • @Anonymous_moron
    @Anonymous_moron 2 ปีที่แล้ว +12

    Hey Dianna - your content is incredibly useful, and I wish your subscribers and views reflected it. I have an upcoming interview that has a Product Sense component, and your videos have been invaluable in my study. Your content is great, incredibly well structured, and I really appreciate your communication style. Wishing you the greatest success! I just want you to know today that your content has really, truly benefited a stranger out there, and someone is incredibly grateful for your contribution today :) Keep up the awesome work.

    • @diannayau
      @diannayau  2 ปีที่แล้ว +1

      thank you for the kind words and making my day! Stories like these are what keeps me going despite barely having much time to work on the channel. Will keep growing this so more people like yourself get to benefit from it! Thank you for your support!!

  • @calmrelaxationmusic8856
    @calmrelaxationmusic8856 2 ปีที่แล้ว +3

    Dianna : Wow, your content is super awesome. People have already given you a lot of praise in the comments. Your channel needs to have more views. Just want to thank you for the efforts

  • @oots_
    @oots_ ปีที่แล้ว +1

    I love how you don't mention your company now and then to gain followers or sell yourself. it's your amazing content that speaks.

  • @masha3365
    @masha3365 ปีที่แล้ว +3

    You didn’t mention how did you pick user segment, why this group? In the previous group you only gave them scores

  • @user-hn3zq9pw5z
    @user-hn3zq9pw5z 10 หลายเดือนก่อน +1

    the toughest part is building the creative muscle in the spur of the moment under interview tension :)

    • @diannayau
      @diannayau  10 หลายเดือนก่อน

      Yes you’re so right! That’s why we gotta drill it so many times so it becomes a stronger muscle

  • @ishanvirdhi6713
    @ishanvirdhi6713 5 หลายเดือนก่อน

    This is gold ! Thanks a ton for the quality content

  • @efrattalmon4523
    @efrattalmon4523 6 หลายเดือนก่อน

    thank you so much for the great content! your clear and concise answers are super helpful!!

  • @islandcoma
    @islandcoma 2 หลายเดือนก่อน

    thanks for your videos. besides communicating the approach which can be generic, what if the subject matter is outside someones experience or knowledge. how would you approach that? just stick to the process you would follow or communicate the process + make assumptions on the rest?

  • @Amy-rt9hq
    @Amy-rt9hq ปีที่แล้ว +2

    Hi Diana! Great suggestions for empathizing as a consumer but any tips for how to identify pain points for SaaS products?

  • @anmolrastogi2884
    @anmolrastogi2884 2 ปีที่แล้ว +9

    Hey Dianna, This is all great information. However, at times I feel that in a 45 mins interview, you only have 20-25 mins to run through a case end to end keeping introductions and time to ask questions at end. There is lot to cover in a case from mapping landscape and designing solutions. How can one manage time throughout the process?

  • @WorldExploration-qq8vn
    @WorldExploration-qq8vn 3 หลายเดือนก่อน

    How do you demonstrate these ranking sections on the interview? is it just by stating each scores or delivering a overall thought process?

  • @rahulsr5731
    @rahulsr5731 2 ปีที่แล้ว +1

    (1) List all pain points - Prioritizing Pain points - select 1 or 2 top pain points - brainstorm features for those pain points - prioritize feature.
    (2) List Pain Points - Brain storm feature for all - Then Prioritize based on impact/effort etc
    which method works better ?

    • @diannayau
      @diannayau  2 ปีที่แล้ว

      (1) is going to help you save time

  • @junqichen6241
    @junqichen6241 3 ปีที่แล้ว +1

    Thank you for sharing! Great content!

  • @YourJustin
    @YourJustin 10 หลายเดือนก่อน

    Really appreciate the content Dianna! Did you create the background music with that guitar?

  • @productmanagementbyutsav3069
    @productmanagementbyutsav3069 3 ปีที่แล้ว

    Your videos are very nice , please make more of them .thanks Dianna

    • @diannayau
      @diannayau  3 ปีที่แล้ว

      Haha I will try! Doing this on top of my full time PM job :p

  • @amirfakhim7797
    @amirfakhim7797 2 ปีที่แล้ว +1

    Hi Diana, Thank you again for the great video. I have a follow-up question. When you started you identified all the stakeholders in the ecosystem. However, you just focused on the patient side. This is multi-sided case. Don't we need to analyze, segment, find the pain points for the other users in the ecosystem?

    • @diannayau
      @diannayau  2 ปีที่แล้ว

      great question amir! I prioritized the patients and went deeper there and because I prioritized them, I didn't need to waste time going into painpoints for the other users

    • @amirfakhim7797
      @amirfakhim7797 2 ปีที่แล้ว

      @@diannayau do we have to go in the real interview?

  • @kumarrishav1641
    @kumarrishav1641 3 ปีที่แล้ว

    Great Video ! 👍

  • @apekshagupta9127
    @apekshagupta9127 ปีที่แล้ว

    One question here, how do you justify choosing "users requiring speciality doctors" as a segment when in the previous video "users with chronic illness" ranked higher as per your chosen criteria and scores.

  • @ninth_of_november
    @ninth_of_november 2 ปีที่แล้ว +2

    Why do you multiply pain points instead of adding them up?

    • @aishr11
      @aishr11 8 หลายเดือนก่อน

      Does anyone knows the answer to this?

  • @OnionKnight541
    @OnionKnight541 2 ปีที่แล้ว +1

    How did we prioritize the User that we found the pain points for? Or is User not applicable in this situation?

    • @diannayau
      @diannayau  2 ปีที่แล้ว +1

      I use criterias such as Total Addressable market, and frequency of use. You'll find another video in my playlist that teaches how to come up with and prioritize user segments :)

  • @AIEthicsOrg
    @AIEthicsOrg 2 ปีที่แล้ว +1

    Hi Dianna, thanks for the great video. How would you go about accurately mapping out the user journey in a case where you have never experienced the situation you're being asked to build for (e.g. Finding a lawyer or building a product as PM for Instagram Reels) ?

    • @diannayau
      @diannayau  2 ปีที่แล้ว +1

      Yesss this is a question I get a lot! Stay tuned for the next video on product sense, in short-you’ll want to either think about if a friend or family member has experienced it or if you had to go do that thing tmrw, what steps would you take?

    • @mshibinz
      @mshibinz ปีที่แล้ว

      @@diannayau can you tag the video where you've answered this, please?

  • @vishalshah9619
    @vishalshah9619 11 หลายเดือนก่อน

    In pain point prioritization, you didn't mention relating the pain point back to objectives. Why is that?

    • @diannayau
      @diannayau  11 หลายเดือนก่อน

      Good point! Would recommend connecting it to the above objectives- if you want to get even more advanced I’d recommend calling out a metric here and using that to prioritize

  • @sabogo619
    @sabogo619 2 ปีที่แล้ว

    Hey Dianna,
    Thank you so much for your content, it’s been a great prep resource for me. My question is if you are asked to design a product that competes with an existing product, do you have to go in depth to talk about basic features as prt of MVP? Or are those kind of implied and you should focus on differentiating features?
    For example, if I am asked to design a maps app for Meta, should I think of out of the box features and painpoints? Or should I still consider the basic flow of using google maps for example?

    • @diannayau
      @diannayau  2 ปีที่แล้ว

      You’d want to think of existing painpoints that aren’t solved by google maps to differentiate your answer vs. just rebuilding google maps

    • @sabogo619
      @sabogo619 2 ปีที่แล้ว +1

      @@diannayau thank you so much! Really appreciate the content you are providing here :D

  • @junqichen6241
    @junqichen6241 3 ปีที่แล้ว +1

    Hi Dianna, for this type of product design questions, do we need to define success metrics?

    • @diannayau
      @diannayau  3 ปีที่แล้ว +1

      It depends on the company but usually for product design questions, no you don’t need to cover metrics unless they explicitly ask.

  • @Only1Swami
    @Only1Swami 2 ปีที่แล้ว

    keep up the amazing videos...you'll have 100k subs in no time
    you mentioned at the end "start with the criteria, then pick your pain points" - didn't we kind of do the reverse in this example? you went into the 4 pain points in detail, then stated the criteria, then we multiplied. I could be misunderstanding but would love any clarification. Thank you!

    • @diannayau
      @diannayau  2 ปีที่แล้ว

      Thank you for all the support! The painpoints process is 1) go through pain points 2) share criteria for prioritization 3) then prioritize

  • @martinc2604
    @martinc2604 2 ปีที่แล้ว

    HI Dianna, just wondering - do you think it makes sense to sometimes switch around pain points for opportunities, objectives, etc.? Or would say the User Journey > Pain Point framework works for all product sense questions? It saves a lot of time and effort with the consistent framework, but wonder how adaptable we need to be to avoid maybe sounding too rigid? Thanks for your help!

    • @diannayau
      @diannayau  2 ปีที่แล้ว +1

      i'd recommend sticking with user journey & painpoint :) you'll only sound rigid if you're JUST using the framework without depth in your response related to the prompt