<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Volker Gersabeck on Medium]]></title>
        <description><![CDATA[Stories by Volker Gersabeck on Medium]]></description>
        <link>https://medium.com/@volkergersabeck?source=rss-535df5cf08aa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*HGoa_zBcve8Y-xgoHxQqiQ.jpeg</url>
            <title>Stories by Volker Gersabeck on Medium</title>
            <link>https://medium.com/@volkergersabeck?source=rss-535df5cf08aa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:39:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@volkergersabeck/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Empowering People to Innovate Products]]></title>
            <link>https://medium.com/@volkergersabeck/empowering-people-to-innovate-products-28fd0b70fed4?source=rss-535df5cf08aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/28fd0b70fed4</guid>
            <category><![CDATA[psychological-safety]]></category>
            <category><![CDATA[empowerment]]></category>
            <category><![CDATA[product-innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Volker Gersabeck]]></dc:creator>
            <pubDate>Tue, 11 Aug 2020 19:27:43 GMT</pubDate>
            <atom:updated>2020-08-11T19:27:43.432Z</atom:updated>
            <content:encoded><![CDATA[<p>Creating innovative products in a complex and uncertain world requires empowered people that perform real teamwork. Psychological safety¹ is the most important ingredient that sets successful teams apart from others².</p><h4>Why is psychological safety so important?</h4><p>In order to succeed in today’s digital economy, products need to be created by teams that found a way to bring all their talent together and build upon each other’s knowledge and ideas. It is not sufficient anymore for an individual to have a bright idea and then to dictate it’s implementation on to a hoard of employees. Especially in a world that is highly uncertain and solutions get so complex that one person cannot understand them in their entirety anymore.</p><p>In many research projects, psychological safety was identified as the most important driver of team performance. In a culture of low interpersonal fear, every team member is more likely to speak up and contribute their point of view. When better ideas are the ingredient for creating successful products, sharing each other’s point of view is key to generating more and better ideas. Having good ideas is not correlated to one’s position in the hierarchy, but speaking about them might be hindered by the fear of the consequences. In a work place with high psychological safety, people are less afraid of a colleagues reaction to them sharing feedback and will do so more often.</p><h4>What creates psychological safety?</h4><p>A team culture with high psychological safety is directly connected to how the team accepts failure. When people understand that failing is an essential part on the road to success, they become more willing to take a step into uncertain terrain. In order to know whether an idea leads to a better result, it needs to be tested. Since the outcome is unknown, each test might prove that the idea does not lead to better results. However, in any case the tests (should) lead to new insights that the team learn about.</p><p>At Pixar³, the company has established a routine that they call the “Braintrust”. In these meetings different people are shown movie plots in various stages of development. By testing the plots, people can share honest feedback and support the director of the movie to come up with even better plots. Everybody involved knows that each movie begins with a plot that sucks and needs several iterations of testing and giving feedback before a great movie can be shown to the masses.</p><p>At Apple⁴, they use the concept of a Directly Responsible Individual (DRI). By passing the responsibility for creating individual solutions to the persons that know best about how to solve these problems, they encourage everybody to step up and feel safe to raise concerns. This way, managers emphasize that they are not the ones that know every detail of a new product. With the expectation of creating and testing many prototypes and demos, the DRI has to figure out why one solution is better than the other.</p><p>At my current work place, Camunda, we acknowledge the fact that software development is not predictable by explicitly not estimating new features. This opens the door for people to be wrong initially and then to learn and improve along the way. Our product teams regularly speak up when they see a plan has become unrealistic. It is part of our culture to then discuss alternatives and adjust the plan. This way, we successfully solve our customer’s problems in a timely fashion.</p><h3>How to create an environment for experimentation and failure</h3><p>While we already have an exceptionally high psychological safety at Camunda, our product teams still needed to understand how to make more out of it.</p><h4>Allowing people to fail</h4><p>When I joined Camunda, the first thing that I did as a product manager was to talk with our customers and understand their particular needs. After identifying the most important problems to solve in my product, it became clear that the core piece of this solution would be too complex for a traditional approach. A full specification of it would have been half way into the implementation already and would have required too much effort on my side. Instead, I explained the situation to one of the engineers on the team and asked him to become the DRI. He happily agreed and made this topic his own.</p><p>We regularly met in our daily stand-ups and weekly meetings, but other than that, I had left him trying his way of tackling the new topic. It took a couple of weeks until he invited us, the engineering manager, the tech lead, and myself, to a first demo session. In that session he showed his result, which was a lot of everything but still far away from a good solution. While this demo session was very depressing for him, it was also very important that he could take the full responsibility for the new component. Only after this demo did I start to coach him to develop this new component. In the end, it became the core of the product presentation at our next customer conference.</p><p>Because he had the freedom to initially follow his instinct in solving the problem, he was open to constructive feedback afterwards and able to do a really good job. Without the special culture at Camunda, it would have been very difficult to give this engineer the time to fail. In other companies, I could well imagine that some managers would have involved themselves too early and the overall result would not have been that excellent.</p><h4>Understanding what you don’t know yet</h4><p>In another project, we had learned that one of our product components had accumulated a lot of usability issues and required a major overhaul. We started this initiative by listing all the issues that we already knew. It became clear that we could not tackle everything at once.</p><p>Together with one engineer that was the DRI, we re-phrased the issues into hypotheses. Each hypothesis was one idea of how we could improve this component in a way that one or several usability issues would be solved. One of the hypotheses was “The different views of a decision model can be navigated in a better way without the need for the tab navigation in the bottom”, another one “A less flexible layout of the decision graphs (that could potentially be generated) is sufficient for our users”.</p><p>To prioritize them, we first estimated how many users would be affected (all, most, several, few) and how uncertain we were about whether the hypothesis would prove to be true. The more uncertain a hypothesis was, the more experiments we wanted to do. The hypothesis with most uncertainty and most users affected was the one that we investigated first.</p><h4>Learning how to know what is right</h4><p>Camunda has a long tradition of doing hack days and allowing employees to experiment with our software as part of their work time. This produces many little projects that are usually open source and available to our community. However, what we are not good at yet is actively testing those projects and understanding the actual value they might bring to our customers.</p><p>At the core of both projects mentioned above, we introduced a new practice of creating prototypes and actively testing them with our internal colleagues and external users. The DRIs were responsible for creating the concepts and prototypes, which is what our engineers are good at. What they do not have experience with is how to get access to test users and how to moderate a prototype test. By providing both myself, they could draw their own conclusions about what worked well in their concepts and which parts still required further attention.</p><p>One commonality in all prototypes was the fact that we always tested multiple variants for the same topic. When testing a prototype with users, you can never know what “good” actually means to the user. However, when you show them two or three alternatives, they can easily express which aspects they prefer in either solution. As a result we usually picked a mix of all alternatives to create an even better solution.</p><h3>Conclusion</h3><p>When your job is to create innovative products, a good starting point is to understand the level of psychological safety that your team currently has. Creating an environment where people feel safe to express their thoughts and ideas is mandatory, if you want to benefit from the people’s talent. Giving people room for failure and coaching them how to learn from those failures brings product teams into a position to be successful.</p><p>[1] Amy C. Edmondson —<em> The fearless organization</em></p><p>[2] Julia Rozovsky — <em>The five keys to a successful Google team</em> <a href="https://rework.withgoogle.com/blog/five-keys-to-a-successful-google-team/">https://rework.withgoogle.com/blog/five-keys-to-a-successful-google-team/</a></p><p>[3] Ed Catmull —<em> Creativity, Inc.</em></p><p>[4] Ken Kocienda —<em> Creative Selection</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28fd0b70fed4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>