<?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[Product Maestro Blog - Medium]]></title>
        <description><![CDATA[Thoughts on Storytelling, Product Management, and Work from Home Culture - Medium]]></description>
        <link>https://medium.com/product-storytelling?source=rss----9834a544f4f4---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Product Maestro Blog - Medium</title>
            <link>https://medium.com/product-storytelling?source=rss----9834a544f4f4---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:51:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/product-storytelling" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why Covid is the perfect test for every Product Manager]]></title>
            <link>https://medium.com/product-storytelling/why-covid-is-the-perfect-test-for-every-product-manager-79d78ab13d67?source=rss----9834a544f4f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/79d78ab13d67</guid>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[storytelling]]></category>
            <dc:creator><![CDATA[Connie Kwan (Product Maestro)]]></dc:creator>
            <pubDate>Wed, 13 May 2020 12:56:00 GMT</pubDate>
            <atom:updated>2020-05-15T02:27:45.367Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Arpqc1gR2tzL_0ipIGq4jA.jpeg" /></figure><p>Covid is wartime. The future is suddenly extremely uncertain, and the entire organization is looking for direction. Wartime requires a wartime leader. Here’s what makes a wartime leader tick.</p><ul><li>Wartime leaders find that<strong> Chaos creates clarity</strong>.</li><li>Wartime leaders view <strong>Resets as opportunities</strong>.</li><li>Wartime leaders <strong>Prioritize</strong> ruthlessly.</li><li>Wartime leaders thrive on <strong>Dates</strong> and Deadlines.</li><li>Wartime leaders focus on <strong>Winning the War,</strong> not the battle.</li></ul><p>If you’re a Product Manager during Covid, you either lost your job or got 2x busier. All your roadmaps are suddenly obsolete, and you’re back to the drawing board, prioritizing ruthlessly. That might suck, but for many PMs I know, they see this as their moment to shine. They see this as a moment when the entire organization is suddenly rallied behind a central cause. And for those who lost their jobs, they see this as an opportunity to re-tool, re-set and find their next opportunity. Since the pandemic started, I have not talked to a single career PM who became a deer in the headlights. Everyone single one I talked to because intensely focused. PMs are people of action, and they see a way forward through the chaos. Career PMs are strong <a href="http://www.productmaestro.com/"><strong>storytellers</strong></a> who paint visions of the future. Those are traits of a wartime leader. And that’s why Covid was the perfect test.</p><h3>Rise to the challenge or quit being a PM</h3><p>Covid is wartime. It doesn’t matter if you’re in a peacetime organization. Every PM is impacted, because the future is suddenly extremely uncertain, and the entire organization is looking to you to provide direction. If you thrive on being a PM, then you are probably loving it. You might not like the reason for the chaos, but you’re loving the chaos itself. Because it doesn’t matter if a PM is in a chaotic startup, or the PM is in a large organization like Google or Amazon. What makes them tick is eerily similar the list of wartime leader traits above.</p><ul><li>PMs like <strong>Dates</strong> and Deadlines.</li><li>PMs <strong>Prioritize</strong> ruthlessly.</li><li>PMs focus on <strong>Winning the War</strong>, not the battle.</li></ul><p>That’s 3 of 5 in the list that are indisputable because they are literally in the job description. But let’s examine the other two on the list.</p><ul><li>PMs think <strong>Chaos creates clarity</strong></li><li>PMs view <strong>Resets as opportunities</strong></li></ul><p>When I was working at larger companies, the biggest challenge by far was galvanizing the team to action. There were many ways to do this. Deadlines was one of them. Sometimes these were driven by external factors such as industry events.</p><blockquote>But none of these levers of motivation were as effective as a good defeat.</blockquote><p>A good defeat causes resets. If a competitor wins a major account from us or we see a drastic fall in daily active users, these factors cause resets because they challenge our previous worldview. This reset causes some chaos because the future was suddenly uncertain. And a great PM would know to do the right <a href="http://www.productmaestro.com/"><strong>storytelling</strong></a> in these moments to galvanize the team and push initiatives forward. PMs in peacetime organizations are the ones trying to light a fire so they can move their team. Which means,</p><blockquote>Every PM is a wartime leader looking for a good war. Some are just stuck in peacetime organizations trying to create a war.</blockquote><p>And that’s why Covid was the perfect test. If you are a PM who thrived on the Reset, then you probably love your job. If it threw you into chaos as well, then PM might not be the right path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vY7kIakn0LQCZ1-0fR0Ehw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@joseantoniogall?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jose Antonio Gallego Vázquez</a> on <a href="https://unsplash.com/s/photos/reset?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Why are Resets so great for PMs?</h3><p>A PM leads through <a href="http://www.productmaestro.com/"><strong>storytelling</strong></a>, and Resets create blank canvases upon which new stories can be told and a new vision for the future can be painted. Resets create new realities that suddenly make previously crazy ideas seem possible, even relevant. Everyone works from home? That’s a crazy idea, until we are all suddenly forced to do it. Taking a manufacturing line that produces window shades and turning it into one that produces face shields? Impossible, until Halcyon Shades did it in 3 weeks. With our minds open to new, crazy ideas, what else could be possible? If you’re a PM, then you’d have 10 stories ready for this question. Because if you’re a PM, then you’re a wartime leader ready to leverage the next reset by telling the right <a href="http://www.productmaestro.com/"><strong>story</strong></a>.</p><p><em>Connie Kwan teaches </em><a href="http://www.productmaestro.com/"><em>Storytelling for Product Leaders</em></a><em>. She has crafted and delivered thousands of stories in her 16 years in Product Leadership. Whether it’s rallying executives, motivating teams, or convincing candidates to join a company, storytelling is at the heart of her work. She is a co-creator of the Storyteller Type system that turns the art of storytelling into a science. Find out your </em><a href="http://www.productmaestro.com/storyteller"><em>Storyteller Type</em></a><em> here.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fhpnaq7%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fhpnaq7&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/bab2986c19a430fe2a3a7c39c0ee86a6/href">https://medium.com/media/bab2986c19a430fe2a3a7c39c0ee86a6/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79d78ab13d67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-storytelling/why-covid-is-the-perfect-test-for-every-product-manager-79d78ab13d67">Why Covid is the perfect test for every Product Manager</a> was originally published in <a href="https://medium.com/product-storytelling">Product Maestro Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Discovering the Service Blueprint]]></title>
            <link>https://medium.com/product-storytelling/discovering-the-service-blueprint-27f28606ae94?source=rss----9834a544f4f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/27f28606ae94</guid>
            <category><![CDATA[service-blueprint]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[customer-journey]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Erica Salinas]]></dc:creator>
            <pubDate>Thu, 23 Apr 2020 23:26:00 GMT</pubDate>
            <atom:updated>2020-04-25T03:17:13.825Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Product Managers use the Service Blueprint to map out infrastructure services</h3><h4>Connecting the Customer Journey to Infrastructure Services</h4><p><em>Erica Salinas is a guest writer for Product Maestro’s blog. If you enjoyed this topic, subscribe to our blog and join 600+ leaders who </em><a href="https://www.productmaestro.com/gettips"><em>receive bi-weekly tips on Storytelling and Product Leadership</em></a><em>.</em></p><p>Product Managers and Researchers love maps. Empathy maps, customer journey maps, experience maps… I’m here to introduce you to the lesser known and severely underappreciated: Service Blueprint.</p><p>For those of you unfamiliar with this format, it tends to often be used to capture customer-employee interactions and employee-system interactions. However, here I’d like to share with you why the Service Blueprint is especially apt for those of us providing network/infrastructure services or providing services as part of a larger partner ecosystem. I’ll start with a brief tour of a sample Service Blueprint that I flagrantly stole off the internet. Let us begin…</p><h3><strong>What is a Service Blueprint?</strong></h3><p>A Service Blueprint is a diagram from the <strong><em>organization’s perspective</em></strong> that visualizes the relationships between customer actions, touchpoints, supporting processes, and underlying business processes as they tie into a specific customer journey.</p><p>The service blueprint is complementary to a customer journey map. In the digital service realm, it’s particularly awesome at mapping complex scenarios spanning multiple internal and external partners and systems.</p><h3><strong>Anatomy of a Service Blueprint</strong></h3><p>So what does one look like? Here is an example that I like because it is for a website, which means it does not have employee touchpoints like many examples do. Below I’ll walk through the key components and some optional ones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*chD0VAIqI9jYZ3wW65dalA.jpeg" /><figcaption>Image Credit: <a href="https://uxdesign.cc/ux-case-study-bookstore-responsive-website-redesign-195d15fe83c1">https://uxdesign.cc/ux-case-study-bookstore-responsive-website-redesign-195d15fe83c1</a></figcaption></figure><h4><strong>Lanes</strong></h4><p><strong>Physical Evidence:</strong> What the customer is interacting with to perform their actions. Examples include a website or a mobile app.</p><p><strong>Customer Actions: </strong>Actions the customer takes. Essentially the customer journey. Examples include adding an item to their shopping cart or making a payment.</p><p><strong>Frontstage Interaction: </strong>Actions that occur directly in view of the customer. Examples include a payment confirmation or a shipping notification.</p><p><strong>Backstage Interaction: </strong>Steps and activities that occur behind the scenes to support frontstage happenings. Examples include payment handling or shipping label creation.</p><p><strong>Support Processes: </strong>Internal steps and interactions that support the organization in delivering the service. Examples include maintaining a CRM system or collecting network data analytics.</p><p>In the case of a network or infrastructure provider, frontstage interactions is where partners often provide key functionality. Understanding their desired functionality helps us optimize functionality to support partner success and provide consulting services while they’re building it. Backstage interactions is where we will most often be represented. These boxes are what will turn into future engineering features and grow to contain user stories.</p><h4><strong>Lines</strong></h4><p><strong>Line of Interaction: </strong>Depicts the direct interactions between the customer and the underlying ecosystem.</p><p><strong>Line of Visibility:</strong> Separates all service activities that are visible to the customer from those that are not visible.</p><p><strong>Line of Internal Interaction: </strong>Separates processes that directly support interaction with customers from those that do not.</p><h4><strong>Optional Elements</strong></h4><p><strong>Emotion:</strong> Represents where employees are happy or frustrated.</p><p><strong>Pains / Gains:</strong> Identifies areas of inefficiency and efficiency to allow for correcting of process issues or sharing of best practices.</p><p><strong>Metrics: </strong>As-is or success metrics that are associated with each step along the customer journey</p><p>Metrics is my favorite optional element. Since that is lacking in the example above, here is another example showing time as a metric.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ke__4AciJPXNXawsFIeuqQ.png" /><figcaption>Image Credit: <a href="https://www.lucidchart.com/blog/what-is-a-service-blueprint">https://www.lucidchart.com/blog/what-is-a-service-blueprint</a></figcaption></figure><h3><strong>Why a Service Blueprint?</strong></h3><p>So why should we, infrastructure or network providers, leverage this particular artifact? Well, let me count the ways:</p><ol><li>As a network, it can often be difficult to see how the functionality we are building is tied directly to the customer journey. However, it is in understanding where we fit in and provide value to the larger ecosystem that will ensure we are prioritizing and developing the right things. The service blueprint provides a comprehensive understanding of our service ecosystem, what processes are ours to support, and how those directly tie to a successful customer journey.</li><li>Given that we have a clear picture of our service ecosystem, we can also see the required functionality and integration points across the totality of the customer journey for both internal and external partners. This allows us to ensure success and consistency throughout the entire value chain.</li><li>As we continue to evolve our network, we will be both building new functionality and modifying existing functionality to support new business use cases. The service blueprint allows us to identify what can be leveraged, what can be refactored, what can be modularized, and what must be built new. Having this visibility substantially reduces the likelihood that there will be gaps in the final implementation.</li><li>Given that we can identify the different types of functionality as detailed in #3, we are also able to identify opportunities for optimization and eliminate redundancy. Meaning, we can prevent ourselves from always building new functionality for each new use case and we can keep our code clean.</li><li>Finally, should we run into an issue with a current service offering, having a service map allows us to trace a customer issue down to its root cause process. With a map of clear dependencies and interfaces between partners, we are able to discover weaknesses that need resolution.</li></ol><p>I know you are all now wondering where Service Blueprint has been your whole life. Thus, for those wanting a deeper look, I’m also including resources to learn more below. I would love to hear stories from those of you that have already leveraged a service blueprint. And if you haven’t, try it and let me know how it goes.</p><p><em>Erica Salinas is a guest writer for Product Maestro’s blog. If you enjoyed this article, subscribe to our blog and join 600+ other leaders who </em><a href="https://www.productmaestro.com/gettips"><em>receive bi-weekly tips on Storytelling and Product Leadership</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27f28606ae94" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-storytelling/discovering-the-service-blueprint-27f28606ae94">Discovering the Service Blueprint</a> was originally published in <a href="https://medium.com/product-storytelling">Product Maestro Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Entrepreneur Support for COVID-19]]></title>
            <link>https://medium.com/product-storytelling/entrepreneur-support-for-covid-19-9c96072cf506?source=rss----9834a544f4f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/9c96072cf506</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[covid19]]></category>
            <dc:creator><![CDATA[Connie Kwan (Product Maestro)]]></dc:creator>
            <pubDate>Thu, 09 Apr 2020 04:39:48 GMT</pubDate>
            <atom:updated>2020-04-09T04:53:26.915Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*W8Tb0h_AqjCBXClglPVlmw.jpeg" /></figure><p>If you have a startup / small business impacted by COVID-19, here is a short list of resources that are available to you. Go get grants. Survive and thrive. Wishing you and your family good health.</p><ul><li><strong>SheaMoisture</strong> launched a <a href="https://www.sheamoisturefund.com/">$1 Million Fund</a> to support <strong>entrepreneurs of color</strong>. Applications open <strong>today </strong>(4/8) and have a quick turnaround.</li><li><strong>Spanx </strong><a href="https://www.spanx.com/the-red-backpack-fund">Red Backpack fund</a> is a $5 Million fund targeting <strong>women entrepreneurs</strong>. Applications opened 4/6.</li><li><strong>Facebook </strong>is offering $100 Million in cash grants and ad credits for up to 30,000 small businesses. More information can be found <a href="https://www.facebook.com/business/grants">here</a>.</li><li><strong>Verizon </strong>has donated $2.5 million to the national nonprofit Local Initiatives Support Corporation (LISC). LISC is targeting grants up to $10,000 to <strong>entrepreneurs of color and women-owned businesses</strong>. To register for the <strong>mid-April round</strong> of funding, click <a href="https://www.lisc.org/our-stories/story/verizon-and-lisc-fire-25-million-small-business-covid-19-recovery-fund">here</a>.</li><li><strong>Hello Alice</strong> is offering $10,000 grants to help small business owners. For more information about those grants and other small business resources, click <a href="https://www.covid19businesscenter.com/">here</a></li><li><strong>Microsoft </strong>is providing six months of Office 365 tools <strong>for free </strong>to enable remote collaboration, file sharing and video conferencing. For more information, click <a href="https://docs.microsoft.com/en-us/microsoftteams/e1-trial-license">here</a></li><li><strong>Tory Burch Foundation</strong> has a useful list of resources (for both funding and advice) for small businesses that can be found <a href="http://www.toryburchfoundation.org/resources/operations/business-resources-covid-19/">here</a>.</li></ul><p><em>Connie Kwan is the founder of Product Maestro. We offer Storytelling classes for Startup CEOs and Product Leaders. We also offer bespoke Storytelling and VP of Product as a service to B2B technology companies from Series A to C.</em></p><p><a href="https://www.productmaestro.com/gettips"><em>Subscribe to</em></a><em> the Product Maestro blog to receive weekly notes on Storytelling and Product Leadership for startups.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c96072cf506" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-storytelling/entrepreneur-support-for-covid-19-9c96072cf506">Entrepreneur Support for COVID-19</a> was originally published in <a href="https://medium.com/product-storytelling">Product Maestro Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Ghostbuild Your Way to A Lean Launch]]></title>
            <link>https://medium.com/product-storytelling/how-to-ghostbuild-your-way-to-a-lean-launch-3153274a5773?source=rss----9834a544f4f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/3153274a5773</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Connie Kwan (Product Maestro)]]></dc:creator>
            <pubDate>Fri, 27 Mar 2020 23:37:50 GMT</pubDate>
            <atom:updated>2020-04-20T21:34:02.527Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article is part of my blog series. Subscribe today and join 600+ other leaders who </em><a href="https://www.productmaestro.com/gettips"><em>receive my bi-weekly notes on Storytelling and Product Leadership</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*FhkpVaM3HHMiWSdX.jpg" /><figcaption><em>Originally published at </em><a href="https://www.heavybit.com/"><em>https://www.heavybit.com</em></a><em> on March 12, 2020.</em></figcaption></figure><p>Every startup team has limited resources. You have questions to answer and hypotheses to test before committing engineering resources to build the scalable version. Practicing lean launches helps your team use those resources effectively. Ghostbuilding is a great way to check the market acceptance for your products before actually building.</p><p>One of the key principles of lean launches is that you want to optimize for cycles of learning. If you can get product feedback before you invest engineering resources, you’ll be able to learn as much as possible up front, so you can ensure that more of your engineering resources are focused on building a market-accepted product.</p><p>In this article, I’ll explain what Ghostbuilding is and how you can use it to build products more efficiently.</p><h3>What is Ghostbuilding?</h3><p>Ghostbuilding is the act of creating just enough illusion of the product to test your hypotheses. This approach helps you gain higher confidence on market-acceptance of your product by the time you build your MVP.</p><p>A Ghostbuild is a light-weight product that tests your most important hypotheses. The customer sees the product working and may think that the functionality is automated by technology. But, like Wizard of Oz’s man behind the curtain, humans are powering the product behind the scenes. The product maturity progression is pictured below. You can see where Ghostbuilding fits in the products maturity lifecycle:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*Tr8l6uokXT6YSHHh.jpg" /></figure><p>A Ghostbuild sits somewhere between a prototype and a proof-of-concept. A prototype is useful for a company who is going through early stage fundraising. A prototype is also useful for <a href="https://www.heavybit.com/library/blog/navigating-enterprise-needs/">selling a complex idea to an enterprise customer</a>. The prototype has a very limited functional scope. It may need to be used only under supervision.</p><p>Conversely, the proof-of-concept is a more expensive build-out that can be used “in-the-wild” by the customer who commissioned the POC. Enterprises may pay $25k to $100k for a proof of concept. The notion does not exist for B2C companies, who typically fund their own way to their MVP.</p><h3>Ghostbuilding Software &amp; Tools</h3><p>Ghostbuilding requires many of the same software and tooling you’d need to design and launch a product. WordPress websites are useful for approximating a user interface. Other software can be used to emulate the product’s functionality, like chat integrations (Intercom or Slack), spreadsheets with macros or Google Sheets with Google Apps Script, MailChimp and IFTTT.</p><p>In addition to tooling, there is one more requirement for Ghostbuilding: a team of humans with great communication skills. The Ghostbuilding phase is full of valuable user data and feedback. Making sure that your team is collecting and processing all that valuable feedback is essential.</p><h3>Ghostbuilding Examples</h3><p>So what does a Ghostbuild really look like? Here are examples of different ways of Ghostbuilding:</p><h4>Example 1. I want to offer a role-based reporting dashboard.</h4><p>Reporting dashboards is a common feature across many different SaaS products. Different users often need different insights. The challenge here is learning what information is most useful for which user persona. A project like this doesn’t necessarily need any engineering work at all — the simplest way to test this is to simply send human-created PDF reports to customers. Your customers will give you feedback on what else they’d like to see on the PDF. By the time you’re ready to build out the dashboard, you’ll be very close to knowing what the customer actually needs.</p><p>This is a relatively simple example of Ghostbuilding. But what if you need to test something more complex?</p><h4>Example 2. I want to offer an AI for choosing restaurants.</h4><p>If I want to test the market demand for this, I don’t need to actually build the AI engine. I would build a WordPress website and integrate Intercom. Then people can message in their requests for restaurant recommendations. I would hire a few humans, probably customer service agents, give them a playbook on how to answer questions, and let them go at it. The playbook information will be based on some research that I do ahead of time on the scope of questions an AI engine could answer, and extrapolate slightly from there. Because I don’t intend to use real humans in my eventual product, this approach lets me collect data on a feasible version of the product.</p><p>After a week of testing this Ghostbuild, I would analyze the data. Sample metrics for this project might be:</p><ul><li>User adoption rates</li><li>Customer satisfaction</li><li>How close the agents were able to stick to the Playbook while satisfying customer inquiries</li><li>What kind of questions customers are asking</li></ul><p>This will all help guide me in deciding whether to build this product, and if I do, what I should optimize for before I invest in any deep engineering to build out this AI engine.</p><h3>When to Ghostbuild a Feature (and When Not to)</h3><p>Where Ghostbuilding will have the most impact will vary depending on if you are selling to consumer or enterprise. In enterprise, you have the option to acquire a POC contract. Basically, you can have one customer pay your way to an MVP. In that case, you need to build light, but may choose not to Ghostbuild because you have a committed user and you need more robust automation. But Ghostbuilding is still possible, especially if your product needs a bridge path to a real product, like AI. Or, if your customer is rolling out a limited pilot, you can offer a lower cost proof of concept to them by Ghostbuilding.</p><p>For a consumer audience, you likely have to pay your own way to an MVP. Because customer acquisition cost is lower than in enterprise, it really makes sense to Ghostbuild.</p><p>Keep in mind that when you Ghostbuild, you might have to discontinue the service temporarily while you transition to the real product, so you don’t want to get to the point where customers are relying on your Ghostbuild for too long.</p><h3>The Cost of Ghostbuilding</h3><p>While Ghostbuilding is a way to conserve engineering resources, you will need a person with <a href="https://www.heavybit.com/library/blog/kwans-hierarchy-of-product-needs-the-four-levels-of-product-managers/">product sense and user research experience</a> to lead the effort. In more complex projects, you may also need some engineering to Ghostbuild.</p><p>Typically, you’d spend 1- 3 months Ghostbuilding. Depending on your Ghostbuild path, You may need a software configuration expert (IT), which may be in the range of $5–10K per month. Or you can do this part yourself by googling how to configure certain software. In the reporting PDF sample above, you might do this entirely without engineering. For a more complex project, you might need one front end engineer and half a backend engineer’s time, or one full stack engineer for $10K-30k/mo, to help you hook things up. Properly scoping the project before you begin will help you estimate how much to budget for a Ghostbuild.</p><p>In summary, if you’ve decided to Ghostbuild, consider the overall cost of the project, including:</p><ul><li>Are there SaaS products you’ll need to sign up for and connect for the Ghostbuild?</li><li>How many hours of engineering time will you need?</li><li>Can you do the product and user research part yourself or do you need to contract a product resource who can advise you?</li></ul><h3>Ghostbuilding Pitfalls to Avoid</h3><p>Ghostbuilding shares many of the same pitfalls of classic product building. For instance, you might try to build too large of a scope. To avoid this, start with determining the questions that you need answered before you start building. Make a list of the variations you’re considering, and look for ways to quickly Ghostbuild.</p><p>Another common pitfall is creating too magical of an experience with Ghostbuilding that cannot be recreated in the real version. Remember, you are using humans to underpin some of the functionality that you will automate later, and some of these functionalities might not translate that well into automation. If you can, consult the technology architect halfway through your Ghostbuilding phase. They should be able to give you a better sense of how the real version will be built later on, and whether it’s feasible to support the features you want.</p><p>Keep in mind that the point of the Ghostbuilding is to validate hypotheses, not to serve customers in a sustainable way. It’s easy for teams to forget that they’re Ghostbuilding and try to use that code to support users at scale. As soon as you have your questions 80% answered, then it’s time to start actually building. When hypotheses are proofed and the spec is ready, hire a real engineering team with an architect and start over.</p><p>What am I missing? I would love to hear your ideas in the comments below.</p><p><em>If you enjoyed this article, please </em><a href="https://www.productmaestro.com/gettips"><em>Sign Up</em></a><em> for the Product Maestro blog, my bi-weekly leadership note read by 600+ leaders.</em></p><p>Connie Kwan is the founder of Product Maestro, offering Storytelling and VP of Product as a service to B2B technology companies from Series A to C. <a href="https://www.productmaestro.com/gettips">Subscribe to</a> the Product Maestro blog to receive weekly notes on Storytelling and Product Leadership.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3153274a5773" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-storytelling/how-to-ghostbuild-your-way-to-a-lean-launch-3153274a5773">How to Ghostbuild Your Way to A Lean Launch</a> was originally published in <a href="https://medium.com/product-storytelling">Product Maestro Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Work From Home Transition Guide for Leaders]]></title>
            <link>https://medium.com/product-storytelling/the-work-from-home-transition-guide-for-leaders-561eb51b6541?source=rss----9834a544f4f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/561eb51b6541</guid>
            <category><![CDATA[remote-leadership]]></category>
            <category><![CDATA[work-from-home]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Connie Kwan (Product Maestro)]]></dc:creator>
            <pubDate>Wed, 18 Mar 2020 21:47:44 GMT</pubDate>
            <atom:updated>2020-05-15T02:31:17.136Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Leader’s transition guide to Working from Home</h3><p>My husband kisses me goodbye, starts his car, and drives into morning traffic. I wave, hug my warm mug and walk the 5 steps to my home office. I never thought I would be able to do it while in a leadership role.</p><p>I’ve been leading teams for years. And for years I’ve heard, and believed, that leadership cannot be done from home. How would I “walk the halls?” But in the last 6 months I’ve transitioned to leading a team that works from home, while I work from home myself. I now have colleagues and clients in Europe, Asia, and across North America. This was a deliberate move because I believe work-from-home will be the future of knowledge workers and I wanted a front row seat to how it’s done. For a long time, the lonely engineer who has one meeting a week was allowed to work from home. But with the advance of technology and culture, it is possible, nay, more <em>effective</em>, to not just work from home but also lead from home. Leading from home is different than leading by walking through the halls. And there is a way to set up a team for success when they work from home. So allow me to share with my observations and lessons learned while the transition is still fresh on my mind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OTJ550tDwdcqBK0P_osYOQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mimithian?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mimi Thian</a> on <a href="https://unsplash.com/s/photos/work-from-home?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>First, some context on my journey. For years I’ve been leading teams of Product Managers, with a sprinkle of members from design and marketing. I’ve led teams who are:</p><p>(1) Co-located, completely from top to bottom, so I can walk the halls.</p><p>(2) Hybrid, with co-location between PM, Design and Engineering, and remote reporting lines to leadership. I had to lead part of my team from afar, but each of my teams could have hallway conversations.</p><p>(3) Work from home, completely fromtop to bottom. Everyone is set up to work from home. There is a physical office in a HQ city and some people drop in a few days a week. But many prefer to work from home or co-working spaces. Half the company does not live in the HQ city, so they always dial in. Each year we all fly to one location for a one-week workshop.</p><p>Transitioning to work from home as a leader was not easy. But technology has finally caught up to support a work from home arrangement for knowledge workers. And working in the Hybrid environment has given me the foresight to screen for a team that would succeed in a work from home arrangement.</p><p>There are three aspects to enabling success when working or leading from home: 1) Home set-up, 2) Company Culture, and 3) Tooling.</p><h3>Setting up your Home for Work from Home success</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_re56tsAl8hAkalNo8vkIg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jonathan_francisca?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jonathan Francisca</a> on <a href="https://unsplash.com/s/photos/work-from-home-woman?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>My first three weeks were rough. Working from home can be isolating and distracting at the same time. While it may seem easier to focus without interruption from co-workers, my mind wanders to the pantry whenever the work becomes challenging. My body was less happy too because I had less built-in walking in my routine as I often stay in the house all day. On top of that I had a time zone difference with my team, so my workday started at 5pm. After testing out a number of set-ups, I have found the following to be the most helpful:</p><ul><li><strong>Set up a separate space as the office, away from the main area of the home. </strong>The space needs to have a door. Ideally it’s up a flight of stairs so there is a commute, even a short one. Working from the family couch may work for a meeting or two, but did not work very well on a sustained basis. It’s also more respectful to everyone else on the calls if you have good audio quality. There’s nothing worse than someone calling in from a cafe with a noisy background, especially if that person is leading the meeting.</li><li><strong>Set up the workstation with a treadmill, or exercise bike</strong>. Some people are disciplined about going for a morning run. I shy away from the cold air when it’s cloudy outside. But if I’m literally sitting on an exercise bike while I dial into every meeting, it’s easy enough to move my legs and get some bonus exercise.</li><li><strong>Set up social phone calls.</strong> Going to an office often means heading into town or a busier area where it’s easier to meet up for lunch with friends. Working from home means I’m in a more residential area. I would have to ‘commute’ to attend a social lunch, which is just enough of a barrier to keep it from happening too often. Since there are no water cooler conversations either, I’m no longer hitting my human-interaction quota each day to stay healthy. Scheduling social phone calls with friends really helped keep me sane.</li><li>Pro-tip: <strong>Use two devices</strong>. You might dial in from the mobile phone on occasion while screen sharing from the desktop. This can greatly improve the audio quality. It seems mobile phones have better audio compression than laptops.</li></ul><blockquote>Want more articles like this? Subscribe at <a href="https://www.productmaestro.com/tips">https://www.productmaestro.com/tips</a></blockquote><h3>Setting up your Culture for Work from Home success</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-hOquUgIuJNgMYWHy9NGA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mnm_all?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">mnm.all</a> on <a href="https://unsplash.com/s/photos/culture?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The culture of the company is paramount when it comes to work from home. With less face-time, norms and work styles have to change. With no serendipitous hallway brainstorms, deliberate effort has to be made to move random thoughts forward into an action plan. Here’s what I learned about setting up a company’s culture for work-from-home success:</p><ul><li><strong>Autonomy, Purpose, &amp; Mastery has to be the motivator for every employee. </strong>And leadership is responsible for ensuring this. This was explained in Dan Pink’s book Drive. While this ought to be true in every company, the truth is that at co-located companies it’s possible to get away without it for some time. Employees show up for work, they sit next to their peers, they do the work through social motivation. But in a work-from-home company it’s not possible to get away without it. As a leader, here’s how I think about the three.</li><li><strong>Autonomy</strong> refers to a clear delegation of authority. What decisions can the employee make on their own vs escalate to leadership? Being clear about this autonomy allows people to execute in their own time zone and unblock their own work. In a work from home culture that incorporates multiple time zones, this clear delegation of authority is particularly important. Otherwise employees can be blocked in their work for hours before a decision can be taken to unblock it.</li><li><strong>Purpose</strong> is the reason they show up. This may be different from the company purpose though. As a product leader, I work on creating a compelling company vision. As a people leader, I also tap into each person’s personal purpose, which may be different. Some join the company to help people. Some join the company to be a part of something bigger. Some join to have steady, flexible work that gives them a chance at mastering a skill. Making sure each person is compelled by the company vision is step one. But the second, more relevant step is understanding each person’s individual purpose so that I can align their deliverables with that purpose. When their purpose and deliverables align, I don’t have to look over anyone’s shoulder, ever.</li><li><strong>Mastery</strong> is their source of pride. Every person is an expert at something or interested in becoming an expert at something. In co-located companies it’s easier to spot each other’s strengths, but in work-from-home companies I need to deliberately call out these attributes in my team. When new hires join I ask them to write a “How to work with me” blog post that highlights their own strengths, so that others can come to them for those strengths. For those working on becoming an expert at something, I pull in people and resources who can help them build up that expertise. When work becomes a source of pride, I have a very happy, productive team.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fhpnaq7%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fhpnaq7&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/bab2986c19a430fe2a3a7c39c0ee86a6/href">https://medium.com/media/bab2986c19a430fe2a3a7c39c0ee86a6/href</a></iframe><ul><li><strong>Get religious about Writing things down</strong>. With limited face to face interaction, different time zones and different cultures, it’s impossible to move the ball forward without writing things down, religiously. There are many tools that enable communication, and I’ll get to those in the next section, but more importantly, the culture needs to support the use of these tools. People’s habits would have to change. Every meeting, every decision, every idea thread, every discussion and more needs to be deliberately written down then kept in a place where others can see and add comments. Sometimes it’s written casually in Slack, sometimes the topic elevates to a Confluence page. Then someone needs to own that page, and actively integrate new comments into the body of the page and evolve the idea, decision, or plan. This means you need the next item, which is:</li><li><strong>At least one Strong Communicator on every team. </strong>Communicators are people who understand the channels of communication, and which to use for which type of communication. They’re the ones who know when it’s appropriate to send messages back and forth on Slack, and when that conversation should elevate to a meeting. They know when decisions can be closed by sending around a written <a href="https://medium.com/product-storytelling/the-most-powerful-tool-in-the-product-management-toolbox-d88078ab961d">DACI</a>, or when a face to face discussion is necessary. Having a sprinkle of very strong communicators across different teams will help broker communication efficiency, and ultimately teach everyone else to make good judgments regarding communication mediums.</li><li><strong>Low egos. Giving people the benefit of the doubt. </strong>There is a greater chance of miscommunication in a work-from-home setting. Written messages sometimes come across differently than spoken ones. In addition to having strong communicators set at standard for communication, make sure you hire for low ego. These are people who seek to understand rather than jump to conclusions. These are people who engage in a time of tension rather than disengage.</li><li><strong>A Transparent, high-trust ethos.</strong> When communication is a bottleneck, the last thing you want is to create more ‘grapevines.’ Silos naturally form in any organization. In work-from-home settings, it’s even more important to shatter those silos. Take appropriate Slack DM (direct messages) and move them to the group chat. Shine light on decisions in progress that may affect certain employees. There is a tremendous amount of trust in operating this way. You’ll have to trust that sensitive information will not be leaked by your employees. You’ll have to trust that people will show up with low egos and keep the broader objective in mind when they read about decisions that may affect them. You’ll have to trust that people will stay constructive when they contribute to the conversation. You’ll have to trust that people are paying attention to the conversation in the first place.</li></ul><blockquote><strong>Trust is an incredibly important aspect of leading a work-from-home team, and establishing that trust with and among the team is the most important job for any leader of a work-from-home team.</strong></blockquote><blockquote>Get more articles like this, subscribe at: <a href="https://www.productmaestro.com/tips">https://www.productmaestro.com/tips</a></blockquote><h3>Setting up your Tooling for Work from home success</h3><p>When transitioning from a co-located team to a work-from-home team, there are only two main toolset areas to pay attention to. These are collaboration tools, and timezone management tools. You may be using many of these collaboration tools already. By transitioning to work-from-home, you will lean on these tools more and discover ways to use it that may even surprise you. Here are the most important tools in your work-from-home toolset.</p><h4><strong>Collaboration tools for the whole company:</strong></h4><ul><li>General Collaboration and social interaction (Confluence, Slack, Notion etc)</li><li>Brainstorm tools for short 1–2h brainstorms (Jamboard, Miro, Trello, etc)</li><li>Cultivating Culture (Google Meet, Zoom, Slack, Microsoft Teams)</li></ul><h4><strong>Collaboration tools specific to Product and Engineering:</strong></h4><ul><li>Leading and Communicating Vision and WorkPlans (Dragonboat, Loom, Confluence, etc)</li><li>Product demo and gathering feedback (Loom, Invision, etc)</li><li>Tracking execution (JIRA, <a href="http://www.dragonboat.io/">Dragonboat</a>)</li></ul><h4><strong>Timezone management tools:</strong></h4><p>These are mostly settings within your current calendar system rather than a new toolset. It also involves a coordinated use of the calendar so each employee’s availability and work hours are clear. I use Google Calendar but I imagine Outlook would have similar features as well.</p><ul><li>Multiple Timezone setting, so you can view 2 time zones at once next to the calendar</li><li>Setting up a separate calendar to track vacations / out of office</li><li>Setting up “work hours” so a moon symbol shows up next to your name when a meeting is outside your office hours.</li><li>Grant permission for everyone in your organization to see the contents of your calendar. This speaks to the Transparent, high-trust ethos mentioned earlier. When my colleagues can see what my meeting is, it’s easier for them to schedule a group meeting over my 1:1 time, assuming that I can move that 1:1 easily. This requires a high-trust environment, and not everyone is ready to do this. But it saves me and my colleagues an incredible amount of time in scheduling. There is also an added benefit of understanding what others are working on. For example, during a meeting with my CEO, she observed on my calendar that I have a meeting with another executive later the same day. So she asked me to relay a concept she just shared with me to that executive, and to evolve that concept. This saves her the 30 min or more necessary to separately schedule time with that executive. It’s extremely efficient.</li></ul><p>Lastly, since I work with multiple time zones, I have a separate app to show multiple time zones at once called Worldtimebuddy. I use it to find a time for those crazy meetings involving three extreme timezones.</p><p>As you can see, working and leading from home can take some transition work. But as I watch my husband pull into traffic again today, I have to say that it’s all worth it.</p><p><em>Connie Kwan offers VP Product as a Service for B2B technology companies. She coaches CEOs on product and brand story, roadmap strategy and work-from-home culture. Find our more at </em><a href="http://www./"><em>www.productmaestro.com</em></a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fhpnaq7%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fhpnaq7&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/bab2986c19a430fe2a3a7c39c0ee86a6/href">https://medium.com/media/bab2986c19a430fe2a3a7c39c0ee86a6/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=561eb51b6541" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-storytelling/the-work-from-home-transition-guide-for-leaders-561eb51b6541">The Work From Home Transition Guide for Leaders</a> was originally published in <a href="https://medium.com/product-storytelling">Product Maestro Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The most powerful tool in the Product management toolbox]]></title>
            <link>https://medium.com/product-storytelling/the-most-powerful-tool-in-the-product-management-toolbox-d88078ab961d?source=rss----9834a544f4f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/d88078ab961d</guid>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[tools-of-titans]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Connie Kwan (Product Maestro)]]></dc:creator>
            <pubDate>Mon, 09 Mar 2020 15:36:01 GMT</pubDate>
            <atom:updated>2020-03-12T06:38:51.226Z</atom:updated>
            <content:encoded><![CDATA[<p>Product Management makes decisions, lots of them. Some days it’s 10 small decisions about the product interface, some days it’s one major decision about a $3M acquisition. Decision making is part and parcel to the job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xVAOuSmrd1VCKirVS6RzCg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@soymeraki?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Javier Allegue Barros</a> on <a href="https://unsplash.com/s/photos/decision?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Yet, decision making is the most critical and contentious activity that any team undertakes. Thus, having a trustworthy and systematic way to approach decision making is an important part of any Product team’s arsenal.</p><p>There are many ways to make a decision. Here are some common frameworks:</p><ul><li>The loudest person in the room wins (I’m sure we’ve all seen this movie before)</li><li>The most mentioned name/item/project wins (sadly, this is how elections work)</li><li>Choose two people who represent opposite views, have them arm-wrestle for it (bring some popcorn for this one)</li><li>The most senior in rank decides (unfortunately, this person might not be close enough to problem to make an informed decision)</li><li>Everyone votes and everyone has to agree (this often creates a stalemate)</li><li>Everyone chickens out and delay the decision for as long as possible (sadly, this happens more often than we’d like, and makes life very hard for the execution team, as they need to build for all scenarios)</li></ul><p>As much as we claim to be objective when making a decision, we are only human. And we are subject to:</p><ul><li>Recency bias</li><li>Anchoring bias</li><li>Availability bias</li><li>Bandwagon effect</li><li>Choice-supportive bias</li><li>Confirmation bias</li></ul><p>And this is not even the <a href="https://minnstate.edu/system/hr/talent_management/documents/12%20Cognitive%20Biases%20Infographic%20v%204.pdf">full list</a>. When it comes to decision making, we are influenced by all of the above, company politics and personal fears. “How will I be perceived if I push for decision A?” “Will voting against decision B alienate me from manager X?”. Talk about a minefield.</p><h3>Deciding to Decide</h3><p>In order to streamline decisions then, it’s necessary to remove personal fears, company politics and help the team focus on the work. To do this, one of my favorite decision making frameworks is the DACI.</p><blockquote><strong>D</strong> <strong>=</strong> Driver — the person who shepherds the decision</blockquote><blockquote><strong>A =</strong> Approver — the person making the final call, ideally one person. If it’s a committee, then it should be an odd number of people.</blockquote><blockquote><strong>C =</strong> Contributor — all persons providing data and point of view to build the options and pros/cons table.</blockquote><blockquote><strong>I = </strong>Informed — all persons who are interested in the decision outcome, and whose work may be impacted by the outcome.</blockquote><p>The DACI document also includes:</p><ul><li>The Decision Statement</li><li>The Background</li><li>The Pros/Cons table</li><li>The due date of the decision</li><li>A revisit date for the decision, if applicable</li></ul><h3>How does the DACI work?</h3><p>In this framework, the Driver first makes a determination about how to decide. This is an important step that establishes an environment for objective decision making. First, the Driver assigns an Approver. Whereas a decision without an explicit Approver often defaults to the highest-ranked person in the room, this framework allows a deliberate assigning of the Approver. Thus, the best person to make the decision, usually someone closer to the problem, can be assigned. In some instances, multiple Approvers may be assigned on a decision. In this case an odd number of Approvers can prevent a deadlock and speed up the decision.</p><p>The Driver also writes up the DACI document and pulls in Contributors to add relevant information. The most important part of the DACI document is the Decision Statement. Sometimes this can take a while to write up properly. I’ve seen 3–4 re-writes on the Decision Statement itself. But by going through this process, the decision itself is clarified and properly scoped, which makes the decision making easier and the post-decision communication much much easier. Then the pros/cons table is created.</p><p>Finally, the Driver facilitates a discussion on the decision to make sure the Approver(s) have enough information at their disposal to make an informed and objective decision. Let’s see an example of a DACI write-up in this simple but illustrative decision scenario.</p><blockquote><strong>Background:</strong></blockquote><blockquote>We’ve had many request for a dog-friendly workplace, we would like to evaluate whether we will allow it, and if so, how.</blockquote><blockquote><strong>Decision Statement: </strong>Shall we allow dogs at work?</blockquote><blockquote><strong>Status: </strong>In progress</blockquote><blockquote><strong>Driver:</strong> @Connie Kwan</blockquote><blockquote><strong>Approver</strong>: @CEO</blockquote><blockquote><strong>Contributors: </strong>@Head of HR @General Counsel</blockquote><blockquote><strong>Informed: </strong>@everyone</blockquote><blockquote><strong>Due date: </strong>Mar 3, 2020</blockquote><blockquote><strong>Decision Outcome: </strong>Option 2B: All<strong> </strong>dogs who have obedience training are allowed to come to work. There is a 3 strike policy, after which the dog cannot return to to the workplace for 1 year. We will have a trial period of 30 days before confirming this new policy.</blockquote><blockquote><strong>Re-visit Date: </strong>Apr 3, 2020, when trial period is over. Decide on whether to make policy permanent.</blockquote><blockquote><strong>Options Considered</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*S5z9fHa_PMPymHRzLeskZA.png" /></figure><p>The DACI lays out the options clearly for the stakeholders to debate. As new considerations were brought up, such as adding a trial period, it was added as an option. By writing this up in an internal forum such as a Confluence page, Notion page, or other collaboration spaces, all employees can see the decision in progress, and we could collect input as the decision moved forward.</p><p>The final decision included additional layers on Option 2B, such as requiring obedience training and a 3-strike policy. So this DACI document is a living document that evolves as the discussion progresses. It also serves as an audit trail for future reference, which has come into use more times than I can count.</p><h3>When should I use a DACI?</h3><p>While not all decisions require a fully fledged DACI, critical decisions that span multiple teams can use a clear DACI.</p><p>I’ve used DACIs to decide pricing strategy, finalize website copy, debate marketplace policies, weigh the pros and cons of architecture options. I’ve used it to finalize branding details, and to choose a contracting agency to hire. I’ve used it so much that, even when I don’t write out the DACI, I run through a virtual DACI. In my head, I decide who should decide, by when to decide, I clarify my decision statement, and juggle an abbreviated pros/cons table. It’s useful for deciding on a company acquisition, or for couples buying a house. It is, without question, the most powerful tool in my product management, and life, toolbox.</p><h3>What are the common pitfalls of a DACI?</h3><p><strong>Common pitfall #1: Using DACI to replace actual stakeholder management</strong></p><p>I’ve seen DACI misused. The most important thing to remember is that:</p><blockquote>A DACI does NOT replace the stakeholder management aspect of your decision shepherding process.</blockquote><p>So keep those meetings you would otherwise have to talk things through with the right people. Have the 1:1 and group meetings that are necessary to align the team. The DACI shall not and will not replace any of that. What it does provide though is a framework, a way to document and standardize the process.</p><blockquote>A DACI provides clarity to all stakeholders, transparency to the organization, and closure on the decision.</blockquote><p>A DACI also allows you to trace past decisions and improve the organization’s decision making capability over time. But what it does not do is replace the work required to shepherd the decision to a meaningful close.</p><p><strong>Common Pitfall #2: A culture that does not respect the DACI</strong></p><p>A DACI requires a culture that respects its use. One of the main problems a DACI solves for is the unnecessary re-opening of decisions. This re-opening of past decisions causes a lot of thrash in an organization. A DACI solves this problem with decision finality. But for this to work, everyone involved in the decision must respect that when a final decision is taken and documented in the DACI, it stays that way barring either the “revisit date” on the DACI, or truly extenuating circumstances.</p><p>If this culture does not already exist, then introducing the use of a DACI often requires introducing the culture of respecting the DACI. Executive sponsorship is a must. Some organizations adapt nicely to this, some don’t. Keeping an eye on who is causing decision thrash, and re-training on the DACI concept over time helps the organization transition. It often takes 5–10 DACIs before the organization truly understands how to use the framework.</p><p>Have you used a DACI? How has your experience been implementing DACI at your organization? And what is your most powerful tool in your toolbox? Tell us in the comments!</p><p><em>Please 👏 this article. For further reading, check out:</em></p><ul><li><a href="https://medium.com/product-storytelling/kwans-hierarchy-of-product-needs-the-four-levels-of-product-managers-d598ac09b25b">Kwan’s Hierarchy of Product Needs</a></li><li><a href="https://medium.com/@connie.kwan/agile-is-a-mindset-not-a-methodology-ddad66d813f0">Agile is a mindset not a methodology</a></li></ul><p><em>Want more actionable tips on Product Management? Subscribe at: </em><a href="http://www.productmaestro.com/tips?utm_source=medium_blog&amp;utm_medium=blog&amp;utm_campaign=medium_blog">www.productmaestro.com/tips</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d88078ab961d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-storytelling/the-most-powerful-tool-in-the-product-management-toolbox-d88078ab961d">The most powerful tool in the Product management toolbox</a> was originally published in <a href="https://medium.com/product-storytelling">Product Maestro Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kwan’s Hierarchy of Product Needs: The Four Levels of Product Managers]]></title>
            <link>https://medium.com/product-storytelling/kwans-hierarchy-of-product-needs-the-four-levels-of-product-managers-d598ac09b25b?source=rss----9834a544f4f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/d598ac09b25b</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[organization-design]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Connie Kwan (Product Maestro)]]></dc:creator>
            <pubDate>Mon, 01 Apr 2019 15:16:00 GMT</pubDate>
            <atom:updated>2019-07-08T21:57:20.106Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*D8UA1RR09YlSysTkmmQWkg.jpeg" /></figure><p>For a young company, the value of a VP of Product or CPO can be difficult to ascertain. Many argue that a senior PM with 3–8 years of experience would satisfy the business’ strategic needs. And that’s indeed true for the first PM hire as I outlined in <a href="https://medium.com/product-storytelling/from-0-to-1-hiring-your-first-product-manager-c0cd98d2cdc6">my 0–1 article</a>. On the other hand, a CPO brings a deeper and more strategic product perspective that can help companies build a vision for the future and optimize their current focus.</p><blockquote><em>The dilemma is that while CPOs add significantly greater value than junior and senior PMs, they are expensive resources.</em></blockquote><p>To successfully navigate this dilemma, let’s break it down by understanding the product needs your business is likely to encounter. First off, know that your PM’s job is to drive decisions. The higher stakes your decision, the more experience you’d want in your PM to help drive those decisions. Before product-market fit, many hypotheses are being tested, so each decision has minimal impact as you only have 5 customers. But most successful businesses will outgrow their initial product staff and need experience at the table as their audience grows. So by understanding your future needs today, you can find ways to get what you need without overspending.</p><p>The real question might not be how long can you survive, but how soon will you start benefiting from the contributions of an experienced product leader. Thus I have broken it down into Kwan’s “Hierarchy of product needs” below. In my experience, the best way to judge whether or not your company needs to hire a CPO, or a fractional CPO, is by assessing where you stand on this hierarchy of needs.</p><h3>Kwan’s Hierarchy of Product Needs</h3><p>Much like <a href="https://en.wikipedia.org/wiki/Maslow%27s_hierarchy_of_needs">Maslow’s Hierarchy of Needs</a>, a business has a hierarchy of product management needs. These are displayed in the chart below. The product titles associated with each hierarchy are estimations, and provide an easier way to think about the framework. Clearly a CPO at a large enterprise has a different role to play than in a small company. But regardless of the title under consideration for your hire, laying out these points helps clarify the product scope that you need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*sqbSMFLsK76zH2ST2gct0w.jpeg" /><figcaption>Get additional tips on Product Management at <a href="http://www.producmaestro.com/tips">www.productmaestro.com/tips</a></figcaption></figure><p>As business needs progress so do the skills, experience, and network needed to perform them. Different businesses will grow each need differently. But each lower level need must be met before a higher level need can be addressed. Let’s start at the bottom of the pyramid.</p><h3>Level 1: Shipping ⛵</h3><p>The most basic need that a PM satisfies is shipping features. At smaller companies, your tech lead and/or your first PM will handle this need. At larger companies a project manager may satisfy this need, especially when cross-product features are involved. This involves day-to-day tackling of large and small decisions that block the successful release of a new feature.</p><p>This can range from debating with design on the right feature specifics, to testing some of those specifics with customer input. From communicating the feature on a specification to engineering to working with engineering day-to-day to ensure a successful release of the new feature. It involves informing customers of the new release and managing the success metrics of the release. Your PM is showing up at team standups, weighing in on JIRA and Invision (or equivalent), and often participating in retros.</p><h3>Level 2: Planning 🚂</h3><p>The role of a more senior PM is to continually challenge product-market fit and keep the team aligned on a 3–6 month, mid-term vision, of the product. This role requires considerably more EQ on both the customer and the stakeholder management front.</p><p>On the customer front, the PM needs to be able to creatively draw out real customer needs. This survey and interview technique is more of an art than a science, and comes with experience. The PM also needs to build the vision for the product using multiple inputs, then rally your team on this vision. Major EQ needed here. The vision needs to continue to drive product-market fit, and adjustments are elegantly made along the way.</p><p>At small companies your PM at this level also handles the Shipping function. When paired with a strong technical lead who can take on the burdens of engineering team operations, this senior PM would more fully take on both competitive analysis, and pricing and packaging decisions.</p><h3>Level 3: Strategic ✈️</h3><p>At this stage of the company, you are taking off. You have product-market fit and enough runway to survive 2–3 years. So it makes sense for your PM to start visioning for the 2 year mark. Don’t confuse this with the overall company vision, which is a BHAG (big hairy audacious goal) laid down by the founder that can be as far out as 5–10 years. That company vision is meant to be a rally-cry, blood-stirring, moonshot.</p><p>Your Strategic PM, usually director level or VP level, will take that company vision, and lay out the pathways that pave your way towards that BHAG. This PM will raise a debate on the validity of each of those pathways, and explore ways to test and de-risk each. For example, a decision to use cloud or on-prem deployment, to build vs. buy certain features within the product, or to invest in a new product area to win market share. These decisions move the company down a very different path, and rallying stakeholders through these decisions is what your Strategic PM will do.</p><h3>Level 4: Strategic Partnering 🚀</h3><p>If you’re considering a full time CPO-only PM, meaning a PM dedicated to only CPO level functions and not other earlier level functions, then your company is likely experiencing rocketship growth. You’re looking to bolster your moat with product bets while designing an organization that will sustain your growth.</p><p>Your CPO will help set and reinforce that culture for your product organization. You might be courting very lucrative and strategic enterprise accounts beyond a basic customer relationship. These can require roadmap commitments and multi-year contracts. Your CPO needs to flank your VP Sales on customer visits to tell the product story, close the deals and make sure you can deliver without compromising your product strength in your market.</p><p>Partnerships from outside the company become important, and your CPO needs to bring these opportunities to the table alongside your CEO and CFO. Your CPO will take your BHAG moonshot and lay out the 5 year plan to it, identifying key product holes that you must fill with product bets or M&amp;A opportunities before getting to the moon.</p><p>Finally, your CPO tells your powerful product story, for your board, for your customers, for your team, and helps you keep the funding or revenue flowing.</p><h3>The Right Startup CPO</h3><p>You might find yourself needing some of the functions of a CPO before you are in rocketship stage. Consider what you need specifically before making this hire. It is more economical and flexible to retain the services of a fractional CPO for certain needs.</p><p>For example, fundraising, assessing product bets, winning key enterprise accounts, designing the organization for growth, and product vision facilitation are often better accomplished with a well-networked part time CPO who has an outside perspective. On the other hand, ongoing board relations, carrying the product vision and building culture are better handled with a full time dedicated hire.</p><p>The luckiest scenario would be finding a PM with Level 3 capabilities who can stretch to Level 4. Then you can backfill specific needs with a fractional CPO until you’re ready to expand. The appointment of a CPO indicates readiness for more sophisticated strategic planning and execution. And ultimately the founder and board would have to determine the right timing based on the circumstance. Good luck out there!</p><p><em>Please 👏 this article. For further reading, check out:</em></p><ul><li><a href="https://medium.com/product-storytelling/why-is-a-product-manager-like-a-head-chef-5978a76ab70c">Why is a Product Manager like a Head Chef?</a></li><li><a href="https://medium.com/@connie.kwan/how-a-migrating-giraffe-gives-a-brand-a-boost-b39b27d9496a">How a migrating giraffe gives a brand a boost</a></li><li><a href="https://medium.com/@connie.kwan/agile-is-a-mindset-not-a-methodology-ddad66d813f0">Agile is a mindset not a methodology</a></li></ul><p><em>Have questions about hiring or Product Strategy? Get tips at </em><a href="http://www.productmaestro.com/tips"><em>www.productmaestro.com/tips</em></a><em> </em>🎭👊🙏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d598ac09b25b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-storytelling/kwans-hierarchy-of-product-needs-the-four-levels-of-product-managers-d598ac09b25b">Kwan’s Hierarchy of Product Needs: The Four Levels of Product Managers</a> was originally published in <a href="https://medium.com/product-storytelling">Product Maestro Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why is a Product Manager like a Head Chef?]]></title>
            <link>https://medium.com/product-storytelling/why-is-a-product-manager-like-a-head-chef-5978a76ab70c?source=rss----9834a544f4f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/5978a76ab70c</guid>
            <category><![CDATA[analogy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[food]]></category>
            <dc:creator><![CDATA[Connie Kwan (Product Maestro)]]></dc:creator>
            <pubDate>Wed, 20 Mar 2019 00:29:03 GMT</pubDate>
            <atom:updated>2019-03-20T00:29:03.600Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fMqhJU6OL8Z4XvGpAvJ69Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/boaDpmC-_Xo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Fabrizio Magoni</a> on <a href="https://unsplash.com/search/photos/chef?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Today, a product manager asked me: How much time should I spend on the current sprint vs future features? Good question. A better one is, what should I be doing when the current sprint is under-way? Should I be so swamped that I don’t have time to contemplate the next 3 sprints?</p><p>Imagine for a moment that you’re the chef de cuisine, or head chef, of a restaurant. You have designed the recipes, the team is trained on the menu, and the restaurant is open for dinner service. Now, how much time should you spend in the kitchen? The answer: none. Head chefs of well run restaurants are always standing at “the pass.” The pass is the place where finished dishes are passed from the kitchen to the waiting staff to be served. The head chef is quality checking to make sure the finished product meets the agreed standard before hitting the customer’s table, and to send anything back that doesn’t qualify. You can identify this person by the cloth they’re holding to wipe the rim of any less than perfect plate.</p><p>In this way, the product manager is like a head chef. The recipes you designed is your spec, the team is trained on the “menu” during your spec hand-off meeting, and the restaurant, or your sprint, is open. You product is being produced, and it’s your job to make sure what hits customer’s hands is of the quality specified. Product managers that find themselves re-writing recipes on the fly have failed to prepare adequately. Sure, questions come up during implementation, but 99% of those questions should be small trade-offs handle-able by the designer. Major implementation hiccups should have been contemplated prior to sprint start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*AZO8MuBePa8L2IeOn58V-A.png" /><figcaption>Subscribe at: <a href="http://www.productmaestro.com/tips">www.productmaestro.com/tips</a></figcaption></figure><blockquote>“Being Agile doesn’t mean changing the recipes on the fly while tonight’s dinner service is in progress. It means having the systems in place to respond to changing customer tastes rapidly. It means creating and serving an entirely different menu next week, if that’s what it takes to stay relevant.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*AXppXUBwJDmF8KOR6TG8jQ.jpeg" /><figcaption>Photo by Monty Rakusen. At Scratch Bar and Restaurant, where they have no servers. <a href="https://www.foodtribute.com/621/621/">https://www.foodtribute.com/621/621/</a></figcaption></figure><p>So to answer the original question of how much time a product manager should spend on current sprint vs future features, the answer is 5% vs 95%. By the way, once the excellent chef de cuisine has spent some time at the pass, they often circulate out to the tables to meet some diners, all the while imaging the next menu in their head.</p><p><em>Please 👏 this article. For further reading, check out:</em></p><ul><li><a href="https://medium.com/@connie.kwan/what-do-managers-look-for-when-hiring-pms-8c4be3736d75">What do managers look for when hiring PMs?</a></li><li><a href="https://medium.com/@connie.kwan/how-a-migrating-giraffe-gives-a-brand-a-boost-b39b27d9496a">How a migrating giraffe gives a brand a boost</a></li><li><a href="https://medium.com/@connie.kwan/agile-is-a-mindset-not-a-methodology-ddad66d813f0">Agile is a mindset not a methodology</a></li></ul><p><em>Have questions about hiring or Product Strategy? Get tips at </em><a href="http://www.productmaestro.com/tips"><em>www.productmaestro.com/tips</em></a><em> </em>🎭👊🙏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5978a76ab70c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-storytelling/why-is-a-product-manager-like-a-head-chef-5978a76ab70c">Why is a Product Manager like a Head Chef?</a> was originally published in <a href="https://medium.com/product-storytelling">Product Maestro Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile is a mindset not a methodology]]></title>
            <link>https://medium.com/product-storytelling/agile-is-a-mindset-not-a-methodology-ddad66d813f0?source=rss----9834a544f4f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/ddad66d813f0</guid>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Connie Kwan (Product Maestro)]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 01:45:36 GMT</pubDate>
            <atom:updated>2019-03-19T01:47:11.285Z</atom:updated>
            <content:encoded><![CDATA[<p>“Agile is a mindset not a technology.” That’s what the head of a 500 person org at SAS said to me once. I had the pleasure to meet her along with 50 other software leaders at the <a href="https://www.modev.com/exo-software-summit">EXO Software Leadership Summit</a> this month where we discussed how companies large and small experience Agile and Cloud transformations. Attendees include CTO of Cloud Platform Business at VMWare, Head of UX at WebMD, Managing Director at Schwab and Directors for engineering and product from Uber. I also had the pleasure to meet Tarah Wheeler van Vlack, author of Women in Tech and CEO of <a href="https://fizzmint.com/">Fizzmint</a>. Here’s my picture of her autographed book:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*ZudFEw4gXrZ98fJo.jpg" /></figure><p>Unlike a conference with scheduled talks and a zombie audience, we sat UN style and had frank discussions about the topics du jour. This year the conversation tended towards Engineering leadership, the structure of engineering teams, and the realities of adopting Agile and Cloud into a company. In general, there are three strong factors that correlate heavily with a company that runs Agile:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*AZO8MuBePa8L2IeOn58V-A.png" /><figcaption>Subscribe at: <a href="http://www.productmaestro.com/tips?utm_source=medium_blog&amp;utm_medium=blog&amp;utm_campaign=medium_blog">www.productmaestro.com/tips</a></figcaption></figure><ol><li>Being in Cloud and having a strong micro services architecture</li><li>Having a new codebase, usually hosted in the Cloud and less than 5 years old</li><li>Having a large number of customers that each have weaker voices on the product roadmap, as opposed to a handful of very large customers that are on long contracts and strongly influences the roadmap</li></ol><p>We also had a discussion on OKRs, and since we are still early in our adoption curve, I thought I’d share some bullets on what I learned:</p><p><strong>How other companies experience OKRs</strong></p><ul><li>Generally takes a few quarters for the organization to adopt</li><li>Not all implementations are across company, at two of the attending companies only one division is using it fully, but full company adoption is best.</li><li>O = Objectives and KR = Key Results, both can carry over across quarters, though objectives are more likely to be across-quarters.</li><li>There should be no more than 3–4 objectives and key results per level</li><li>OKRs should be measured by business value, instead of technical accomplishment</li><li>This 1+ hour video about OKRs is highly recommended</li><li>BetterWorks is a product used at one attending company to track OKRs.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*AZO8MuBePa8L2IeOn58V-A.png" /><figcaption>Subscribe at: <a href="http://www.productmaestro.com/tips?utm_source=medium_blog&amp;utm_medium=blog&amp;utm_campaign=medium_blog">www.productmaestro.com/tips</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddad66d813f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-storytelling/agile-is-a-mindset-not-a-methodology-ddad66d813f0">Agile is a mindset not a methodology</a> was originally published in <a href="https://medium.com/product-storytelling">Product Maestro Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Great Product Managers are not experts on the product, but on the customer]]></title>
            <link>https://medium.com/product-storytelling/great-product-managers-are-not-experts-on-the-product-but-on-the-customer-ad34339d6550?source=rss----9834a544f4f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/ad34339d6550</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Connie Kwan (Product Maestro)]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 01:41:18 GMT</pubDate>
            <atom:updated>2019-03-19T01:41:11.258Z</atom:updated>
            <content:encoded><![CDATA[<p>I found two great quotes from Abhishek at Freshdesk’s <a href="https://hackernoon.com/why-the-best-product-managers-don-t-build-the-features-their-users-ask-for-beb75fcc540b">excellent article</a>. Thought I’d share. The main points are very valid.</p><ol><li>“At it’s core, the fundamental responsibility of a product manager is not to be the company’s leading expert on the product but to be the company’s leading expert on the customer. At a fundamental level, product management deals with the most difficult problem in human experience: how to see things from other people’s point of view.”</li><li>“A company isn’t a product-creating and product-enhancing establishment, but rather a customer-creating and customer-retaining establishment.”</li></ol><p>Is your product organization experts on your customers?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*AZO8MuBePa8L2IeOn58V-A.png" /><figcaption>Subscribe at: <a href="http://www.productmaestro.com/tips?utm_source=medium_blog&amp;utm_medium=blog&amp;utm_campaign=medium_blog">www.productmaestro.com/tips</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad34339d6550" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-storytelling/great-product-managers-are-not-experts-on-the-product-but-on-the-customer-ad34339d6550">Great Product Managers are not experts on the product, but on the customer</a> was originally published in <a href="https://medium.com/product-storytelling">Product Maestro Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>