<?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 Radical Optimist</title><link>https://radoptimist.org/en/tags/product-management/</link><description>Recent content in Product Management on Radical Optimist</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://radoptimist.org/en/tags/product-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Ticketing Systems Are an Antipattern for Team Collaboration</title><link>https://radoptimist.org/en/post/ticketing-systems-are-an-antipattern-for-team-collaboration/</link><pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate><guid>https://radoptimist.org/en/post/ticketing-systems-are-an-antipattern-for-team-collaboration/</guid><description>&lt;h1 id="the-ticketing-system-user-interface-is-an-antipattern-for-cross-team-collaboration">The ticketing system user interface is an antipattern for cross-team collaboration&lt;/h1>
&lt;p>If your team spends most of its time managing a ticketing system — filing requests, triaging queues, waiting for answers — you have already made your collaboration legible to a machine.&lt;/p>
&lt;p>That is not a metaphor. Ticketing systems only work for the kind of work AI handles well: routine, well-defined, known destination, repeatable process. If your collaboration looks like a queue, it can be automated. And it will be.&lt;/p></description></item><item><title>How to Escape the Brown Compromise Trap</title><link>https://radoptimist.org/en/post/how-to-escape-the-brown-compromise-trap/</link><pubDate>Sun, 24 Mar 2024 00:57:47 +0000</pubDate><guid>https://radoptimist.org/en/post/how-to-escape-the-brown-compromise-trap/</guid><description>&lt;h2 id="we-are-all-painters">We are all painters&lt;/h2>
&lt;p>The brown compromise is an analogy from the painting world. The story goes like this: if you ask a family of five folks living in the same house which colour they prefer, you may end up with a dataset like this one: green, yellow, blue, violet, and I don’t care (yes, this is not a colour!). You may also end up in a family (like mine) where one of the users (me!) is colour-blind and has a very different perception of the world than the other four family members.&lt;/p></description></item><item><title>📖 Nudge: Why Product Managers Should Become Proficient Choice Architects</title><link>https://radoptimist.org/en/post/nudge-why-product-managers-should-become-proficient-choice-architects/</link><pubDate>Wed, 23 Jun 2021 11:49:49 +0000</pubDate><guid>https://radoptimist.org/en/post/nudge-why-product-managers-should-become-proficient-choice-architects/</guid><description>Designing a great choice architecture should be one of your core responsibilities as a product manager.</description></item><item><title>Don’t Ask For More Resources: Do More With What You Have!</title><link>https://radoptimist.org/en/post/dont-ask-for-more-resources-do-more-with-what-you-have/</link><pubDate>Mon, 22 Feb 2021 06:44:26 +0000</pubDate><guid>https://radoptimist.org/en/post/dont-ask-for-more-resources-do-more-with-what-you-have/</guid><description>Instead of asking for more, focus on helping your team succeed. Ensure you align your goals with the team’s current capacity: this is the…</description></item><item><title>Trifecta: How to maximize a product teams impact</title><link>https://radoptimist.org/en/post/trifecta-product-teams-and-impact/</link><pubDate>Sun, 20 Sep 2020 07:03:22 -0400</pubDate><guid>https://radoptimist.org/en/post/trifecta-product-teams-and-impact/</guid><description>&lt;h1 id="introduction--definition">Introduction &amp;amp; Definition&lt;/h1>
&lt;p>In this blog post, we’ll explore the concept of “trifecta” (also called triad in some organizations) that I have seen used successfully in the past both at start-up and even at large scale organizations (ex: Shopify).&lt;/p>
&lt;p>Let’s start with a definition. The trifecta represents a subset of a product team whose goals are to capture systematically:&lt;/p>
&lt;ul>
&lt;li>value: for the business&lt;/li>
&lt;li>usability: for the user&lt;/li>
&lt;li>feasibility: technological, ethical, legal, etc.&lt;/li>
&lt;/ul>
&lt;h1 id="valuable--usable--feasible-are-the-trifecta-goal">Valuable &amp;amp; Usable &amp;amp; Feasible are the trifecta goal!&lt;/h1>
&lt;p>I will use the term craft in this article and would also like to define it: a craft is one or more people inside the product-team with their hierarchy, rituals and specialties. Example of craft includes engineering (sometimes back-end, front-end, mobile), UX (designer, researcher, content specialist, etc.), Product (product manager, product owner, product lead, etc.), data-science (data-scientist, etc.), commercial, legal, etc. Each organization is different and has a different structure to execute its mission. In this article, I will refer to “craft” as the various specialties &amp;amp; hierarchies that exist within the organization.&lt;/p></description></item><item><title>Don't give us MVPs we want minimally enjoyable products!</title><link>https://radoptimist.org/en/post/dont-give-us-mvps-we-want-mjps-minimally-enjoyable-products-an-analysis/</link><pubDate>Fri, 01 May 2020 07:25:40 -0400</pubDate><guid>https://radoptimist.org/en/post/dont-give-us-mvps-we-want-mjps-minimally-enjoyable-products-an-analysis/</guid><description>&lt;h1 id="minimally-viable-products-are-a-myth-or-if-you-prefer-a-mental-model-always-wrong-but-sometimes-useful">Minimally Viable Products are a myth or, if you prefer a mental model. Always wrong but sometimes useful.&lt;/h1>
&lt;figure class="zoomable-img" onclick="window.__zoomImg(this.dataset.zoomSrc || this.querySelector('img').src, this.querySelector('img').alt)">
 &lt;img src="https://radoptimist.org/images/how-to-build-a-mvp.webp"
 alt="Original Image: Making sense of MVP (Minimum Viable Product) and why I prefer Earliest Testable/Usable/Lovable by Henrik Kniberg"
 loading="lazy" />
 &lt;svg class="zoomable-hint" xmlns="http://www.w3.org/2000/svg" width="22" height="22" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">&lt;circle cx="11" cy="11" r="8"/>&lt;line x1="21" y1="21" x2="16.65" y2="16.65"/>&lt;line x1="11" y1="8" x2="11" y2="14"/>&lt;line x1="8" y1="11" x2="14" y2="11"/>&lt;/svg>
 &lt;figcaption>Original Image: Making sense of MVP (Minimum Viable Product) and why I prefer Earliest Testable/Usable/Lovable by Henrik Kniberg&lt;/figcaption>
