<?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 Ellen Gottesdiener on Medium]]></title>
        <description><![CDATA[Stories by Ellen Gottesdiener on Medium]]></description>
        <link>https://medium.com/@ellengott?source=rss-34455d614558------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tv3s9sUMImjJ7RegogsyPw.jpeg</url>
            <title>Stories by Ellen Gottesdiener on Medium</title>
            <link>https://medium.com/@ellengott?source=rss-34455d614558------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:51:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ellengott/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[Workshop by Design Canvas: Making Collaboration Work]]></title>
            <link>https://medium.com/@ellengott/workshop-by-design-canvas-making-collaboration-work-75b41ef549df?source=rss-34455d614558------2</link>
            <guid isPermaLink="false">https://medium.com/p/75b41ef549df</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ellen Gottesdiener]]></dc:creator>
            <pubDate>Thu, 10 Sep 2020 18:26:16 GMT</pubDate>
            <atom:updated>2020-09-11T15:24:44.512Z</atom:updated>
            <content:encoded><![CDATA[<p>The heart of successful product management and product development is a collaborating community of team members operating with shared goals, mutual trust, and learning mechanisms for evolving products and processes. I have found one of the best ways to create a healthy product community is with facilitated workshops.</p><p>These workshops are driven by product management requiring buy-in of multiple work products, including:</p><ul><li>Clearly defined product vision, goals, strategy, and quantifiable customer outcomes</li><li>Market research results, competitive analysis, and pricing strategy</li><li>User research and product discovery plans and findings</li><li>Product roadmap, release and launch plans, and ongoing retrospectives</li></ul><p>After defining what a workshop is, you’ll learn how to use the <em>Workshop by Design Canvas</em> to help your product organization improve collaboration.</p><h3>What Are Workshops?</h3><p>A workshop is an event that includes a carefully selected group of product stakeholders and content experts who work together to explore, define, create, correct, and decide upon deliverables and work products. A workshop goes well beyond a meeting. Meetings typically involve information exchange and often involve little or limited participation.</p><p>Workshops (facilitated workshop, collaborative workshop, or design session) should offer a rich learning experience. A successful workshop needs to be structured, having a standard set of attributes where participants:</p><ul><li>Join together to create work products designed to achieve shared goals</li><li>Agree ahead of time on the work products to be discussed in the workshop</li><li>Define and use a <a href="https://www.ebgconsulting.com/blog/decide-how-to-decide-empowering-product-ownership/"><strong>decision-making rule and process</strong></a></li><li>Follow an agreed-upon process and agenda</li><li>Use visual tools that ignite diverse views and encourage creative thinking</li><li>Have the right mix of skills, experience, and knowledge to produce and reach closure on work products interdependently</li></ul><p>But active workshop participation doesn’t “just happen.” <a href="https://www.ebgconsulting.com/blog/collaboration-works-ingredients-for-successful-workshops/"><strong>Collaboration must be designed into the workshop</strong></a>. How can a workshop be designed to tap into the collective wisdom of a product team? The key is preparation.</p><h3>When not to use a workshop</h3><p>Reconsider having a workshop when any of these circumstances take place:</p><ul><li>There isn’t the necessary commitment that the right people will attend or prepare for the workshop. Surrogate (or last-minute) participants are always a bad idea.</li><li>A skilled, neutral facilitator isn’t available.</li><li>Team members cannot make product decisions or take action right away.</li><li>There is a lack of clarity on the workshop’s purpose.</li><li>Conflict is brewing, ill will is high, or trust is low among the participants. In that case, a workshop dedicated to surface issues, address conflicts, and focus on values-based collaboration would be important. [3, 4]The Six Ps and the Workshop by Design Canvas</li></ul><p>To design a collaborative workshop, define using what I call the <strong><em>Six Ps</em></strong>: purpose, participants, principles, products, place, and process. [1, 2] These six elements provide a framework for designing a successful workshop, regardless if it is held live in a conference room or virtual.</p><p>The <strong>Workshop by Design Canvas</strong> is a visual tool for using the Six Ps. It helps the team answer the purpose (why), participants (who), principles (how), products (what), place (where), and process (when) for any workshop to be successful:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hr-y8sXnXRykjxIk.png" /></figure><p><em>Source: EBG Consulting | Workshop by Design Canvas | Download the </em><a href="https://www.ebgconsulting.com/WorkshopByDesignCanvas(EBG-Gottesdiener).pdf"><strong><em>Workshop by Design Canvas</em></strong></a></p><p>Filling out each of the Six Ps on the canvas for a product roadmapping workshop is described below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1G-psMZ7rRYJMyPa.png" /></figure><p>Source EBG Consulting | Workshop by Design Canvas</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*dDqLh-DkLmFy6Mo_.jpg" /><figcaption>Workshop Purpose (image by Ellen Gottesdiener)</figcaption></figure><h3>Purpose (the Why for Having the Workshop)</h3><p><strong>Description:</strong> Summarize a brief description of the reason the workshop is being held.</p><p><strong>Rationale:</strong> The workshop purpose outlines the reason and justification for the workshop. It explains why the workshop is being conducted and serves as a frame of reference. Don’t undervalue the benefits of a well-defined yet straightforward statement of purpose.</p><p><strong>Tips:</strong></p><ul><li>Limit the purpose to three or fewer sentences, keep it short and sweet.</li><li>Avoid listing the workshop’s products.</li><li>Always ensure that the purpose is understood, shared, and motivating to all participants.</li></ul><p>Ask the following questions:</p><ul><li>Why do we need this facilitated workshop?</li><li>What is the problem, need, or opportunity to be solved together?</li><li>Who has a stake or interest in the purpose (this leads you to possible participants)?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/319/0*QfiAQ007DMpQoVAs.jpg" /><figcaption>Workshop Products (image by Ellen Gottesdiener)</figcaption></figure><h3>Products (What the Workshop Produces)</h3><p><strong>Description:</strong> The identification of work products (inputs and outputs) needed for a successful workshop.</p><p><strong>Rationale:</strong> Specify the format, level of precision, and completion criteria for each output deliverable. To achieve the outputs to the level of detail and completeness participants require, workshop inputs should be identified. Workshop input products help jumpstart and accelerate workshop activities. Inputs are also used to test that workshop completion criteria are associated with each output.</p><p><strong>Tips:</strong></p><ul><li>Identify the workshop’s output products and then identify the inputs that will create them.</li><li>Specify “doneness” tests (acceptance criteria) for all outputs, including their format, format, and completion criteria.</li><li>Identify any templates, standards, style guides, formats, and other elements that guide how your output products will be represented<br>Represent workshop products using visual models, images, and shapes to increase learning, spark innovation, and improve retention.</li></ul><p>Ask the following:</p><ul><li>What will the workshop produce?</li><li>What tangible deliverables will be created?</li><li>What intangible deliverables will be produced (e.g., decisions, retrospective feedback)?</li><li>What input products will be used to create the output products (e.g., prioritization criteria, customer data, glossary of product terms, personas, market data, strategic goals, marketing collateral)?</li><li>What pre-work or pre-reading would be useful for participants to “get their head in the game” before the workshop?</li></ul><h3>Participants (Who Is in the Workshop)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/0*-Sdu_6Vz8avPG_iQ.jpg" /><figcaption>Workshop Participants (image by Ellen Gottesdiener)</figcaption></figure><p><strong>Description:</strong> The individuals who will attend and sponsor the workshop.</p><p><strong>Rationale:</strong> The right participants are essential for the exploration, evaluation, and confirmation of work performed in the workshop. Having the right participants can literally save weeks (if not months) and reduce the cost of delays when participants:</p><ul><li>Offer a mix of disciplines, knowledge, and skills</li><li>Have the authority to make decisions in real-time</li></ul><p><strong>Tips:</strong></p><ul><li>Clarify early in planning who the workshop sponsor is and consult with her on the workshop purpose, products, and participants.</li><li>Ensure that content participants are committed the entire time and are knowledgeable and empowered to participate in decision-making.</li><li>Include all the necessary workshop roles (see sidebar “Workshop Roles”)</li><li>Content participants include product partners that represent these three voices:<br><strong>Customer:</strong> Use the product, buy the product, or advise on the purchase or use of the product.<br><strong>Business:</strong> Authorize, legitimatize, or pay for product development or purchase of a commercial software product.<br><strong>Technology:</strong> Design, build, buy, test, deploy, deliver, and support the product.</li><li>How many participants should attend a workshop? Additional people require more time or fewer workshop products. Follow this guideline:<br>“Invite as few as possible and as many as necessary.”</li><li>Two facilitators are needed in virtual workshops. They can switch off the facilitation role while one manages the virtual environment and technical issues.</li><li>Consider having a workshop <strong><em>Readout</em></strong> (see “The Workshop Readout” sidebar at the end of the article)</li></ul><p>Ask the following:</p><ul><li>Who can help us achieve the purpose?</li><li>Who holds useful information to be shared or has skills helpful to create workshop products?</li><li>Who needs to participate in the decisions to be made?</li></ul><h3>Can the Product Manager Facilitate?</h3><p>The best workshop experiences occur when the facilitator is both a skilled facilitator and neutral to an expected outcome. Example collaborative workshops a Product Manager should design and plan include:</p><ul><li>A product strategy</li><li>Discovery research, planning sprints, releases, and launches</li><li>Product roadmap and plans, synchronized with sales, marketing, and customer support plans</li></ul><p>It is often challenging to remain neutral since a Product Manager typically has a stake in all of these work products.</p><p><em>Can you facilitate?</em></p><p>Ask yourself if you have the group facilitation skills necessary to serve the participants toward achieving shared outcomes. Can you neutrally manage conflict, recognize the ebb and flow of energy, adjust the process, and objectively evaluate progress to make course corrections?</p><p>Next, can you be objectively neutral to the outcomes? If so, determine if the workshop participants believe that you can be a neutral facilitator. If not, identify another facilitator.</p><h3>Workshop Roles</h3><p>A well-designed workshop includes these roles:</p><p><strong>Sponsor:</strong><em> The person with the administrative and financial authority to ensure the workshop takes place. </em>It is usually helpful for the sponsor to reach out to participants before the workshop to encourage their full preparation and participation. If the sponsor isn’t an attendee, she is ideally a Readout attendee.</p><p><strong>Content participants:<em> </em></strong><em>Individuals who are committed to attending the entire session.</em> They are knowledgeable and empowered to participate in making decisions. No surrogates allowed!</p><p><strong>Facilitator: </strong><em>A skilled, content-neutral person who helps plan, design, and facilitate the event. </em>The facilitator has these responsibilities:</p><ul><li>Before the workshop: Meets with the sponsor and works with the planning team to design the session.</li><li>During the workshop: Guides the group by helping participants achieve their purpose to deliver products. Intervenes only as needed.</li><li>After the workshop: Follows up with participants to adjust future workshops based on progress made.</li></ul><p><strong>Observer:</strong> <em>Those who need or want to learn about the workshop content or process but don’t participate. </em>They attend only with the agreement of the participants.</p><p><strong>Readout attendee:</strong> <em>Stakeholders with a stake or interest in the workshop but do not need to participate in the workshop product creation.</em> See sidebar: “The Workshop Readout” for more information.</p><p><strong>Recorder:</strong><em> Someone who captures real-time documentation for use during and after the workshop.</em> Maybe not needed if the participants are documenting their work.</p><p><strong>Supporting cast:</strong> <em>Subject matter experts requested to be on call to answer potential questions during the workshop.</em></p><p><strong>Workshop planning team:</strong><em> participants who collaborate with the facilitator to design and plan the workshop.</em> The planning team should be on call for “adjustment huddles” during the workshop. A balanced planning team includes representatives from the customer, business, and technology communities. Including the facilitator, strive for no more than four members to the workshop planning team.</p><h3>Principles (Guidelines for How Participants Will Interact)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/0*IW4A7Ln6tDo1oBHR.jpg" /><figcaption>Workshop Principles (image by Ellen Gottesdiener)</figcaption></figure><p><strong>Description:</strong> The rules of engagement (sometimes called working agreements or ground rules) for the workshop.</p><p><strong>Rationale:</strong> Principles are the guidelines for participation and codes of conduct that participants agree to follow. These principles should dictate decision-making rules and processes for <a href="https://www.ebgconsulting.com/blog/decide-how-to-decide-empowering-product-ownership/"><strong>deciding how to decide.</strong></a></p><p>Workshop principles serve as a process guide for the facilitator as well as the participants. The facilitator needs to collaborate with the workshop sponsor and the participants to establish principles that must be clear and acceptable to all participants. The facilitator verifies workshop effectiveness with regular check-ins and makes adjustments, if necessary.</p><p><strong>Tips:</strong></p><ul><li>Strive for no more than nine.</li><li>Go beyond the usual procedures grounds rules (i.e., start and end on time) and employ values-based group rules. [3, 4]</li><li>Have the planning team seed a few workshop principles and then ask participants to collaborate early on to review, revise, and extend them.</li><li>Always include the workshop decision process and decision-making rules.</li><li>Visit rules of engagement periodically throughout the workshop.</li></ul><p>Ask:</p><ul><li>How will we function as a group to optimize our time?</li><li>What working agreements or guidelines for participation will enable us to have a productive session?</li><li>What decision rules and decision processes will we use in our workshop to reach closure?</li><li>What values inform how we will collaborate?</li></ul><h3>When Decision-Makers Are Not Available</h3><p>Workshop outcomes usually demand real-time decisions by high-level decision-makers. Swift closure maintains momentum, saves time and money, and respects the time spent by participants. At times, decision-makers are unavailable to participate in a collaboration workshop. They often do not need to be present for the entire workshop because they may not have the detailed subject matter expertise required to create work products. These decision-makers can be instrumental in reaching closure or lending final approval on the workshop outcomes. There is one rule for making decisions in a workshop:</p><p><em>Don’t put off making decisions until later. Don’t let decisions linger.</em></p><p>Ask non-participating decision-makers to attend the Readout (see sidebar: “The Workshop Readout”). If they are not available for the Readout, schedule a specific date decision-makers will commit to the following:</p><ul><li>Sharing decisions</li><li>How decisions will be communicated to workshop attendees</li></ul><p>At the start of a workshop, share these commitments with all participants.</p><h3>Place (Where the Workshop Is Located)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*Ks_v5VE-rUBwSMu7.jpg" /><figcaption>Workshop Place (image by Ellen Gottesdiener)</figcaption></figure><p><strong>Description:</strong> The physical or virtual location for the workshop.</p><p><strong>Rationale:</strong> The location of a workshop and the physical space (whether real-time or virtual) can influence the outcome.</p><p>During the COVID-19 pandemic, most organizations use virtual spaces. The facilitator must prepare the space on virtual platforms (such as <a href="https://www.mural.co/"><strong>Mural</strong></a> and <a href="https://miro.com/"><strong>Miro</strong></a>). Be sure to prepare participants by giving them early access to warm-up boards to practice using the visual platform. By completing a few visual activities, the team will gain familiarity with the tool and connect everyone with the workshop’s purpose.</p><p>In evaluating the best place to hold a physically co-located workshop, consider room size, wall space, support for refreshments, seating (a u-shaped seating arrangement is best), availability of outlets, access to on-call subject matter experts (via physical proximity or phones), space for observers and Readout attendees, and the benefits of participants being near their usual workspace.</p><p><strong>Tips:</strong></p><p>Virtual workshops:</p><ul><li>Ensure and test bandwidth for the tools you will use.</li><li>Setup the workspaces in advance and be ready with pre-defined groups for breakout activities.</li><li>Test, test, and test the workspace that has been designed. (Just in case, consider having a backup plan.)</li><li>Request everyone’s video camera is enabled, and be sure everyone has enough bandwidth to support streaming video.</li></ul><p>Physically co-located workshops:</p><ul><li>Be sure there is sufficient wall space, and that permission is granted for using walls and windows for hanging posters.</li><li>Reserve the space and include sufficient lead-time to set up the room and post-workshop time to capture and dismantle wall work.</li><li>Plan for tables, chairs, and any equipment: projector, easels, conference phone, a camera for photographing walls, and a clock-timer.</li><li>Order materials, and don’t forget food, snacks, and beverages</li></ul><p>Ask:</p><ul><li>What location (virtual or physical)?</li><li>What time and duration?</li><li>What tools will we use for our virtual space? What tools and materials will be used for the physically co-located session?</li><li>For physical space, what room setup and supplies are needed?</li></ul><h3>Process (When Activities Take Place)</h3><p><strong>Description:</strong> The ordered set of activities and their timing (e.g., the agenda).</p><p><strong>Rationale:</strong> Activities need to follow a logical flow where the outputs from one activity can be used as inputs by another workshop activity (or in a post-workshop follow-up action).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*-kbVUwzyAM7Q8hjdaqw5uA.png" /><figcaption>Workshop Process (image by Ellen Gottesdiener)</figcaption></figure><p>To streamline the process and improve your workshop products’ quality, it’s always a good idea to follow <a href="https://www.ebgconsulting.com/CollaborationPatterns.pdf"><strong>collaboration patterns</strong></a>. For example, the Divide, Conquer, Correct, and Collect pattern provides process guidance on how to create a complex work product (such as a product roadmap). Participants tackle component elements of that work product in subgroup breakouts. Then, in the plenary (when the whole group is together), synthesize the elements, ensure quality, and build group synergy.</p><p><strong>Tips:</strong></p><p>Design:</p><ul><li>Craft the process based on output products.</li><li>Design and assign pre-work to accelerate the workshop.</li><li>Conduct a workshop orientation if you have a complex set of products to create.</li><li>Start the workshop by setting the context with the Six Ps and a short sponsor kickoff.</li><li>Use icebreakers that help participants, both individually and as a group, relate to the workshop purpose.</li><li>Make generous use of breaks and mix the makeup into small groups in breakouts. This allows for adequate plenary time to debrief breakout work in a shared space.</li><li>Engage and energize participants with varied activities, interaction styles (e.g., individual, small group, whole group/plenary), and materials (if physically collocated).</li><li>Don’t underestimate the power of short breaks to maintain energy.</li><li>Draw on a rich legacy of activities skilled facilitators use. [4–10]</li></ul><p>Group Dynamics:</p><ul><li>Honor the immutable law of group dynamics: forming, storming, norming, performing, adjourning. [11] As teams tend to progress through these phases, they often transition in a non-linear fashion.</li><li>Conflict is energy. Help the group use it productively.</li><li>Inject short retrospectives throughout the workshop: inspect and adapt the workshop process.</li><li>In the final workshop retrospective, ask observers to share their views after participants provide retrospective feedback.</li></ul><p>Timing:</p><ul><li>Be realistic about allocating time for each activity. Divide activities into a maximum of 60-minute increments to keep focus and maintain energy.</li><li>Schedule short breaks every 60 to 90 minutes.</li><li>Assess the total time participants will require to produce outputs. Keep in mind that larger groups of 6 or more usually need more time. If your estimated time is longer than planned, divide the workshop into multiple sessions (adjusting purpose, products, and participants as required.)</li></ul><p>Ask:</p><ul><li>When activities occur during the workshop?</li><li>What is the flow, sequence, and timing for each item?</li><li>What kickoff and close interaction do we include for each activity and the entire workshop?</li><li>When do we inject short retrospectives to inspect and adapt workshop progress? What retrospective activities will be used?</li><li>What will be the POP (purpose, outcome, process) shared to introduce each activity?</li></ul><h3>The Workshop Readout</h3><p>A <em>Readout</em> is an optional information session delivered by the workshop participants to interested non-attendees (executive management and decision-makers). During the Readout, participants share their outcomes, learnings, recommendations, and requests. These are shared in a way that impacts the workshop experience.</p><p>Readouts are typically held at the end of a facilitated workshop (or a series of related workshops) before the final workshop retrospective.</p><p>The Readout has these characteristics:</p><ul><li>Takes place in the workshop room or shared virtual space</li><li>Lasts about 45 minutes</li><li>Uses the work products in the room</li></ul><h3>Summary</h3><p>Thriving product communities collaborate continually using well-designed facilitated workshops. The<em> Workshop by Design Canvas</em> provides a framework to help you think through your workshop design. It provides the structure necessary to permit flexibility during the workshop and helps set the context for healthy collaboration.</p><p><em>Note: this blog was originally posted </em><a href="https://www.ebgconsulting.com/blog/workshop-by-design-canvas-making-collaboration-work/"><em>here</em></a><em>, on </em><a href="https://www.ebgconsulting.com/blog/"><em>EBG’s Blog</em></a><em> on 4 September 2020.</em></p><h3>References</h3><ol><li>Gottesdiener, Ellen. “Collaborate for Quality.” STQE Magazine, March/April 2001.</li><li>Gottesdiener, Ellen. Requirements by Collaboration. Addison-Wesley Professional, 2002.</li><li>Schwarz, Roger. The Skilled Facilitator. A Comprehensive Resource for Consultants, Facilitators, Managers, Trainers, and Coaches. 3rd Ed. Jossey-Bass, November 2016.</li><li>Note: For an online sampler of values-based group rules read Rogers “8 Ground Rules for Great Meetings”, available at: <a href="http://www.schwarzassociates.com/managing-performance/8-ground-rules-for-great-meetings/"><strong>http://www.schwarzassociates.com/managing-performance/8-ground-rules-for-great-meetings</strong></a>.</li><li>Bens, Ingrid. Facilitate with Ease! Core Skills for Facilitators, Team Leaders and Members, Managers, Consultants, and Trainers. Fourth edition. J. Wiley and Sons, October 2017.</li><li>Gray, Dave, Sunni Brown, and James Macanufo. Gamestorming: A Playbook for Innovators, Rulebreakers, and Changemakers. O’Reilly Media, 2010.</li><li>Hohmann, Luke. Innovation Games: Creating Breakthrough Products Through Collaborative Play. Addison-Wesley, 2006.</li><li>International Association of Facilitators Methods Library. Available at: <a href="https://www.iaf-world.org/site/pages/methods-library"><strong>https://www.iaf-world.org/site/pages/methods-library.</strong></a></li><li>Liberating Structures. Available at: <a href="http://www.liberatingstructures.com/ls/"><strong>http://www.liberatingstructures.com/ls</strong></a>.</li><li>Tabaka, Jean. Collaboration Explained: Facilitation Skills for Software Project Leaders. Addison-Wesley, 2006.</li><li>Jensen, Mary Ann C. and Bruce W. Tuckman. “Stages of Small-Group Development Revisited. ” Group &amp; Organizational Studies, December 1977 (2:4, 419–429).</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75b41ef549df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons Learned in Becoming a Product-Centric Organization]]></title>
            <link>https://medium.com/@ellengott/lessons-learned-in-becoming-a-product-centric-organization-f327757b737b?source=rss-34455d614558------2</link>
            <guid isPermaLink="false">https://medium.com/p/f327757b737b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[change]]></category>
            <dc:creator><![CDATA[Ellen Gottesdiener]]></dc:creator>
            <pubDate>Tue, 01 Sep 2020 23:59:31 GMT</pubDate>
            <atom:updated>2020-09-01T23:59:31.892Z</atom:updated>
            <content:encoded><![CDATA[<p>“A large, global financial service firm (we’ll call it BigFin) was three years into its journey to adopt agile ways of working. To accelerate customer experience improvements that had already been achieved, the technology infrastructure division decided to align its structure and delivery to become product-centric. The focus was primarily on products used internally by its employees.</p><p>Toby Sinclair, an internal coach in the strategy and transformation team, brought in Ellen Gottesdiener to fill gaps in the team’s product management knowledge and experience. With Ellen’s product coaching expertise, both Toby and Ellen touched almost all parts of the organization. It changed how the company viewed what was valuable to its customers (employees) and how to organize to deliver this value.”</p><p>Thus begins the in-depth report <a href="https://www.tobysinclair.com/"><strong>Toby Sinclair</strong></a> and I recently published as part of the Agile Alliance’s Experience Report initiative.</p><p>Experience reports are resources for people who seek perspectives and lessons learned for others. The process of creating this report has deepened my practice as an agile product coach.</p><p>To identify what happened during the transition to become truly product-centric, Toby and I:</p><ul><li>Created an events timeline with an emotional seismograph</li><li>Mined the timeline for themes</li><li>Created a set of proto personas for the roles in the organization</li><li>Produced a force field analysis</li><li>Drew several visuals to articulate concepts (see one of them, below)</li><li>Developed and multiple versions of causal loop diagrams</li><li>Conducted numerous Zoom conversations to discuss our learning and writing</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hhvNkjmDVCq4LSCi.png" /><figcaption>© 2020, Gottesdiener and Sinclair: “Narrow, inside-out versus broad, outside-in product definition”</figcaption></figure><p>One that stands out for me as a powerful tool for deep learning is the causal loop diagram. The final version we included in the report, shown below, explores the complex interaction of factors that influenced the transformation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_udRyC2m9wciAeiS.jpg" /><figcaption>© 2020, Gottesdiener and Sinclair: “The dynamics of transitioning to being product-led in BigFin’s infrastructure organization”</figcaption></figure><p>I hope you will find the report informative in your work. I am grateful to <a href="https://www.linkedin.com/in/tobysinclair/"><strong>Toby</strong></a> for the opportunity to work with him both on this engagement and as a learning partner to create this report.</p><p>Read the full report on the Agile Alliance site, <a href="https://www.agilealliance.org/resources/experience-reports/lessons-learned-in-becoming-a-product-centric-organization/"><strong>here</strong></a>.</p><p><em>Note: this blog was originally posted </em><a href="https://www.ebgconsulting.com/blog/lessons-learned-in-becoming-a-product-centric-organization/"><em>here</em></a><em>, on </em><a href="https://www.ebgconsulting.com/blog/"><em>EBG’s Blog</em></a><em> on 4 August 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f327757b737b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Answer This Question: “What is Your Product?”]]></title>
            <link>https://medium.com/@ellengott/answer-this-question-what-is-your-product-e23632d2bc8f?source=rss-34455d614558------2</link>
            <guid isPermaLink="false">https://medium.com/p/e23632d2bc8f</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Ellen Gottesdiener]]></dc:creator>
            <pubDate>Mon, 31 Aug 2020 16:00:02 GMT</pubDate>
            <atom:updated>2020-08-31T16:00:02.259Z</atom:updated>
            <content:encoded><![CDATA[<p>This essay is part of the book <strong><em>97 Things Every Scrum Practitioner Should Know</em></strong>, by Gunther Verheyen (editor)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/60/0*NVp69nX6QGkXR-zq" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*hIdFf46GKvyslrrK.jpg" /><figcaption>97 Things Every Scrum Practitioner Should Know (book cover)</figcaption></figure><p>Alice, wandering in Wonderland, said it best. “If you don’t know where you are going, any road will get you there.” This certainly applies to software development teams. Even some of the best Scrum teams can’t answer the simple question, “What is your product?”</p><p>Scrum is about continual discovery and delivery of products. For a product to be successful, it must be desirable to customers, viable for the business, and feasible for technologists to build and support. Notice the subject of that sentence: product. Not knowing what your <em>product</em> is manifests itself in numerous ways.</p><p>As intuitive as Scrum might be, the Product Owner needs to provide guidance and product oversight. The role of a Product Owner isn’t easy. Failing to define the product leads to all sorts of issues, ultimately impacting team satisfaction and product outcomes:</p><p>A plethora of Product Backlogs exist, often with the same customers and the same domain. They overlap and have items that conflict with one another. Moreover, functionality can be duplicated among multiple ‘products’. Coordinator roles such as release managers, project, or program managers are introduced. The customer experience for completing an end-to-end value stream using the product experience is clunky, laborious, and abrasive. Product Owners struggle to prioritize and provide focus. Local optimization exists, resulting in decisions, actions, and structures that impede achieving overall organizational goals. These are but a few of the maladies for not having product clarity.</p><p>Scrum Masters can facilitate the important work of helping Product Owners, the Development Team, and business stakeholders define their product. Apply these three product definition principles:</p><p><strong>Principle 1: Adopt outside-in thinking</strong>. Define your product from the perspective of customers, both users, and choosers. <em>Users</em> directly interact with the product to obtain some benefit or to solve a problem. <em>Choosers</em> are those who make buying choices. It isn’t unusual for Development Teams to create products based on their own, or their Product Owner’s, inside-out bias. Outside-in thinking, on the other hand, is both humbling and enlightening. It allows the entire Scrum Team to approach product work with empathy and curiosity.</p><p><strong>Principle 2: Take the long view.</strong> Projects come and go. Successful products live a long and healthy life. Products evolve and morph through all stages of their lifecycle from introduction, to growth, maturing, and then decline. Products benefit from continuous discovery and delivery. New technology adoption and feature development are critical to improving your product’s value proposition. This principle reduces the need to create separate products. Innovations improve your product’s business viability, customer experience, and improve product quality.</p><p><strong>Principle 3: Define the product as broadly as possible.</strong> A broadly defined product gives a Scrum Team more product options, simplifies communication, clarifies roles, and forces prioritization. Refraining from narrowly scoped products, enables organizations to optimize people and resources. Broadly defined products have many benefits:</p><ul><li>Organizational systems optimization ensures that high-level goals are met</li><li>Backlog management and prioritization become simpler to manage</li><li>Decision-making is streamlined</li><li>Strategic planning and roadmapping become more straightforward to define</li><li>Customer and organizational communication become clearer</li><li>The product influences your organizational structure</li></ul><p>Product development with Scrum requires clear product direction. Establishing a shared, consistent, and coherent answer to the fundamental question, “What is your product?” offers a huge benefit. Knowing <em>what your product is</em> provides the necessary foundation to deliver successful products with Scrum.</p><p>Note: <em>This essay was originally posted on </em><a href="https://www.ebgconsulting.com/blog/"><em>EBG’s Blog</em></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e23632d2bc8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Make Product Decisions With Transparency and Trust — EBG Consulting]]></title>
            <link>https://medium.com/@ellengott/how-to-make-product-decisions-with-transparency-and-trust-ebg-consulting-78aa2f88d060?source=rss-34455d614558------2</link>
            <guid isPermaLink="false">https://medium.com/p/78aa2f88d060</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Ellen Gottesdiener]]></dc:creator>
            <pubDate>Wed, 13 Nov 2019 23:36:30 GMT</pubDate>
            <atom:updated>2019-11-16T18:01:25.167Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Make Product Decisions With Transparency and Trust — EBG Consulting</h3><p><em>Originally published on </em><a href="http://www.mindtheproduct.com/"><em>www.mindtheproduct.com</em></a><em>, 24 October 2019 and </em><a href="https://www.ebgconsulting.com/blog/how-to-make-product-decisions-with-transparency-and-trust/"><em>EBG’s Blog</em></a><em>, 13 November 2019.</em></p><p>Product managers can make better decisions if they’ve built transparency and trust with their team. How these decisions are made is also important, and it requires a clear and collaborative process. Here’s a straightforward framework for collaborative decision making that is founded in transparency and trust.</p><h3>Product Decisions</h3><p>Product decisions are either tactical or strategic. Tactical decisions usually result in short-term actions — like deciding which backlog items to focus on the next delivery cycle and which experiments to run in the next sprint. Strategic decisions provide direction and focus for your product, guide product development action, and ensure alignment within your product ecosystem. Strategic decisions include delineating the product vision, value proposition, product differentiators, and product roadmap.</p><p>Both require a product manager to be the decision leader.</p><h3>Product Decision-Making Traps and Pitfalls</h3><p>As decision leader you can face challenges that prevent you from making the optimal decision. I’ve frequently seen the following decision-making traps and pitfalls:</p><ul><li>Having insufficient or missing information.</li><li>Being blinded by your biases. This includes confirmation bias (ignoring evidence that doesn’t support your preference) and overconfidence bias (thinking you know more than you do know).</li><li>Having your decision overridden by others — the HiPPO (highest paid person’s opinion) effect.</li><li>Stakeholders who challenge or even sabotage the decision.</li></ul><h3>Collaborative Decision Making</h3><p>Decision-making difficulties like those above need more than just a decision leader. When product stakeholders aren’t consulted — or their input is obtained without asking about the reasoning behind their thinking — then you risk making unsustainable and poor decisions. You may also reduce trust in your team.</p><p>What’s needed is a collaborative decision-making process with the following characteristics:</p><ul><li>Diverse stakeholders in the product ecosystem who participate in the decision-making process. These stakeholders provide specific product expertise and a broad perspective that benefits the team.</li><li>The decision leader obtains the relevant information used to make sound product decisions.</li></ul><p>This results in a decision-making process that enhances the team’s ability to work effectively together. There are three benefits when people participate in decisions in which they have a stake:</p><ul><li>Commitment to the product is higher.</li><li>The quality of decisions and their outcomes are more successful.</li><li>A culture of trust develops.</li></ul><p>Recently I ran a product planning workshop where we needed to decide which experiments to focus on to affect our conversion metrics. The customer service team leader shed light on the support required for user trial sign-up. Without their involvement in the workshop, the sign-up support needs wouldn’t have come up and we would have missed information important to our decision.</p><p>I use two tools to improve team collaboration and reach closure on product decisions: decision rules and the gradient of agreement. Together they comprise a simple framework I call “Decide How to Decide” that relies upon transparency and trust.</p><h3>Decision Rules</h3><p>A decision rule is a mechanism to reach closure. It tells participants in the decision-making process when a decision has been made, something many product teams are not explicit about. When a decision rule is not explicitly defined, there is often too much discussion and debate. People are left unsure when and if a decision has been reached and what the decision is. They delay taking action and often act without commitment. The team loses energy and valuable time.</p><p>The figure below shows common decision rules. Each decision rule has a different effect on group behavior and is useful in different circumstances. An effective decision rule balances the need to reach closure in a timely manner with the decision’s impact on the business and team. The goal is to be transparent about which decision rule you use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y934mHPLBY6eNYfV.png" /></figure><p>There are two participatory decision rules that work best for medium- to high-stakes product decisions, such as decision to identify which market segment to focus on for the next product release, or which actions are needed to validate your product strategy. These two participatory decision rules — <strong>consensus</strong> and <strong>decision leader</strong> <strong>decides after discussion</strong> — are best used in a collaborative workshop and give participants the context and relevant information to efficiently discuss options.</p><p>Consensus means reaching mutual agreement among all stakeholders, whereby all legitimate concerns have been addressed to reach closure. Consensus can work but is often not practical. I recommend using the <strong>decision leader decides after discussion</strong> rule for most product decisions.</p><h3>Gradient of Agreement</h3><p>The gradient of agreement is a mechanism for testing people’s level of agreement with a proposed decision. It’s shown in the figure below. After discussing relevant information about the decision and generating options about the decisions at hand, the decision leader polls all participants using a four-point scale to find out to what degree each person agrees with the proposed decision. The decision leader then uses this information to inform their decision. If the decision rule used consensus, everyone who participates needs to be in the “zone of agreement” (1s and 2s).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-Pw2hAp5m4d78Tgw.png" /></figure><p>I recently ran a planning workshop where the product team needed to decide which feature to include in the next development sprint. The decision rule selected was <strong>decision leader decides after discussion.</strong> Amy, the product manager, was the designated decision leader. We reviewed and analyzed each option. Once there were no further questions, I asked each person to write their level of agreement (1 to 4) with the proposal. The result was a mix of 1s and 2s. I then asked the 2s to share their reservations. Next, Amy explained her rationale for selecting that feature and thanked everyone for their input. We had a decision in just 15 minutes and moved on.</p><h3>When the Product Manager is not the Decision Leader</h3><p>There are times when the product manager is not the decision leader because of organizational or ownership issues.</p><p>I recently worked with an organization where the ultimate decision leader was the product steering committee, chaired by the VP of product and customer experience. The committee had several members so it was important to be clear what decision rule they would use to reach closure. They selected <strong>decision leader decides after discussion </strong>as the decision rule and the VP of product and customer experience was designated as the decision leader. Everyone involved in creating the strategy briefed the steering committee at the end of our launch planning workshop. The steering committee agreed to make a timely final decision within four business days of being briefed on the proposed launch plan.</p><p>There may be times when a product manager should delegate the decision to someone else who has greater expertise in the topic of the decision. For example, the lead engineer could be the decision leader for topics on a product’s technical architecture.</p><p>Empowering the decision leader to choose the decision rule builds trust and accountability among the product team. A good decision-making process naturally builds a positive decision culture.</p><h3>Steps for Making Collaborative Product Decisions</h3><p>A product team can make collaborative product decisions with the “Decide How to Decide” framework and the two participatory decision rules as follows:</p><h3>1. Frame the Decision</h3><p>Identify the decision to be made and who the decision leader should be. For product decisions, it will most often be you, as product manager. You should provide your participants with all the necessary information about the decision: the purpose, timing, and available analysis, and ask them to prepare for the decision by completing a scoring matrix, effort/impact grid, or plus-minus-interesting-points list for the known options.</p><h3>2. Explore Options</h3><p>Participants should work together to explore alternatives, share views, and add analysis. They should review qualitative and quantitative data, such as interview findings or product metrics. The decision leader should assign small groups to work on the analysis or the use of prioritization tools (such as Kano analysis or a cost of delay calculation). One more thing: always timebox this step.</p><h3>3. Make the Decision</h3><p>When time is up for exploration or the group seems near closure, close the discussion, clarify the proposals for the decision, and poll the group using the gradient of agreement. It is always a good idea to ask anyone who polls at 2 (or higher) to briefly share the reasoning behind their degree of agreement.</p><p>Ultimately, you make the final decision. It is your responsibility to inform other stakeholders who were not decision participants of the reasoning behind your decision.</p><h3>4. Analyze the Decision Retrospectively</h3><p>Product retrospectives are one of the best ways to improve your decisions and to evolve your product culture. Always analyze product decisions retrospectively. This is an opportunity for reflection and learning. Hopefully, you’re conducting regular <a href="https://www.ebgconsulting.com/blog/retrospectives-makes-better-product-outcomes/">retrospectives</a> and you incorporate the product decisions made as part of those retrospectives.</p><h3>Building Trust</h3><p>This collaborative process speeds up decision making, allows you to make better-informed decisions, and builds a healthy product culture. It promotes <a href="https://hbr.org/2017/08/high-performing-teams-need-psychological-safety-heres-how-to-create-it">psychological safety</a> and trust.</p><p>The “Decide How to Decide” process enhances trust among the product team. <a href="https://www.amazon.com/Trust-Betrayal-Workplace-Relationships-Organization/dp/1626562571">Reina and Reina</a> identified that organizations need three types of trust: contractual, communication, and competence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/0*mFyk1KuWZWt6hP9F.png" /></figure><p><strong><em>Contractual</em></strong> trust (trust of character) is based on an unstated contract:</p><p>“You will look out for my best interests, and I will look out for yours. If things change, we will renegotiate. Ultimately, we are jointly responsible for our success.”</p><p>Being transparent about your decision-making process builds contractual trust.</p><p><strong><em>Communication</em></strong> trust calls for honest and frequent communication. Team members tell the truth, admit their mistakes, maintain confidentiality, and seek to provide feedback. Actions must be consistent with participants’ words and vice versa. A decision-making process that allows people to openly share their perspective builds communication trust.</p><p><strong><em>Competency</em></strong><em> </em>test (or trust of capability) occurs when product team members respect each other’s ability to get their jobs done. People promote mutual learning and development of everyone’s skills and knowledge. Engaging in participatory decision making demonstrates respect for the expertise of others. The building of competency increases mutual learning.</p><h3>Healthy Decision Making Means Better Product Teams</h3><p>Decision making requires the right decision-making process — deciding how to decide. When you are clear about product decision-making rules and engage the right people in the decision-making process, you get better decisions and better teams. When done well, your product decision process results in a culture of transparency and trust.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78aa2f88d060" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Is Your Product?]]></title>
            <link>https://medium.productcoalition.com/what-is-your-product-14420b35a1b3?source=rss-34455d614558------2</link>
            <guid isPermaLink="false">https://medium.com/p/14420b35a1b3</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ellen Gottesdiener]]></dc:creator>
            <pubDate>Sat, 20 Jul 2019 21:52:02 GMT</pubDate>
            <atom:updated>2020-09-14T15:52:08.254Z</atom:updated>
            <content:encoded><![CDATA[<h3>What Is Your Product?</h3><p>“So, what is your product?” That was the key question I posed in my Agile Cincinnati keynote recently.</p><p>In my product coaching work, I have come to realize that many organizations don’t have a clear and consistent answer to this fundamental question. This has serious consequences. A poorly defined product impacts your ability to respond to changing customer and market needs. It results in less than satisfying product outcomes. It causes organizational and communication woes. It thwarts organizations efforts to scale agile product development.</p><h3>Everyone in your product development ecosystem should have a shared, consistent, and coherent answer to the fundamental question, “What is your product?”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*uzqmvUPh5hxbl2wy.png" /></figure><p><em>You need a shared, consistent, and coherent answer to “What is Your Product?”<br></em>Image by EBG Consulting</p><h3>The Five Principles</h3><p>There are five principles that can help you to define your product:</p><p><strong>1. Adopt outside-in thinking.</strong></p><p>Many organizations erroneously define their products by taking a technology perspective. They consider the product’s underlying technologies, components, and tools and call a logical grouping of them a “product.” This approach defines the product from an engineering perspective and not from a customer perspective.</p><p>Alan Cooper’s prescient book, <a href="https://www.amazon.com/Inmates-Are-Running-Asylum-Products/dp/0672326140"><strong><em>The Inmates are Running the Asylum</em></strong></a>, was a wake-up call back in 2004. Its title comes from the bizarre 1989 cult film by the same name involving a plot whereby an experiment mind fluid exchanges in an insane asylum that goes array. Consequently, the doctor becomes the patient and the patient becoming the doctor. Cooper (the father of Visual Basic and originator of personas) makes the point that technology products are horribly designed and make users feel stupid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*0lvNEIg9JVPJhjpA.png" /></figure><p><em>Define your product outside-in (not inside-out).</em><br>Image by Ellen Gottesdiener, EBG Consulting</p><p>This represents inside-out product thinking and it simply doesn’t work. Instead, define your product from the perspective of customers, both users and choosers. Users are those people who directly interact with the product to obtain some goal or solve a problem. Choosers are those who making buying choices. Outside-in thinking is both humbling and enlightening. It allows you to approach your product work with empathy and curiosity.</p><p><strong>2. Take the long view.</strong></p><p>Some seven years ago, I gave a presentation about <a href="https://www.ebgconsulting.com/blog/7-ways-of-creating-and-sustaining-an-agile-product-roadmap/"><strong>product roadmapping </strong></a>with the title “Products, Not Projects.” Even before I started I noticed that some attendees, many of whom were professional project managers, were not happy with the title. Projects come and go while successful products live a long and healthy life. A healthy product evolves and morphs through its lifetime, benefiting from continuous discovery and delivery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/0*G99wUh0hwBJxLUuR.png" /></figure><p><em>A healthy product has a long lifecycle, from birth (introduction and launch) through decline.</em><br>Image by Ellen Gottesdiener, EBG Consulting</p><p>When organizations fall into the trap of viewing technology innovations as products in-and-of-themselves, they usually end up with multiple products that are serving the same customer or market. Some with the same core capabilities. This complicates organizational processes and confuses customers.</p><p>The better approach is to take the long view of your product. New technology variations and developments are part of ongoing improvements to your product’s value proposition. They can improve your product’s business viability, customer experience, and improve product quality.</p><p>A product organization taking the long view operates as a single virtual product community despite having distinct product management and product development organizations. Developers and engineers actively participate in discovery to validate technology innovations, parity imperatives, and new product capabilities. The product community invests in fast, efficient experiments before making costly changes to the product.</p><p>A clear product definition should help you shift-left<strong><em>er</em></strong>. Shift-left is all about <a href="https://www.mabl.com/blog/shift-left-shift-right-shifting-and-why"><strong>using tests to guide product development </strong></a>to reduce risk and build shared understanding early in development. Great product teams migrate even more to the left through validation to determine if they are building the right thing. Product options should be continually validated to ensure a long and healthy product lifecycle.</p><p><strong>3. Define your product as broadly as practical.</strong></p><p>Many organizations I work with define their products narrowly. This results in numerous kinds of organizational maladies including:</p><ul><li>Products with multiple overlapping and conflicting backlogs</li><li>Functionality duplicated across multiple products</li><li>Bottlenecks caused waiting for technology specialist teams</li><li>Excessive coordination and product roles</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*r_zu93uN6Sn8Kqj_.png" /></figure><p><em>Narrowly defined products lead to negative customer experience.<br></em>Image by Ellen Gottesdiener, EBG Consulting</p><p>Most importantly, narrowly defined products can result in a bifurcated user experience. Completing an end-to-end value stream using your product is clunky, laborious, and abrasive. Customers needing to communicate with the organization to solve problems or answer questions are faced with a confusing array of disparate support teams in different departments. Problems and questions are slow to resolve as the customer gets passed from department to department.</p><p>A narrowly defined product has another unfortunate side effect. It promotes a natural bias to optimize outcomes that serve only that particular product’s narrow goals. This phenomenon is known as<em> local optimization </em>and results in decisions, actions, and organization structures that impede the overall, and more global organizational goals.</p><p>On the other hand, when you define your product as broadly as possible, you “see the whole.” This affords you a view of a wider terrain of product options, simplifies communication, clarifies roles, and forces prioritization. Broadly defined products allow your organization to optimize people and resources for the entire organizational system. This is called <a href="https://hbr.org/2016/01/optimizing-each-part-of-a-firm-doesnt-optimize-the-whole-firm"><strong>systems optimization</strong></a>. Systems optimization through broader product definition facilitates your organization’s ability to meet your higher-level goals. It also eases and simplifies:</p><ul><li>Strategic planning and roadmapping</li><li>Backlog management</li><li>Organizational and customer communications</li><li>Prioritization and decision making</li><li>Role definition</li></ul><p>Another benefit with systems optimization is simplified organizational design. This is discussed in the next section.</p><p><strong>4. Structure must follow product.</strong></p><p>Some organizations fall into the trap of defining products according to their organization chart. Parts of products supported by a particular functional group or reporting line is declared to be a product. Chaos and confusion ensue each time there is a reorganization. Over time, the product architecture emulates a hairball of intertwined interfaces, technology knots, Wild West of cowboy code, and <a href="https://en.wikipedia.org/wiki/Cruft"><strong>cruft</strong></a>. The product and product team suffers from the unfortunate effect of <a href="https://en.wikipedia.org/wiki/Conway%27s_law"><strong>Conway’s Law</strong></a> where a product’s design is “<a href="http://www.melconway.com/Home/Conways_Law.html"><strong>a copy of the organization’s communication structure</strong></a>.”</p><p>When a product is defined outside-in, your organization benefits with a more product-centric design. Feature teams and end-to-end value stream teams are formed based on customer outcomes. You have one backlog per product, which helps ease prioritization and avoids the trap of local optimization. You can learn more about local optimization pitfalls from Michael James’ excellent video about “<a href="https://www.youtube.com/watch?v=cr2rjaGmUzo"><strong>team output owners</strong></a>.”</p><p>Finally, Craig Larman’s’ brilliant <a href="https://www.craiglarman.com/wiki/index.php?title=Larman%27s_Laws_of_Organizational_Behavior"><strong>Laws of Organizational Behavior</strong></a> states that “culture follows structure”. When you have defined products in a customer-centric manner, with a long view in mind, and as broadly as possible, structure follows product.</p><p><strong>5. Defining your product requires collaboration.</strong></p><p>To obtain a shared definition of your product, employ team collaboration. In my keynote, I shared some of the experiments from product thinking facilitated workshops in which we defined a product through a series of progressive, interactive activities. These activities include clarifying the <a href="https://www.ebgconsulting.com/blog/right-things-not-everything-product-management-ownership/"><strong>work of product management and ownership</strong></a>, using the <a href="https://www.ebgconsulting.com/blog/using-product-canvas-define-product-getting-started/"><strong>Product Canvas</strong></a>, <a href="https://www.ebgconsulting.com/blog/decide-how-to-decide-empowering-product-ownership/"><strong>decision-making rules</strong></a>, customer research, and value proposition canvas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*HyrLEe-Vrnau3_Za.png" /></figure><p><em>People Collaborating to Define Product<br></em>Photo from Product Definition Workshop by Ellen Gottesdiener, EBG Consulting</p><h3>The Importance of Knowing Your Product</h3><p>Agile product development is about continual discovery and delivery of products that are desirable to customers, viable for the business, feasible for technology people to build, and supportable. How you define your product guides drives your discovery and delivery.</p><p>The first thing to do when you are starting or reinvigorating your product organization is to answer the question, “What is your product”?</p><p>You can view my “What Is Your Product” keynote slides <a href="https://www.slideshare.net/ellengott/what-is-your-product">here</a>.</p><p>Many thanks to <a href="https://www.linkedin.com/in/andyrepton/"><strong>Andy Repton</strong></a>, <a href="https://www.linkedin.com/in/michaeljamesseattle/"><strong>Michael James (MJ),</strong></a> <a href="https://www.linkedin.com/in/cesarioramos/"><strong>Cesario Ramos</strong></a>, and <a href="https://www.linkedin.com/in/tim-ottinger-tla-wth-omgz-jk-istm-yolo-nvm-a8b0183/"><strong>Tim Ottinger</strong></a> for their helpful feedback on this blog.</p><p>A Russian version of this blog is now available at <a href="http://blog.agilix.ru/2019/07/12/%d1%87%d1%82%d0%be-%d1%82%d0%b0%d0%ba%d0%be%d0%b5-%d0%bf%d1%80%d0%be%d0%b4%d1%83%d0%ba%d1%82/#more-637"><strong>Agilix Consulting</strong></a>. Thank you, Illia Pavlichenko!</p><p><em>Note: this blog was originally posted </em><a href="https://www.ebgconsulting.com/blog/what-is-your-product/"><em>here</em></a><em>, on </em><a href="https://www.ebgconsulting.com/blog/"><em>EBG’s Blog</em></a><em> on 4 July 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14420b35a1b3" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/what-is-your-product-14420b35a1b3">What Is Your Product?</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Retrospectives Make Better Product Outcomes]]></title>
            <link>https://medium.com/@ellengott/retrospectives-make-better-product-outcomes-7472b71b2ae7?source=rss-34455d614558------2</link>
            <guid isPermaLink="false">https://medium.com/p/7472b71b2ae7</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[retrospectives]]></category>
            <dc:creator><![CDATA[Ellen Gottesdiener]]></dc:creator>
            <pubDate>Sat, 09 Mar 2019 17:42:24 GMT</pubDate>
            <atom:updated>2019-03-09T17:42:24.781Z</atom:updated>
            <content:encoded><![CDATA[<p>Frustrated with the outcomes of your products? Are you, as a product manager, struggling with your development team? In my work as a product coach, achieving less than stellar product outcomes is all too common.</p><p>Surprisingly, the solution to better outcomes may be right under your nose. The answer is in <em>retrospectives</em>. To create and sustain a culture for creating better product outcomes, product leaders encourage and participate in product retrospectives. Retrospectives tap into the wisdom of the product community to continually learn and improve the product as well as the product development process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/0*KhLed0lKwIeaixh9.png" /><figcaption>Image by Ellen Gottesdiener</figcaption></figure><p>Retrospectives are a simple, yet powerful tool that relies on transparency, curiosity, and learning. Mastering retrospectives need to be in every product manager’s toolkit.</p><h3>What Is a Retrospective?</h3><p>A retrospective is a reality-based learning experience resulting in action and change. A retrospective can be timed to happen regularly, such as at the end of iteration or sprint, release, or at some other regularly occurring event such as a quarterly roadmap review. It can also take place after an importance occurrence such as a product launch, client sales meeting, or hypothesis test. Unlike a traditional meeting where information and status is shared, a retrospective generates new information and an agreement for action.</p><p>A retrospective is a ritual involving the product community. This community can include the development team, product team, customers, and stakeholders. The purpose is to review what happened for some timeframe, outcome, deliverable, or event. A retrospective review should do the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/0*Xxyh2eiIdev3k4fK.png" /><figcaption>Image by Ellen Gottesdiener</figcaption></figure><ul><li>Harvest the collective wisdom of the community</li><li>Tell the truth without blame or judgment</li><li>Identify what to appreciate and what needs to be improved</li><li>Generate insights that could potentially benefit the product</li><li>Commit to actions to improve, change, or try</li></ul><p>Many product people think that retrospectives are focused solely on the team process and the quality of teamwork. That can be an opportunity lost. The best and most lasting product improvements happen when product people do the following:</p><ul><li>Actively engage in retrospectives</li><li>Use retrospectives for more than the development team’s process</li><li>Use quantitative product data as part of retrospectives</li></ul><p>Let’s take each in turn.</p><h3>Active Engagement in Retrospectives</h3><p>Product development teams are widely familiar with retrospectives, popularized mainly because it is a key Scrum event. Development teams tend to use retrospectives regularly and product managers are involved — <em>sometimes.</em></p><p>Product managers have a tendency to avoid retrospectives when the meetings are not well run or when there are issues such as problems with product quality. As a product leader, you have every right to point these issues out and seek ways to make them better. If there are deeper issues at play such as strained relationships, consider using retrospectives as a forum for mutual learning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/196/0*3ZvpkNhIpmKOeh33.png" /><figcaption>Image by Ellen Gottesdiener</figcaption></figure><p>I’ve seen development teams struggle when product leaders are reluctant to surface their concerns. Conversely, I have encountered product leaders who are disappointed or frustrated with their development team and avoid attending team retrospectives all together.</p><p>Product leadership is about setting a safe environment for curiosity and transparency. Everyone should have the courage to <em>discuss the undiscussables</em>. By using the structure of a retrospective, which includes setting the stage with safety (See sidebar “Structure for a Retrospective”), a skilled and neutral facilitator can transition a team to become a high-performing product team. Now that is how retrospectives shine!</p><h3>Use Retrospectives for More Than the Development Team’s Process</h3><p>Retrospectives are useful for more than just iterations (sprints) or product releases. Retrospectives can be used to reflect and learn from an important event including as a product launch, customer or product research, hypothesis test, roadmap outcomes, customer sales meeting, or customer conference.</p><p>Your <em>mileage will</em> vary as to which events are most important for your product. Consider those that you do on an ongoing basis, and for which the stakes are high. Inject post-event retrospectives and engage the right people to get better the next time.</p><h3>Using Product Data to Make better Product Decisions</h3><p>Of the five steps in a typical retrospective, two of them (gather data and generate insights) require product managers to focus on product data.</p><h3>Structure for a Retrospective</h3><p>A typical retrospective structure includes activities for the following steps:</p><ol><li><strong><em>Set the stage [readying]:</em></strong> Collect data prior to the retro, kick-off the session, define success, and create safety.</li><li><strong><em>Gather data [past]:</em></strong> Recreate the story; share a common pool of both qualitative and quantitative data.</li><li><strong><em>Generate insights [present]:</em></strong> Interpret the data, understand the big picture, answer five questions, and reflect on facts and feelings.</li><li><strong><em>Decide what to do [future]:</em></strong> Select what to change, improve, or try, and identify concrete implementation actions.</li><li><strong><em>Close [Retrospect the Retrospective]:</em></strong> Reflect on the retrospective process and identify how to improve future retrospectives.</li></ol><p>Data includes both qualitative data (reactions, happiness, and so on) as well as quantitative data (code quality, technical debt, and defects). Meaningful quantitative data also includes information such as product usage and outcomes. This can include win/loss results, revenue and corresponding costs over a certain timeframe, marketing campaign metrics, hypothesis test findings, conversion rates, and HEART metrics (customer happiness outcomes, engagement, adoption, retention, task success).</p><h3>Retrospectives Help Us Learn</h3><p>For learning to stick with us, it must have immediacy, relevance, and self-direction. Retrospectives help us learn.</p><p>Immediacy means that you have opportunities to apply what you learn soon after learning occurs. This is based on the thought process, “I can remember it.” That’s why it’s important to time your retrospectives within days of the endpoint you are retrospecting.</p><p>Relevance means that the learning is important to us and that it applies to our current situation (“I care,” “I need it,” and “I can practice or test this now”). Plan your retrospectives around you and your team’s goals. Be sure to cover topics the team cares about.</p><p>Self-direction involves taking ownership and control of our own learning and making necessary changes (“I own it,” “I choose it,” and “I will do it”). Always include steps in the retrospective for everyone to decide and plan what needs to change and how to change it.</p><h3>A Recent Interactive Retrospective Learning Experience</h3><p>There is more to retrospectives than you might think. To have better product outcomes, product leaders must set the stage for psychological safety, learn who is best to facilitate retrospectives, determine when to use retrospectives, and establish appropriate timing and duration of retrospectives.</p><p>Our <a href="http://www.agileproductopen.org/"><strong>Agile Product Open</strong></a> community joined up with <a href="https://www.bostonproducts.org/"><strong>Boston Product Management</strong></a> on <a href="http://worldretroday.com/"><strong>World Retrospective Day</strong></a><strong> </strong>in Cambridge, Massachusetts, USA on Wednesday, February 27, 2019. That evening, we explored how product people can effectively use retrospectives. The event included mining data and wisdom from the participants and a simulation of a retrospective. We explored how to inject retrospectives into our product work.</p><p>To view photos of the event, visit our <a href="https://www.meetup.com/Agile-Product-Open/photos/29679370/"><strong>Meetup photos page</strong></a>. You are welcome to the <a href="https://www.ebgconsulting.com/AgileRetrospectives(APO_Boston)(Feb2019).pdf"><strong>retrospective summary resource</strong></a> we provided to attendees and Agile Product Open Boston community members.</p><p>How are you doing with using retrospectives for better product outcomes?</p><p><strong>Note</strong>: This article was originally posted on EBG’s blog: <a href="https://www.ebgconsulting.com/blog/">https://www.ebgconsulting.com/blog/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7472b71b2ae7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using the Product Canvas to Define Your Product’s Core Requirements]]></title>
            <link>https://medium.productcoalition.com/using-the-product-canvas-to-define-your-products-core-requirements-47e85c074ccc?source=rss-34455d614558------2</link>
            <guid isPermaLink="false">https://medium.com/p/47e85c074ccc</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Ellen Gottesdiener]]></dc:creator>
            <pubDate>Sun, 17 Feb 2019 15:57:01 GMT</pubDate>
            <atom:updated>2020-09-14T15:51:43.864Z</atom:updated>
            <content:encoded><![CDATA[<p>The Product Canvas can help address a number of challenges as you transition to a product-centric organization. You may want to take a step back to rethink your product strategy. Perhaps you realize you’re not organized for optimal product development and need to redesign your organization so its structure follows product. Or, maybe you need to improve your product management practices.</p><p>For all these scenarios, defining your product is your starting point.</p><p>The Product Canvas has two parts. In my last blog, <strong>“</strong><a href="https://medium.com/@ellengott/using-the-product-canvas-to-define-your-product-getting-started-efd2889958f6"><strong>Using the Product Canvas to Define Your Product: Getting Started</strong></a><strong>”,</strong> you learned about the strategic and positioning benefits of the Product Canvas Part 1. Product Canvas Part 2, the subject of this blog, helps you define the essence of your product by defining its compositional requirements.</p><p>Using the same example company, Squeeky Kleen, a window cleaning business that currently services residential properties. Product Canvas Part 1 for Squeeky Kleen is as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*apZlrcEcDQlQeJRl.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 1 for Squeeky Kleen</em></figcaption></figure><p>Product Canvas Part 2 for Squeeky Kleen is the topic of this blog looks like the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I-0vi--MOn57YEX7.png" /><figcaption><em>Source: EBG Consulting | The Product Canvas Part 2 for Squeeky Kleen</em></figcaption></figure><h3>Filling Out Product Canvas Part 2</h3><p>The sample Product Canvas Part 2 identifies a product’s 7 Product Dimensions. [1]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W3te9rl782EXAQfL.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 2 | Download the </em><a href="https://www.ebgconsulting.com/ProductCanvas.pdf"><strong><em>Product Canvas</em></strong></a></figcaption></figure><p>As in Product Canvas Part 1, fill the overall product information first (product, your organization, date, and version):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PN2gA14pWFL_-Vx9.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 2 | Header row A. Product, B. Organization, C. Date, D. Version</em></figcaption></figure><h3>7 Product Dimensions</h3><p>The 7 Product Dimensions give you a holistic, comprehensive understanding of your product. No single dimension, by itself, is sufﬁcient. You need to identify all seven to obtain a full understanding of your product, and product possibilities. [1]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/0*IIwJI9GY96phoK7o.png" /><figcaption><em>EBG Consulting, Inc. The 7 Product Dimension</em></figcaption></figure><p>A unique color and image is used to visually identify each dimension. Download them from the visual language section of the <a href="http://www.discovertodeliver.com/visual-language.php"><strong>Discover to Deliver resources </strong></a>site. Use visual models where possible to enhance and enliven conversations in Product Canvas and <a href="https://www.ebgconsulting.com/blog/the-eyes-have-it-how-visuals-can-energize-your-product-discovery/"><strong>product discovery workshops</strong></a>. Models also help reviewers understand the essence of any given product dimension, quickly. I provide examples of useful visual models in the explanations below. Remember to keep the models for the Product Canvas coarse-grained, not detailed.</p><p>The columns of Product Canvas Part 2 has the following information:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hoCZFHL77PYMzvoq.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 2 | Column row A. User, B. Interface, C. Action, D. Data, E. Control, F. Environment, G. Quality Attribute</em></figcaption></figure><p>To complete each block, follow these instructions:</p><p>A. <strong>User Dimension:</strong> Users value, benefit from, and directly interact with the product. Users trigger actions and can receive data from the results of actions. Include people, systems, and devices that interact with the product. In addition to listing users, represent them on your canvas with personas, roles maps, empathy maps, and customer journey maps.<br><em>Canvas </em><strong><em>User Dimension</em></strong><em> tip:</em> Users (people, systems, devices) that interact with the product.</p><p>B. <strong>Interface Dimension:</strong> This represents the connections the product needs to interact with all its users, systems, and devices. Interface mechanisms can be human-computer (e.g., visual interface, touch, audio, or facial scan), system-to-system (via APIs), and messages (how the product interfaces with devices or systems). Visually represent interfaces using a context diagram or relationship map.<br><em>Canvas </em><strong><em>Interface Dimension</em></strong><em> tip:</em> The product connects to and from users, systems, and devices.</p><p>C.<strong> Action Dimension:</strong> This specifies what the product does for its users. Name the actions at a high-level with, for example, features, capabilities, or functional names ending in “ing” or “ment” (e.g., invoicing, fulfillment). Supplement the list with visual models such as an experience map, story map, business process diagram, value stream map, dependency graph, service blueprint, or capability map. You can also use text-based scenarios or jobs-to-done for the Action dimension.<br><strong><em>Canvas Action Dimension</em></strong><em> tip:</em> The product provides capabilities for users.</p><p>D. <strong>Data Dimension:</strong> This represents the persistent data the product stores and uses. This includes data needed by actions and which is sent and received via product interfaces. List them using domain nouns (e.g., data entities such as Customer, Payment, or Property). Better still, visually communicate the Data dimension with a conceptual data model. Important lifecycle changes of important data entities can be visualized with a state diagram.<br><em>Canvas </em><strong><em>Data Dimension</em></strong><em> tip:</em> The data and useful information the product stores and uses.</p><p>E. <strong>Control Dimension:</strong> Identify the policies, regulations, and business rules that the product must enforce. Controls originate from the business itself, from external sources such as regulatory bodies, or both. Include controls that are enforced in the product via software or hardware configuration, manually through business processes, or both.<br><em>Canvas </em><strong><em>Control Dimension</em></strong><em> tip:</em> Specify the product constraints that need to be enforced such as policies regulations, and business rules.</p><p>F.<strong> Environment Dimension:</strong> Clarify the product’s technology platforms (hardware and software) and, if it is a physical product, its physical properties.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*cRvMkkA0xt-giMOq.png" /><figcaption><em>EBG Consulting: Metamodel of The Environment Dimension [1]</em></figcaption></figure><p>Don’t forget to include standards the product must conform to, as well as the product’s environment of use. For example, a software product’s user might be located in an office using a limited set of devices (e.g., desktop, mobile) with a limited set of browsers and operating systems. If the product is a system comprised of both hardware and software, you need to identify physical aspects of its usage environment. A technician may be holding the product in their hand, in the cold and rain, using gloves.</p><p>The Environment dimension identifies constraints on your product’s design and implementation options, thus it is visually represented as a vise (also doubling as a provocative question mark) constraining the product box.</p><p><em>Canvas </em><strong><em>Environment Dimension</em></strong><em> tip:</em> The product conforms to physical properties and technology platforms — software and hardware components and standards.</p><p>G. <strong>Quality Attribute Dimension:</strong> define the characteristics that contribute to the product’s operation (e.g., availability, usability, and security) and development (e.g., efficiency, portability, and testability), as shown in the figure below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*GvlUkkkTO8LyNu8w.png" /><figcaption><em>EBG Consulting: Metamodel of Quality Attribute Dimension [1]</em></figcaption></figure><p>G.<em> Canvas </em><strong><em>Quality Attribute Dimension</em></strong><em> tip:</em> Quality attributes are predefined levels of service for the product’s functionality and Interfaces. These should be measurable properties that qualify the product’s operation and development.</p><h3>Tips and Techniques to Create Product Canvas Part 2</h3><p>Because the Product Canvas is a tool to build shared understanding, the best approach for building the Product Canvas Part 2 is in facilitated workshops with customer, business, and technology representatives. As with Product Canvas Part 1, always prepare before your collaborative Product Canvas session (a.k.a. facilitated workshop). Consider creating draft models for some of the dimensions in mini-workshops with a subset of participants prior to the larger workshop.</p><p>You can work on both canvases together or split the work into separate sessions. If there is a diversity of opinion on what your product is, I recommend starting creating Product Canvas Part 2 to gain agreement on the gist of the product. This is because it is difficult to tackle the higher level blocks in Product Canvas Part 1 without shared agreement on what the product does, for whom, and how. Product Canvas Part 2 helps you do just that.</p><p>Here are some high-level guidelines that have worked for me:</p><p>1.<strong> Keep it High-Level.</strong> Clarify that you are looking broadly at the product, not depicting fine-grained aspects of the product. For example, for the Data dimension you are not listing data attributes such as “resident street address” or “job schedule date”) but rather big chunks of data such as “Customer,” “Property,” and “Job.”</p><p>The initial intent is to have the canvas depict the “as is” product. If you want to include “to be” aspects, I recommend denoting them as such with a note (e.g. “to be” or “planned for Q1 2010”).</p><p>2. <strong>Know your Navigation Strategy.</strong> Select a starting product dimension to lead with, and then navigate across dimensions. For any given product, some dimensions may communicate more powerfully than other dimensions. [1]<br>For example, for a transactional product (such as ordering, billing, or managing inventory), I might start with the User dimension, move next to Action, then Data, and continue onto the other dimensions.</p><p>For an analytic or configuration product, I recognize that data and business rules are crucial. I prefer identifying the key data domains (Data), then shift to Action by asking about the questions, queries, or decisions that need to be made by the product. This navigation strategy, in turn, provokes uncovering business rules (Control dimension) that must be enforced.</p><p>For platform or infrastructure products, I am likely to start with the Environment dimension and then navigate to the User and Action dimensions. However, for some products, I’ve found using a context diagram (useful to define the Interface dimension) helps pull participants back into a broader product perspective to give them a birds-eye view of the product. From there, I navigate to the other dimensions.</p><p>All seven product dimensions weave a multi-colored and multi-dimensional tapestry that makes up your product. One dimension informs another. A feature listed in your Action dimension operates on data (Data dimension) enforces business rules (Control dimension), is used by a user (User dimension) connected via an interface (Interface dimension) on some hardware and software platform (Environment dimension), and requires a level of performance and security (Quality Attribute dimension).</p><p>Regardless of where you start and the sequence of navigating across the product dimensions, you need them all to get the full picture.</p><p>3.<strong> Make it Visual.</strong> Use a variety of ways to express your product’s dimensions, including visual models, and text descriptions. Supplement the text with visual models (e.g., data model for the Data dimension, role map for the User dimension, and experience map for Action dimension). Still, it is a good idea to select the minimum combination to not overwhelm participants with too many models.</p><p>4. <strong>Reflect and Retrospect.</strong> Post the completed Product Canvas for internal review and share it with a broader audience. Then, share it with your customers (remove any sensitive info for commercial products, such as your competition sections in Product Canvas Part 1). Do they quickly and easily understand it? What might be missing, conflicting, or erroneous? Seek ways to improve the quality of the content of your Product Canvas.</p><p>5. <strong>Reassess your Product Strategy Roadmap.</strong> Consider using tools such as the <a href="https://www.blueoceanstrategy.com/tools/four-actions-framework/"><strong>Four Actions Framework</strong></a> and the companion <a href="https://www.blueoceanstrategy.com/tools/strategy-canvas/"><strong>Strategy canvas</strong></a>. [2] Pay particular attention to your Action, User and Environment dimensions to consider factors (or product dimensions) you might rise above standard, reduce (due to excessive competition), eliminate from competition or create. You can also use the <a href="https://www.kanomodel.com/"><strong>Kano model</strong></a>, <a href="https://strategyzer.com/canvas/value-proposition-canvas"><strong>value proposition canvas</strong></a>, or exploring <a href="https://www.marketing91.com/4-types-market-segmentation-segment/"><strong>different market segments</strong></a>.</p><p>6.<strong> Consider Product Backlog Implications.</strong> Product Canvas Part 2 identifies the essence of the product: its composition and what it does and for whom. You can derive any backlog item from it, and visa versa. Indeed, using the 7 Product Dimensions helps <a href="https://www.ebgconsulting.com/blog/streamline-agile-requirements-avoiding-bloated-backlogs/"><strong>avoid a bloated backlog</strong></a> and is a powerful tool for <a href="https://www.ebgconsulting.com/blog/slicing-user-stories-delivering-value/"><strong>slicing (a.k.a. “splitting”) backlog items</strong></a>. Reassess your backlog in light of your strategic reassessment. As a <a href="https://www.ebgconsulting.com/blog/product-manager-product-owner/"><strong>product person</strong></a>, ask yourself questions to optimize your product content as well as your product management practices.</p><ul><li>Is your backlog and difficult to manage?</li><li>Do you share and use transparent prioritization criteria?</li><li>Are you considering the <a href="https://www.ebgconsulting.com/blog/factors-for-making-value-based-product-decisions/"><strong>relevant factors needed to make value-based decisions for your product</strong></a>?</li><li>Are you using <a href="https://www.ebgconsulting.com/blog/decide-how-to-decide-empowering-product-ownership/"><strong>transparent decision-making rules</strong></a>?</li><li>Do you <a href="https://www.ebgconsulting.com/blog/five-ways-a-product-owner-can-build-trust/"><strong>build trust in your product community</strong></a>?</li></ul><p>7. <strong>Make it a Living, Go-To Tool.</strong> Decide how to keep your Product Canvas alive and well. At a minimum, bring it forward in your ongoing roadmapping and backlog refinement sessions.</p><h3>Why the Product Canvas Is Necessary</h3><p>The purpose of the Product Canvas is to align product managers, product owners, product development teams, and associated organizations with a shared understanding of their product. Feed your product strategy and tactics with it. Use it to onboard new people, set content for product planning and discovery, and as a tool for shifting toward becoming a product-focused and customer-centric organization.</p><p>This is what I find most amazing about the Product Canvas:</p><p><strong>The collaborative process used to create and maintain the Product Canvas is its most valuable benefit.</strong></p><p><a href="https://www.ebgconsulting.com/ProductCanvas.pdf"><strong>Download the Product Canvas here</strong></a>. Please share your experiences, comments, and suggestions by emailing me at <a href="/service/mailto:ellen@ebgconsulting.com"><strong>ellen@ebgconsulting.com</strong></a>.</p><h3>References</h3><ol><li>Gottesdiener, Ellen and Mary Gorman. Discover to Deliver: Agile Product Planning and Analysis. EBG Consulting. 2015. <a href="http://www.discovertodeliver.com/download.php"><strong>http://www.discovertodeliver.com/download.php</strong></a>.</li><li>Kim, Chan W and Renée Mauborgne. Blue Ocean Shift: Beyond Competing — Proven Steps to Inspire Confidence and Size New Growth. 2017. New York: Hachette Books, 2017.</li></ol><p><strong>Note</strong>: This article was originally posted on EBG’s blog: <a href="https://www.ebgconsulting.com/blog/">https://www.ebgconsulting.com/blog/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47e85c074ccc" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/using-the-product-canvas-to-define-your-products-core-requirements-47e85c074ccc">Using the Product Canvas to Define Your Product’s Core Requirements</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using the Product Canvas to Define Your Product: Getting Started]]></title>
            <link>https://medium.productcoalition.com/using-the-product-canvas-to-define-your-product-getting-started-efd2889958f6?source=rss-34455d614558------2</link>
            <guid isPermaLink="false">https://medium.com/p/efd2889958f6</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Ellen Gottesdiener]]></dc:creator>
            <pubDate>Mon, 28 Jan 2019 23:15:15 GMT</pubDate>
            <atom:updated>2020-09-14T15:51:57.939Z</atom:updated>
            <content:encoded><![CDATA[<p>I usually find a diversity of opinion when I ask anyone within an organization what their products are. This is true for product companies whose primary source of revenue is their product and for companies who use products internally to run their business.</p><p>This comes from a lack of shared understanding.</p><p>Not having agreement on “what is our product” is particularly problematic in large enterprises that have built complex organizational structures. It also surfaces in organizations attempting to modernize their product development practices. Many organizations recognize the need to take an outside-in approach to their business in order to focus on their customers. Even when organizations shift from <em>project</em> thinking and embrace <em>product </em>thinking, the problem remains the same. We don’t agree on what our products are and what our products are not.</p><p>Not having agreement on what your product is, has broad implications for product strategy, internal organizational design, and ongoing operations. Whether you are faced with this challenge or want to take a step back to improve your product management practices, the first step is to define your product. And that’s where the Product Canvas comes in.</p><p>This blog introduces the Product Canvas and will be followed up with another blog on how to effectively create and use the Product Canvas.</p><h3>What a Product Canvas Is All About</h3><p>Since Alex Osterwalder and colleagues introduced the <a href="https://strategyzer.com/canvas/business-model-canvas"><strong>BMG canvas</strong></a>, many people have found a canvas to be an appropriate tool to succinctly communicate important business information. A canvas provides a compact, cohesive, and concise format to build and sustain shared understanding. [1] Canvas favorites of mine are Ash Maurya’s <a href="https://leanstack.com/leancanvas"><strong>Lean Canvas</strong></a>, Jeff Patton’s <a href="https://www.jpattonassociates.com/opportunity-canvas/"><strong>Opportunity Canvas</strong></a>, Dave Gray’s <a href="https://medium.com/the-xplane-collection/updated-empathy-map-canvas-46df22df3c8a"><strong>Empathy Map</strong></a>, and my own <a href="https://www.ebgconsulting.com/blog/matchup-canvas-improve-team-interdependency/"><strong>MatchUp Canvas</strong></a>.</p><p>The BMG canvas inspired me in 2014 to create the first version of a Product Canvas when I was product coach as a global car-sharing company. Since then, I’ve experimented with product canvases when I worked as a product coach at a variety of companies. As a result, I have formalized the Product Canvas defined as:</p><h4>The Product Canvas is a concise yet content-rich tool for conveying what your product is and how it is strategically positioned.</h4><p>My Product Canvas has evolved into two parts and is used to help a diversity of stakeholders agree on what their product is. The Product Canvas has the following benefits:</p><ul><li>Helps identify product outcome metrics</li><li>Prepares you for collaborative product roadmapping</li><li>Provides insight for restructuring an organization (product and engineering teams)</li><li>Facilitates product discovery, backlog management, and release planning</li></ul><h3>An Example Product Canvas</h3><p>Let’s explore the power of a Product Canvas with an example based on a case study in <a href="https://discovertodeliver.com/"><strong><em>Discover to Deliver</em></strong></a>. [2] Squeeky Kleen is a residential window cleaning business. Squeeky Kleen plans to expand to commercial properties, but for simplicity sake, we’ll focus on their residential business.</p><p>The Product Canvas has two parts.</p><p>Product Canvas Part 1 provides an overview to the product, its stakeholders, what stakeholders value, the product’s profitability, product’s marketing methods, and competitive information needed for product strategy. Part 1 of the Product Canvas for Squeeky Kleen might look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gcv-dXX9Xh58yXZX.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 1 for Squeeky Kleen</em></figcaption></figure><p>Product Canvas Part 2 identifies the 7 Product Dimensions to provide a holistic, comprehensive understanding of the product. You could say that part 2 is used to define product requirements:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mVKZ_4qginNn-lJ_.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 2 for Squeeky Kleen</em></figcaption></figure><p>The Product Canvas Part 2 is discussed <a href="https://medium.com/@ellengott/using-the-product-canvas-to-define-your-products-core-requirements-47e85c074ccc">in my next blog</a>.</p><h3>The Product Canvas in Context</h3><p>As shown below, the Product Canvas feeds two important product management tools: the product roadmap and the product backlog:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-WclrWx9fpuwCiyl.png" /><figcaption><em>EBG Consulting | The Product Canvas in Context</em></figcaption></figure><p>The product roadmap depicts how your product will evolve to realize your vision and achieve value for your customers and business. For that reason, the product roadmap is strategic. The product backlog contains near-term (Now-View), mid-term (Pre-View), and longer-term (Big-View) items that may be delivered to achieve the outcomes defined in the roadmap. Thus, the product backlog is tactical.</p><p>Product Canvas Part 1 concisely lays out your product’s strategic information. It feeds creating a <a href="https://www.ebgconsulting.com/blog/7-ways-of-creating-and-sustaining-an-agile-product-roadmap/"><strong>continually adapting product roadmap</strong></a>. It helps you define the themes to array across time horizons on the roadmap.</p><p>You might use classic product management tools to help you define the blocks on Product Canvas Part 1. This includes SWOT (strengths, weaknesses, opportunities, and threats) matrix, a strategy table (financial targets, release frequency, market segment adoption or penetration, and operational changes), PRESTO analysis (political, regulatory, and economic, social, and technology), and the classic 4P Marketing Mix (product, price, place, and promotion).</p><h3>Filling Out Product Canvas Part 1</h3><p>The figure below shows the information needed to complete Product Canvas Part 1:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0fA42OUD9UjX8xTb.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 1 | Download the </em><a href="https://www.ebgconsulting.com/ProductCanvas.pdf"><strong><em>Product Canvas</em></strong></a></figcaption></figure><p>Fill the overall product information first (product, your organization, date, and version):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b-TaUJILyKQP2JdS.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 1 | Header row </em><strong><em>A</em></strong><em>. Product, </em><strong><em>B</em></strong><em>. Organization, </em><strong><em>C</em></strong><em>. Date, </em><strong><em>D</em></strong><em>. Version</em></figcaption></figure><p>As the Product Canvas Part 1 will likely change over time, get into the practice of using a date and version. For the product, enter in the product name. For a commercial product, this is your branded name.</p><p>If your branded name is not intuitive, consider using a parenthetical name that clarifies the product’s purpose (e.g. “FutureForge: Commercial Lending”). Use a customer-focused name for internal products (ones not providing B2B or B2C revenue). Make sure the name is sustainable, as it will likely survive future management changes and organizational charts. Always avoid vendor names or acronyms that do not directly clarify the product’s core purpose.</p><p>The top row of the Product Canvas Part 1 is about the product big picture. The blocks are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kYr4Z1RrEbSu6VK1.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 1 | First row: </em><strong><em>A</em></strong><em>. Vision, </em><strong><em>B</em></strong><em>. Revenue Streams, </em><strong><em>C</em></strong><em>. Cost Factors, </em><strong><em>D</em></strong><em>. Channels</em></figcaption></figure><p>To complete the blocks for the product big picture, follow these instructions:</p><p><strong>A. Vision:</strong> This is the long-term, aspirational concept of your product. A vision is concise, compelling, and communicates the core purpose of the product. You can represent the vision in a variety of ways including as a tagline, meme, a product differentiation statement [3], a visual image, or a storyline.<br><em>Canvas </em><strong><em>Vision</em></strong><em> tips:</em> What do we strive to be? What do we do that changes the world? What differentiates us? What is our product’s tagline? Is there a visual image?</p><p><strong>B. Revenue Streams:</strong> Identify how you stay in business with this product. For a commercial product, this is revenue sources including license fees and B2C or B2B income. For internal products, revenue streams come from per-seat, team, or organization-level chargeback or allocation you expense to operate.<br><em>Canvas </em><strong><em>Revenue Streams</em></strong><em> tips: </em>How do we fund our product? Where does our revenue come from?</p><p><strong>C. Cost Factors:</strong> Identify the market, technological, economic, environmental factors that are at play as you handle all product lifecycle events. Factors can include changing licensing models, industry trends, consumer fickleness, shifts in hardware and software technologies, demographic changes in your user base, and marketing partnerships.<br><em>Canvas </em><strong><em>Cost Factors</em></strong><em> tips:</em> What cost factors are there to discover, deliver, market, sell, and service our product? What activities and assets are the most expensive? And what ones are most risky?</p><p><strong>D. Channels:</strong> What are the means you use to acquire, retain, and grow customers. Channels can be push (i.e., outbound marketing), pull (i.e., inbound marketing), or both. They might include leveraging internal communities or customer groups, early adaptor programs, newsletters, town halls, conferences, and education sessions.<br><em>Canvas </em><strong><em>Channels</em></strong><em> Tips</em> — How do we keep our customers coming back? How do we obtain, retain, and grow customer awareness of our product?</p><p>The middle row of Product Canvas Part 1 is about the product partners and what they value. The blocks are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ptQ6k-iEjk18HVl0.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 1 | Second row: </em><strong><em>A</em></strong><em>. Product Partner: Business, </em><strong><em>B</em></strong><em>. Value, </em><strong><em>C</em></strong><em>. Product Partner: Customer, </em><strong><em>D</em></strong><em>. Value, </em><strong><em>E</em></strong><em>. Product Partner: Technology, </em><strong><em>F</em></strong><em>. Value</em></figcaption></figure><p>Your product success relies on a partnership of business, customer and technology stakeholders. To complete the blocks for the product partners and what they value, follow these instructions:</p><p><strong>A. Product Partner: Business</strong>: Business partners include sponsors who authorize, legitimize and pay for product development. Other titles people who fit here include backer, benefactor, buyer, guarantor, and owner. Business partners also include product managers and external business partners with whom you participate in B2B relationships.<br><em>Canvas </em><strong><em>Business Product Partner</em></strong><em> tips</em>: Who are the people in the business who legitimize, authorize, pay, or help us promote the product? Who has domain experience we need to draw upon?</p><p><strong>B. Value (Business Partner):</strong> Business partner value is essentially about viability. You can view an overview of value considerations <a href="https://www.ebgconsulting.com/AnOverviewOfValueConsiderations(EBG_Consulting).pdf"><strong>in an article on my site</strong></a>.<br><em>Canvas </em><strong><em>Value (Business Partner)</em></strong><em> tips</em>: What outcomes do business partners want (e.g., increased revenue, cost reduction, risk reduction, brand projection, and customer satisfaction)?</p><p><strong>C. Product Partner: Customer:</strong> Customer partners include end users who directly interact with the product as well as buyers (sometimes buyers are not users), support users (such as help desk staffers, installers, operators, trainers), and people who influence or advocate for purchasing the product.<br><em>Canvas </em><strong><em>Customer Product Partner</em></strong><em> tips:</em> Who needs or uses our product? Who are our target customers? What market or market segment do we serve?</p><p><strong>D. Value (Customer Partner):</strong> customer partner value is essentially about product desirability — its usefulness and usability. You can view an overview of value considerations <a href="https://www.ebgconsulting.com/AnOverviewOfValueConsiderations(EBG_Consulting).pdf"><strong>in an article on my site</strong></a>.<br><em>Canvas </em><strong><em>Value (Customer Partner)</em></strong><em> tips:</em> What outcomes do customer partners want (e.g., save time, reduce effort, simplify access, and appeal to aesthetics)?</p><p><strong>E. Product Partner: Technology:</strong> Technology partners include internal staff as well as third-party staff. Also include people who have vital technology information about the product (even if they don’t build or maintain the product), such as information about implementation, governance and compliance, architecture, and training.<br><em>Canvas </em><strong><em>Technology Product Partner</em></strong><em> tips:</em> Who designs, builds, tests, deploys, services, trains, and supports the product?</p><p><strong>F. Value (Technology Partner):</strong> A technology partner value is essentially about product feasibility. You can view an overview of value considerations <a href="https://www.ebgconsulting.com/AnOverviewOfValueConsiderations(EBG_Consulting).pdf"><strong>in an article on my site</strong></a>.<br><em>Canvas </em><strong><em>Value (Technology Partner)</em></strong><em> tips:</em> What outcomes do technology partners want (e.g., increase architectural readiness, improve reliability, reduce future cost to service, and develop technical expertise)?</p><p>The bottom row of Product Canvas Part 1 is about the product competitive and innovation situation. The blocks are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y5K5utm-UFDiXdc4.png" /><figcaption><em>EBG Consulting | The Product Canvas Part 1 | Third row: </em><strong><em>A</em></strong><em>. Competitive/Leader Landscape, </em><strong><em>B</em></strong><em>. Innovation Waves (technology | platforms | standards)</em></figcaption></figure><p>To complete the blocks for the competitive and innovation situation, follow these instructions:</p><p><strong>A. Competitive/Leader Landscape:</strong> Know your product’s competitor and what they do that threatens your product’s market position. Identify the leader in your product’s domain and what the individual does exceptionally well.<br><em>Canvas </em><strong><em>Competitive/Leader Landscape</em></strong><em> tips:</em> Who competes with us? What are their strengths? Weaknesses? Who is the leader? What is their superior capability?</p><p><strong>B. Innovation Waves (technology | platforms | standards):</strong> Research and identify new (and potential) changes. This applies to technologies, business models, development platforms, delivery platforms, and industry standards. This requires practical knowledge and insight with product technologies and your vertical market.<br><em>Canvas </em><strong><em>Innovation Waves (technology | platforms | standards)</em></strong><em> tips:</em> what changes are happening now or possibly in future to hardware, software, platforms, or standards? What trends might impact the design, development, acquisition, deployment or servicing of the product?</p><h3>How to Create Product Canvas Part 1</h3><p>The Product Canvas Part 1 is a tool to build shared understanding. The best way to accomplish this is in facilitated workshops with representatives from the customer, business, and technology as participants. Here are some high-level guidelines:</p><ol><li>Start with your product vision. The vision defines the core “why” behind your product. I always use</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/0*VLjgFI-tReLzNVId.png" /></figure><p>collaborative sessions to define and refine the vision. There are various useful techniques to arrive at a vision, including Product Box, Vision Mandela, Newspaper Headline, or creating future scenarios and accompanying visual images.</p><p>2. Once your product vision has been defined, define the WHO and WHY by completing the middle row: your product partners (stakeholders from the customer, business, and technology realms), and what they value. This prepares you for completing the other three blocks on the top row of the Product Canvas Part 1.</p><p>3. After clarifying the Who and Value aspects of your product, layout the financial information. How you stay in business (revenue streams), cost factors, and mechanisms you use for connecting with customers (channels).</p><p>4. Next, tackle your competitive and leader landscape. The competitive analysis informs your product roadmap. It helps you understand what your competition offers that might draw customers to them (and away from you). It also leads you to consider short-term product hypotheses you and your product development team might undertake to either achieve parity or offer new product differentiators.</p><p>5. Continue with strategic thinking by completing the Innovation Waves block. Consider your product’s technology platform and global trends. Note: you may need to reconsider to this block after having completed the Environment dimension in Product Canvas Part 2.</p><p>6. Knowing the competition and innovations in your product space promotes strategic thinking. Ask yourself, “Will your product swim in a red ocean (highly competitive market space) or a blue ocean (uncontested market space)”? [4, 5]</p><h3>In Closing</h3><p>The Product Canvas provides you with a concise way to define and communicate the essence of your product. Part 1 articulates critical strategic information you need to guide product planning, development, pricing, marketing, funding, servicing, and deployment.</p><p>In my next blog, I’ll share how to create the Product Canvas Part 2.</p><p>As always, please share your experiences, comments, and suggestions by emailing me at <a href="/service/mailto:ellen@ebgconsulting.com?subject=MatchUp%20Canvas%20feedback"><strong>ellen@ebgconsulting.com</strong></a>.</p><p><em>Thanks to Cesario Ramos for his feedback</em>.</p><h3>References</h3><ol><li>Roberts, Andi. “Canvas Collection I — A List of Visual Templates” and “Canvas Collection II — A List of Visual Templates.” Andi Roberts Coach &amp; facilitator (blog). <a href="https://masterfacilitator.com/canvas-collection/"><strong>https://masterfacilitator.com/canvas-collection/</strong></a> and <a href="https://masterfacilitator.com/canvas-collection-2/"><strong>https://masterfacilitator.com/canvas-collection-2</strong></a>.</li><li>Gottesdiener, Ellen and Mary Gorman. <em>Discover to Deliver: Agile Product Planning and Analysis</em>. EBG Consulting. 2015. <a href="http://www.discovertodeliver.com/download.php"><strong>http://www.discovertodeliver.com/download.php</strong></a>.</li><li>Moore, Geoffrey. <em>Crossing the Chasm</em>. 3rd ed. New York: Collins Business Essentials, 2014.</li><li>Kim, Chan W and Renée Mauborgne. <em>Blue Ocean Strategy: How to Create Uncontested Market Space and Make the Competition Irrelevant.</em> Expanded Ed. Boston: Harvard Business Review Press, 2005.</li><li>Kim, Chan W and Renée Mauborgne. <em>Blue Ocean Shift: Beyond Competing — Proven Steps to Inspire Confidence and Size New Growth</em>. 2017. New York: Hachette Books, 2017.</li></ol><p><strong>Note</strong>: This article was originally posted on EBG’s blog: <a href="https://www.ebgconsulting.com/blog/">https://www.ebgconsulting.com/blog/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efd2889958f6" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/using-the-product-canvas-to-define-your-product-getting-started-efd2889958f6">Using the Product Canvas to Define Your Product: Getting Started</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Doing the Right Things, Not Everything: 
Product Management and Ownership]]></title>
            <link>https://medium.com/@ellengott/doing-the-right-things-not-everything-product-management-and-ownership-20e862c77528?source=rss-34455d614558------2</link>
            <guid isPermaLink="false">https://medium.com/p/20e862c77528</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Ellen Gottesdiener]]></dc:creator>
            <pubDate>Sat, 15 Sep 2018 15:47:57 GMT</pubDate>
            <atom:updated>2018-09-15T15:47:57.765Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/572/0*3Qka9ksEhuPFxqNt.png" /><figcaption>Image Source: EBG Consulting | www.ebgconsulting.com</figcaption></figure><p>In my product coaching work, I often find product people (Product Managers and Product Owners) struggling to do too much. It can be exhausting to attempt to do everything rather than focus on doing only the right things.</p><p>There needs to be a way to do two things. First, show how Product Managers and Product Owners can lean on their development team while providing appropriate product leadership. Second, show how a product development team supports product people. It is vital that product people have the bandwidth to focus on product strategy while building healthy interdependence and increasing the development team’s domain expertise.</p><p>I have posted an <a href="https://www.ebgconsulting.com/pdfDocs/Agile_Product_Management-Do_the_Right_Things-Not__Everything(EBG)(Gottesdiener).pdf"><strong>activity</strong></a> designed to help product folks and their development team to do just that. This consists of a three-part series of activities and a learning game called Delegation Poker. Each part has a specific goal that builds upon one another:</p><ul><li>Part 1: Gain a unified understanding of the work product management and ownership.</li><li>Part 2: Establish clear and transparent decision-making rules and process.</li><li>Part 3: Increase the empowerment the product person delegates to the product development team to make product-related decisions.</li></ul><p>The article provides you with all the instructions you need to be able to manage the activity yourself with a skilled, neutral facilitator who is knowledgeable about product management and development.</p><p>As always, let me know your comments and feedback. I’m always available to help.</p><p>Note: this article was originally <a href="https://www.ebgconsulting.com/blog/right-things-not-everything-product-management-ownership/?utm_source=Medium&amp;utm_campaign=Medium">posted on EBG’s blog </a>10 September 2018</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20e862c77528" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using the MatchUp Canvas to Improve Team Interdependency]]></title>
            <link>https://medium.com/@ellengott/using-the-matchup-canvas-to-improve-team-interdependency-fba87d12a664?source=rss-34455d614558------2</link>
            <guid isPermaLink="false">https://medium.com/p/fba87d12a664</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <dc:creator><![CDATA[Ellen Gottesdiener]]></dc:creator>
            <pubDate>Tue, 04 Sep 2018 16:16:06 GMT</pubDate>
            <atom:updated>2018-09-04T16:16:06.498Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.ebgconsulting.com/blog/author/ellen/"><strong>Ellen Gottesdiener</strong></a></p><p>Note: this article was originally <a href="https://www.ebgconsulting.com/blog/using-matchup-canvas-improve-team-interdependency/?utm_source=Medium&amp;utm_medium=Medium&amp;utm_campaign=MatchUpCanvas">posted on EBG’s blog</a> 4 August 2018</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xAJ0heq9tp3c7RlXIF2Ngg.png" /><figcaption>The MatchUp Canvas by Ellen Gottesdiener, EBG Consulting | <a href="http://www.ebgconsulting.com/">www.ebgconsulting.com</a></figcaption></figure><h3>What Makes a Great Product Development Team?</h3><p>Have you experienced working with a great product development team? Key characteristics of a great team I’ve witnessed include clear product outcomes understood by everyone, outstanding product leadership, regular customer engagement, and continuous product discovery and delivery cycles. While achieving outcomes with joy and purpose, a great team also enhances its own skills and knowledge.</p><h3>Agile Teamwork Requires Reciprocal Interdependence</h3><p>Agile product teams rely on each other’s skills and knowledge to achieve shared outcomes. Together, a great team continually adjusts what and how they are working together.</p><p>For example, the Product Manager identifies and shares product outcomes for the next quarter via Objectives and Key Results (OKR). [1] Their OKRs include reducing customer pain in one area of the product that takes customers too long to successfully complete. Typically, the Product Manager, UX expert, and engineer work together to design and conduct research via observation and low-fidelity prototypes. Once completed, the entire team gets involved to discuss their findings to identify the best bet for improving the user experience and reducing customer pain. They conduct a brief <a href="https://www.ebgconsulting.com/blog/structured-conversations-to-discover-your-mvp/"><strong>Structured Conversation</strong></a>, identify several backlog items with clear acceptance criteria, and proceed to run a <a href="https://svpg.com/discovery-sprints/"><strong>discovery sprint</strong></a> to try out their ideas.</p><p>At the conclusion of this discovery, the team reviews the outcomes of their key results using both qualitative (NPS or Net Promoter Score) and quantitative (time on task data instrumented into the product) methods. Adjustments can be made and retested in another round of discovery and delivery.</p><p>This team collaboration throughout discovery and delivery is the basis for interdependence as a form of mutual dependence. Their reciprocal interdependence relies on the team adjusting their work as new information arises. [2]</p><p>The other forms of interdependence identified by organizational theorist James Thompson are sequential and pooled. [3] These are less complex forms of interdependence, and require standardization and planning to achieve. Reciprocal interdependence, the most complex form of interdependence, embodies how agile teams need to collaborate, whereby the team mutually adjusts uncertainty and change.</p><h3>Why are Teams in Pain?</h3><p>To this day, I witness product development teams constantly stressed about who does what during a project lifecycle. They struggle with knowing how to ask for help, how to get help, and how to help each other. They are unaware of each other’s personal development goals and don’t consider how they can be a resource to each other. Team members can feel overwhelmed with too many requests for help from teammates while others feel underutilized. Too often, this weakened form of “teaming” results in less than satisfying product results. This results in lower personal motivation and job satisfaction.</p><p>I have found a way to make this unhappy teaming situation better.</p><h3>Make Explicit Agreements</h3><p>To improve this situation, simply discuss it and make explicit agreements about what each person can expect from each other. Everyone working on a team wants to know, “Am I in?”, “Am I out?”, or “Does my team need me?”. [4] Borrowing a term from political philosophy, organizational development and management experts refer to this as <em>social contacting</em>. [5]</p><p>Social contracting includes making explicit agreements that starts from a place of genuine curiosity about your teammates. What goals do we have? What skills and knowledge do we possess? Can we help each other develop and grow as we collaborate toward shared product outcomes? Answering these questions leads to mutual understanding of each other’s capabilities, builds a team with healthy interdependence, increases each person’s motivation, and leads to better product outcomes.</p><h3>The MatchUp Canvas — A Tool for Healthy Team Interdependence</h3><p>To build and sustain a healthy working relationship through team interdependence, I’ve developed a tool called the MatchUp Canvas.</p><p>Whether you are forming a new team and conducting a Liftoff, [6] reconfiguring a team with changing members, or recognizing that your team could benefit from a reboot, one way to accomplish this is a social contracting tool I call the Matchup Canvas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/0*mFsN_KaC13MrmXOo.png" /><figcaption>The MatchUp Canvas by Ellen Gottesdiener, EBG Consulting | www.ebgconsulting.com</figcaption></figure><p>Source: EBG Consulting | <a href="https://www.ebgconsulting.com/wp/wp-content/uploads/2018/08/The_MatchUp_CanvasGottesdiener_EBG.zip"><strong>Download The MatchUp Canvas</strong></a></p><p>The MatchUp Canvas purpose is to serve as means to help teams make explicit agreements about how they will improve their mutual interdependence. The value is in the activity the teams engages in to deliver their MatchUp Canvases to and with each other.</p><p>I’ve combined the MatchUpCanvas together a set of instructions for using the MatchUp Canvas as a <a href="https://www.ebgconsulting.com/wp/wp-content/uploads/2018/08/The_MatchUp_CanvasGottesdiener_EBG.zip"><strong>download package</strong></a>.</p><h3>The MatchUp Canvas Helps Build Great Agile Product Teams</h3><p>Great teams act interdependently to achieve product outcomes. That doesn’t happen by accident. It takes deliberate effort. By proactively determining how teams depend on each other, agreements can be made on the “give and take” required to improve teamwork. Doing so strengthens team partnerships and customer relationships. Ultimately, this leads to better product outcomes and makes work more joyous.</p><p>The MatchUp Canvas is a tool you can freely use to facilitate great teamwork. Please share your experiences, comments, and suggestions by emailing me at <a href="/service/mailto:ellen@ebgconsulting.com?subject=MatchUp%20Canvas%20feedback"><strong>ellen@ebgconsulting.com</strong></a>.</p><h3>References</h3><ol><li>Wodtke, Christina. <em>Radical Focus: Achieving Your Most Important Goals with Objectives and Key Results</em>. Cucina Media LLC, 2016.</li><li>Thompson, James D. <em>Organizations in Action: Social Science Bases of Administrative Theory</em>. New York: Routledge, 2017.</li><li>Schwarz, Roger. “Is Your Team Coordinating Too Much, or Not Enough?” <em>Harvard Business Review</em>. March 23, 2017. <a href="https://hbr.org/2017/03/is-your-team-coordinating-too-much-or-not-enough"><strong>https://hbr.org/2017/03/is-your-team-coordinating-too-much-or-not-enough</strong></a>.</li><li>Weisbord, Marvin R. <em>Productive Workplaces Revisited: Dignity, Meaning, and Community in the 21st Century</em>. 2nd San Francisco: Jossey-Bass, 2004.</li><li>Riordan, Christine and Kevin O’Brien. “For Great Teamwork, Start with a Social Contract.” <em>Harvard Business Review</em>. April 17, 2012. <a href="https://hbr.org/2012/04/to-ensure-great-teamwork-start"><strong>https://hbr.org/2012/04/to-ensure-great-teamwork-start</strong></a>.</li><li>Larsen, Diana and Ainsely Nies. <em>Liftoff: Start and Sustain Successful Agile Teams, Second Edition</em>. Raleigh, NC: Pragmatic Bookshelf, 2016.</li></ol><p>Note: this article was originally <a href="https://www.ebgconsulting.com/blog/using-matchup-canvas-improve-team-interdependency/?utm_source=Medium&amp;utm_medium=Medium&amp;utm_campaign=MatchUpCanvas">posted on EBG’s blog</a> 4 August 2018</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fba87d12a664" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>