<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="https://elezea.com/wp-content/themes/elz_2023/styles/pretty-feed-v3.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:slash="http://purl.org/rss/1.0/modules/slash/" >
  <channel>
    <title>Elezea by Rian van der Merwe - RSS Feed</title>
    <atom:link href="https://elezea.com/2019/06/you-dont-own-your-product/feed/" rel="self" type="application/rss+xml" />
    <link>https://elezea.com/2019/06/you-dont-own-your-product/</link>
    <description>A personal blog about product, technology, and interesting things that are worth sharing.</description>
    <lastBuildDate>Thu, 02 Apr 2026 17:43:52 +0000</lastBuildDate>
    <language></language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <generator>https://wordpress.org/?v=6.9.4</generator>
          <item>
        <title>You don’t own your product</title>
        <link>https://elezea.com/2019/06/you-dont-own-your-product/</link>
        <pubDate>Mon, 17 Jun 2019 17:44:54 +0000</pubDate>
        <dc:creator>Rian van der Merwe</dc:creator>
        <guid isPermaLink="false">https://elezea.com/?p=7169</guid>
        <description>
          <![CDATA[Jonas Downey argues that nobody really owns anything in a product made by a team.]]>
        </description>
        <content:encoded>
          <![CDATA[<p>Jonas Downey argues that <a href="https://m.signalvnoise.com/nobody-really-owns-product-work/">nobody really owns anything in a product made by a team</a>. I agree with both his argument, and with how difficult it can be for product managers to make this shift. He gives some advice on how to get used to the idea:</p>
<blockquote>
<p>The trick is to change how you evaluate forward progress: the long-term survival of your own contributions is irrelevant. The important thing is that the product is evolving into the best version your team can create together.</p>
<p>The more you appreciate the power of the group over the individual, the sooner you’ll become a more effective collaborator. You’ll be more willing to hear and absorb others’ viewpoints. You’ll be more eager to seek out everyone’s best ideas, instead of digging in and defending your own. And you’ll be able to celebrate other people’s achievements with authenticity instead of territorial resentment.</p>
</blockquote>
<p>This is something I tried to articulate last year in a post called <a href="https://elezea.com/2018/04/humble-product-manager/">The humble product manager</a>:</p>
<blockquote>
<p>But equally important — and this is why humility is so important — they need to be open to the possibility that some of their decisions might be wrong. They should hang on to a measure of self-doubt every time they present a new solution to the team or the world. Admitting that someone else’s ideas are better than your own, and making changes based on good critique do wonders to improve products — and build trust within the team.</p>
</blockquote>
          <br>
          <br>
          <hr>
          Thanks for still believing in RSS! Get in touch <a href="https://elezea.com/contact">here</a> if you'd like.]]>
        </content:encoded>
                      </item>
      </channel>
</rss>