Many teams provide solid features, regularly fill their sprint backlog and manage to produce outputs in small cycles. But in the end, the one who often disappears is an important question: what effect does it really have with the user? This is what is about this episode. Oliver Winter and Tim Klein three often take mixed words output, results and effects and classify them in a practical way – not as a buzzwords, but as the basis of meaningful product function.
Develop products that create changes
The output is quickly visible. One is released, a feature live. But that alone is not enough. Autakam means change that arises – ideally with the user. A behavior that changes. A task that is easy. A problem that is no longer present. And this is why it should be possible: the effect before delivery. This effect is that we must walk after product development – not only the prepared feature.
What makes it difficult: the result is often not immediately tangible. This is not cured when a button is live or a flow is adjusted. It requires the desire to understand observation, real general understanding, hypothesis and an impact as a learning field. Many teams stop at the output as it is easy to measure. But if you really want to know if a product is successful, then you have to focus on the result – even if it means to bear uncertainty.
At the same time, good basics are required, as there is no result without reliable, high quality output. But pure distribution should not be an end in itself. It is about developing the product in such a way that it actually changes something – for those who use it and eventually also with the company that provides it.
Here the effect comes in the game. Because if a feature is used because it creates a real difference, a (positive) business results can also be the result.
Consequently, Oliver Winter and Tim Klein show how product owners can take this perspective – not as a dogma role, but as a conscious step. Outkam-oriented work means behaving more than the user’s behavior, preparing a hypothesis, questioning the effects of features and reflecting the team together-what else is not. This project is about loosening from thinking, making space for learning and measuring not only the number of distributed features, but also for the change they make causes.
The results are not always clearly assigned. Sometimes it takes patience, sometimes there is an effect, even if the output was good. But it is absolutely the origin of modern product development. This is not about prediction, but about the responsibility for the effect. And if you want to design this effect as a product owner, you cannot avoid the result.
Further links
Video mentioned to explain the conditions
Earlier episodes that have been given references:
The current version of the podcast is also available in the product worker’s blog: “Output, results and effects,
(May)
