If we think about how we develop (or should develop) products, there are certain macro-steps we usually go through. A high level overview may look like this: We define a that match the business/company objectives product strategy and product goals We define , usually through research activities problems and who has those problems We define through discovery techniques the right solution We based on our goals and maximizing value prioritize We , delivering customer value in small iterations execute and develop the product During the last 8 years I have been working with product teams as they mature the way they develop products. And a common pattern is that we start developing our techniques and skills in the reverse order: First we move away from waterfall towards a more agile and “sliced” approach to delivering value. Then we improve prioritization with data-driven techniques, start saying no to stakeholders and avoid HIPPO decision making Later we start thinking about how we can build a solution that improves the impact of the initiative, and start working with prototypes and contacting users Afterwards we get more comfortable interacting with users and we move to deeper research techniques that help us understand the problem better. Finally that understanding of the user, the problem, the industry, let us became more strategic thinkers. I feel in some sense this is a normal emerging pattern. We and closer to what we can master, and when we nail that down we achieve by moving one step “up” in the process. start from what is closer to what we know we find that there is a better way to improve the impact Of course this are not the same “steps” in every company or team, but if you are leading product teams I would say that your job is to . make the team grow and mature in tiny bits but in the 5 steps at the same time Having a strategy, although a basic one will improve the chances of having successful products much more than being great at execution. Doing some discovery techniques are an invaluable input to improve the accuracy of your prioritization. I would love your comments! And if you enjoyed it, why not a little clap :) If you enjoyed it and want to receive more tools & tips to improve your product, you can subscribe here and join hundreds of readers!

Discovery

One of the most unmentioned factors of successful OKRs — Granularity

Product Developer: 6 skills that make developers shine in product teams and how to interview them

Download a section of my book Product Direction

Read My Stories

Too Long; Didn't Read

Download free Tech Leaders Productivity Report!

How do product teams evolve? Is it the best way to achieve high performing teams?

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

10 Challenges in Setting OKRs

10 Types of User Feedback You Need to Build a Better Product

10 Things To Do Right Away Before Starting Your Product Journey

9 Product Design Themes That Will Improve Your Product’s User Adoption, Your Team’s Design Process…

#Busted: 10 Laughable Myths About Product Designers

10 Challenges in Setting OKRs

10 Types of User Feedback You Need to Build a Better Product

10 Things To Do Right Away Before Starting Your Product Journey

9 Product Design Themes That Will Improve Your Product’s User Adoption, Your Team’s Design Process…

#Busted: 10 Laughable Myths About Product Designers

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps