<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Product Management on E7Coding</title><link>https://www.e7coding.com/en/tags/product-management/</link><description>Recent content in Product Management on E7Coding</description><generator>Hugo</generator><language>en</language><managingEditor>Joy</managingEditor><webMaster>Joy</webMaster><lastBuildDate>Tue, 30 Jun 2026 13:00:00 +0800</lastBuildDate><atom:link href="https://www.e7coding.com/en/tags/product-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Five Archetypes of Future Product Teams: From Job Functions to Value Functions</title><link>https://www.e7coding.com/en/posts/five-archetypes-future-product-teams/</link><pubDate>Tue, 30 Jun 2026 13:00:00 +0800</pubDate><author>Joy</author><guid>https://www.e7coding.com/en/posts/five-archetypes-future-product-teams/</guid><description>&lt;p&gt;I recently saw an interesting tweet: as engineering, product, design, data science, and other functions begin to merge into more hybrid roles, will future teams stop defining people by job titles and instead define them by how they create value?&lt;/p&gt;</description></item></channel></rss>