<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mario Lenz on Medium]]></title>
        <description><![CDATA[Stories by Mario Lenz on Medium]]></description>
        <link>https://medium.com/@drlenzmario?source=rss-a3d448eb3308------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*67xmId-X8WRhdVCLOWf4BA.jpeg</url>
            <title>Stories by Mario Lenz on Medium</title>
            <link>https://medium.com/@drlenzmario?source=rss-a3d448eb3308------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:11:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@drlenzmario/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Create a Product Strategy]]></title>
            <link>https://medium.com/design-bootcamp/how-to-create-a-product-strategy-bf3b3ab69a35?source=rss-a3d448eb3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf3b3ab69a35</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[b2bplaybook]]></category>
            <dc:creator><![CDATA[Mario Lenz]]></dc:creator>
            <pubDate>Fri, 28 Jul 2023 05:57:57 GMT</pubDate>
            <atom:updated>2023-07-29T21:58:53.536Z</atom:updated>
            <content:encoded><![CDATA[<h4>7+1 steps to get you started.</h4><p>Are you a Product Manager struggling with your product strategy? Or did you recently start as a Product Leader and now need to build a strategy to align the team?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*t7Vy7JSY-ql1tWqgM1XqPg.png" /></figure><p>Here is a quick step-by-step guide to get you started.</p><h3>🔭Step 1:<br>Understand the purpose &amp; vision of the company.</h3><p>Why do they exist? What will the world look like after they have succeeded?</p><p>✅Do: Envision the changed behavior of customers.</p><p>❌Don’t: Think about internal goals, such as revenue or becoming the market leader. It’s all about the customer here.</p><h3>🎯Step 2:<br>Define the product mission to serve that vision.</h3><p>Specifically in B2B, other departments, such as Customer Success, Marketing, and Sales are important too. So what exactly is the product’s contribution?</p><p>✅Do: Define the category and key aspects of the future product. Be bold.</p><p>❌Don’t: Include empty slogans such as “great UX” or “best tool”.</p><h3>🧭Step 3:<br>Derive the product strategy as a rough plan to achieve the vision &amp; mission.</h3><p>Be specific about what you want to do — and <strong>what not</strong>. Explain how you differentiate and why you win. To do that, conduct thorough customer research and competitor analysis. Gather valuable insights to identify opportunities in the market that your product can address uniquely.</p><p>✅Do: Be sharp about your ICP, market segments, industries, and geographies.</p><p>❌Don’t: Try to be everybody’s darling.</p><h3>📈Step 4:<br>Define measurable product goals.</h3><p>Think about how to measure the success of customers. Have a catchy claim for these success factors but also try to find metrics that will indicate that they get value out of your product.</p><p>✅Do: Identify a North Star Metric and potentially some other leading metrics that feed into the North Star.</p><p>❌Don’t: Fiddle around with financial KPIs, such as ARR or LTV — rarely can they be influenced directly by product initiatives. See the bonus step below.</p><h3>🗺️Step 5:<br>Structure your roadmap with strategic intents.</h3><p>Identify key work streams to address in order to deliver on the above goals. Use them, e.g., as swimlanes to organize your roadmap.</p><p>✅Do: Shape each strategic intent so that it has a compelling mission and dependencies between those areas are minimized.</p><p>❌Don’t: Accept too many different work streams if you don’t have the capacity for them.</p><h3>💎Step 6:<br>Fill the roadmap with product initiatives.</h3><p>Only now think about specific opportunities and product initiatives following the strategic intents. Consider them as hypotheses and constantly revise based on your learnings.</p><p>✅Do: Use all of the above to guide proper product discovery.</p><p>❌Don’t: Consider a roadmap as a committed plan with fixed content and deadlines.</p><h3>❤️Step 7:<br>Underpin your strategy with values and principles.</h3><p>Explicitly list core values, cultural aspects, or product principles that serve as guardrails in everyday decision-making. Include factors regarding internal collaboration, trust, transparency, or autonomy.</p><p>✅Do: If such values don’t exist yet, kick off an initiative with leadership to discuss across the entire company.</p><p>❌Don’t: Promise what you cannot keep.</p><h3>💰Bonus Step:<br>Map product initiatives to financial KPIs.</h3><p>Build the key elements of the financial model of your company into a KPI tree. Map how your product initiatives contribute to certain business metrics. <a href="https://medium.com/@drlenzmario/business-kpis-vs-product-outcomes-57faa698d781">Try this</a>.</p><p>✅Do: Aim for a significant overlap to show how the product work contributes to the company’s financial goals.</p><p>❌Don’t: Exaggerate by applying precise mathematical formulas. A schematic mapping is often sufficient.</p><p>All of the above is explained in slightly more detail in the respective <a href="https://b2b-product-playbook.com/home/purpose-vision/">chapters of the B2B Product Playbook</a>.</p><p>🎁As a giveaway, find a more visual explanation of the above combined with a fictitious example <a href="https://maven.com/p/05d5d9">here</a>.</p><p>If you are eager to learn more and want to practice, I will be running a cohort-based course “From Product Manager to Product Leader” in which product strategy will be addressed in a dedicated module. Sign up for the <a href="https://maven.com/forms/78fdd7">waitlist </a>to be updated.</p><p>#B2BPlaybook #ProductManagement</p><p><em>This article was initially published on </em><a href="https://open.substack.com/pub/b2bproductblog/p/how-to-create-a-product-strategy?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web"><em>https://open.substack.com/pub/b2bproductblog/p/how-to-create-a-product-strategy?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf3b3ab69a35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-to-create-a-product-strategy-bf3b3ab69a35">How to Create a Product Strategy</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reality Check for PLG]]></title>
            <link>https://medium.com/@drlenzmario/reality-check-for-plg-a466d8be96b4?source=rss-a3d448eb3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/a466d8be96b4</guid>
            <category><![CDATA[plg]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Mario Lenz]]></dc:creator>
            <pubDate>Wed, 26 Jul 2023 19:09:08 GMT</pubDate>
            <atom:updated>2023-07-26T19:09:08.182Z</atom:updated>
            <content:encoded><![CDATA[<h3>PLG is the Next Big Thing?!</h3><p>PLG, PLG, PLG. If you haven’t come across <em>soooo </em>many posts about Product-Lead Growth, I don’t know where you have been. It feels like a huge bubble second only to Generative AI.</p><p>Wait. Did I say “bubble”?! To be fair, there is huge potential in PLG; there are great examples of highly successful companies; and elements of PLG can probably be utilized for nearly every product. But then there is also a lot of hype, stating that no Non-PLG business will survive. And there are quite some “influencers” out there where, given their job profiles, you wonder where they collected all that wisdom and why they didn’t apply it…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9LZiDQpgOKqVeJKC-biOUQ.png" /></figure><p>As for most things, I believe that a bit of healthy skepticism is appropriate. I will give examples below but let’s first clarify what we are talking about.</p><h3>What Exactly is PLG?</h3><p>I prefer Wes Bush’s definition which essentially states that you are using the product itself as the tool for the complete customer lifecycle:</p><blockquote>Product-Led Growth is a go-to-market strategy that relies on using your <strong>product as the main vehicle to acquire, activate, and retain customers</strong>.<em> — </em><strong><em>Wes Bush</em></strong></blockquote><p>There are variants of it, for more details see e.g. the <a href="https://b2b-product-playbook.com/tool/product-led-growth/">dedicated page in our B2B Product Playbook</a> where we argue that most companies will still need, e.g., Demand Generation to create sufficient awareness for their product offering. Still, let’s assume that you utilize your product</p><ul><li>to <strong>acquire</strong> new users, e.g. by intense word-of-mouth from happy customers;</li><li>to <strong>activate</strong> new users, e.g. by giving them free trials or freemium versions of your product;</li><li>to <strong>monetize</strong> your users by turning them into paying customers;</li><li>and to <strong>retain</strong> these customers by providing enough value for repeat usage.</li></ul><p>Sounds great, right? Until there are limits.</p><h3>When Usage of PLG is Limited</h3><p>I have experienced several situations where PLG couldn’t be implemented, at least not to the full extent:</p><blockquote><strong>When your company is operating in a blue ocean, where customers need to be educated about the problem and a demand needs to be generated.</strong></blockquote><p>Let’s go back in history for 15 years and assume Bitcoin doesn’t exist yet. Not only that, apart from a few technology enthusiasts, few people will even understand the benefits and usage scenarios of cryptocurrencies. Instead, the market needs to be educated first before users can self-adopt.</p><p>In that situation, the PLG flywheel will not start turning. There won’t be any word-of-mouth, and customers need to be educated about the problem being addressed — rather than applying some solution in a self-service manner.</p><blockquote><strong>When your company is operating in a complex domain that requires extensive consulting to train users.</strong></blockquote><p>Note that I explicitly refer to the <em>domain</em> being complex — not the <em>product</em> itself. It’s your job as a Product Manager to provide easy-to-use products. But when the domain itself is hard to understand?</p><p>Currently, I see that in ESG. There are so many different frameworks, so many requirements, so many disclosures. And these even change constantly. Some companies have been early adopters — but the majority of the market will require extensive consulting to even understand what they have to report, how data shall be collected, or how their ESG strategy should be defined to reduce their environmental footprint.</p><blockquote><strong>When your company provides a product for which free trials are not viable.</strong></blockquote><p>For example, when you are building a dedicated marketplace — say for real estate, rental cars, or furniture — then the seller wants to receive the money and the buyer wants to have the goods. There is no way you can offer a free trial.</p><blockquote><strong>Finally, when buying decisions are usually top-down, with many stakeholders involved, to ensure uniformity or regulatory compliance.</strong></blockquote><p>This is particularly relevant in (a) regulated domains and (b) Enterprise B2B. Even when you were able to acquire and activate some users by way of your PLG motion, that does not mean that you are even close to monetizing. Instead, you might be far away from the buyer, i.e. the person or group owning the budget and in charge of any buying decision. Even worse, this group might even have some completely different needs than the original user — so they might ignore whatever they experienced during the trial.</p><p>Let’s dig a bit deeper into the latter aspect by taking a look at Slack, being a poster child of PLG.</p><h3>A Quick Review of Slack’s Performance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R-z3zyAHAiDYLyBqYz_L_g.png" /><figcaption>Projected number of DAU / MAU of Slack worldwide from 2019 to 2025 (Statista)</figcaption></figure><p>To start with, Slack is obviously doing very well. They are steadily growing, based on the chart above we can estimate a 33% YoY growth in daily active users. Pretty impressive.</p><p>Slack was even way ahead of Microsoft Teams back in 2019:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SY8-KsZF09kmRgB7bTGuBQ.jpeg" /><figcaption>Source: Statista</figcaption></figure><p>Note that this was Pre-COVID. Of course, we all know that COVID forced many companies to implement remote work, so for sure this will have a big boost on Slack. So, let’s look at more recent data:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Pf5HnG6yR6qM5J756z3zQ.png" /><figcaption>Source: <a href="https://www.businessofapps.com/data/slack-statistics/">https://www.businessofapps.com/data/slack-statistics/</a></figcaption></figure><p>Oops?! What happened? Sure, Slack grew — but Microsoft Teams completely outpaced them. Why did that happen?</p><ul><li>I don’t think it is because of superior <strong>functionality</strong> or <strong>user experience</strong>. I have worked with both tools, you need to get used to them, but then they offer highly similar functionality, specifically for mass markets when it boils down to some simple chat and collaboration tools. In fact, I even experienced quite some problems with quality and reliability with Microsoft Teams. For sure, Microsoft didn’t win here.</li><li>However, the <strong>distribution</strong> is entirely different. Microsoft Teams is part of Office 365. So when companies are already using Microsoft’s cloud offering, it’s a no-brainer to also utilize Teams. And since many of these companies had to change to cloud offerings to support remote work (COVID, remember), the impact of the pandemic was even more significant for Microsoft than it was for Slack.</li><li>What’s more, <strong>compliance</strong> aspects and <strong>top-down decision-making</strong> are in favor of Microsoft. I can hear the COO: “<em>Hey, we already have an agreement with Microsoft, the legal work had been done already, and all our employees can get instant access via SSO — why worry about another provider?</em>”</li></ul><p>In the end, it is classic Enterprise Sales that cause the huge gap visible in the above chart. Among other things, a Sales-Led Growth (SLG) approach relies on building robust sales teams, establishing strong customer relationships, and driving revenue through personalized interactions. E.g., so-called <em>objection handling</em> is an important step in any such sales process.</p><p>But even in these markets, PLG is better at communicating value to users, i.e. when prospective customers can try and experience the true value for their needs — as opposed to some sales pitch when the customer doesn’t understand how much of the show is reality and how much is over-selling. When combining Sales-Led Growth and Product-Led Growth, both approaches form a powerful synergy that drives sustainable growth and maximizes customer lifetime value:</p><h3>Combining PLG and SLG Will Drive Growth</h3><p>When combining SLG with PLG, vendors can offer prospective B2B customers a seamless journey. By way of PLG tools, such as user-friendliness, self-guided trials, and triggered engagement, users can navigate the product and experience its benefits, they can build an understanding of its potential value for their organization — much better than they could do during some pre-canned sales demo. At this crucial stage, a well-integrated sales team can step in, offering personalized assistance, addressing specific pain points, and guiding prospects through the decision-making process. But not based on a standardized sales pitch but rather based on the signals that have been detected while users were trying the product. This combined approach significantly reduces the sales effort, allows for a much more focused conversation, and enhances the likelihood of conversion, resulting in accelerated growth and improved customer satisfaction.</p><p>One of the most compelling reasons to combine SLG and PLG in the Enterprise B2B space is the substantial reduction in Customer Acquisition Cost (CAC). As users are enabled to explore the product independently, the burden on the sales team to perform initial demos or extensive outreach diminishes. This self-qualification process filters out leads that may not be the best fit for the product, ultimately saving time and resources for both the sales and marketing teams. Additionally, the interplay between PLG and SLG generates a powerful word-of-mouth effect, as satisfied users share their positive experiences with their peers and industry networks, further enhancing brand credibility and organic lead generation.</p><p>But, even then, it’s a common misconception to achieve <strong>zero CAC</strong>. Unless you are the undisputed and well-known market leader, you still need to create awareness of your product and drive prospective customers to your site. Hence, Marketing remains an indispensable piece of the puzzle to drive awareness, generate interest, and nurture leads through targeted campaigns, content creation, and branding initiatives — with implications for the corresponding budgets.</p><p>Last but not least, following a land-and-expand approach, PLG becomes a potent tool for B2B enterprises to grow inside their existing customer base. In that situation, most barriers mentioned above have already been removed, the buying decision had been made, and a relationship with the buying center is in place. By ensuring a seamless and intuitive product experience, PLG methods can be utilized to recommend additional features, upgrades, or premium offerings — at the exact moment when they provide the biggest value for the user. This will lead to upsells and cross-sells and, thus, to an organic expansion within the installed customer base. If done well, NRR can skyrocket.</p><h3>Summary</h3><p>As said in the introduction, elements of PLG can for sure be implemented in nearly every product. We have cited some examples in our <a href="https://b2b-product-playbook.com/tool/product-led-growth/">B2B Product Playbook</a>.</p><p>However, depending on the domain and the nature of the product, it may not be appropriate to implement PLG to the full extent but, instead, blending with classic Sales-Led Growth strategies will provide better business outcomes.</p><p><em>This article was initially published on </em><a href="https://open.substack.com/pub/b2bproductblog/p/reality-check-for-plg?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web"><em>https://open.substack.com/pub/b2bproductblog/p/reality-check-for-plg?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a466d8be96b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Content as a Service to Improve Product Experience]]></title>
            <link>https://medium.com/@drlenzmario/content-as-a-service-to-improve-product-experience-3a82dc7dfcd3?source=rss-a3d448eb3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a82dc7dfcd3</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Mario Lenz]]></dc:creator>
            <pubDate>Fri, 21 Jul 2023 08:45:52 GMT</pubDate>
            <atom:updated>2023-07-21T08:45:52.306Z</atom:updated>
            <content:encoded><![CDATA[<h3>Never let customers start with a blank sheet of paper.</h3><p>Imagine Miro just as a blank canvas — without its templates, libraries, or other apps.</p><p>Imagine Notion just as a writing app — without all its blocks, boards, and embeddable content.</p><p>Imagine Canva just as a plain white sheet of paper — without its templates, styles, and apps.</p><p>Any of these tools would be half as useful, probably even less so. I believe the same is true for any software company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2nD59Oe7YaVYmHMbPRnKQ.png" /></figure><p>Let’s explore why:</p><h3>Content Reduces Time-to-Value</h3><p>A major benefit of Software-as-a-Service (SaaS) for customers (among several others) is <strong>improved time-to-value</strong> because there is no more need to buy and install hardware, then administrate software, then configure it, before it can eventually be used.</p><p>Instead, many SaaS services today provide instant access, either via free trials or after the tool has been licensed. In more complex B2B setups, a certain amount of configuration will still be needed — but to a much lesser extent than with classic on-premise software.</p><p>But great SaaS providers go even further. Not only do they provide the <em>toolbox</em>, so to speak, but also <em>prefill </em>that toolbox: They provide <strong>ready-to-use content</strong> as part of their offering, such as templates, guides, tutorials, or pre-built configurations, in addition to the core software solution.</p><p>For customers, such content provides several benefits:</p><ul><li><strong>Faster time-to-value</strong>: With ready-to-use content, customer onboarding is accelerated which enables them to start using the software efficiently and deriving value more quickly.</li><li><strong>Best practice</strong>: Assuming the content has been created by domain experts, customers will find it helpful to trust those experts rather than having to create content from scratch and risk errors or omissions.</li><li><strong>Improved User Adoption</strong>: Even beyond the software itself, comprehensive content can help to better understand the software’s capabilities, features, and best practices, leading to higher user adoption rates and better utilization of the solution.</li><li><strong>Increased productivity</strong>: By way of leveraging pre-built templates and other content assets, customers can get their jobs done more efficiently and, thus, achieve higher levels of productivity.</li><li><strong>Faster learning</strong>: If the content is well-structured, it supports learning on the job thus making it easier for customers to get to know the software. Also, time and effort for dedicated tool training will be reduced significantly.</li><li><strong>Continuous learning</strong>: When the content is not only provided as-is but also updated and extended in combination with the underlying software, then customers will be supported in their learning journey.</li></ul><p>That sounds like a promising approach, right? But how can a classic SaaS software provider start that journey toward <strong>Content-as-a-Service</strong> (CaaS)?</p><h3>Content Shall Be Part of the Product Strategy</h3><p>We suggest the following 10 steps for implementing a content strategy:</p><ol><li>As always, understand <strong>customer needs</strong>. See where they struggle most, what blocks their adoption, and what slows them down during the implementation. By engaging with customers and gathering feedback, identify the specific content requirements that would add value to their experience with the software.</li><li>Align on <strong>internal goals</strong>. Agree on what you want to achieve with your CaaS strategy, and which business objective you are aiming for: faster onboarding, increased adoption, more reliable configuration, or what else?</li><li><strong>Develop a content strategy</strong>: Handle content as a product line on its own. Based on customer needs and company vision, determine the most relevant types of content, such as configuration presets, onboarding guides, tutorials, document templates, case studies, or best practice guides.</li><li><strong>Think of a North Star Metric</strong>: Specifically for the content part inside the overall product, what would be a good product metric to aim for that indicates a changed behavior of customers and that you can track directly in the product? Will they create more content, use the product more often, be quicker in completing their tasks, or what else?</li><li><strong>Plan content initiatives</strong>: Regard content as strategic intent, consider potential initiatives in these and <a href="https://open.substack.com/pub/b2bproductblog/p/business-kpis-vs-product-outcomes?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web">tie them back to business metrics</a> so that you consciously drive financial KPIs.</li><li><strong>Consider a CMS</strong>: Very much like software teams use highly specialized software, implement a robust content management system to organize, store, and distribute the content effectively. Even more so when you are dealing with a large variety — say in the case of multilingual content.</li><li><strong>Create content</strong>: Invest in creating high-quality, valuable, engaging, and user-friendly content that addresses the identified customer needs. When relevant, involve subject matter experts or external partners to create comprehensive content.</li><li><strong>Ship and promote</strong>: Actively communicate the availability of the content-as-a-service offering through Marketing channels, Customer Success, and any other customer touchpoint. Consider implementing ideas from Product-led Growth, such as free trials around content usage,</li><li><strong>Collect feedback</strong>: As with the software itself, encourage customers to provide feedback on the content and its effectiveness. Try to measure the effectiveness of the content directly in the product but even beyond that offer channels for users to report issues, suggest improvements, or request additional resources.</li><li><strong>Update and expand</strong>: Regularly update the pieces of content so that they are always up-to-date. Stay informed about industry trends, new regulations, and customer feedback so that the content is always fresh, relevant, and engaging.</li></ol><p>When you are an experienced Product Manager, the above should look very familiar because it shares a lot of commonalities with PM-ing a classic software product and developing a proper strategy for it. Even frameworks such as <a href="https://b2b-product-playbook.com/tool/pirate-metrics/">Pirate Metrics</a> are applicable.</p><h3>Consider a Content Ecosystem</h3><p>Sure, the big players, like Apple, Google, Salesforce, and several others, also allow software tools (or apps) to be built by partners and then incorporated into their platforms. But let’s be honest, that requires massive investment and is challenging in so many dimensions: For example, when you allow 3rd party contributors to add or modify the actual software, then you have to think about usage quota, load balancing, IT security, or anti-virus protection. This is mostly for the giants in the industry. E.g. Salesforce operates a large team to conduct safety assessments before any new app gets submitted on their AppExchange platform.</p><p>While your organization might not be at that stage, think of a content ecosystem: What if tutorials, templates, standard configurations, onboarding guides, and all that would be provided by a community, not just the original software vendor? Key players here can be <strong>partners</strong> who even specialize inside the domain and, for example, provide ready-to-use content for certain industries or regions. Likewise, a collaboration with external consultants, trainers, or auditors could be promising. Establishing such an ecosystem will bring several benefits:</p><ul><li><strong>Subject matter expertise and trust</strong>: In a vast network of specialized partners, there will be one or more who are specialized in a certain topic, industry segment, jurisdiction, or such. Specifically, StartUp and ScaleUp companies will not be able to organically provide that coverage.</li><li><strong>Faster delivery and better scalability</strong>: On a new topic, or on topics that change rapidly (just think of regulations around ESG), an extended partner network can respond much quicker and toward a broader community of customers.</li><li><strong>Expanded reach and increase stickiness</strong>: Partners can help to promote not only the content in their networks but by doing so will also facilitate the adoption of the software itself. When customers always find relevant content in a specific tool, they are likely to stick to that tool.</li><li><strong>Co-creation with partners</strong>: SaaS companies can collaborate with specialized partners to co-create content, thus joining forces in delivering comprehensive and valuable content. By partners providing feedback and their insights, the effectiveness of the content can be increased.</li></ul><p>Depending on the industry, customers might even be willing to share and exchange information about their setups, configurations, templates, and guides — less so on highly competitive information but potentially around secondary business processes.</p><p>To summarize, content-as-a-service is a promising strategy using which SaaS companies can not only extend their offering but also enhance the customer experience. Using a partner ecosystem, their reach and expertise can be extended significantly.</p><p><em>This post was initially published on </em><a href="https://open.substack.com/pub/b2bproductblog/p/content-as-a-service-to-improve-product?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web"><em>https://open.substack.com/pub/b2bproductblog/p/content-as-a-service-to-improve-product?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a82dc7dfcd3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Debunking Common Misconceptions Around the MVP]]></title>
            <link>https://medium.com/@drlenzmario/debunking-common-misconceptions-around-the-mvp-c56344271881?source=rss-a3d448eb3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/c56344271881</guid>
            <dc:creator><![CDATA[Mario Lenz]]></dc:creator>
            <pubDate>Fri, 21 Jul 2023 08:22:44 GMT</pubDate>
            <atom:updated>2023-07-21T08:22:44.694Z</atom:updated>
            <content:encoded><![CDATA[<h3>Be clear whether it’s an experiment or version 1</h3><p>Product teams love “Minimum Viable Products” (MVP). This concept helps so much in focusing on what is needed next and eliminating or postponing everything else. However, behind this seemingly straightforward concept lies a web of misunderstandings that often lead to misinterpretations and missed opportunities.</p><p>Maybe we should even ditch the term? But not so fast. Let me try to shed some light.</p><p>Before we start, let’s immediately scope out <em>the first clunky version of a product which is neither valuable nor usable nor anything else but just a minor iteration of the engineering team</em>. In no way, this should be called an MVP.</p><p>Also, forget this ill-famous illustration of the idea of an MVP:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_L3FXg1_swOg_Ps6q2XXQ.jpeg" /></figure><p>I believe this is totally misleading because these different “products” shown do not address the same needs. When you add functional as well as emotional jobs to be done, this becomes apparent immediately:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Im3h9WkO9d-yCBXbIFLbXw.jpeg" /></figure><p>Would you travel long distances with the family on a skateboard? Or cruise the Alps on the weekend with your buddies from high school on an e-scooter? See…..</p><p>Below, I will explain a better visual. But before that, let’s focus on two relevant interpretations of the term:</p><h3>MVP as an Experiment to Learn From</h3><blockquote>“Think of an MVP as the ‘test’ version of your product, designed to validate assumptions and gather user feedback, rather than a complete, polished solution.”<em> — Eric Ries</em></blockquote><p>With that definition, Eris Ries popularized the concept of an MVP. Note how he emphasizes the <strong>learning</strong> aspect here. In that sense, an MVP is an <strong>experiment</strong> more than it is a product. It serves as a vehicle to test and validate critical assumptions about a product.</p><p>Of course, it could be a product or feature, implemented just enough to collect feedback. But it doesn’t have to be — it doesn’t have to be working software even: In <a href="https://b2b-product-playbook.com/reading_list_item/value-proposition-design/">Value Proposition Design</a>, Alex Osterwalder and co-authors explain how both, the Business Model Canvas and the Value Proposition Canvas can be utilized as MVPs to validate assumptions about the Ideal Customer Profile (ICP) and their specific jobs, pain, and gains. Just with paper and Post-It’s, no software at this stage.</p><p>And even when we build software, it might be a <strong>prototype</strong> rather than a “Version 1” (see below). I like to call it prototype because:</p><ul><li>It focuses on the <strong>key parts</strong> of the user journey but ignores edge cases.</li><li>It is working software but <strong>in no way complete</strong>, e.g. it ignores QA aspects, coding conventions, or scalability issues.</li><li>It is what I love to call <strong>throwaway software</strong>: not even meant to be used later on but focused purely on learning — maybe even built with specific tools, such as Low Code / No Code platforms.</li></ul><p>While this approach is totally reasonable, I wonder whether the term MVP is actually right: it is neither a product (<em>nobody can really use it</em>) nor viable (<em>we cannot sell it</em>). Hence, I would recommend referring to <strong>experiments</strong> or <strong>prototypes</strong> instead.</p><p>OK but what if we really build a working product? This brings us to the second interpretation of MVPs:</p><h3>MVP as Version 1</h3><blockquote>“Remember, an MVP is not the final destination; it’s the starting point. It’s the foundation upon which you can iterate, improve, and create a remarkable product.”<em> — Marty Cagan</em></blockquote><p>That definition, even though it doesn’t explicitly say so, already goes more in the direction of <strong>working software</strong>: a version 1 product, a beta program, a feature only made accessible with an <a href="https://b2b-product-playbook.com/home/distribution/">early access program</a>, or similar. Something that at least a certain fraction of customers can try and use — as opposed to sticky notes or fake door landing pages.</p><p>Even more, it’s assumed to serve as a starting point for later iterations, as an initial version of our product (software in our case) that will be extended and built upon. Very much in line with the <strong>Build — Measure — Learn</strong> loop of Lean UX, it assumes:</p><ul><li>We consider a future product but then <strong>reduce to the max</strong> in order to focus on the most essential capabilities first.</li><li>We truly <strong>build and deliver</strong> that bare minimum and ship it as our version 1 product to customers, at least to some of them.</li><li>We <strong>observe</strong> customers using it, ideally with built-in metrics.</li><li>We <strong>learn</strong> from that usage data, extend, and improve our product.</li><li>We then continue the loop.</li></ul><h3>Why the ICP is Critical</h3><p>A visual also shared oftentimes to illustrate the idea of an MVP is this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*R8snjN67CCScAGITEFD76w.jpeg" /></figure><p>This diagram is very much consistent with the above definition of a Version 1: Imagine the full product across all relevant aspects of the software (light green), but then focus on only the bare minimum to create something already valuable enough (dark green). Think of it as a small piece of cake from the bottom to the cream — not just one layer of the cake.</p><p>To select that bare minimum, you need to be crystal clear about your ideal customers and their jobs, pains, and gains. Specifically for B2B, just the type of customer won’t be enough but you need to understand target user personas. Imagine, you are building a better product for truck-based logistics — will you improve the life of their CFOs (e.g. by providing efficiency gains), their Logistics Managers (e.g. by making route planning easier), or their truck drivers (e.g. by providing simpler tools to be used while on the road)? Only with that, you will be able to sufficiently narrow down the required user journey.</p><p>Based on the learnings from that initial version, you can then extend your product offering:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*HtVON62EhHWn7z9he2w0hw.jpeg" /></figure><p>Depending on stage and maturity, this might mean still focusing on the same customer segment but extending your offering along their user journey — or addressing adjacent customer segments.</p><p>In any case, it’s crucial that you initially reduce to the bare <strong>Minimum</strong> of your customer’s needs, then validate your assumptions to find a <strong>Viable</strong> solution that you, finally turn into a <strong>Product</strong>.</p><p><em>This post was initialy published on </em><a href="https://open.substack.com/pub/b2bproductblog/p/debunking-common-misconceptions-around?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web"><em>https://open.substack.com/pub/b2bproductblog/p/debunking-common-misconceptions-around?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c56344271881" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When You Are a Leader, Create Your Own User Manual]]></title>
            <link>https://medium.com/@drlenzmario/when-you-are-a-leader-create-your-own-user-manual-e017d974f46a?source=rss-a3d448eb3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/e017d974f46a</guid>
            <dc:creator><![CDATA[Mario Lenz]]></dc:creator>
            <pubDate>Mon, 17 Jul 2023 09:21:13 GMT</pubDate>
            <atom:updated>2023-07-17T09:21:13.501Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine you started as a product leader, or any leader for that matter, in a new group. Maybe you have just been promoted or, even more challenging, you joined a new company, and people who don’t know you expect leadership traits from you.</p><p>Each new role will have its unique challenges, including understanding company culture, building relationships and trust in your team as well as with stakeholders, or getting into the respective industry and market. But primarily, you’ll be responsible for managing and developing your (product management) team. A team for who you are like an alien, an unknown species, they don’t know how to deal with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IRlfsWpx3lb2GzFTh-YTeA.png" /></figure><p>Since they don’t know you:</p><ul><li>They will not immediately understand your way of thinking and how you want to provide guidance and direction. Specifically, how your leadership style differs from their previous experience to which they are accustomed, say in terms of directive vs. supportive management.</li><li>They will not share your visions, at least not in the beginning. Maybe there was a clear objective for which you were hired. Maybe you bring your own mission on how you want to bring the organization forward. In any case, the team cannot know.</li><li>They won’t know your background, skills, and work experience. Hence, they cannot assess to what extent you can help them in their daily job, how much personal responsibility and autonomy you will provide them, or support them in their professional growth.</li><li>Finally, they will not know your little quirks. The way you respond to proposals, how you express dissatisfaction or delight, or what it means when you shake your head or speak faster than usual.</li></ul><p>To cross that initial chasm and help people to get to know you better, I strongly recommend:</p><blockquote><strong><em>Create a User Manual that describes key aspects of your personality, the way of working with you, and what you expect from others.</em></strong></blockquote><p>Specifically:</p><ul><li>Provide some <strong>career background</strong>. Not your full CV (which probably is on LinkedIn anyways). But highlight a few aspects that are relevant for future collaboration.</li><li>Include <strong>hobbies</strong> to provide a more complete picture of your personality. When you enjoy activities such as motorbike riding or downhill, the team can expect a fast-paced leader. When you work for NGOs in your spare time, it shows you care about social responsibility.</li><li>Describe how you work, what your <strong>principles</strong> are, and how you organize your way of thinking. Which mental models do you apply?</li><li>Clearly describe what others can <strong>expect</strong> from you — and what you will expect from them. Not in detail, of course, that’s a topic for later 1:1s. But in terms of social behavior, ownership, or collaboration on the job.</li><li>Be honest and include your little <strong>quirks</strong>. Not only does that make you human, but also your team will better understand your reactions and emotional attitudes.</li></ul><p>If you want to see an example, check out my <a href="https://www.linkedin.com/in/mariolenz/">LinkedIn profile</a> which includes my very own User Manual. I explain</p><ul><li>how I moved into Product Management leadership and how my tech education still influences me,</li><li>that I am a speed-lover, maybe I should even add having ants in my pants,</li><li>how I think in triangles to simplify my life,</li><li>what I am trying to be for my team but also that I demand, e.g., owning your monkey,</li><li>and that I often use sarcasm or other means of an exaggeration to emphasize a certain point I want to make.</li></ul><p>I highly recommend thinking about such a personal inventory, regardless of the final format of the document. Even beyond your next team, it will also help you to get clarity about your own thinking and way of working.</p><p><em>This article was initially posted on </em><a href="https://open.substack.com/pub/b2bproductblog/p/when-you-are-a-leader-create-your?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web"><em>https://open.substack.com/pub/b2bproductblog/p/when-you-are-a-leader-create-your?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e017d974f46a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business KPIs vs. Product Outcomes]]></title>
            <link>https://medium.com/@drlenzmario/business-kpis-vs-product-outcomes-57faa698d781?source=rss-a3d448eb3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/57faa698d781</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Mario Lenz]]></dc:creator>
            <pubDate>Fri, 14 Jul 2023 14:08:24 GMT</pubDate>
            <atom:updated>2023-07-14T14:08:24.616Z</atom:updated>
            <content:encoded><![CDATA[<h3>Bridging the gap between financial metrics and product initiatives</h3><p>I have recently observed some discussions about business outcomes vs. product outcomes. I believe this is driven by the current economic environment where Product Managers and Leaders are no longer measured by just how quickly they grow their teams or deliver free trials — but rather have to prove they <strong>contribute to business results</strong>, such as revenue or profitability.</p><p>While a Product Manager shouldn’t take the role of their CFO, it definitely helps to understand how product initiatives relate to business results. In the following, I will explain my mental model and illustrate this with a fictitious company which, I guess, will resonate with most of us immediately:</p><blockquote>In today’s IT, project management and product development often are related to drowning in tickets, tickets, tickets with no end in sight. It feels clunky and cumbersome. Our mission at <strong>Zira </strong>is to make project management fast and enjoyable. We are mobile-first and adopt modern concepts that resonate with Generation Z users.</blockquote><p>Even though I just made this up, you know who I am talking about, right?!😉</p><p>OK, back to our topic. No matter what the exact business model is or what notion of a flywheel our company is adopting, in its most basic version, there are 2 elements:</p><ul><li><strong>Delivering</strong> value for the user by means of the product</li><li><strong>Capturing</strong> value from customers for the business</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EbxtxVvWYFGzNN4QQRBdKA.jpeg" /><figcaption>Two sides of the same coin: Delivering and capturing value</figcaption></figure><p>Both need to be in balance. If either of them falls short, there is no sustained business model:</p><ul><li>If there is no customer value, it will be difficult to acquire paying customers; and even if that’s achieved by a certain level of over-selling, they will soon churn — which will impact the ability to capture value.</li><li>If a company fails to capture value in a sufficient manner, it will not be able to operate or pay salaries and other expenses — ultimately leading to a business failure (unless you are an NGO relying on donations or similar).</li></ul><p>So, both aspects are closely related yet different. For experienced Product Managers and Product Leaders it is essential to understand both and how they play together.</p><h3>KPI Trees for Capturing Value</h3><p>The capturing side is typically measured by business KPIs, such as profit, revenue, retention, or churn. Depending on the <a href="https://b2b-product-playbook.com/home/startup-vs-scaleup/">growth stage</a> of the company, the specific top-most KPI may differ: sometimes it’s revenue (to focus on growth), sometimes it’s margin (to focus on profitability), etc. But once that top-level KPI has been defined, it can be decomposed into the contributing factors and, thus, a KPI tree can be defined as sketched here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DBMpwIKdI0XkenWrty5vhQ.jpeg" /><figcaption>KPI Tree to visualize key factors how a company captures value</figcaption></figure><p>In a nutshell, for this simplified example, the growth is measured in ARR (i.e. ignoring one-time fees and such) which in turn is determined by the number of net new customers, the number of seats sold to these customers, and the price per seat. The number of net new customers, in turn, is the number of newly acquired customers minus churned customers, and so on. While not shown in the diagram, there is strict math behind it which every CFO should be able to explain. And, yes, in reality, these KPI trees will be much more complex, including things like taxes, interest, and depreciation. For illustration purposes, I kept it simple.</p><p>The problem with these KPI trees is: Typically none of the metrics shown can be <strong>directly influenced by the product team</strong>. For example, net new customers could come via the Sales team, partners, or conversions after a PLG-like free trial. In any case, it will be highly dependent on other teams rather than directly measurable inside the product.</p><p>Hence, we need another tool for the product side of the house:</p><h3>North Star Metrics for Delivering Value</h3><p>A great candidate for that other tool is the North Star Metric which can then be decomposed into specific product goals:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*UIrje-tn5J2X4vtJzvSK9A.jpeg" /><figcaption>North Star Metric four our fictitious product</figcaption></figure><p>So, we adopt the <a href="https://amplitude.com/north-star">North Star Framework</a> and think about a single metric that indicates the success of users when using your product. Maybe they will buy more (when you are in e-commerce), will book more hotels (when you are in the hospitality business), will spend more time with your product (e.g., when you are a streaming service or gaming company), become faster or more efficient in completing their jobs-to-be-done (e.g., when you offer products for logistics), or reduce their environmental footprint (e.g., when you are in ESG). The essential idea here is that we find a metric that</p><ul><li>truly indicates <strong>customers derive value</strong> from using our product,</li><li>can be <strong>measured directly inside the product</strong>, and</li><li>is <strong>time-bound</strong> so when we measure, we will see changes in that metric.</li></ul><p>In our simple example illustrated above, we want our customers to enjoy our products and we believe a great indicator for that is the total number of tickets being created or worked on every month. If that number goes up, it shows that customer adoption increases which, in turn, indicates they love using our product to get their jobs done.</p><p>Once we agreed on that North Star Metric, we can think about ways by means of which it can be influenced. For Zira, we, of course, need to focus on top-notch <strong>usability</strong> because this is part of our core value proposition. But there might be adjacent themes, such as making sure that IT <strong>compliance</strong> needs don’t get in our way when selling to enterprise customers. Thus, we can define <strong>strategic intents</strong> which then help to structure product work:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JHfRX7O7aI7F36jCgwf2CQ.jpeg" /><figcaption>Strategic intents supporting the North Star Metric</figcaption></figure><p>Note how each of these strategic intent will have its own metrics that, in the end, contribute to the single North Star Metric. For usability, we measure ease of use — either by directly observing users or indirectly via <a href="https://b2b-product-playbook.com/tool/nps-csat-and-ces/">Customer Effort Scores</a> or similar tools. For the IT compliance, we could look at successful RFPs but since we want to measure inside the product directly, we better track how often these specific features are used. The goal is to find a metric that</p><ul><li>contributes to the North Star Metric</li><li>is specific to the respective strategic workstream</li><li>is a leading metric rather than some lagging indicator.</li></ul><p>With that, it’s time to operationalize the product strategy by adding product initiatives:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KVUdIh9JLpJhasVxeYBT3Q.jpeg" /><figcaption>Potential product initiatives added to strategic workstreams</figcaption></figure><p>Note that this isn’t a roadmap yet, it’s not a plan, it doesn’t tell what gets done when and in which order. Instead, it is a collection of hypotheses about how the specific strategic intent might be served. I don’t want to go into the discussion of Now / Next / Later roadmaps here; nor do I want to be dogmatic about the style of these initiatives. Instead, I believe:</p><ul><li>Some initiatives will be more like big bets, with lots of unknowns, intense discovery needed by the entire product team; and maybe engineering even has to build something completely new: <em>How might we provide a lightning-fast user experience even in environments when the internet is sparse?</em></li><li>In some other cases, it will be more like a simple task list: <em>Integrate with a specific identity management service to provide SSO.</em> (With “simple” I mean: hardly any unknowns — it might still be complicated to build.)</li></ul><p>OK, now we have the business side of the house with KPI Trees. And we have a great collection of product initiatives serving the North Star Metric. Now it’s time to connect both.</p><h3>Combining KPIs and the North Star Metric</h3><p>While both structures, as explained, are different and serve different needs, they are related to one another. Or to be more precise: they <em>should</em> be related to one another and have a certain overlap. In other words:</p><p><strong>We have to be able to explain how our product initiatives contribute to certain business metrics.</strong></p><p>By doing so:</p><ul><li>We aim for a <strong>significant overlap</strong> even when we don’t have to achieve a 100% alignment. There are business metrics that we can barely influence (for example when pricing is owned by Sales). And there are product initiatives that do not directly influence business metrics (just think of tech debt).</li><li>We start with <strong>qualitative statements</strong> and only later aim to quantify the impact.</li></ul><p>Let’s look at some examples for our <strong>Zira </strong>startup:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C7FLmRlxlBXiKJ7Iz8Z58Q.jpeg" /><figcaption>Linking product initiatives to business KPIs — Example 1</figcaption></figure><p>As indicated by color-coding, <strong>we believe that with great UX, fast response times across all devices, and additional guidance we can reduce churn</strong>. Sounds pretty plausible, right? In e-commerce, there is even data on how every few milliseconds of page load impacts revenue. But for Zira, we don’t want to make quantitative guesses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xX-Hs5KQSXzbrLBfZBsM7g.jpeg" /><figcaption>Linking product initiatives to business KPIs — Example 2</figcaption></figure><p>Likewise, <strong>we believe that the initiatives in the Enterprise Theme as well as easy administration of workflows will be important to help Sales win deals with enterprise customers</strong>. Again, pretty much obvious. And by talking to our Sales team, we will learn about priorities for the initiatives sketched here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PqzMmBAAxzKUgBEF6zcNjA.jpeg" /><figcaption>Linking product initiatives to business KPIs — Example 3</figcaption></figure><p>As a third example, <strong>we believe that fast and easy-to-use UX as well as feature-rich trials will help to convert users into paying customers</strong>. This will strengthen the Product-Led Growth layer of our Zira product as a complementary approach to standard enterprise Sales.</p><h3>Summary</h3><p>Above, I have sketched how some core business metrics might look like, how product initiatives should be derived based on a product strategy that serves a North Star Metric, and — most importantly — how these two views at our business can be connected to each other.</p><p>I am convinced that we, as Product Managers, are much better positioned and will have higher chances of success if we manage to bridge both positions. At least for a significant part of our product initiatives, we need to be able to explain why we pursue them and how we believe they will impact the business. With that, our next planning session with stakeholders will become <em>sooooo </em>much easier.</p><p><em>This article was initially posted on </em><a href="https://open.substack.com/pub/b2bproductblog/p/business-kpis-vs-product-outcomes?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web">https://open.substack.com/pub/b2bproductblog/p/business-kpis-vs-product-outcomes?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57faa698d781" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Product Management Will Remain Vital]]></title>
            <link>https://medium.com/@drlenzmario/why-product-management-will-remain-vital-2c01caddbf5d?source=rss-a3d448eb3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c01caddbf5d</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Mario Lenz]]></dc:creator>
            <pubDate>Tue, 27 Jun 2023 16:32:35 GMT</pubDate>
            <atom:updated>2023-06-27T16:32:35.266Z</atom:updated>
            <content:encoded><![CDATA[<p>Several heated debates have been triggered after Airbnb recently announced its decision to combine Product Management and Product Marketing into one department. This may or may not be the right step for Airbnb, maybe it helps them to improve communication and collaboration within the organization.</p><p>But in general, I strongly disagree. I cannot see Product Management going away anytime soon. At least not in innovative companies trying to bring new solutions to solve problems of customers. I am deeply convinced that embedding Product Management in Marketing (or any other team for that argument) will be counterproductive in the long run.</p><h3>What is Product Management?</h3><p>To start with, I don’t care about job titles. Instead, I am referring to a Product Manager as the person being accountable for reducing the <a href="https://b2b-product-playbook.com/home/the-four-key-risks/">four key risks</a> around products:</p><ul><li>Customer <strong>value</strong>, sometimes called desirability, so that customers receive a benefit</li><li><strong>Usability</strong> so that target users can effectively utilize the product or even better love it</li><li><strong>Viability</strong> so that a sustained business can be built</li><li><strong>Feasibility</strong> in terms of technology</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*_P34Efv2apApdc6WK7KJ2w.png" /></figure><p>In early-stage companies, the founders might be in charge. But later, when the company grows, a dedicated team needs to take over. To me, this is Product Management: a person or team that is accountable to reduce and mitigate these four risks and, thus, increasing the chances of success for the business.</p><p>Why am I so convinced that our guild is here to stay? Let’s dissect a few arguments in favor of Airbnb‘s decision that I have come across (*):</p><h3>#1 The Gap Filled by Product Management Will Disappear</h3><p>One argument that I came across repeatedly was like this:</p><blockquote>Traditionally, creative, technical, and business functions used to be separated by way of a huge gap. Product Managers acted as the glue to bridge that gap. But this gap is closing now.</blockquote><p>I think exactly the opposite is true: Technology is getting increasingly complex and evolving quickly. The variety of devices grows. Customers are more and more demanding. All of that will result in higher degrees of specialization, both on the technology as well as the creative side. Ideally, such a team of specialists cooperates in an empowered team guided by a clear vision — defined by Product Management.</p><p>Of course, members of technology or creative teams can take over parts of the Product Manager‘s job. Tony Fadell might be a role model here, initially leading creative teams, then building innovative products, and finally ending up as the CEO and Founder of Nest. On a much smaller scale, I experienced a similar path from software engineer to Engineering Leader to CTO to CPO. But in these cases, the person who previously worked in another role becomes a Product Manager — rather than making the role obsolete.</p><h3>#2 Automation Will Make Product Management Obsolete</h3><p>A second argument I often hear is:</p><blockquote>With advances in Generative AI as well as No Code tools, the entire Product Management job will be automated.</blockquote><p>Sure. All Product Managers will be replaced by a Generative AI that applies web3 on top of the blockchain. Sarcasm end.</p><p>As impressive as some of the tools are, Generative AI involves training models to learn patterns and characteristics from existing data and then using that knowledge to produce original content that resembles the training data. As a consequence, all these tools do not possess genuine understanding or creativity to come up with new solutions.</p><p>It requires human curiosity to dig deeper into the problems of customers. It needs empathy to truly understand the pain points of users. Even more so in business domains that are not fully digitized, where not every single step taken by users is immediately visible in some data log. It’s simple to eye-track users of a digital app to optimize usability. Now try the same for construction workers, in industrial manufacturing or chemical plants.</p><h3>#3 CPG Successfully Worked with Brand Managers</h3><p>I have read something like that by a brand manager in one of the global players around fast-moving customer goods (FMCG):</p><blockquote>It’s been like that forever in CPG. We never needed Product Managers because it’s the brand that matters. So, like in CPG, everybody should have just Brand Managers.</blockquote><p>C’mon. I have built products for that market in previous roles. I know a bit so let’s be honest. CPG and FMCG are barely about product innovation. Maybe they innovated in advertising and marketing, where all their budgets go. To tell us that their junk food consisting of 50% fat, 45% sugar, and 4% highly processed chemicals is healthy. Or to make us buy detergents that wash whiter than white (for 100 years). „<em>Raider is now Twix</em>“ — wow, what an innovation.</p><p>Also, Brand Managers barely do any customer research but instead outsource this to external research agencies, such as Mintel, Kantar, and the likes. As a result: they do not research and they do not build something innovative — OK, I see the point, they might not need a true Product Manager.</p><p>But this is completely different for digital products.</p><h3>#4 Product Management Needs to Own the Business</h3><p>Finally, I hear an argument that goes like this:</p><blockquote>Product Managers have to be accountable for the business success of the products they build. Hence, they will become more business leaders, similar to General Managers or Brand Managers, and their Product Management role will vanish.</blockquote><p>The first part is true. Business viability is one of the <a href="https://b2b-product-playbook.com/home/the-four-key-risks/">four key risks</a> to be addressed by Product Management. To make things even more complicated, that question arises at different levels:</p><ul><li>On the <strong>feature</strong> level: When we enhance our product with that specific feature, how will we distribute, market, and sell? How will it help the business?</li><li>On the <strong>product</strong> level: When we build that specific product, what is our target market, how do we implement Go-To-Market, and why will we win?</li><li>On the <strong>company</strong> level: What are purpose, vision, and mission? And how can we turn this into a sustained business?</li></ul><p>The latter is probably managed on the executive leadership level but feature and product level have to be considered by Product Managers.</p><p>Sometimes, I hear people arguing in favor of Product Managers owning full P&amp;L. Frankly, this is not realistic in most companies as it would involve so much more. But a Product Manager needs to care about selling and growing their product.</p><p>Product-Led Growth (PLG) is a strong movement in that direction. But when the product shall be used as the vehicle to acquire, onboard, monetize, and expand customers — who will design the details of the PLG strategy if not the Product Manager?</p><p>To summarize, I believe that the business success of products will become a more important aspect for Product Managers. This will strengthen their role — instead of making this function disappear.</p><p><em>(*) I recall these arguments top of my head as I have come across them in various blog posts or articles on LinkedIn etc. Hence, no references to specific sources or authors were given.</em></p><p><em>This post was initially pubished on </em><a href="https://open.substack.com/pub/b2bproductblog/p/why-product-management-will-remain?r=7bvtz&amp;utm_campaign=post&amp;utm_medium=web"><em>https://open.substack.com/pub/b2bproductblog/p/why-product-management-will-remain</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c01caddbf5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Illusion of Total Agility in Software Engineering]]></title>
            <link>https://medium.com/@drlenzmario/the-illusion-of-total-agility-in-software-engineering-d29c35f5c2cf?source=rss-a3d448eb3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/d29c35f5c2cf</guid>
            <dc:creator><![CDATA[Mario Lenz]]></dc:creator>
            <pubDate>Wed, 21 Jun 2023 08:13:25 GMT</pubDate>
            <atom:updated>2023-06-21T08:13:25.298Z</atom:updated>
            <content:encoded><![CDATA[<p>As a product leader, I often come across a passionate debate in favor of agile ways of working, about being open-minded and outcome-oriented instead of focusing on velocity and plans. Specifically, many software engineers demand total freedom and agility in their work without any commitments. They argue that this is the only way to foster innovation and bring about disruptive change.</p><p><strong>However, I believe that this is a flawed and unrealistic view of software engineering.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tYncZvgukTZ_ODalG_2U8g.png" /></figure><p>Firstly, not all software engineering is highly innovative. Our teams do not disrupt every single day. While there are certainly areas of software development that require cutting-edge research and development, the majority of software engineering work involves building and maintaining existing systems. I am lacking data but would assume that &gt;90% of product work is about incremental changes with hardly any unknowns: <em>The next version of an app that fixes some bugs. An extension of a mobility tool to enter markets in a neighboring country. An update of the legal stack or HR tools to cater to recent legislation. The next version of Office 365 or Google Docs.</em> Those kinds of things. This work may not be as glamorous or exciting as working on a brand-new product, but it is critical to the success of any software product. Without these foundational elements in place, any attempt at innovation or disruption is likely to fail. For that, a high level of discipline is required as well as attention to detail and a willingness to work within established frameworks and guidelines.</p><p>Secondly, even in cases where software engineers are working on innovative and disruptive projects, total freedom and agility are not necessarily ideal. In order to achieve business goals, engineers must work within certain constraints and guidelines. For example, they must adhere to industry standards and best practices, work within a defined budget and timeline, and ensure that their work integrates seamlessly with other parts of the system. Contrary to that, the demand for total freedom and agility sometimes comes at the expense of stability and predictability. When engineers are allowed to work without any commitments or constraints, they can easily become distracted and lose sight of the larger goals of the project. This can lead to missed deadlines, poor quality work, and ultimately, a failed product.</p><p>Thirdly, total freedom and agility can create a sense of chaos and confusion within the engineering team. Without clear guidelines and expectations, team members may struggle to understand their roles and responsibilities, leading to duplication of effort, miscommunication, and a lack of accountability. This is not to say that software engineers should be micromanaged or forced to work within rigid structures. Rather, it is important to strike a balance between flexibility and structure. Engineers should be given the freedom to experiment and explore new ideas — but within the context of a clearly defined project plan and timeline.</p><p>Finally, software engineering is a collaborative effort. While individual engineers may have their own ideas and approaches, they must work together as a team to achieve the desired outcome. This requires a level of commitment and accountability that cannot be achieved through total freedom and agility alone. As product managers, we must work with our engineering teams to strike a balance between innovation and stability — and foster a culture of collaboration and accountability.</p><p>Coming back to my initial statement: Don’t get me wrong. Focusing on outcomes and delivering true value are important. Disrupting an outdated industry is great. For that, a certain level of autonomy and agility is required. And most of us love that…</p><blockquote>…until, well, it comes to the monthly paycheck that most of us depend on until we have reached a certain level of financial independence.</blockquote><p>How many of us would truly go all-in? I have read quite a bit about, for example, the early days of Netflix or SpaceX, and I am not sure I would be willing to jump on these rocketships during their early days. Leave a well-paid job in a well-known company with stable growth for an unknown adventure, poorly paid, with limited chances of success? Spend months on a lonely island in the middle of the ocean, not seeing friends &amp; family for quarters, because only here you can test rockets?</p><p><strong><em>Would you?</em></strong></p><p><em>This post was initially published on </em><a href="https://open.substack.com/pub/b2bproductblog/p/the-illusion-of-total-agility-in">https://open.substack.com/pub/b2bproductblog/p/the-illusion-of-total-agility-in</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d29c35f5c2cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bringing Disruptive Innovation to B2B Customers]]></title>
            <link>https://medium.com/@drlenzmario/bringing-disruptive-innovation-to-b2b-customers-ec906a9c3b20?source=rss-a3d448eb3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec906a9c3b20</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Mario Lenz]]></dc:creator>
            <pubDate>Sun, 18 Jun 2023 17:42:50 GMT</pubDate>
            <atom:updated>2023-06-18T17:59:29.581Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>7 Tips for Successful Implementation.</strong></p><blockquote><strong>“Improve and extend — but don’t change.”</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7-p7FEUVXXEJJG6Bwhz3JQ.png" /></figure><p>As consumers of B2C apps, we enjoy frequent updates. I guess most of us have all our private systems on auto-update so that we not only benefit from the latest features but also receive security updates and such. That said, many of us probably count as early adopters in terms of the technology adoption cycle.</p><p>But then meet B2B, specifically Enterprise B2B. When many users are forced to use a certain tool because already the task at hand is a job to be done (literally) not a job they love.</p><p>Also, many of these users are occasional users because the job at hand doesn’t occur every day but maybe only once a month or even per quarter.</p><p>Or consider fluctuation in the workforce, such as in the construction industry or even businesses that are seasonal by definition (think amusement parks).</p><p>Then these users need to be trained for any (new) product, organized by the managers and HR teams of the companies. So, every change in tooling also means: new pieces of training required, and new training material, probably even in many different languages. Back we are:</p><blockquote>“Improve and extend — but don’t change.”</blockquote><p>We have all experienced it: There is an important event the next day, you rehearse carefully, and you think you are well prepared. Then Zoom or Microsoft Teams gets updated overnight and when you want to start the event, you are struggling to find your way. Now, this is annoying but not life-threatening. Picture this in harsh environments, when people work under stress in situations that could cause serious harm to humans, the environment, or equipment.</p><p>So what to do? How can you still bring the required change, specifically when it’s not just a tiny little pixel change but massive?</p><p>One key element is to involve existing customers early. Set up a <a href="https://b2b-product-playbook.com/home/implementing-customer-discovery-a-case-study/">Customer Discovery Program</a> to collect their feedback as early as possible. In a bit more detail, here are 7 tips for bringing innovation to customers successfully:</p><h3>#1 Plan Long-Term</h3><p>This will be a marathon, maybe even Iron Man. It will take a while to implement but even longer to roll out and migrate all customers.</p><blockquote>„This is great, but not so fast.“</blockquote><p>is what we heard so many times. Your customers will need time to adopt. Hence, plan for a more extended transition period. Think in quarters and years, not Sprints.</p><h3>#2 Involve Your Customers</h3><p>Do your homework and implement a <a href="https://b2b-product-playbook.com/home/implementing-customer-discovery-a-case-study/">Customer Discovery Program</a> (CDP) in order to involve existing customers as early as possible, for example by organizing <a href="https://b2b-product-playbook.com/tool/customer-advisory-board/">Customer Advisory Boards</a> (CABs). During the CDP, get as close as possible to actual users and those who are truly accountable for the business processes your product is used for.</p><h3>#3 Involve Customers Early</h3><p>Use the CDP to inform your customers as early as possible, even about blurry ideas. The earlier you share your plans with them, the sooner you will get valuable feedback that might change your plans.</p><h3>#4 Co-Develop with Customers</h3><p>Not only inform but involve them. Ideate, brainstorm ideas, prioritize, prototype, and test these prototypes — until you have achieved a good result.</p><p>As a hint, think of running something like <a href="https://b2b-product-playbook.com/tool/discovery-sprint/">Discovery Sprints</a> with your CDP, just not in a single week, five days in a row (remember, they have a business to run) but stretch the process over a longer period, say a few weeks or months.</p><h3>#5 Be Transparent Toward All Customers</h3><p>Even beyond the CDP, announce upcoming changes early to your entire customer base. Let all of them know what’s coming. Probably not at the very early stage, you will frighten them. But as soon as the ideas and plans become a bit more tangible, as soon as you have something to show and at least a rough plan.</p><h3>#6 Implement an Early-Access Program</h3><p>Initially targeting the CDP participants but later for all customers: Let them try. Ideally, this can happen in a sandbox or non-production environment so that the actual usage of your product during the daily business is not affected — for example via some training systems. This will give your customers time to prepare and also bring valuable feedback for you.</p><p>Customers want to feel they are in full control. Hence, let them decide when to test or even switch to the new experience. For that, provide configuration options so that they can decide, specifically in the early stage of the project. Think about some kind of feature toggles to opt-in, later switch to opt-out (making the new experience the new default) until you can retire the old version and thus even force the laggards among your customers.</p><h3>#7 Communicate, Communicate, Communicate</h3><p>Share status and updates both internally but also with customers. Provide opportunities to ask questions. Be prepared to answer the same questions again and again. Do all of that via every channel available to you, such as a Customer Community, dedicated webinars for Q&amp;A sessions, of course, the CDP, but also every other customer interaction.</p><p>To summarize:</p><blockquote><strong><em>Innovate to improve the life of your customers — but don’t overtax them.</em></strong></blockquote><p><em>This post was originally published via </em><a href="https://b2bproductblog.substack.com/p/bringing-disruptive-innovation-to?sd=pf">https://b2bproductblog.substack.com/p/bringing-disruptive-innovation-to</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec906a9c3b20" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Breaking Free from the Bind]]></title>
            <link>https://medium.com/@drlenzmario/breaking-free-from-the-bind-d086baa8f308?source=rss-a3d448eb3308------2</link>
            <guid isPermaLink="false">https://medium.com/p/d086baa8f308</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Mario Lenz]]></dc:creator>
            <pubDate>Mon, 12 Jun 2023 07:03:20 GMT</pubDate>
            <atom:updated>2023-06-12T07:03:20.937Z</atom:updated>
            <content:encoded><![CDATA[<h3>Overcoming the Paradox of Print vs. Agility in Product Management</h3><p>Inside today’s Product Management community, agile practitioners, and related disciplines I observe a trend that confuses me: it seems like everybody wants to publish a book. Let me be clear here when I say “book”, I mean this: <em>a long piece of text, 300+ pages, created over several months, reviewed by a few people only, then printed on paper, shipped as hard copies, and hard to change afterward</em>.</p><blockquote><em>🔥🔥🔥</em>Isn’t this exactly the waterfall approach?<em>🔥🔥🔥</em></blockquote><p>To me, it’s a paradox: while, in our daily jobs, we advocate for agility, we rely on nearly 600 years old processes to share ideas?!</p><p>To further illustrate what I am referring to, let’s compare to digital products:</p><ol><li>For digital products, we create MVPs, Fake Doors, A/B tests, and much more to ensure value and usability. But a book gets printed, shipped, and sold — take it or leave it!</li><li>Even more, for digital products we implement continuous delivery in order to be able to iterate and adjust quickly. But once a physical book is printed, it is “final” and cannot be changed at all.</li><li>For digital products, we carefully craft User Personas to understand their jobs and to optimize for these. But the book is one-size-fits-all.</li><li>We are keen to build deep analytics into digital products in order to observe and understand the behavior of users. But how do we know how readers get along with the book?</li><li>We also engage with users and customers for qualitative feedback on digital products. But before a book gets printed, it is only reviewed by maybe a handful of people.</li><li>PLG is becoming mainstream, we want to use the product for all things activation, onboarding, or selling. But every hard-copy book requires old-style Marketing.</li></ol><blockquote><strong><em>Shouldn’t every Product Manager steer clear of these situations?!</em></strong></blockquote><p>A few great exceptions exist, for example, Amplitude’s <a href="https://amplitude.com/north-star">North Star Playbook</a> or the <a href="https://herbig.co/product-discovery-hub/">Product Discovery Resources Hub</a> by Tim Herbig. They have taken the concept of a <em>book</em> and adapted it for the Internet.</p><p>We are on a similar mission by compiling our ideas, tools, frameworks, and experiences into the <strong>B2B Product Playbook</strong>. Not only is it a FREE resource but we also plan to update and extend constantly, including the involvement of other thought leaders.</p><p>Actually, it is already version 2 of our “product” since the PM Curriculum, as a free collection of resources published via Notion has been around for some years. Time not just for a minor update but a huge rework. Including a completely new website that gives us more control over structure and design — and will also allow for better engagement with our readers.</p><p>As a sneak preview, the following depicts the process we are discussing in very much detail apart from extensive libraries of tools and books:</p><figure><img alt="Double Diamond and Dual-Track Agile combined" src="https://cdn-images-1.medium.com/max/1024/1*tjvmMfMNsoEnTgRo87sepQ.png" /><figcaption>Double Diamond and Dual-Track Agile combined</figcaption></figure><p>No fluffs, not just repeating standard textbook knowledge. But proven processes, tools, methods, and hints that worked for us.</p><p>Actually, the website is already live at <a href="https://b2b-product-playbook.com/">https://b2b-product-playbook.com/</a>. It is not final yet (and probably will never be) but, hey:</p><blockquote><strong>If you are not embarrassed by the first version of your product, you’ve launched too late.</strong><br> — Reid Hoffman</blockquote><p>Being Product Managers at heart, we consider this as an <strong>experiment</strong>. We will keep adding, changing, and adjusting content based on feedback. We are also open to more contributors — just contact us.</p><p><em>This post was orginally published on </em><a href="https://b2bproductblog.substack.com/p/breaking-free-from-the-bind"><em>https://b2bproductblog.substack.com/p/breaking-free-from-the-bind</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d086baa8f308" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>