Keeping a product successful can be tricky: New features have to be developed to ensure that the product stays beneficial and attractive. At the same time, smaller improvements and bug fixes are required to maintain the product. How can this be done? This post shares my answer how to balance innovation and maintenance work.
Learning what a product should look like and do, and building solid, shippable software are different concerns. Separating the two aspects and distinguishing between learning and execution helps you manage the stakeholder expectations, select the right research and validation techniques, and choose the right sprint goals.
This article provides practical tips on how to use the product demo as an effective product validation tool: collect helpful user feedback, test your ideas, and improve the product.
Working with a sprint goal is a powerful agile practice. This post helps you understand what sprint goals are, why they matter, how to write and how to track them.
This post explains how to write user stories at the right level of detail, and how to derive small, ready stories from big, coarse-grained epics.
“This is your last chance. After this, there is no turning back. You take the blue pill – the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill – you stay in Wonderland, and I show you how deep the rabbit-hole goes,” says Morpheus to Neo in the movie “The Matrix”. This quote reminds me of the choice we face when dealing with a new product idea: Should we walk away from it, or should we implement it? To help you decide if and how to progress an idea, I have developed the Product Vision Board. In this post, I show how the board can be applied to kick-start the product discovery process and to create a new digital product.
Scrum is a simple framework based on the idea of inspect and adapt: Create a product increment, show it to the stakeholders, and use the feedback to see if the right product is developed. This post describes what I regard as the essence of Scrum: a cyclic three-step process. It shows how the three steps help create a product with the right features and the right user experience (UX).
Employing experiments is a powerful technique to facilitate the creation of new products and new features. But to experiment effectively, we need to be clear where innovation takes place and uncertainty resides. Is it the user experience, the business model, or the technologies? Without the right understanding, it’s difficult to ask leap-of-faith questions, formulate meaningful hypotheses, and carry out helpful experiments. This blog posts introduces a simple model that helps you effectively innovate.
This post introduces my Product Canvas, a simple but powerful tool that helps you create a product with a great user experience and the right features. It combines Agile and UX by complementing user stories with personas, storyboards, scenarios, design sketches and other UX artefacts. It’s designed to work with Scrum, Lean Startup, and Business Model Generation. The canvas supports Lean UX by combining user centred-design and agile techniques.
Making the right product decisions is tough. Some product owners trust their intuition, others rely on data. Find out which approach is more helpful to create a successful product.