<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Enablement on  rlang // tech</title>
    <link>https://blog.rlang.tech/tags/enablement/</link>
    <description>Recent content in Enablement on  rlang // tech</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Rico Lang (CC BY 4.0)</copyright>
    <lastBuildDate>Sun, 16 Mar 2025 11:13:05 +0100</lastBuildDate>
    <atom:link href="https://blog.rlang.tech/tags/enablement/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>On enabling an unexperienced Product Owner</title>
      <link>https://blog.rlang.tech/posts/on-enabling-unexperienced-an-po/</link>
      <pubDate>Sun, 16 Mar 2025 11:13:05 +0100</pubDate>
      <guid>https://blog.rlang.tech/posts/on-enabling-unexperienced-an-po/</guid>
      <description>Did you ever an experience a time, where you did feel that you really had to drag along your PO, because they themselves didn&amp;rsquo;t properly fill the role ? I recently found myself in such a situation, thats what i learned from it.</description>
      <content:encoded><![CDATA[<p>Have you ever found yourself in a situation where you felt like you had to drag your Product Owner along because
they weren&rsquo;t fully owning their role?</p>
<p>I recently experienced this firsthand, growing increasingly frustrated with a product Owner in my project not performing
their duties as expected.</p>
<h1 id="have-some-empathy">Have Some Empathy</h1>
<p>While I&rsquo;ve never been a Product Owner myself, I can only imagine the challenge of bridging the gap between the business
and technical worlds. From a developer&rsquo;s perspective, a Product Owner&rsquo;s job might seem straightforward: a few meetings
here, some prioritization there, preparing for the next sprint. Sounds easy, right?</p>
<p>As simple as it might sound, being a PO demands significant skill and, most importantly, experience. You need a deep
understanding of the business domain and its goals. You must weigh the importance of meeting deadlines against the risk
of accumulating too much technical debt. On top of that, you&rsquo;re responsible for managing diverse stakeholders: managers,
end-users, and your own development team.</p>
<p>If you take on their hat for a second it can really help you understand what kind of work they have to do.
So the best way to start empowering your Product Owner is by <strong>showing empathy</strong> and striving to understand their
challenges.</p>
<h1 id="your-product-owner-is-a-team-member">Your Product Owner is a Team Member</h1>
<blockquote>
<p>Business people and developers must work together daily throughout the project.</p>
</blockquote>
<p>Too often, I observe teams treating their Product Owners as if they are managers or some kind of higher authority.
However, if we recall a key quote from the Agile Manifesto, it&rsquo;s clear that business people and developers are meant to
collaborate closely, so might as well treat them like a team member :) .</p>
<h1 id="practical-ways-to-help">Practical Ways to Help</h1>
<p>Here are some actionable steps you can take to support your Product Owner:</p>
<ul>
<li>
<p><strong>Communicate Effectively:</strong> As a senior engineer, you should maintain close and direct communication with your
Product Owner. Most problems a development team faces can be solved through open dialogue. If possible, set up regular
one-on-one sessions to foster a strong working relationship.</p>
</li>
<li>
<p><strong>Exchange Constructive Feedback:</strong> Giving and receiving feedback is one of the most powerful tools in your
professional career. It not only helps your peers and team members grow but also provides ample opportunities for your
own development. Use honest feedback to highlight areas where the team feels unsupported and suggest how your Product
Owner can better assist.</p>
</li>
<li>
<p><strong>Lend a Hand:</strong> Although it might not be explicitly your job, pairing with your Product Owner — for example, on
writing tickets or preparing for planning sessions — can be incredibly beneficial. Both of you can gain valuable
insights into how the other side operates and what people need to accomplish their work.</p>
</li>
<li>
<p><strong>Be Transparent:</strong> Transparency is another crucial factor in enabling your Product Owner. They most likely have
deadlines to meet, so be upfront about any blockers, dependencies, bugs, or other issues. Highlighting these early gives
your Product Owner the opportunity to adjust plans or manage stakeholder expectations effectively.</p>
</li>
</ul>
<h1 id="summary">Summary</h1>
<p>While none of these tips are revolutionary and might not apply to every person or situation, I believe these are the
most effective actions you can take to build a stronger relationship with your Product Owner, thereby empowering them to
excel in their role.</p>
<p><strong>TLDR:</strong> Don&rsquo;t work against each other; <strong>work with each other!</strong></p>
]]></content:encoded>
    </item>
  </channel>
</rss>
