Lukas Pleva

There are countless product management prioritization frameworks available, such as RICE (Reach, Impact, Confidence, Effort) and MoSCoW (Must have, Should have, Could hav...

One of the benefits of working with a mature product is that you likely have access to a large pool of existing users from whom you can solicit feedback. In contrast, new...

I tend to focus on two groups of indicators.First, did we deliver a delightful user experience that added value to the customer? My go-to for answering this is Google’s H...

Most roadmaps indeed focus on both. The balance of prioritizing prospects versus existing customers will depend on the business objectives your product roadmap is designe...

I'm a big fan of publicly available roadmaps. They provide current and prospective customers with insight into where you plan to focus and serve as a great resource for S...

It depends on who the other team is and what I expect them to do with the information.If it's another team that I depend on to execute my goals, I'll share more details. ...

Creating a product roadmap is fraught with challenges, regardless of whether you’re working on a new/growing or a mature product. That said, when dealing with mature prod...

This is a gross over-generalization, but in my experience, there are two kinds of product development cultures:Sales-led, where you build what you sell.Product-led, where...

The unsatisfying, but honest, answer is “it depends.” As a general principle, addressing tech debt should be a continuous consideration. Without it, you put your product’...

It’s common to assume that mature products have a static, well-defined persona. However, product teams should aim to continuously challenge and pressure-test that assumpt...