Speaker unverified: commitment

Transcript context

…And then what do you look for in an answer there? Like what are a couple of bullet points of a good answer to that? A lot of it, I mean, it's so different for every question, but I'm definitely looking for, I try to get something recent. So I want it to be something that like matches the level that they're applying for, right? So there's going to be a really big difference between the way that an APM answers this question and the way that a director of PM answers the question. I look to see how did they think about strategy? What was their judgment on different choices? What was hard? I have a framework for this. So this is the PEARL framework for answering questions like this is problem, epiphany, action, result in learning. So it's a little bit like the STAR framework, but I kind of want to know like, what's the problem that you thought was worth solving? Is that a problem that I think is big enough? What's your epiphany? What's the insight that you had? Do you notice something that nobody else did? And how valuable was that? So a lot of times that's what makes these PM stories so interesting is that like, Meeting with customers head on and they said one weird word and you dug into it and you learned this whole new customer need that no one else had seen before. And then there's going to be the action, like what did you actually do to make this happen? And was it hard? Because usually it is hard, but understanding the ways in which it's hard and how you overcame each of those challenges. And then I like to, obviously, PMs should care about results and be picking. The thing they pick that they're proud of should have good results or have at least results that they learned from. And then, yeah, that last part of learning, did you grow from this? Especially if it's a failure, which is like lots of people love to talk about the products that failed or sometimes the interviewer asks them to talk about a product that fails. But I don't want them to leave it at like, yeah, it was a big loss. Our company lost $50 million and we couldn't get it back. But then you want to say like, okay, but what I learned from that is now I need to always run a load test on a staging server constantly. And then I've had many successful launches since then that we like didn't have that same problem in. Wow. What a fruitful lightning round. So many nuggets. We've got a new framework in there too. Okay. Where can folks find you online? And then any last words of wisdom?…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.