<?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 Andrea Stubbe on Medium]]></title>
        <description><![CDATA[Stories by Andrea Stubbe on Medium]]></description>
        <link>https://medium.com/@andrea.stubbe?source=rss-fe61140b7dd0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*HMOE1GnGiB_mqGV1aI33Vg.jpeg</url>
            <title>Stories by Andrea Stubbe on Medium</title>
            <link>https://medium.com/@andrea.stubbe?source=rss-fe61140b7dd0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:52:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andrea.stubbe/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[Product & Tech — Better Together!]]></title>
            <link>https://medium.com/commercetools-tech/product-tech-better-together-7d8ced10d83f?source=rss-fe61140b7dd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d8ced10d83f</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[human-centric]]></category>
            <dc:creator><![CDATA[Andrea Stubbe]]></dc:creator>
            <pubDate>Tue, 02 Aug 2022 06:54:12 GMT</pubDate>
            <atom:updated>2022-08-02T06:54:12.803Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product &amp; Tech — Better Together!</h3><figure><img alt="soda and burger falling in love" src="https://cdn-images-1.medium.com/max/1024/1*3BqLth-IJZrDqdU56WPWLg.png" /><figcaption>Soft drink and burger — better together! <a href="https://www.vecteezy.com/free-vector/nature">Nature Vectors by Vecteezy</a></figcaption></figure><p><em>The one big challenge in product development is that there are always so many ideas and so little time! Or so they say. The far bigger challenge is that we’re all humans, with our own ambitions, biases, strengths, egos, and flaws — all the things that make us our amazing and wonderful selves.</em></p><p><em>At commercetools, we believe that no matter how well established your processes and methodologies are, you can only be successful if you set up your organization for people, and not for cogs in a machine. We are a true “</em><a href="https://www.humanocracy.com/"><em>humanocracy</em></a><em>” (human centric org), intentionally seeking to spark off everyone’s human potential.</em></p><p>Just like the biological model tells us we are powerless to our genetics, old school companies with obsolete practices have created fixed work environments where people are conditioned to act within restricted boundaries. But new sciences like <a href="https://www.cdc.gov/genomics/disease/epigenetics.htm">epigenetics</a> tell a different story. They highlight how our behaviors and environmental factors can change our gene expression or how our genes work.</p><p>Why shouldn’t this be the case for organizations as well? We’ve done it. We’ve organically built our own core environmental elements and principles ceaselessly and positively altering our “collective genes” and helping us be and do better together. Here is how:</p><h3>We don’t know everything, but<strong> everyone knows something</strong></h3><p>Different from traditional companies, where product and technology argue over sparse development time and roadmap space, we — Product Managers, UX and Tech — have a collaborative approach and use everyone’s skills and expertise to determine what brings the most value — for a <a href="https://www.youtube.com/watch?v=vzwSezZ-8uo">MACH architecture</a> product in a <a href="https://commercetools.com/company/our-journey">fast-growing company</a>, tech, growth, UX, and features all contribute!</p><ul><li>The Product side brings the knowledge about customer value, user satisfaction, and market potential doubled down by the right methodologies to prioritize.</li><li>Technology leadership has a deep understanding of the value that architectural, security and technological advancement brings.</li><li>Engineering leadership and agile coaches contribute with their knowledge of organizational design, process and tool improvements, plus give answers to the challenges of building and nurturing engineering teams.</li></ul><p>The different skills, relevant experiences and motivations are the reason why on all levels of the organization, tech, product, engineering and agile coaches are better together — we need each other, and cannot succeed in isolation and silos.</p><figure><img alt="Cute egg and bacon" src="https://cdn-images-1.medium.com/max/1024/1*39lOfsOIzX8hFa9HifqZhA.png" /><figcaption>Egg and bacon — better together! <a href="http://Cartoon Food Vectors by Vecteezy">Cartoon Food Vectors by Vecteezy</a></figcaption></figure><p>Sometimes the topics we work on can be complicated. That’s why we have a group of internal experts and advisors. <a href="https://techblog.commercetools.com/staff-and-principal-engineers-why-do-we-need-them-now-part-2-a6dcf2d6ad34">Principal Engineers</a> consult on technology and drive technology or initiatives, Principal UX and Market / Competitive Intelligence help on UX and product value topics, and Business &amp; Leadership Coaches support and guide organizational change and leadership practices.</p><p>We are mindful of <a href="https://www.youtube.com/watch?v=Vn9BUfUCL4I">our own limitations</a> and create space for everybody’s strengths to shine. The close collaboration deepens the respect for areas we would otherwise know nothing about, and with that, our respect for the people working in them.</p><p>At the same time, working at the edge of our abilities as individuals or teams — where we’re neither over-competent or complacent nor overwhelmed — allows us to build a work environment where our skills and what we know can exist in sheer harmony with the challenges of the unknown. We’re constantly optimizing our internal seesaw to balance our knowing, being, and working together.</p><h3><strong>We listen to each other and to our own thoughts</strong></h3><p>Our strong collaboration doesn’t stop at prioritizing. Feasibility assessment and delivery are also a team effort. The team discusses whether they are set up for successful delivery and commit to deliverables together and unanimously. We’re not a process-driven company. We are a team-driven organization with an <a href="https://www.extremeuncertainty.com/outcomes-not-outputs/">outcome-driven</a> mindset. We are focused on how to create value together as opposed to pushing out features as fast as we can.</p><p>We follow the same pattern for all important decisions, on all levels. Whether it’s about how we restructure our organization while growing, interviewing candidates for key positions, or deciding on ways of working within a team:</p><ul><li>CTO, CPO, Director of Tech Leadership, VP Product, and Head of Agile Coaches work together as equal peers on high-level goals for the product &amp; organization.</li><li>Head of Products, Head of Engineering, Staff Engineers and Product Managers, and Lead Agile Coaches do the same on the product group level.</li><li>Product Managers, Engineering Managers, and Agile Coaches do the same on the team level.</li></ul><p>Truly listening to others’ ideas and thoughts and practicing the <a href="https://www.implicity.org/Downloads/Bohm-Senge-Team%20Learning.pdf">discipline of dialogue</a> is not only important to make better decisions and produce extraordinary results. It also reminds us every day that the truth is more than just our own mental model of the world and makes us aware of the biases and assumptions we may have. Only then can we access authentic and earnest “thinking together.”</p><figure><img alt="Cute coffee cup and croissant" src="https://cdn-images-1.medium.com/max/1024/1*3zIdegWq-Upg8rJjImmExQ.png" /><figcaption>Croissant and coffee — better together! <a href="http://Cartoon Food Vectors by Vecteezy">Cartoon Food Vectors by Vecteezy</a></figcaption></figure><p>It isn’t easy to speak up and share a viewpoint different from what others said. As humans, we want to fit in and earn the approval of others while avoiding being shunned and “sentenced to unworthiness.” At commercetools, we work on giving people an environment of trust and blamelessness and actively encourage dissenting opinions. Not only does it make discussions more interesting, but it also helps us not to get stuck in an <a href="https://theconversation.com/the-problem-of-living-inside-echo-chambers-110486">echo chamber</a>, where the most prominent idea gets reinforced and never challenged. A good conversation is one where everybody walks away with a new perspective.</p><h3><strong>We don’t hide </strong>and we show up even when it’s hard</h3><p>For commercetools, the product is front and center. There are a lot of colleagues who rely on us to deliver not only a product but also transparency about where we are, what we’re up to next, and why sometimes not everything is running perfectly. We take the time to build our information architecture and have many ways to share what we know, from real quick status meetings to product demos and retrospectives.</p><p>This transparency is only possible because there is <a href="https://www.davidsonmorris.com/no-blame-culture/">no need to hide</a> even uncomfortable truths. We know that all teams want to do good, and when things don’t go as planned, everybody chimes in to help and remove roadblocks. We have each other’s backs, regardless of reporting lines or which team someone is on. This leads to being rewarded when you share that you have a problem instead of being punished and reinforces the behavior of communicating openly and often. And that’s how we engage everyone in the company and foster and encourage a culture of continuous participation and empowerment.</p><p>In postmortems (those are retrospectives we do whenever something bad happens, for example, a bug in production), we are just as open and transparent. The goal here is not to identify opportunities for short-term solutions but to learn through reflection and aim to get better as a team.</p><figure><img alt="Cute waffle and ice cream" src="https://cdn-images-1.medium.com/max/1024/1*AaMi3uIRgLxJzD2UuFgc0A.png" /><figcaption>Waffle and ice cream— better together! <a href="http://Cartoon Food Vectors by Vecteezy">Cartoon Food Vectors by Vecteezy</a></figcaption></figure><p>Another area where we don’t hide is feedback and <a href="https://review.firstround.com/the-ics-guide-to-driving-career-conversations-25-tips-for-purposeful-career-planning">career conversations</a>. Reflect on yourself, reflect on your colleagues, and share your criticism, feelings, appreciation, and expectations. Behind this is a strong belief that we can trust each other to be treated fairly, respectfully, and accepted as we are — and coached and guided to become better versions of ourselves every day.</p><h3><strong>Now and forever</strong></h3><p>We are big fans of liminal spaces (from the Latin term “limen,” which means threshold). In architecture, they describe all corridors, hallways, and in-between areas that connect one space to another. In our daily work matters, liminality is the term describing all of our in-between mental spaces that help us transition across all sorts of boundaries and borders: the comfort of the familiar and the thrill of the unknown, the supposedly untouchable territories of our domains to new opportunities of interconnecting them. We have found our liminal spaces, our daily thresholds we deliberately cross so we can be and build better together.</p><p><strong>We don’t know everything, but everyone knows something. </strong>We are the sum of all parts, and while each part — Product, UX, Internal Experts, Tech — has a well-defined area of practice and impact, we are stronger, wiser, and nimbler when we unite our domains, minds, and hearts and work together.</p><p><strong>We listen to each other and to our own thoughts.</strong> While we may have one big purpose, we are more than one voice. We actively listen to each other and ensure everyone has the time and space to express themselves. We avoid echo chambers and aim to elevate our perspectives and learn.</p><p><strong>We don’t hide and we show up even when it’s hard.</strong> We have created a safe space where the hard truth and the uncomfortable facts can be shared with candor. We don’t hide; we reflect. We don’t keep it to ourselves, we communicate openly and involve everyone.</p><h4><strong>We Are Humans.</strong></h4><h4><strong>We Are Better Together.</strong></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d8ced10d83f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commercetools-tech/product-tech-better-together-7d8ced10d83f">Product &amp; Tech — Better Together!</a> was originally published in <a href="https://medium.com/commercetools-tech">commercetools tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we Roadmap in 2021]]></title>
            <link>https://medium.com/@andrea.stubbe/how-we-roadmap-in-2021-d024a4c6b180?source=rss-fe61140b7dd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d024a4c6b180</guid>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[rice]]></category>
            <category><![CDATA[weighted-score]]></category>
            <dc:creator><![CDATA[Andrea Stubbe]]></dc:creator>
            <pubDate>Wed, 23 Jun 2021 11:58:16 GMT</pubDate>
            <atom:updated>2023-03-24T16:03:49.365Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the recurring tasks as Head of Product is coming up with quarterly roadmaps. After six iterations of trial and improving, I feel like we’re getting somewhere good. Good enough to be worth sharing anyway.</p><h3>Why roadmap anyways (and how to do it well)</h3><p>I’ll admit it — when I started as a product manager, I was not a fan of building roadmaps. Hated it. Because they looked like this:</p><figure><img alt="A project plan displaying boxes in a sequence, each representing a piece of work. The boxes are sorted into a timeline from January to March." src="https://cdn-images-1.medium.com/max/1024/1*25n9w9ozP15LeVLD0ZBqXQ.png" /></figure><p>More of a project plan, listing all the outputs in a specific order (with mostly improvised box-sizes and dates), than a document that highlighted what we were planning as the next steps to deliver on the product vision and bring value to customers and company alike.</p><p>So, why have a roadmap? We use them for three main reasons:<br>1. Make sure we don’t stray from our vision: We roadmap quarterly, which gives us a built-in quarterly checkpoint to remind the product teams where we want to go, and what the next steps for getting there are.<br>2. Help customers make wait vs. build decisions: One of our product’s strengths is that it can be extended and customized, allowing our customers to implement a large variety of use cases with it. It’s great. But it is even greater for our customers if their challenges are solved out of the box. By being transparent about our plans and progress, customers can focus and plan their investments better.<br>3. Start a dialog between product and customers: We do have a lot of brilliant, innovative, and enthusiastic customers. When we show them what we plan to work on, they do share their thoughts, ideas, and pains with us — and we listen and learn.</p><p>In short, we love our roadmaps. And make them without fidgety boxes.</p><h3>A sixty-second summary of all prioritization methodologies I used or researched</h3><p>Prioritization methodologies or frameworks (<a href="https://www.scaledagileframework.com/wsjf/">Weighted-Shorted-Job-First</a>, <a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/">RICE</a>, <a href="https://www.productplan.com/glossary/moscow-prioritization/">MoSCoW Analysis</a>, and a dozen more) all aim to bring work items into a specific order: What do we start working on? And then? And then? And then?</p><p>They do this by looking at value and risk.</p><p><strong>Value = good. Risk = bad</strong>.</p><p>Some go to great lengths to define how to calculate both, others are more like: Hey, how about starting with the most valuable one? Which isn’t exactly helpful advice.</p><p>Summarized, high values in the “good” section will put items to the top of your list, high values in the “bad” section move them to the bottom.</p><figure><img alt="Good: Value, Impact, Importance, Reach, Satisfaction, Increase in satisfaction, Contribution to “drivers” (which are dimensions you define as valuable), Urgency, Cost of Delay. Bad: Item complexity, Implementation efforts, Uncertainty about the scores given for value, Costumer’s Dislikes" src="https://cdn-images-1.medium.com/max/792/1*44rdCTu_zrDlYXY_m5qbHw.png" /></figure><h3>The challenge</h3><p>Find a way to quantify value and risk that is not susceptible to biases that do harm (some biases are sort of okay, and can even be good), and is not impossible to use for your team.</p><p>Some influencing factors to consider:</p><ul><li>The scale of the operation: Are you roadmapping for the whole product org or one team? Within a feature or smaller, or from 10k feet?</li><li>The stage your <a href="https://corporatefinanceinstitute.com/resources/knowledge/finance/business-life-cycle/">company</a> and <a href="https://corporatefinanceinstitute.com/resources/knowledge/other/product-life-cycle/">product</a> are in</li><li>Product quality and stability within the last quarter</li><li>How the teams are doing: <a href="https://www.youtube.com/watch?v=ysWWGf8VsOg">Forming, norming, storming, or performing?</a></li><li>Company culture and people: If you have strong <a href="https://dzone.com/articles/stop-estimating-the-noestimates-movement">#noestimates</a> advocates, stay away from using efforts or complexity to quantify. If you work with people that understand statistics, be careful with quote-unquote <a href="https://www.optimizely.com/optimization-glossary/aa-testing/">“statistics”</a>.</li></ul><h3>Our situation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jIAX1RXfZiJW1IqPdJH0kQ.png" /></figure><p>Sooo… looking at this, we can rule out all frameworks that depend on effort or complexity. It cannot be too heavy on statistical data but has to take customer input as well as growth plans into account. As I work with people that are too smart to just believe what they are told, the methodology needs to be research-driven, data-informed, and as opinion-free as possible.</p><p>Another challenge we faced is that our <a href="https://lethain.com/productivity-in-the-age-of-hypergrowth/">system</a> was close to the limits it could handle — both organizationally, and technically. That meant we needed to invest in costly and <a href="https://luxafor.com/the-eisenhower-matrix/">urgent</a> growth initiatives. “Costly” meaning a couple of developer years, “urgent” meaning that we now wish we would have done it earlier. Sort of like when you wish you would have gone to the dentist before the toothache started.</p><p><em>Very relevant side note: When reading that we postponed getting our metaphorical teeth checked, you might have thought: “Well, that wasn’t smart.” But, and this is what this article is about, it </em><strong><em>was</em></strong><em> smart. When previous roadmaps have been built, a prioritization method that favored technical innovation, fast progress, and winning new customers absolutely made sense. It all depends on the situation. Also, </em><a href="https://glenndejaeger.wordpress.com/2010/04/05/programming-antipatterns/"><em>premature optimization smells</em></a><em>. We have since made the investment to set our system up for a higher magnitude of load and scale.</em></p><h3>How we roadmap in 2021</h3><p>Just looking at the <strong>value</strong> aspects of prioritization methodologies, we need something that works equally well for innovation, improving user experiences, <a href="https://www.thoughtworks.com/insights/articles/demystifying-conways-law">organization together with architectural setup</a>, and scaling up our platform to work with x times the load from last year.</p><p><a href="https://www.thoughtco.com/what-is-a-weighted-score-3212065">Weighted scores</a> are pretty perfect for that, as they do not prescribe what matters to you, and allow you to rank the influence each of the dimensions has.</p><p>Weighted scores can be a bit hard to wrap one’s head around. Here’s a food-based example to illustrate it: Deciding what’s for lunch.</p><p>Dimensions that matter:</p><ul><li>Healthiness</li><li>Yumminess</li><li>Speed of preparation and eating</li><li>Food-coma-likelihood</li></ul><p>Each day, those dimensions can have different importance (weight) for you. Monday, your mean calendar only gives you a 30-minute lunch break, so you weigh Speed at 70%, No-Food-coma at 25%, and Yumminess at a has-to-be-edible-5%. Which results in a “whatever is in the fridge” sandwich. On Saturdays you have plenty of time and want to indulge yourself and go for 20% Health, 80% Yummy — and I leave the rest to your imagination.</p><p>When deciding on what to eat, you assign a value to each of those dimensions to every single food item you have on your shortlist, sort by rank, and pick the top one — or for a roadmap, the top n ones. This is what we do in our quarterly plannings. This is how it looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ixD0I2NzfIPKdfw4ozLOZg.png" /></figure><h3>Using data to inform weights and scores</h3><p>We review these dimensions once per year and adjust the weights with each quarterly planning. The main data point we use to inform the weight for “enjoyable experiences” and “scaling” is the number and impact of incidents, measured by <a href="https://medium.com/kudos-engineering/managing-reliability-with-slos-and-error-budgets-37346665abf6">SLOs and error budgets</a>. Another important source is customer feedback and questions our support team gets.</p><p>To rank an individual item in the “innovation” and “enjoyable experiences” dimensions, the most important data point we use is the <em>user impact score</em>. It is basically the first two letters of <a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/">RICE</a> — Reach (“how many customers are having this problem?”) and Impact (“how important is it to them?”). We diligently collect every piece of customer feedback throughout the year and use that to determine the user impact score.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9Hl4y8GChzrvW8YuqEP5g.png" /></figure><h3>Evaluating risk</h3><p>This is a challenge I struggled with for years. Having been a software engineer for about half my career, I know the difficulties of estimating efforts or complexity for pretty much any programming work that couldn’t also be <a href="https://www.wired.com/story/ai-write-code-ordinary-language/">done by a program</a>. That is especially true for topics around scaling and optimizations, which by nature require a lot of experimentation and testing; or those nasty <a href="https://www.techopedia.com/definition/3810/heisenbug">Heisenbugs</a>. Additionally and as mentioned earlier, using efforts or complexity to measure risk is fundamentally biased against tackling tooth-ache preventing work.</p><p>But ignoring delivery risk completely doesn’t seem wise either — reliable roadmaps are helpful, internally and for customers.</p><p>Curtains up for: “The Managing Complex Change Model“ (<a href="https://www.linkedin.com/in/marylippitt/">Mary Lippitt</a>, 1987), also referred to as the Knoster model for managing change. The model identifies five key elements for successfully implementing organizational changes — and it applies well for all sorts of change, including changes to a product. In a nutshell, if one of those elements is missing, you won’t be able to deliver what you set out to do.</p><figure><img alt="To succeed, you need vision + skills + incentives + resources + action plan. No vision =&gt; confusion. No skills =&gt; anxiety. No incentives =&gt; slow progress. No resources =&gt; Frustration. No action plan =&gt; False starts." src="https://cdn-images-1.medium.com/max/1024/1*6D7RoSYo6M201Msq9EAN9A.png" /></figure><p>Using this, we can reduce the risk part to a set of yes / no questions, leading to a simple yes/no on whether or not a team can deliver the product change. If the answer is yes — brilliant, put it on the roadmap! If the answer is no — identify what is missing, and put these items on the roadmap. It is as easy as it sounds, and leads to great insights to improve teams or the organization.</p><h3>TL;DR and Related Thoughts</h3><ul><li>When prioritizing work, we look at everything that takes time holistically — product innovation, organization, and tech. We think this is a better alternative than budgeting for tech or org work and planning those separately.</li><li>We assembled different parts of different frameworks into something that is a good fit for our situation and context. Tip: Look at completely different areas, don’t only stick to product management. You’ll find that there is a treasure trove of inspiration and ideas to try!</li><li>We do collect customer insights throughout the year, and it is… another treasure trove! Tip: If you use data to prioritize, make sure it is complete and correct enough to be valuable.</li><li>Tools help! We use and love <a href="https://www.productboard.com/">productboard</a> (the screenshots you see in this post are taken from there), but <a href="https://www.linkedin.com/company/product-for-product-podcast/">there are others, too</a>.</li><li>Lastly, but most importantly — Let your <a href="https://medium.com/radical-product/north-star-framework-7e167e250a4a">north star</a> guide you. No roadmapping methodology can ever replace a solid vision.</li></ul><p><em>TL; Don’t want to read? Watch the </em><a href="https://vimeo.com/537445308/7b1103dcbe"><em>video</em></a><em> of my presentation at the OSN Speaker series!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d024a4c6b180" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving Organizational Issues like a Product Manager]]></title>
            <link>https://medium.com/@andrea.stubbe/solving-organizational-issues-like-a-product-manager-f638a71a80e2?source=rss-fe61140b7dd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f638a71a80e2</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Andrea Stubbe]]></dc:creator>
            <pubDate>Thu, 20 Aug 2020 18:38:03 GMT</pubDate>
            <atom:updated>2023-03-24T16:07:44.541Z</atom:updated>
            <content:encoded><![CDATA[<p>Working to carve out solutions that address the problems they’re meant to solve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hRbUcELWLjqhEt2MY_marw.jpeg" /></figure><p>Where I work, we strive to have an environment where everyone and every team feels, and is, valued/respected.</p><p>To strive towards something also means that we’re never quite satisfied with the status quo, and constantly look for ways to improve. That leads to having plenty of ideas, and no way to work on all of them at the same time! And how do we know if an idea is actually effective at solving a problem? Sounds an awful lot like the day-to-day challenges which product teams have, right? Let’s explore if a product team’s way of working can be transferred to tackling organizational issues.</p><ol><li>What’s the value of solving the problem?</li><li>Understand the problem, before jumping to solutions</li><li>Build empathy and hear all sides</li><li>Define and measure success</li><li>Find solutions</li></ol><h3>What’s the value of solving the problem?</h3><p>Start with deciding whether a problem is worth investigating further. All the following steps take considerable effort, and we only want to go there if the impact is high. How often was it raised in 1:1s, team meetings, postmortems, or informal chats? How badly does it affect people? Were there escalations? Does it impact company, product, or customers in a bad way?</p><p>Other than when assessing the value of solving problems within the product, we haven’t seen a strong correlation between how many people bring up an organizational issue and the value of solving it. This might be different for you, so take good care of carefully interpreting the <a href="https://bunch.ai/blog/what-you-need-to-think-about-before-using-people-data-to-make-decisions/">data</a> at hand.</p><p><strong>Examples — High value</strong></p><ul><li><strong>Product</strong>: <em>The API to add an item to a cart takes more than 1000 ms to reply. That is a long wait time, and the store notices a decline in sales.</em> High value as 40% of customers abandon the site after wanting to add an item to the cart. Meaning all users of the Cart API are affected.</li><li><strong>Organizational</strong>: <em>Handing over on-call duties between time zones leads to hiccups in incident handling. It doesn’t happen often — it’s been that way for many years and everybody is used to it — yet whenever it does, it leads to miscommunication with customers and longer recovery times.</em> High value since it happens for an extended period of time, affects many people, and impacts customers.</li></ul><p><strong>Examples — Low value</strong></p><ul><li><strong>Product</strong>: <em>One customer, who is using a browser that has been deprecated by the vendor, cannot use the storefront and shops somewhere else.</em> Low value as the number of affected customers is barely noticeable.</li><li><strong>Organizational</strong>: <em>Support occasionally sends a ticket to the wrong team. The affected team brought it up in a handful of retrospectives, and things typically improve. But whenever a new person joins the support team, it starts happening again.</em> Low value as it only happens around specific events, does not impact on customers, and is solved without escalations.</li></ul><h3>2. Understand the problem, before jumping to solutions</h3><p>After we decide a problem is worth looking into, we research it thoroughly. The human brain is wired to jump to solutions very early (<a href="https://www.goodreads.com/book/show/11468377-thinking-fast-and-slow">Thinking, Fast and Slow</a> is a good read on that topic), and it takes discipline to stay in the <a href="https://medium.com/@nikhilgupta08/problem-space-vs-solution-space-f970d4ace5c">problem space</a>.</p><p>The effort pays off, however, as only when a problem is understood, can we identify valid solutions. Otherwise, we’ll end up implementing an initiative that sounds like a great idea, but doesn’t perform well in solving the problem.</p><p>To understand an organizational or product problem, look at specific examples. As many as you can find: Ask colleagues, dig through meeting notes and retrospectives from the past, and recall similar situations in other companies you worked at. Be aware of your <a href="https://www.verywellmind.com/what-is-a-cognitive-bias-2794963">biases</a> and challenge <a href="https://www.youtube.com/watch?v=7rr88Szc5q0">assumptions</a>, and take some time to understand the <a href="https://www.goodproductmanager.com/2009/03/09/define-the-problem-before-solving-it/">size</a> of the problem.</p><p>If the problem is defined too narrowly, you will miss out on making a fundamental improvement that would also help with other issues. It also gets a bit <a href="https://www.techwell.com/techwell-insights/2013/06/what-do-about-workplace-culture-blame">blame-y</a> quickly. If the problem is defined too broadly, it is hard to find a solution that actually helps.</p><p><strong>Example:</strong> Team Product is focused on building a new feature. Everybody is excited and things go well until Team Project tells them that they need something else, now, or they will be delayed in delivering critical functionality for a customer project.</p><ul><li>Narrow: <em>“Team Project interrupts Team Product’s flow and focus, which is bad”</em></li><li>Broad: <em>“Communication between departments has to improve”</em></li><li>Middle: <em>“We lack a way of handling dependencies that is not frustrating either party”</em></li></ul><p>So be sure to write down a clear problem statement!</p><p><strong>Examples:</strong></p><ul><li><em>“Whenever responsibilities change during the handling of an incident, we see a decline in speed and quality”</em></li><li><em>“It is hard for new hires in support to understand which team is responsible for which functionality”</em></li><li><em>“Product Managers are worried about the impact a new architecture will have on the product and our ability to deliver value”</em></li></ul><h3>3. Build empathy and hear all sides</h3><p>For products, and especially in UX design, it is important to understand the situation and emotional state a user is in and design the product accordingly.</p><ul><li>Is the user stressed from performing a task? Make it plain and simple.</li><li>Is the user scared, because small mistakes will have big consequences? Add review options and warnings for destructive operations, and reassurance for harmless ones.</li></ul><p>When it comes to organizational problems, emotions play an even <a href="https://www.entrepreneur.com/article/293521">bigger part</a>. The simple act of talking about problems can challenge how people see themselves or may be perceived as criticism. Understanding the emotions involved helps you to phrase problems in a way that does not call people out or triggers defensiveness. Otherwise, your attempt to solve a problem may create additional ones.</p><p>To understand the emotions and build up empathy, nothing beats observing and listening. Schedule interview sessions or group discussions with the main actors and people that came forward.</p><p>Here are two quotes about dependency handling to show the two sides of the story:</p><blockquote><em>“Our team spends the vast majority of our time building something to unblock teams. We don’t make any progress on work we see as more important for the company.”</em></blockquote><blockquote><em>“We are blocked for weeks, as we cannot find a team to build something that we need to proceed, and don’t have the expertise in our team.”</em></blockquote><p>Interestingly, both sides were frustrated about the same thing: Not being able to deliver what they perceive as most important is frustrating!</p><p>Use those learnings as input for finding a solution that works for all sides.</p><h3>4. Define and measure success</h3><p>Before you’re ready to think about solutions, define what success looks like and how you can measure it. And then make it a habit to look at the numbers to see if initiatives should be kept, adjusted, or stopped.</p><p><strong>Examples:</strong></p><ul><li><em>The number of support tickets assigned to a wrong team stays stable at a max of 5%, even when new members join the team</em></li><li><em>Maintenance efforts are reduced to 10% within one year and stay there</em></li></ul><h3>5. Find solutions</h3><p>When building products, we often run into constraints for solutions we find: Do we have the knowledge and skills? Do we have a team to work on this? Is the solution aligned with the product vision, compliant with laws and regulations, can we scale it?</p><p>For initiatives to solve organizational issues, the one big constraint is: Does it fit our vision of the <a href="https://www2.deloitte.com/us/en/insights/deloitte-review/issue-16/employee-engagement-strategies.html">company culture</a>? Just like with your product vision — you’ll want to think twice before implementing something that is not aligned with it.</p><p><strong>Example</strong>: Teams complain that they spend all their time performing maintenance, which they do not enjoy. Your product teams believe in a “you build it, you run it” culture. Consider these two solutions:</p><ul><li><em>Move maintenance to a specific team or another department.</em> While this would make the problem go away quickly, the solution is not a good cultural match.</li><li><em>Give teams the time needed to deliver high quality code in order to lower maintenance efforts in the future.</em> While the results can only be seen in the long run, it is aligned with the culture.</li></ul><h3>Pro Tip: Don’t copy your competition</h3><p>There are plenty of articles and frameworks about how to set up your teams to succeed. <a href="https://www.jeremiahlee.com/posts/failed-squad-goals/">Spotify model, anyone</a>? Just like in product work, it is good to be aware of what your competitors are doing, but not simply copy them. It’s even more dangerous for organizations than for products: A feature that does not fit your customer’s needs can be adopted or rolled back. Solutions to organizational problems often entail changing habits, which are a <a href="https://learningcenter.unc.edu/tips-and-tools/changing-habits/">tough thing to adjust</a>.</p><h3>Does it work?</h3><p>I’ve been trying the methods above for some months now, and we kicked off a handful of initiatives with clearly defined problem statements and OKRs. Those even made it on our internal quarterly roadmap, which we extended to also include organizational improvements. So far it’s looking good, but I’m sure there are plenty of other ways to approach this. I’d love to read “Solving Organizational Issues like a Presales Engineer”, “like a 3 Star Chef”, or “like the Tour Manager for a Punk Band” to discover how other teams and organizations are handling the aspects above.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f638a71a80e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s done! Or is it?]]></title>
            <link>https://medium.com/commercetools-tech/its-done-or-is-it-9fe91b9a6981?source=rss-fe61140b7dd0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fe91b9a6981</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Andrea Stubbe]]></dc:creator>
            <pubDate>Mon, 03 Feb 2020 15:48:29 GMT</pubDate>
            <atom:updated>2020-02-03T15:48:29.157Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S89gBM63qM-_kQ6wVHtBzw.png" /></figure><p>commercetools has been growing a lot lately, and we want to continue doing that. Not only do we have new product owners, UX experts and developers joining, we are also growing areas around the core platform teams. More sales, more training, more support, more marketing; in offices all around the world to support the growing product we’re making.</p><p>Being strong believers in independent teams, we thought about how we can ensure delivering a great product while:</p><ul><li>Minimizing disruption and interference with how the platform teams work</li><li>Simplifying collaboration for all the other departments that contribute to the <a href="https://medium.com/swlh/book-review-crossing-the-chasm-990e133fc733">whole product</a></li></ul><p>Our starting point to this is having a common Definition of Done (DoD) for features, which describes what has to be in place to call a feature “done”. And for the customer, a feature isn’t just about code that’s deployed, but the entire package. That can be all of the software’s inherent <strong>qualities</strong>, but also <strong>additional assets</strong> living next to it, like training material or documentation. Lastly, a feature is not done, if it will be a mess to <strong>maintain</strong> in the future.</p><p>Don’t confuse <em>done</em> in this context with <em>complete</em>. Most features start minimal and then keep evolving based on feedback and learnings. <em>Done</em> means: Whatever was defined is finished. And it’s good.</p><p>The common definition of done for features brings us three benefits:</p><ul><li>Alignment on everything that’s customer facing. Consistency in APIs, documentation, wording, UX, and knowing what to expect makes their work so much easier, and leaves them with a <a href="https://www.mckinsey.com/industries/retail/our-insights/the-three-cs-of-customer-satisfaction-consistency-consistency-consistency">warm and fuzzy feeling of trust</a>.</li><li>Helping colleagues to get their job done. Documentation, support and training, customer success and professional services, marketing — they all contribute to the product. In the end, how much is your feature worth if nobody talks about it, understands it, or recommends it in implementation projects? A Definition of Done is like a playbook for helping everyone understand what’s expected from them (and what they can expect).</li><li>Setting us up for sustainable development and growth. Coming up with a Definition of Done is a fairly straightforward task, but still surprisingly time consuming. Having a common DoD for all teams lets you focus on more fun things, and at the same time ensures we all do have a shared understanding of what is required for a feature to be “done”.</li></ul><blockquote><strong>How does this relate to a team’s own DoD?</strong></blockquote><blockquote>If a team has their own DoD (for stories, sprints, or whatever you want), it goes deeper into details on how to achieve certain things like beautiful code, or having no (known) bugs. A company wide Definition of Done is not there to replace any of the team’s DoDs, but supplements it with a focus purely on qualities and assets visible to the outside world (that is, not the team).</blockquote><h3>Qualities</h3><p><em>“Non-functional requirements are requirements, which, if not fulfilled, make your product non-functional.”</em></p><p>The software we build &amp; deploy has to be of good quality, to be useful. Those qualities are also called <em>non-functional requirements.</em> Making sure those are fulfilled is the responsibility of the platform teams. It’s the responsibility of the product owners to check the quality as part of accepting the story, but they can delegate to specific quality-checkers. Delegating makes a lot of sense for topics which require expert knowledge, such as security or legal requirements.</p><h3>Checklist</h3><ul><li>The feature solves the defined problem</li><li><a href="http://www.nishantverma.com/2010/03/test-case-paths-happy-sad-bad.html">Happy, sad and bad</a> cases work as they should</li><li>UX, design, and wording are consistent and good</li><li>APIs are consistent and good</li><li>Error messages are helpful and understandable</li><li>Performance is okay</li><li>No security and privacy issues</li><li>No negative impact on platform stability</li></ul><blockquote><strong>When is the best time?</strong></blockquote><blockquote>A common concept for security and privacy is to have those built-in, <a href="https://www.owasp.org/index.php/Security_by_Design_Principles">by design</a>, instead of as an afterthought. You can do the same for many other qualities: When defining the feature, you can think about performance implications, limits, API / user interface consistency and usability, architecture and modularisation, and all those things. Which is not to say you should come up with a fixed master plan before you start building, but it often does make sense to give those topics some thought. A similar approach is the Scrum-ish <a href="http://www.agilebuddha.com/agile/improve-sprint-throughput-with-definition-of-ready/">Definition of Ready</a>.</blockquote><h3>Assets</h3><p>Customers are not looking for the most beautiful commerce APIs, they are looking for a product to solve a problem they have. This includes support and documentation, training and consulting on implementation practices, and (obvious, but often forgotten) knowing the feature exists and is exactly what they need to help them out.</p><p>Taking care that all those things around a new feature are in place can be a bit tricky, because the people creating assets around a product feature aren’t always the ones who developed it. Being involved first-hand in feature development, product teams can help everyone a great deal — that includes giving input, answering questions, or even conducting internal training sessions. All that takes time, and it makes sense to see it as part of what you need to do, to get a feature “done”.</p><h3>Checklist</h3><ul><li>Release notes published on all channels</li><li>Documentation published or updated</li><li>Tutorials are published</li><li>Training material is updated</li><li>Professional services knows about the feature, and best practices for using it in projects</li><li>Support knows enough to support the new feature</li><li>Sales and marketing are aware and can explain the new functionality</li><li>Product marketing is aware and ready to evangelise the feature</li><li>Customer success is aware, can explain the new functionality and update specific customers that asked for it</li><li>Is it a good topic to blog or talk about? Do it!</li></ul><h3>Maintainability</h3><p>The last point that is covered in the feature DoD are not for customers, not for colleagues in other departments; they are for the teams. Taking care of those while still working on a feature makes work in the future easier and faster, and is an investment well worth the efforts.</p><h3>Checklist</h3><ul><li>Automated tests to notice when bugs sneak in later (regression tests)</li><li>Code is easy to understand and clean</li><li>Architecture is clean, especially modularity and dependencies</li><li>Logging / monitoring is in place</li><li>Documentation for on-call to know what to do when things break</li><li>Analytics for usage, performance, stability</li></ul><h3>Conclusion</h3><p>Sometimes it is better to be fast than perfect, and the benefits of going live with a new feature early outweigh the downside of not covering that one edge case, inconsistent UX, or documentation that’s still being updated. And that’s okay. The feature can still go live — just be transparent to your team and company that you’re not ‘done’ with work on it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fe91b9a6981" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commercetools-tech/its-done-or-is-it-9fe91b9a6981">It’s done! Or is it?</a> was originally published in <a href="https://medium.com/commercetools-tech">commercetools tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>