<?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>Product Management on Resolver Engineering Blog</title>
    <link>https://engineering.resolvergroup.com/tags/product-management/</link>
    <description>Recent content in Product Management on Resolver Engineering Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Copyright © 2026 Resolver Group</copyright>
    <lastBuildDate>Wed, 15 Sep 2021 17:21:35 +0100</lastBuildDate>
    <atom:link href="https://engineering.resolvergroup.com/tags/product-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A developer team&#39;s approach to not having a Product Manager</title>
      <link>https://engineering.resolvergroup.com/2021/09/a-developer-teams-approach-to-not-having-a-product-manager/</link>
      <pubDate>Wed, 15 Sep 2021 17:21:35 +0100</pubDate>
      <guid>https://engineering.resolvergroup.com/2021/09/a-developer-teams-approach-to-not-having-a-product-manager/</guid>
      <description>&lt;p&gt;Back in July of this year, our Product Manager here in the Consumer Team at Resolver moved on to a new job. This was a great loss both for us and the wider company and we knew that it would take several months to find and recruit the right person for the job. During the interim, it was decided that we would try to become somewhat self-sufficient, with our Tech Lead, CTO, and Head of Content all pitching in and directing our efforts over the following few months.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
