Everything you need to conduct better product discovery.
One of the hardest, yet most important, product management tasks is figuring out how to make decisions amid so many competing priorities. Product managers always deal with conflicting requests from customers, sales teams, developer teams, and customer success teams. Everyone has needs, and they often lean on the product team
In 2001, a group of software developers set off a revolution in the world of tech when they outlined a new way of managing product development—agile. At the time, older models of product management such as waterfall were becoming obsolete. In the unpredictable world of tech, faster and more adaptable
I met Jon Stewart once. He and the head writer of The Onion were promoting their new book, America (The Book): A Citizen’s Guide to Democracy Inaction, at Poets and Prose in Washington, DC. Now, this was before Aasif Mandvi and Hasan Minhaj became correspondents, and I had a plan
We recently wrote about interviewing customers to get beyond their initial asks to find out what they really need. In the article, we mentioned that the “5 Whys” is a popular and effective method for talking to customers. We also elaborated on how we use that framework. Of course, interviewing,
“When you’re a product leader, people look to you for answers. Why is the churn rate high? Why is feature X not being used? How do we get revenue up? And most importantly, what are we going to do to fix it all?” In our free eBook, The Path to
Jeremy Saenz, Kajabi’s Vice President of Product knows only too well how stressful the transition from a technical role like engineering to product management can be, and how that stress can manifest as a kind of impostor syndrome.
Hubert Palan is one of the more curious and enthusiastic people I’ve met in this lifetime. He’s also spent much of the past five years speaking with hundreds of product managers, trying to learn what they’d expect a dream all-in-one tool for product managers to do. So when I asked Hubert recently what piece of advice he’d offer PMs, he did what he often does — responded with a story…
I get asked this question a lot. Either because folks are hiring a product manager or because they want to get better at product management themselves.
We have recently been looking for some great design and engineering minds to join our productboard team. Having done hundreds of interviews in the past, I have been following my recruiting routine of screening candidates, asking about their past experiences, fishing for concrete examples of brilliance, drive, and leadership in their fields.
I want to forget, at least for now, the obvious need for a clear overarching vision, trust, accountability and a culture of cooperation. Without these, you will not build a great product no matter what, so let’s assume that these are in place. (Wishful thinking, I know, but let’s not go there now.)
Given the long history of myriad frameworks and methodologies, it seems like the customer, her goals, pains and motivations are besieged on every front. Everyone is trying to analyze her, everyone is trying to understand her, everyone is trying to learn how to satisfy her.
Now we are familiar with the various product management activities (product strategy, product development, and product marketing). As these activities become specialized and different people (or even distinct teams) take on each function, they align around the same goal of delivering a viable product customers will use and love. Everyone is on the same page when it comes to understanding who exactly the target customer is, what her key goals and pains are, and what solution alternatives are available to her. Nothing can stop them from building a product that will be a runaway success.