by bmj1 on 2/24/13, 6:14 PM with 37 comments
by sardonicbryan on 2/24/13, 8:37 PM
For people with PM experience, I'll ask them about the things they considered and documented in their last spec. If they think a spec is a list of bullet points, that's instant fail. If they considered all user flows in and out of the features, edge cases, user education, analytics/success metrics, release plan and time vs cost tradeoffs that's a win.
by hammerzeit on 2/24/13, 8:01 PM
* How does this person deal with vast uncertainty? Are they excited? Scared? Is their first reaction to impose structure or are they comfortable with lack of structure? If it's the latter, can they meaningful convey confidence with the lack of structure?
* Can this person teach? Can they figure out how to take an abstract idea and articulate it cleanly? When someone doesn't get it, at what point do they fall back to utilizing authority? Are they good at listening closely to what someone is saying to them and framing an argument in their terms?
by dps on 2/25/13, 4:11 AM
The time I flew on the Enron corporate jet to meet Jeff Skilling https://www.kennethnorton.com/essays/enron.html
and I have been referencing this for a couple of years: https://www.kennethnorton.com/essays/leading_cross_functiona...
by nicw on 2/24/13, 9:58 PM
Goes out in person(!) and talks to customers.
It's very easy to add new features to products, but until you sit down with a customer, listen to them, and watch them use your product you won't have a clear understanding of their needs. Good product managers realize they are very close to a product and need to constantly take a step back.
If you're skeptical, sign up for a UserTesting.com account and watch people navigate your site. You'll be surprised.
by metalsahu on 2/24/13, 10:59 PM
Designers, Engineers, Sales perform well when they have deep narrow focus and goals. The Product Managers' job is to allow them to excel in their specialist role much like the conductor of a multi-piece orchestra.
by joonix on 2/24/13, 8:36 PM
by michaelw on 2/24/13, 7:16 PM
Product management is particularly important in non-software companies where the obvious product isn't software. Your e-commerce website is just as much a product as your hipster glasses. Failure to manage it results in the classic IT dept. dysfunctional relationship where everyone hates IT and IT develops a thick skin and says no a lot.
by msutherl on 2/25/13, 7:57 AM
I've been toying with the idea that I'm cut out to be a product manager and this just convinced me.
Also this:
"In fact, that's the first test - how do they react when I say 'I'd like to pose some theoretical problems, is that okay?' The best of the bunch are usually bouncing out of their chairs with excitement. The super smart sometimes counter with questions of their own."
Asking me this alone would make me substantially more interested in the job.
by pinaceae on 2/24/13, 10:26 PM
i do not believe in generic pms. experience in pre-sales, consulting, development, something product related is so important, it builds up that spidey sense.
by jbl on 2/24/13, 8:26 PM
There's a lot in Ken Norton's post, but it's all worth taking to heart. Now, if someone could point me to a good article on interviewing PMs...
by xfax on 2/25/13, 1:12 AM
I'd love pointers to other such great resources that shed light on what makes a good, no great, PM.
by arocks on 2/24/13, 7:19 PM
by wangg on 2/25/13, 12:31 AM