In our earlier episode about how to answer the “product teardown” question in a product manager job interview, we promised a real life example. Here it is! I’m not going to tell you the product – you have to listen to find out.
As you recall, our basic guidelines were the following. Take a listen and see how well we lived up to our theory:
- Get organized – go into your interview with some ideas in mind about how you will use your favorite frameworks for thinking about product
- Set up your assumptions about the product, such as personas and identify the goals or the “job to be done” by the product.
- Go through a process to identify a potential solution using your preferred process – design thinking, jobs to be done, etc.
- Extra credit – identify why they might not have built this new feature so far, and how you might justify the investment.
A few interesting links
In the conversation we discussed a few concepts you might want to read more about (if you’re like me):
- Transclusions – Wikipedia article, Ted Nelson’s Dream Machines/Computer Lib (Wikipedia article, some excerpts (PDF))
- Doug Engelbart, inventor of the mouse as we all know, but also inventor of Augment (Wikipedia page, the seminal paper)
- An interesting talk by Phil Libin