&lt;/figure>



&lt;script>
(function() {
 var dialog = document.createElement('dialog');
 dialog.id = 'zoomable-dialog';
 dialog.innerHTML = '&lt;img class="zoomable-modal__img" src="" alt="" />';
 document.body.appendChild(dialog);

 dialog.addEventListener('click', function(e) {
 dialog.close();
 });

 window.__zoomImg = function(src, alt) {
 var img = dialog.querySelector('img');
 img.src = src;
 img.alt = alt || '';
 dialog.showModal();
 };

 window.__zoomClose = function() {
 dialog.close();
 };
})();
&lt;/script>


&lt;p>Very much like Prometheus and the fire or Icarus and the sun they are powerful analogies and ideas that shape our view of the world. A tribute to their power is that, thousands of years after their creation, we still relate to them even if their initial context is long gone.&lt;/p></description></item><item><title>How to Run a Why, Who, What, How Alignment Session</title><link>https://radoptimist.org/en/post/how-to-run-a-why-who-what-how-alignment-session/</link><pubDate>Sat, 18 Jan 2020 09:01:01 +0000</pubDate><guid>https://radoptimist.org/en/post/how-to-run-a-why-who-what-how-alignment-session/</guid><description>A simple set of questions to remove ambiguity, build team alignment and prioritize</description></item><item><title>How to run a prioritization session using the MosCOW framework</title><link>https://radoptimist.org/en/post/how-to-run-a-prioritization-session-using-the-moscow-framework/</link><pubDate>Thu, 19 Dec 2019 09:01:02 +0000</pubDate><guid>https://radoptimist.org/en/post/how-to-run-a-prioritization-session-using-the-moscow-framework/</guid><description>&lt;p>10x ruthless prioritization&lt;/p>
&lt;p>A prioritization method to rapidly build consensus on the scope and share with your team and any stakeholder.&lt;/p></description></item><item><title>From Product to Platform — Conclusion (5/5)</title><link>https://radoptimist.org/en/post/from-product-to-platform-conclusion-5-5/</link><pubDate>Sun, 08 Dec 2019 22:01:02 +0000</pubDate><guid>https://radoptimist.org/en/post/from-product-to-platform-conclusion-5-5/</guid><description>From product to platform: A PM journey</description></item><item><title>How to Organize a Great Team Retrospective</title><link>https://radoptimist.org/en/post/how-to-organize-a-great-team-retrospective/</link><pubDate>Sat, 07 Dec 2019 14:06:34 +0000</pubDate><guid>https://radoptimist.org/en/post/how-to-organize-a-great-team-retrospective/</guid><description>Retrospective help teams realize their impact and grow.</description></item><item><title>From Product to Platform — Platform Revolutions (4/5)</title><link>https://radoptimist.org/en/post/from-product-to-platform-platform-revolutions-4-5/</link><pubDate>Mon, 02 Dec 2019 22:01:01 +0000</pubDate><guid>https://radoptimist.org/en/post/from-product-to-platform-platform-revolutions-4-5/</guid><description>&lt;p>From product to platform: A PM journey&lt;/p>
&lt;p>How platforms can evolve. Tectonic and violent revolution or more subtle and frequent iterations? How the Pareto principle can help make better decisions.&lt;/p></description></item><item><title>From Product to Platform — Platform Mental Models (3/5)</title><link>https://radoptimist.org/en/post/from-product-to-platform-platform-mental-models-3-5/</link><pubDate>Thu, 28 Nov 2019 15:01:01 +0000</pubDate><guid>https://radoptimist.org/en/post/from-product-to-platform-platform-mental-models-3-5/</guid><description>&lt;p>The journey of a Product manager: from product to platform.&lt;/p>
&lt;p>Useful mental models to better understand platforms: Superset of knowledge, Ecosystem, Infinite Game, Compounded interest&lt;/p></description></item><item><title>From Product to Platform — Increased Complexity (2/5)</title><link>https://radoptimist.org/en/post/from-product-to-platform-increased-complexity-2-5/</link><pubDate>Mon, 25 Nov 2019 15:01:01 +0000</pubDate><guid>https://radoptimist.org/en/post/from-product-to-platform-increased-complexity-2-5/</guid><description>&lt;p>Journey of a Product manager, from product to platform: complexity!&lt;/p>
&lt;p>Platforms are more complex than products. This post highlight the specific domains where platforms are more complex than products.&lt;/p></description></item><item><title>From Product Manager to Platform Manager — the Partners’ Impact(1/5)</title><link>https://radoptimist.org/en/post/from-product-manager-to-platform-manager-the-partners-impact-1-5/</link><pubDate>Sat, 23 Nov 2019 04:01:03 +0000</pubDate><guid>https://radoptimist.org/en/post/from-product-manager-to-platform-manager-the-partners-impact-1-5/</guid><description>Platform Managers listen to the voice of the developer.</description></item><item><title>📖 Book review: Sense &amp; Respond</title><link>https://radoptimist.org/en/post/book-review-sense-respond/</link><pubDate>Tue, 02 Apr 2019 15:39:05 +0000</pubDate><guid>https://radoptimist.org/en/post/book-review-sense-respond/</guid><description>&lt;p>A great book for knowledge workers. This is a map to help you navigate in our increasingly digital world.&lt;/p>
&lt;p>Sense and respond, product management, teal organizations, reinventing organizations&lt;/p></description></item><item><title>The pyramid of the product manager needs (Maslow inspired)</title><link>https://radoptimist.org/en/post/the-pyramid-of-the-product-manager-needs-maslow-inspired/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://radoptimist.org/en/post/the-pyramid-of-the-product-manager-needs-maslow-inspired/</guid><description>A useful and visual mental model that represent the product management role in relation to its environment.</description></item></channel></rss>