Tools

What is your go-to framework for product success?

We all have that one book, article or talk that opened our eyes and helped us build better products. What's yours?

  • Senior Product Manager at busuu

    The Design Sprint (care of Jake Knapp at Google) is a framework I've used many times. Originally a 5 day process that takes you from discovery all the way to testing with actual customers I've found it best to take the parts you need from the process and merge them with other helpful processes.

    For example, we will often fit a design sprint into 3 days. The intention of the design sprint has always been to have a working prototype to test with users quickly to validate ideas and solutions.

    If you bring in some other helpful frameworks like User Story Maps (by Jeff Patton) it can add another layer of understanding and detail about what you really need to work on and what can be left until later.

    And then the great thing about the design sprint is it just allows you to get much better at certain techniques. For example, if you want to hammer out a few ideas for a couple of hours on any project, take the solution sketching approach and you can just do that.

    And because you will have a team in the room with you from varying disciplines it not only allows for fantastic ideation and different view points, but it shares understanding of a problem which is the fundamental basis for delivering a successful product as a disciplinary team and really avoids potential confusion later on.

    I'd also recommend you look at...

    Ask Stephen a follow-up question!

    Ask a question
  • CEO/Product at OnCare

    The book 'What Customers Want' by Anthony W. Ulwick is my product BIBLE.

    I've used the process described in the book (or a slightly lighter touch variation) to build every product I've ever worked on, including my own startup

    The best part is that it forces you to speak to actual people for whom you wish to solve a problem as a starting point. Anyone who calls themselves a Product Manager but doesn't do this, and just does desk research, is not a Product Manager – they're at best an analyst and at worst some person with an opinion. Beyond that, the book gives an easy process to discover, as the name suggests, what customers want, even if the customers didn't realise themselves.

    Ask Alistair a follow-up question!

    Ask a question

Post your tip

Have something to add to this? We'd love to hear from you!

Post a tip

More tips like this...

People & Teams
How do you conduct effective 1:1 meetings with team members?
When do you choose 1:1 meetings as opposed to team meetings? What's their role, and how do you make sure they achieve the intended result?
People & Teams
How to establish if someone is a good fit for your team?
Skills and experience aren't the only factors to establish if a candidate will do well as a team member. How do you check for 'team culture' matching?
People & Teams
How do you keep your design team members growing?
Do you consider your company design led? Design is at the centre of every experience we create. So how do you ensure your design team has a path to improve, up-skill and deliver even more value?
Product Management
Explain 'Product Management' to your grandmother. Go!
You're at a family dinner. Your grandmother is asking: "What is it that you do, exactly?" Explain your role to granny, and help others demystify their job to their family too.