Part of an occasional series of reviews from my product management bookshelf. Author: Jake Knapp, Google Ventures. thesprintbook.com Why you should read this book: Sprint is a recipe-like guide to running your own design sprint. Think of it as “Design Sprints for Dummies”. For those of you familiar with the…

Author: Michael Sippey, VP of Product, Medium.com Video URL: https://www.youtube.com/watch?v=DXVEiARMR1E Why you should watch this video: He’s an original practitioner wrt Product Discovery. He’s concise. His advice is timeless and cuts to the core of how Product teams should spend their time and energy. Don’t write the MRD, PRD, Jira…

Create the Company Culture that Wins by Focusing on Your Customers — I used the process below to personally meet with 100 customers per year. Including my team, we got into the hundreds. You don’t have to worry about reading customers’ minds when you can ask them good questions directly. Having the entire product team and engineering leadership meet weekly with customers…

Agile Engineering is pointless when you send ideas to the engineers without having user tested them — You have the best engineers that recruiter’s fees can find and you’re wasting their time. Untested ideas are the business equivalent of guessing. You probably don’t let your finance team guess at the numbers when closing the books. …

Create a User Experience Map as a “work smarter, not harder” technique to get Product Managers, Designers, Engineers, Subject Matter Experts and Customers on the same page. — Constant communication….Slack, email, text, video chat…does not guarantee that Product teams stay on the same page. Productive teams also don’t (and shouldn’t) write down every last detail. Making a User Experience Map together will create a shared understanding amongst team members that’s more valuable than the most well written user…