<?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 Mike Hutchinson on Medium]]></title>
        <description><![CDATA[Stories by Mike Hutchinson on Medium]]></description>
        <link>https://medium.com/@crikeymiles?source=rss-348af2fe9556------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fzRYxjU2B4ma18WQn6MmiA.jpeg</url>
            <title>Stories by Mike Hutchinson on Medium</title>
            <link>https://medium.com/@crikeymiles?source=rss-348af2fe9556------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:04:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@crikeymiles/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[5 Rules for Better Collaboration Within a Start-Up]]></title>
            <link>https://medium.com/@crikeymiles/5-rules-for-better-collaboration-within-a-start-up-c843847a29be?source=rss-348af2fe9556------2</link>
            <guid isPermaLink="false">https://medium.com/p/c843847a29be</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Mike Hutchinson]]></dc:creator>
            <pubDate>Fri, 27 Mar 2020 14:20:00 GMT</pubDate>
            <atom:updated>2020-03-27T14:51:16.423Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RhxDkFUVXk5_2QB-" /></figure><p>Collaboration is such a banal word. Since our first stumbling interviews as pimpled youths we have repeated the same tired phrases: “I work well in a team”, “I enjoy collaborating with teammates.”</p><p>The problem is that truly effective collaboration is HARD. It requires an intoxicating mix of empathy, subtlety, self-awareness, vulnerability, respect, trust and an openness and willingness to be wrong.</p><p>Most of us collaborate fine. When we are in a high pressure environment (such as a product team) collaborating on a highly uncertain domain (such as the creation of a new category like kidtech) being “fine” at collaboration isn’t good enough.</p><p>How do we become more awesome collaborators? How do we ensure that the intellectually difficult discussions do not become emotionally difficult as well? How can we extract the best from the smart people around us? How can we behave in a way that people <em>actively seek us out</em> to challenge their ideas and assumptions?</p><p>I have five rules:</p><ol><li><strong>Assume sanity</strong> — Assume everyone else is rational and sane, even when they appear not to be.</li><li><strong>Find the real question</strong> — Work to understand the mis-aligned assumptions which are making these rational and sane people temporarily appear to not be.</li><li><strong>Yes, and</strong> — Replace “no, but” with “yes, and” forevermore.</li><li><strong>Meet people’s need to be heard </strong>— and then they will be able to hear you.</li><li><strong>Assume positive intentions.</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LTT_CmtMQijBFRemoWaSXg.jpeg" /></figure><h3>Assume Sanity</h3><p>Open collaboration really relies on a simple principle: start any discussion from the standpoint that both of us are intelligent and logical. If the other person is advocating for a different solution than me, I assume that either they know something I do not, or I have some piece of information that is not yet available to them. Rational people tend to disagree only when an axiom differs between them. When I find myself in disagreement with you, I start by checking our underlying assumptions to find where they differ. I need to find out where you are coming from.</p><p>This doubly applies to very senior people, who often have context that is unavailable to us. One of the best pieces of advice I ever got for dealing with “crazy” founders and CEOs was to <strong>assume sanity</strong>. Founders and CEOs say mad-sounding stuff with distressing frequency. As a less experienced product manager, I made the dangerous assumption that this was because they didn’t have the detailed understanding of our product, our users, our processes or our data. Of course, I didn’t have the context that underpinned their thought-processes and once this context was revealed, the mad ravings of the founder often started to seem kind of logical. Always assume sanity and look for the misaligned underlying assumptions or missing context.</p><h3>Find the real question</h3><p>Sitcoms tell me that it is a theme in marriage counseling that “the argument is never about what you are arguing about.” This is a reasonable model to keep in mind when striving to build consensus and collaborate. If I can’t understand why you are proposing or defending something that seems illogical to me, then I don’t understand the assumptions or axioms that you are operating upon that make your point of view rational. Instead of arguing about the topic, let’s find out why we don’t agree by digging deeper.</p><p>“Why” remains the most powerful word in the English language. If I don’t understand why you are defending what appears to me to be an irrational position, I will ask why you believe this is the best way forward. What is the objective you are optimising for? What are you seeking to preserve or avoid? I am looking to <strong>find the real question</strong> that needs to be answered for us to move forward.</p><p>It could be as simple as me believing we are optimising for revenue growth and you for product adoption regardless of revenue. Perhaps I believe we are optimising for the scalability of the platform, and you for the satisfaction of our most strategic customers. Perhaps I believe we are optimising for rapid iteration, and you for protection of the user experience.</p><p>A key function of the product manager is to build consensus in order to drive the product forward. We can guide teams to find consensus through the illumination and resolution of these misaligned underlying assumptions. Once we identify the underlying question, we can resolve them with data, or agree a compromise, and move forward again as a team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wvUuDZ5kjqmCwT0C" /></figure><h3>Yes, and…</h3><p>The fastest way to put people at ease in an argument is to agree with them. In order to improve the effectiveness of our collaboration, resolve debates and move forward with predictable swiftness, we must find ways to ensure that everyone is heard, and feel like their point of view has been considered, even if it is ultimately rejected.</p><p>An extremely easy and powerful habit is to simply stop saying “no”. Even when you disagree. If you can stop yourself before saying “no” or “but” and instead find a way to phrase your point as “<strong>yes, and”</strong>, you will find people almost immediately collaborate more enthusiastically.</p><p>I have found the <a href="https://www.cleverism.com/scarf-model-influence-people/">SCARF Model</a> extremely interesting and valuable in making my own communication more effective and mindful at work. When we are negated, we experience a threat state, be it a threat to our status or to our autonomy. When we enter a threat state, we are neurologically less able to accept new ideas, so people are scientifically less likely to listen to your point of view if you start a sentence with “no”.</p><p>“Yes, and” is an open acceptance of the other person’s point, even if it is then followed by an explanation of why they are wrong. It says “I have heard and understand you. I accept and am considering your point of view, even as I present an adjacent or alternative position.” Welcoming and open language avoids engendering a threat state in the other person, and makes them more likely to hear you and explore your line of thinking.</p><h3>We need to be heard</h3><p>Have you ever had an experience in which you were desperate to say something? So desperate to say your thing that you are only listening for the opportunity to interject, not actually listening to what is being said?</p><p>When you fear that an upcoming discussion might become heated, there is a powerful technique you can use as a facilitator. Begin the discussion by giving each person a minute or so to summarise their position, objective or key concern. Do not allow anyone to interrupt, and interject yourself only to seek factual clarification if required. Give everyone an opportunity to say their piece and be heard, and you will often find the resulting discussion is much more collaborative, and less disrupted by individuals needing to be heard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZZx29Pete-L02m-i" /></figure><h3>Assume Positive Intentions</h3><p>While this is a post about collaboration at work, I actually think that improving our communication and collaboration skills everywhere is one of the things that can most positively impact your whole life experience. Please excuse a personal example to illustrate.</p><p>Vanessa and I met shortly before my twenty-first birthday. We endlessly enjoy each others’ company, but sometimes have trouble communicating. Recently, exhausted from our new baby, we fell into a mode of interaction which neither of us liked and neither of us knew how to debug. As we talked about it, one of the most impactful phases that we hit upon was to <strong>assume positive intentions</strong>.</p><p>This phrase has been transformational for me. Instead of assuming malice or criticism where none was intended, we try to hear each other’s words as they are. We try not to leap to conclusions about the thought process that lead to the comment, or invent a hidden double-meaning or unspoken criticism it contains. (As an aside, there is a wonderfully sarcastic self-help book called <a href="https://www.amazon.co.uk/gp/product/1626254060/ref=x_gr_w_bb_glide_sout?ie=UTF8&amp;tag=x_gr_w_bb_glide_sout-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=1626254060&amp;SubscriptionId=1MGPYB6YW3HWK55XCGG2"><em>How To Be Miserable: 40 Strategies You Already Use</em></a>, which has an utterly perfect 3 page chapter on this problem, entitled: “React To Their Motives, Not Their Messages”.)</p><p>When Vanessa asks a simple question such as “have the cats been fed?”, I might have leaped to a conclusion and reacted to an imagined criticism then wasn’t present in the comment. “Sorry, I just forgot to do it.” Instead, by assuming positive intentions, (Vanessa just wants to be sure the cats are happy), I respond differently: “Not yet. I’m happy to do it in 10 minutes when I finish this.”</p><p>I am very far from perfect, and the more tired I am the more I fall back into my old patterns. I don’t understand why my default unconscious pattern would be to assume malice and criticism, that is probably a question for a therapist. The important thing is to assume positive intentions. I try to keep this phrase in mind at all times, both at work and at home.</p><h3>Be More Awesome</h3><p>High-quality collaboration requires conscious effort. What’s weird is that by improving your collaboration, you actually become a better leader. You will be able to make better use of your superpowers. You will make other people’s days better. You might even be happier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c843847a29be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Daily Standups: 101]]></title>
            <link>https://medium.com/superawesome-engineering/daily-standups-101-7e4a648d2e6c?source=rss-348af2fe9556------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e4a648d2e6c</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Mike Hutchinson]]></dc:creator>
            <pubDate>Fri, 13 Mar 2020 14:57:49 GMT</pubDate>
            <atom:updated>2020-03-14T06:35:18.950Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lHorOSQpzlQbAF_OnNhuDA.jpeg" /></figure><p>For the last ten years, every single one of my working days has started the same way: with a <strong>daily standup</strong>. I love them. They are a fun and social start to the day, and a fantastic tool for keeping teams collaborating effectively and driving towards the same goals. Here’s how to do them.</p><h3>The Purpose</h3><p>The purpose of a daily standup is to create visibility and alignment among the team, to ensure we help each other to meet our immediate goals. It is not a status update meeting, although that is a partial side-effect of it. It is a quick huddle for the team, to start the day with some friendly human interaction, and to help us move forward together.</p><h3>Yesterday, Today, Blockers</h3><p>Running a standup is simple. Gather together, pick a facilitator, and get them to ask each member of the team, one at a time:</p><ol><li>What did you do <strong>yesterday</strong>?</li><li>What do you plan to do <strong>today</strong>?</li><li>Is anything <strong>blocking</strong> you from achieving what you plan to do today?</li></ol><p>I summarise this as (and frequently just point at people and say): “yesterday, today, blockers?”</p><p>We want to hear what you did yesterday, so we know where progress is being made (and therefore also where progress is not being made). We want to hear what you are planning to tackle or focus on today, so that we don’t duplicate efforts, or miss opportunities to collaborate. It also gives us a chance to commit to what we want to achieve today in front of the team, which can allow us better focus. I said I’d do it in front of the team, so I’d better do it!</p><p>The “blockers” part is really important. If you know that something is going to stop you from being able to tackle or complete what you need to today, the standup is the place to surface that and ask for help or guidance.</p><p>If the team doesn’t love the phrase “blockers”, then you can rephrase the third question as: “Do you need any <strong>help</strong> from anyone to get that done today?”</p><h3>Three Rules</h3><h4>1. Don’t skip it</h4><p>Do it every day. Get in the habit. There is no reason to skip it. If it takes three minutes and no further discussions are needed, great! At least the team knows where they are all at.</p><h4>2. Always do it at the same time every day</h4><p>We don’t wait for people. This isn’t a meeting that we wait until everyone is present for. Get into the habit of gathering and people can jog in late or catch up later if they miss the start. The standup cares not if you are late.</p><h4>3. Maximum of 15 minutes</h4><p>The standup should be no longer than 15 minutes. Under 10 minutes is even better. If it takes longer, check out some of the tips below, and make sure people are just focusing on the key questions: “yesterday, today, blockers”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SRapIvulV-v7VkqrjEMoPQ.jpeg" /></figure><h3>Five Tips</h3><h4>Schedule it</h4><p>Put a recurring meeting in everyone’s calendar. Turn the alerts on for it. Make sure it happens.</p><h4>Don’t solve it at standup</h4><p>The question “is anything blocking you” often reveals some complex and gnarly issue that doesn’t yet have a solution. The objective of the standup is to flush these sorts of issues out, rather than to solve them then and there.</p><p>If a detailed discussion starts, I will interrupt it and politely ask that the folks involved to catch up immediately after the standup to discuss it. That way we avoid the standup becoming a general “solve all the things” meeting, and running longer than 15 minutes. This is a tip, not a rule, sometimes a quick chat at standup can resolve the issue and unblock the team, and that’s perfect!</p><h4>Do it standing up</h4><p>It’s called a standup. If you are all standing up, the standup is guaranteed to be shorter. As soon as one person sits down, it turns into a thirty minute meeting. If I sit down, I expect you to call me on it!</p><h4>Do it in front of a “board”</h4><p>I have found that standups are much more effective when done in front of some kind of “board”. A key purpose of the standup is to maintain alignment. This is more easily done when everyone is looking at the same shared map of the current situation.</p><p>The board should have the “chunks” of work that people are focusing on, be that tasks, projects, customers, reports, documents or whatever you are tackling that day. It should show what is done this week, what is currently being worked on, and what is not. The stuff that is not currently being worked on should be in a priority order, so we know what is most important to tackle next.</p><p>The board could be in JIRA, or Trello, or a spreadsheet, or physical cards on the wall. The format isn’t important. The important thing is that everyone is looking at the same stuff, and we can have sensible and unambiguous conversations about the work we are doing, with less chance of mis-communication or crossed-wires.</p><p>If you are remote, and using Zoom or Teams or whatever, share your screen so everyone can see the board.</p><h4>Keep it light</h4><p>One lovely side-effect of starting the day with a standup is that we get to kick off the day connecting as people. We can laugh about the day yesterday, crack jokes about the current news or get our annoying commute or housemate off our chest. Let people be themselves.</p><p>Although you want to keep the standup short and punchy, I don’t believe you want to do that at the expense of having space to be natural and friendly together. This is triply true when you have remote teammates, as this may be the only time that day they get to interact with the whole team in a casual environment. Keep it light, start the day with a smile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HTavjdHFlUeREyzpUIRjhA.jpeg" /></figure><h3>Weekly Goals</h3><p>Something that goes extremely well with daily standups is having weekly (or sprint) goals. Weekly goals are a short, ordered list of the key outcomes you are trying to drive as a team. Essentially, at the start of the week (or sprint) you contract, as a team, to complete these specific goals. You then organise and prioritise your activities around ensuring you hit those goals.</p><p>At the daily standup, remind each other of the goals, or make them visible, and ask each other if there is anything currently blocking us from making progress towards those goals. If there is, we look for ways to help each other and collaborate to unblock progress.</p><h3>Get Up! Standup!</h3><p>A regular fixture of agile product teams, tons of teams in all kinds of industries and disciplines now use the standup as a way to ensure they are aligned and collaborating in their day-to-day hustle. If your team doesn’t use them yet, I really recommend you give them a shot!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e4a648d2e6c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/superawesome-engineering/daily-standups-101-7e4a648d2e6c">Daily Standups: 101</a> was originally published in <a href="https://medium.com/superawesome-engineering">SuperAwesome Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The One-Pizza Product Team]]></title>
            <link>https://medium.com/superawesome-engineering/the-one-pizza-product-team-92bf25c35162?source=rss-348af2fe9556------2</link>
            <guid isPermaLink="false">https://medium.com/p/92bf25c35162</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Mike Hutchinson]]></dc:creator>
            <pubDate>Thu, 12 Mar 2020 17:05:44 GMT</pubDate>
            <atom:updated>2020-03-13T09:50:38.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gZjKjjvp8ypCzz80EB3cyw.jpeg" /></figure><p><strong>How big should my product team be? </strong>We all know the answer to this question: if you can’t feed your product team with <a href="https://www.inc.com/justin-bariso/jeff-bezos-knows-how-to-run-a-meeting-here-are-his-three-simple-rules.html">two pizzas</a>, it’s too large. <a href="https://blog.nuclino.com/two-pizza-teams-the-science-behind-jeff-bezos-rule">Appetites vary</a>, but I believe it was meant to mean “about 5”. In this post, I argue that when you are innovating new products, you might be ordering too much food.</p><p>The “ideal” size of a product team depends on where the product is in its maturity lifecycle. In the innovation stage of product, you should have the smallest team possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AXlyBQMdaQQY0Ch5" /><figcaption>Accurate and precise drawing the product maturity lifecycle.</figcaption></figure><h3>Innovation At SuperAwesome</h3><p>SuperAwesome exists to make the internet safer for kids. To do this, we are defining an entirely new category: kidtech. There is no map for what “kidtech” is or what it does. Given that no-one knows exactly what kidtech products are supposed to do, or even what the scope of our category is, we have to experiment a lot. Discovering which opportunities could mature into scalable business models for us is critical, as is rapidly eliminating dead-ends.</p><p>For the record, kidtech is technology designed to enable kid-safe digital products by ensuring privacy and responsibility by design. If you want to know more about the principles that underpin kid-safe online products, check out the <a href="https://content.superawesome.com/kidtech">Kidtech Standard</a>, and please consider <a href="https://content.superawesome.com/kidtech#Contact">endorsing</a> it.</p><p>When innovating solutions to new problems, we need a team that is optimised for rapid iteration, high communication bandwidth and low inertia. We also want to remove as much “survival instinct” as we can, so that a product idea that isn’t working can be killed and the team work on something higher impact. Smaller teams are better on all these axes.</p><p>The team must be given a clear and measurable mission. They must be empowered to make day-to-day decisions about the best way to deliver against this mission. The first action of the new innovation team must be to establish it’s core KPI. (It might later prove to be the wrong KPI, but we ship, learn, and iterate.) At some point, its possible they are not making “enough” progress against the KPI, or that the product is “good enough” right now.</p><h3>Case Study: Kidsafe Social Video</h3><p>In 2018, we launched a new product, called <strong>Kidsafe Social Video</strong>. The initial idea for this product emerged from conversations with our customers. The product value proposition was first validated with a “<a href="https://link.medium.com/owQSyBQBw1">concierge</a>” prototype without writing a line of code. The early product got swift adoption, product/market fit was strongly validated, and of course our initial prototype couldn’t scale with customer demand.</p><p>We were able to validate the <a href="https://svpg.com/four-big-risks/">value risk</a> and product/market fit for our B2B solution with zero engineers. This isn’t possible in every situation, but it’s a dream when you can pull it off. We then needed to figure out the right technology needed to deliver on this product’s value proposition and strategic potential.</p><p>We formed a team of two engineers and a product manager to discover and rapidly iterate and innovative the right technical platform to support and accelerate the product’s growth. Our core KPI was initially set around accelerating our nascent operational function. Later, our KPI changed to focus on accelerating the speed at which we could expand the breadth of our offering.</p><h3>Innovation Requires Focus</h3><p>In the initial innovation stage of a product, I believe a good team size is two engineers and a product manager. Why do I think a team this small is a good idea? This is a very fragile size for a team. What if someone goes on holiday, has a baby or gets sick?</p><p>In a team this small, <strong>communication is extremely high-bandwidth</strong>. With only three people, the number of communication lines is minimised. Staying on the same page as each other is easy, reducing the number of miscommunications and bogus assumptions.</p><p>Faster communication means <strong>decision-making is faster</strong>, although not necessarily better. During the innovation phase, I would strongly argue that the speed of failure and learning is more important than the proportion of “correct” decisions.</p><p><strong>Appetite for risk is high</strong>, because the business <strong>impact of failure is low</strong>. The cost of the team is still small, so everyone can feel a little more aggressive without <a href="https://en.wikipedia.org/wiki/Loss_aversion">loss aversion bias</a> kicking in too hard.</p><p><strong>The team can’t multitask</strong> as they just don’t have the capacity. A team this size will struggle to work on more than one thing at a time. The inability to multi-task forces very strict prioritisation. As each item of work is prioritised, the team must ask: is this the piece of work that most directly helps answer our core question, as measured by our KPI?</p><p>For the same reason, the team can’t over-optimise their solutions. The team is simply not going to have the resources to do anything but under-engineer their solution. It will be wonky. It won’t be scalable. For the innovation and early discovery phase of a new product, these are valuable characteristics. <strong>Optimise too early and you are just taking longer to fail</strong>.</p><p>What if your product hypothesis is just too big to be tackled by such a small team? As Jason Fried <a href="https://m.signalvnoise.com/threes-company/">says</a>:</p><blockquote><em>We don’t throw more people at problems, we chisel problems down until they can be tackled by three people, at most.</em></blockquote><h3>Case Study: Kidsafe Filter</h3><p>The Kidsafe Filter is the part of SuperAwesome’s <a href="https://www.superawesome.com/awesomeads-for-advertisers/">AwesomeAds</a> platform that solves the problem of ensuring that <em>any</em> advert, even one that is designed to execute arbitrary client-side code, is completely unable to transmit or receive any personal data from kids. The first version of the product emerged from the crucible of our AwesomeAds product team. (AwesomeAds is a scaled product with a large-ish product team). Within the larger team, an innovation team formed of two engineers. The product management and product design was shared with the host team, but the backlog was somewhat separated.</p><p>It wasn’t clear initially if this would be the right strategy. We considered whether this work should just be a series of epics for the larger team, but the product needed sustained focus on an innovative new technology solution. They adopted a different rhythm to the larger team and were somewhat shielded from the day-to-day operational noise.</p><p>The core KPI for the team shifted over time, essentially following the classic journey of first make it work, then make it scale, then make it cheap.</p><p>The smaller team were able to focus and communicate internally extremely efficiently, testing and discarding technical approaches rapidly on their way to something valuable. After the innovation period, the team rejoined their host team to integrate and scale their nascent product as part of the wider AwesomeAds platform.</p><h3>Survival Instinct</h3><p>Let’s say you disagree with me. Two engineers is unacceptably fragile. It’s too slow. It’s too much at risk of disruption, disagreement or burn-out. Even in the early stages of a product’s innovation lifecycle we should be putting at least four or five engineers on a problem or we aren’t really trying. I don’t buy it. In my experience: the larger the team, the stronger the survival instinct, and the harder it is to fail fast.</p><p>Getting teams to recognise that their usefulness is over is tough. Social groups (and so product teams) <a href="https://www.ncbi.nlm.nih.gov/pubmed/10893943">naturally and unconsciously defend</a> their own existence.</p><p>If you have a brand new product idea and staff the team with five engineers from the start, I think you pretty much always get the answer that the product is worth pursuing, at least initially. The product rapidly builds an ant-hill around it. Unless your team is extremely disciplined about consulting their core KPI daily, a larger team will take more cycles than a smaller team to realise it has failed or succeeded.</p><p>In this larger team, team members will naturally divide up work and begin to specialise. Individuals will be less able to see the whole. Unable to perceive its whole as clearly, the team will be slower to recognise and acknowledge the end of its usefulness.</p><blockquote>Note: For the avoidance of doubt: “teams” here has absolutely nothing to do with “employees”. When a configuration of employees in a product team ceases to be valuable, the employees move onto the next exciting and high-value challenge. It is the team that disappears, not the employees.</blockquote><h3>Wider Context</h3><p>Ensuring teams can assess the value of their current work, within the wider context of the business, is really important. At SuperAwesome, our product teams have direct access to the P&amp;Ls for their product and others, as well as data about our customers adoption and spend across our product. This visibility allows us to provide autonomy with accountability, and with accountability comes the responsibility to make informed decisions to persevere, pivot or disband as makes sense from quarter to quarter and product by product.</p><p>We need to create product environments where everyone is aware of the holistic prioritisation landscape, is actively skeptical about whether what they are currently working on is the highest impact thing they could be doing, and has access to the data to answer that question.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R0Hvkrrt-U3YkNoz" /><figcaption>This article is sponsored by ice-cold fizzy drinks.</figcaption></figure><h3>Ordering Another Pizza</h3><p>Small product teams are awesome, but they aren’t right for every product and certainly not for every stage of a product’s lifecycle.</p><p>If the product begins to succeed, a team with two engineers is not sustainable for long. As the product discovery and technology innovation begins to head towards product/market fit and stable value generation, it’s time to order another pizza. I can’t tell you when that needs to be, but people will start to look hungry.</p><p>If deep tech innovation turns out to be the right solution to a problem, a team constrained by policy may never find that part of the discovery space, and pursue only those solutions that are feasible for them. This is going to depend a lot on your domain.</p><p>As with literally everything in product development, there is no one correct answer to anything. The point remains that keeping teams leaner than you are naturally comfortable with (without endangering the health and happiness of your team members) is a Good Thing.</p><p>If you want rapid and fearless innovation, I believe you should seek to have the smallest team you can. You also save money on pizza.</p><p><em>If you want to share a pizza or two with us while making the internet safer for kids: </em><a href="https://www.superawesome.com/careers/"><strong><em>we are hiring</em></strong></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92bf25c35162" width="1" height="1" alt=""><hr><p><a href="https://medium.com/superawesome-engineering/the-one-pizza-product-team-92bf25c35162">The One-Pizza Product Team</a> was originally published in <a href="https://medium.com/superawesome-engineering">SuperAwesome Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conditional Roadmaps: Product strategy in an emerging category]]></title>
            <link>https://medium.com/superawesome-engineering/conditional-roadmaps-product-strategy-in-an-emerging-category-fe3983dd0638?source=rss-348af2fe9556------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe3983dd0638</guid>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Mike Hutchinson]]></dc:creator>
            <pubDate>Thu, 30 Jan 2020 11:58:15 GMT</pubDate>
            <atom:updated>2020-01-30T15:20:14.444Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xSYorsyRnAGyjwia" /><figcaption>Photo by <a href="https://unsplash.com/@sebastian_unrau?utm_source=medium&amp;utm_medium=referral">Sebastian Unrau</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Dylan Collins on Twitter</h3><p>From @crikeymiles: &quot;Building products in an emerging category is a series of roadmap items, each surrounded by a conditional statement</p><p>SuperAwesome is <a href="https://techcrunch.com/2020/01/27/kidtech-startup-superawesome-raises-17m-with-strategic-investment-from-microsofts-m12-venture-fund/">a category-defining company</a>. That makes it both a fascinating and challenging place to be a product manager. Over the next few articles, I want to share some of my thoughts on how we approach product strategy in a category-defining product company.</p><p>At <a href="https://superawesome.com/">SuperAwesome</a>, we build kidtech. Kidtech exists to make the internet safer for kids by ensuring kid-safe digital products deliver privacy and responsibility by design. If you want to know more about the principles that underpin kid-safe online products, check out the <a href="https://content.superawesome.com/kidtech">Kidtech Standard</a>, and please consider <a href="https://content.superawesome.com/kidtech#Contact">endorsing</a> it.</p><p>Kidtech is an emerging category focused on enabling the internet for kids (who are now over 40% of new online users). We are not alone in attempting to solve kidtech problems, but it’s currently a pretty exclusive club. The kidtech space is still early, and because of this, there are <em>so many</em> problems to solve, and so many potential opportunities to pursue.</p><p>In defining the kidtech category, we need to be aware of where all these opportunities are, but as a product organisation, we know we cannot address them all. We need to eliminate some.</p><p>The problem is that we rarely receive clear signals from the market, as even when we identify our customers’ needs, quite often they don’t recognise them yet. This makes eliminating opportunities in our emerging category extremely difficult.</p><h3>Unrecognised needs</h3><p>SuperAwesome has a couple of superpowers. One of them is our product maturity cycle’s ability to discover our customer’s unrecognised needs.</p><p>When the phrase “unrecognised needs” <a href="https://theageofideas.com/the-unrecognized-need/">comes up</a>, it is normally accompanied by Henry Ford and Steve Jobs quotes. While we aren’t trying to drive adoption of the motor car as a replacement for the horse, or a touch-screen tricorder as a replacement for a Nokia 3310, we are trying to build an internet fit for kids atop an technical ecosystem built in near-total denial of the existence of children.</p><p>I will dig into our product maturity cycle in more detail in another blog post. In summary: we try hard to only build solutions to problems we ourselves are experiencing directly as an organisation, and only develop the solution into an enterprise platform once we are confident the solution works at scale for our business.</p><p>It’s not magic. We are able to recognise our customers’ needs before they do because we are operating a kids digital business and so encounter the same problems as them. We are actively looking for kidtech problems to solve and we have a strategy that priorities fixing them.</p><p>Unfortunately, discovering an unrecognised need doesn’t automatically mean your customer recognises it.</p><p>Another of our superpowers is our <a href="http://kidaware.com/">KidAware</a> program, which provides education about global kids digital privacy legislation, the challenges those laws present to brands and developers and how to address those challenges.</p><p>Education is critical for any product company that is looking to solve an unrecognised need. Before a category is well established, no-one understands what you are selling, or why. Customers don’t even know they have the problem you are solving. Today, everyone wants a touch-screen on their mobile phone, but <a href="https://svpg.com/customer-inspired-technology-enabled/">there was a point</a> where it was provable with science that we didn’t. We can’t force our customers to understand that they have a problem, but we can educate them about the problem space, and hope that they get there.</p><h3>Timing Matters</h3><p>When we initially built <a href="https://superawesome.com/kids-web-services">Kids Web Services</a>, our platform for obtaining verifiable parental consent to use kids personal data to drive personalised experiences, it was to support a consumer experience called <em>SwapIt</em> (RIP).</p><p><em>SwapIt</em> was like an Ebay for kids, allowing them to trade toys instead of buying and selling them. In order to enable the kids to post the toys to each other, we needed to collect their postal addresses. Because COPPA exists, in order to collect and share the kids’ postal addresses, we needed to involve their parents.</p><blockquote><em>Want to know more about COPPA and how to comply with it? Check out our </em><a href="https://www.kidaware.com/"><em>KidAware e-learning courses</em></a><em>.</em></blockquote><p>Based on our own first-hand experience, it was clear to us that providing kids with the kinds of deeply engaging and personalised online services that grown-ups enjoy would require a scaled consent platform that allowed developers to outsource the considerable legal and UX complexity of collecting verifiable parental consent (VPC). The trouble was, at the time we built the platform, very few other developers could see this. We had a solution to a problem we knew existed and others had, but signals were pretty strong: a developer-facing platform for obtaining VPC was not required by the market.</p><p>It was tough. We knew it was the market, not our solution, that was wrong. Heads were buried in the sand that couldn’t stay buried forever. We had experienced the problems of VPC first-hand, and we knew others would too, in time. Inevitably they did in 2018. Thanks GDPR-K!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yQOW9vSkjYXO8Bcd2Y1T5g.jpeg" /></figure><h3>Conditional Roadmaps</h3><p>I’m starting to see product strategy in a category-defining company as a series of roadmap items wrapped in conditional statements.</p><p><strong>When we identify an opportunity, we need to establish what the pre-conditions for success are.</strong> What assumptions underpin this value proposition being real. Do those conditions exist now?</p><p>If they do → let’s see if we can find a minimum valuable expression of the solution.</p><p>If they don’t → Are these conditions feasibly going to emerge in the next 2 years?</p><ul><li>No → Drop it, it’s not worth it.</li><li>Yes → Let’s wrap our product idea in some conditional statements and set about educating our sales team about the right questions to ask to keep us on the pulse, and when to send up a smoke signal that the conditions for life might be emerging.</li></ul><p>The structure of this thinking emerged from our adoption in the product team of “Opportunity Solution Trees”. You can <a href="https://www.producttalk.org/2019/12/adopting-opportunity-solution-trees/">read more</a> about SuperAwesome’s journey with this tool on Teresa Torres’ <a href="https://www.producttalk.org/2019/12/adopting-opportunity-solution-trees/">ProductTalk blog</a>. We analyse our product opportunities in terms of the assumptions that underpin them.</p><h3>A Strained “Trapper” Metaphor</h3><p>Perhaps this sounds like hedging our bets. I think of it more as preparing a “value trap”. Like some sort of hunter in the tangled forest of this emerging category: we scout out the terrain, identify key strategic choke-points, wait to see if a delicious-looking rabbit comes past. If it doesn’t, we set up a snare and make sure to find a way to be notified should a rabbit walk into it.</p><p>For us, this snare can take multiple forms. It might be a well-briefed sales team. It might be a good blog post. It might be an early but imagination-catching prototype.</p><p>What is critical is that we understand the assumptions or pre-conditions that underpin our product/market fit hypothesis, thoroughly ascertain their current validity of those assumptions in conversation with our customers and the market, and have a way to learn quickly if that bit flips</p><p>While we didn’t write it like this at the time, for Kids Web Services in 2016, the conditional roadmap item looked something like this:</p><blockquote>If</blockquote><blockquote>{ regulatory and PR pressure is significant enough for game developers to feel that ignoring kids in their games is an unacceptable business risk }</blockquote><blockquote>then</blockquote><blockquote>{ game developers will want an parental consent management solution }</blockquote><p>When we built the first version of <a href="https://superawesome.com/kids-web-services">Kids Web Services</a>, this conditional statement wasn’t true. The product was good, but the market wasn’t ready yet. We mothballed the product. The snare was set. 18 months later, this conditional statement flipped to true. The trap was sprung and the tarpaulin was pulled off the product.</p><p>To continue our hunting metaphor (I live in the UK, I have literally never hunted anything) education is like beating sticks on the bushes, driving the rabbits before us, hopefully into the snares.</p><h3>Schrödinger’s Roadmap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nOv0wA7bnKqn9fkh" /><figcaption>Photo by <a href="https://unsplash.com/@tobiastu?utm_source=medium&amp;utm_medium=referral">Tobias Tullius</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>These value traps could be seen as bets, but I think that they are something different in actuality. They are opportunities whose ultimate viability is uncertain but known to be in the future.</p><p>Perhaps the practice of constructing a visionary product strategy in an emerging category is an exercise in defining those value propositions you understand to be your market’s unrecognised needs, defining the assumptions about those customers or the market conditions that must be true in order for product/market fit to be credibly possible, and then wrapping your roadmap item in a conditional statement.</p><h3>Strategy or Indecision?</h3><p>But wait: isn’t this just me weedling out of making the hard decisions that it is my job to make as a product leader? Fail fast! Kill your darlings!</p><p>As a product manager, it is very difficult to kill a product when the reason you don’t have product/market fit is that the target market hasn’t realised they have the problem you solve. It’s senseless. It’s excruciating to flush value down the drain just because the philistines have yet to see the light. You can either waste the energy you’ve spent by killing the product, or waste more energy by continuing to work on a product that doesn’t have a market (yet). Is there a third option?</p><p>As a product leader, you must be user and customer-centric, data-driven and decisive. But you must also be highly strategic, and (dare we say it) visionary.</p><p>As a product leader, those around us expect and require a level of certainty from us. We are tasked with relentlessly pursuing product/market fit and ruthlessly killing our darlings when they fail to find it.</p><p>When our answer to “is this product viable?” is “maybe, I’m sort of waiting to see,” then our CEO will rightly be suspicious about whether or not we are just hedging our bets to avoid having to make a hard decision. As product leaders, we are expected to be decisive.</p><p>In terms of our product roadmap, we don’t say: “we will solve for X in Q3” (when we have no way to know if the condition for life will have emerged by then) , or “we’ll reassess X in Q4 with our customers” (when the problem could suddenly become much more important earlier). Instead we say: “we will regularly ask our customers about X. If our currently invalidated pre-conditions change, then we will reassess the priority of solving for X for our customers at that time.” Establishing the methods to frequently test for these pre-conditions and discover when the light goes green is probably something for a later post.</p><p>I’m starting to see product strategy in a category-defining company as an exercise in creating traps for value, placing them smartly, and waiting for them to go off. For the avoidance of doubt, I do not advocate setting bear-traps in the woods for your customers.</p><blockquote><em>Want to join the hunting party and make the internet safer for kids? </em><a href="https://superawesome.com/careers"><em>We are hiring</em></a><em>!</em></blockquote><p><em>Originally published at </em><a href="https://www.superawesome.com/2020/01/30/conditional-roadmaps-how-we-approach-product-strategy-in-the-emerging-category-of-kidtech/"><em>https://www.superawesome.com</em></a><em> on January 30, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe3983dd0638" width="1" height="1" alt=""><hr><p><a href="https://medium.com/superawesome-engineering/conditional-roadmaps-product-strategy-in-an-emerging-category-fe3983dd0638">Conditional Roadmaps: Product strategy in an emerging category</a> was originally published in <a href="https://medium.com/superawesome-engineering">SuperAwesome Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to find the biggest possible question — Part Two]]></title>
            <link>https://medium.com/superawesome-engineering/how-to-find-the-biggest-possible-question-part-two-f40e7e3b5abf?source=rss-348af2fe9556------2</link>
            <guid isPermaLink="false">https://medium.com/p/f40e7e3b5abf</guid>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Mike Hutchinson]]></dc:creator>
            <pubDate>Tue, 13 Aug 2019 18:54:53 GMT</pubDate>
            <atom:updated>2019-08-19T08:58:39.344Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sd1OsdSPn7Au2EN0NwZoWw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@dulgier?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Anastasia Dulgier</a> on <a href="https://unsplash.com/search/photos/star-globe?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>How to find the biggest possible question — Part Two</h3><h3>Finding Your North Star</h3><p>If you are a product person, you will know that the question you are asked most, by pretty much everyone in the company, including every member of your own team, is “what is the vision for our product?” If you are a product person, you will also know what a deep and profound ambiguity often surrounds the answer to that question. It depends on <em>so</em> <em>many</em> things.</p><p>As product people, we have to be extremely comfortable with ambiguity. At the same time, we have to see ambiguity as a call to action to begin analysis and discovery. We must seek to eliminate ambiguity where we can, and yet remain comfortable that we will always be drowning in the stuff.</p><p>At <a href="https://www.superawesome.com/">SuperAwesome</a>, our mission is to <strong>make the internet safer for kids</strong>. We do this by becoming in all aspects of global kids digital privacy law and rigorously applying it to everything we do to ensure we truly live the values of privacy by design and responsibility by design.</p><p>Making the internet safer for kids is a HUGE job. There are just so many interesting problems to tackle. We are drowning in interesting problems we could be tackling. Like many other teams, picking the right things to focus on is the hardest part of our job, day-to-day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GyPvamPbcdJML8BM4BbJqA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jerry_318?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jerry Wang</a> on <a href="https://unsplash.com/collections/4697687/work/b2e74dc5b3413066e28246a57c88a0af?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>A key ingredient in providing this focus is a strong vision for the team. Without getting side-tracked with a discussion of what constitutes a strong product vision, I want to share one technique that I use when I feel particularly beset by uncertainty.</p><p>When I find myself in a particularly thick pea-soup of uncertainty, I often use a simplified version of Scenario Planning to sketch out a map of the surrounding terrain and start making headway again. In my previous article, I showed how to go from a blank piece of paper to a list of your most uncertain and impactful unknowns. In this article, we will use those key uncertainties to sketch out a number of alternative futures, each of which might be your north star.</p><h3>Alternative Futures</h3><p>In Part One of this article, <a href="https://medium.com/superawesome-engineering/how-to-find-the-biggest-possible-question-part-one-1cc6da5c9216">Scenario Planning For Everyone</a>, we defined the topic we wanted to explore and generated an array of “axes of uncertainty” to put structure around the mess of questions that unpin our core problem. Here’s where we got to last time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*67oiS8wjAqkHGV6B" /><figcaption>Our axes of uncertainty from the first article</figcaption></figure><p>Here’s what we do next.</p><h4>1. Choose Two Candidate Axes</h4><p>Choose two of your key uncertainties. It doesn’t really matter which two at first. Stand one of them on end and make a quadrant with them. (I mentioned before that everything in product management is a quadrant, right?). Label each end of the X/Y axis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/1*1XqC9sKODCRrxyss6dd-GQ@2x.jpeg" /></figure><p><em>Should we be a video chat thing or an image broadcast thing, etc.</em></p><h4>2. Plot Your Competition</h4><p>Look at the quadrants you have created. In each quadrant is a kind of business or product that you might focus on being. Think about an obvious competitor. Where do they sit on this graph? Plot them. Do another. We are creating a map of other people’s north stars.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/276/1*29h9Dhs3H7uH4Eh2ffjYcA@2x.jpeg" /></figure><h4>3. Try Another Couple of Axes</h4><p>You likely have a few key uncertainties. Combine them in different ways to make more graphs and experiment plotting your competition again:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*s92UyN2UR57sNPgwSGrOFw@2x.jpeg" /></figure><h4>4. Plot Your Future Selves</h4><p>Put your product or company logo in one of the far corners. That could be you. Is that where you want to be? Try a few other locations. What does your product or business do in each of these cases? These are your Alternative Futures. Presumably, you could be any of these futures. Some will be harder than others. All will require compromises. You can’t be everything. What will you be?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*lakLsyk3MmwNecIHqtQRSw@2x.jpeg" /></figure><p>I find this visualisation, when done well, to be extremely powerful for both the product team and for its senior stakeholders. It boils down a very broad set of uncertainties to a key question: <strong>where do we want to be on this graph?</strong></p><h4>5. Name your Scenarios</h4><p>To bring them to life, and give your team and your stakeholders a shared language, I try to give each alternative future a cute name. In our example, we might have:</p><p>A) Unitato.TV</p><p>B) Chat ‘n’ Watch</p><p>C) Twitch-a-sketch</p><p>D) Draw With Friends</p><p>E) BingeStreak</p><p>These named futures could represent products or business you are or want to become. They aren’t literally, they are just future scenarios that you can make reference to in discussions. Some might become warning signs. If you feel you are heading away from your north star you can tell a story about what you might become instead, and that can be a useful framing device. There are also jumping-off points for more analysis, either through an examination of the hypothesis that underpins their value, or the pre-conditions that must unfold for those futures to become true.</p><h3>How to find the biggest possible question</h3><p>At the end of this <a href="https://medium.com/superawesome-engineering/how-to-find-the-biggest-possible-question-part-one-1cc6da5c9216">pair of exercises</a>, you should have gone from a deeply ambiguous and foggy question to a clear set of questions and areas to focus on next. You have some candidates for north stars and a way of explaining those candidates to team-mates.</p><p>If you have been successful, you’ll have created a new quadrant diagram (I told you everything in product management is quadrants), and you can now ask: <strong>where do I want to be on this graph?</strong></p><p>You won’t learn everything you need to know about your product or business strategy from this exercise, but I guarantee you’ll feel more confident and purposeful after it.</p><p>As I try to navigate through the sea of opportunities we have at SuperAwesome in making the internet safer for kids, I find it very valuable to have tools like scenario planning in my toolbox, and I hope you can find a use for it in your product analysis work.</p><p><em>If you have enjoyed these two articles, you oughta know that </em><a href="https://www.superawesome.com/careers/"><em>we are hiring</em></a><em>! If you want to work with a world-class product and engineering team making the internet safer for kids, click </em><a href="https://www.superawesome.com/careers/"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f40e7e3b5abf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/superawesome-engineering/how-to-find-the-biggest-possible-question-part-two-f40e7e3b5abf">How to find the biggest possible question — Part Two</a> was originally published in <a href="https://medium.com/superawesome-engineering">SuperAwesome Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to find the biggest possible question — Part One]]></title>
            <link>https://medium.com/superawesome-engineering/how-to-find-the-biggest-possible-question-part-one-1cc6da5c9216?source=rss-348af2fe9556------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cc6da5c9216</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Mike Hutchinson]]></dc:creator>
            <pubDate>Tue, 13 Aug 2019 18:54:42 GMT</pubDate>
            <atom:updated>2019-08-14T09:37:43.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xw--P2Ic08QyLAfW-Sa_Tw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kylejglenn?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kyle Glenn</a> on <a href="https://unsplash.com/search/photos/global?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>How to find the biggest possible question — Part One</h3><h3>Scenario Planning For Everyone</h3><p>Working for <a href="https://www.superawesome.com/">SuperAwesome</a> is a real privilege for me. We are pushing out into unexplored territory, attempting to define a whole <a href="https://medium.com/superawesome/5-product-development-challenges-of-building-a-new-category-c43b5d95abc1">new category</a>. The business of creating awesome products is always riddled with uncertainty and the path forward is almost never clear. Never is this truer than when you are leading the charge and have no one else mapping the terrain ahead of you.</p><p>As we attempt to tackle questions of kids privacy in the digital media ecosystem, and how to <strong>make the internet safer for kids</strong>, we find ourselves needing tools to help address big strategic questions and–in many cases–find out what the right question even is. In this pair of articles, I outline one of my favourite techniques for dealing with high-level uncertainty and then iterating towards a tangible vision to guide your product teams.</p><p>Scenario Planning is a well-established strategic analysis technique. It was invented by military intelligence, and businessitized by Shell in the 1960s. Shell’s version is the sort of grandiose thing you need when you are sitting atop the natural fortunes of the Earth and are big enough to have to factor the movement of tectonic plates into your long-term business planning.</p><p>With that provenance, it seems like an unlikely tool for a regular product manager in a small technology company to need to employ. This is not helped by <a href="https://www.penguinrandomhouse.com/books/574940/scenario-planning-in-organizations-by-thomas-j-chermack/9781605094137/">the literature</a>, which gives the impression of an extremely time-intensive and detailed business analysis process, requiring multiple days at a minimum.</p><p>This is a shame, as lurking at the heart of the Scenario Planning process is an incredibly elegant and endlessly applicable tool for reducing uncertainty in, well, anything really.</p><p>When engaged in product management in a category-defining company like SuperAwesome, I find the Scenario Planning tool is fantastic for rapidly exploring the “fog of war” around a particular product or strategic question. The process allows me to quickly identify and sweep aside the things I know (or feel strongly about) and highlight the things I don’t feel confident about yet. It’s a great tool for illuminating areas in which I need to do more discovery, and for forming hypotheses to guide the next experiments.</p><p>The best thing? You can do all of this inside an hour (I’ve even done it in ten minutes when pushed!)</p><p>The full Scenario Planning process employs many different exercises; I like to use two of them. I call the first part of the exercise “Key Uncertainties” and the second part “Alternatives Futures”.</p><p>By the end of the first part of the exercise, you should have a clearer view of what you do and don’t know about your topic. By the end of the second, you should have an impactful visualisation of your possible paths to success.</p><h3>Key Uncertainties</h3><p>We can’t know the future. Often, we don’t even know what it is going to be the cause for success or failure. We rarely even know what possible causes for success or failure lie in front of us. Scenario Planning suggests that if we can imagine and categorise our key uncertainties, we can create scenarios and plans for them. By doing this, we can make strategic decisions now that reduce the risk of the most impactful uncertainties turning against us.</p><p>Everything in product management is a quadrant. Here’s another:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FFip_7mA_x1kP6Q6" /></figure><p>This first part of the scenario planning process is looking for questions to which the answer really matters to the success or direct of the product or company, and which are extremely uncertain: either because they are currently unclear or because they are very much outside our control. The questions whose answers are high impact and highly uncertain are our Key Uncertainties, and we sure as h*ck want to know about them.</p><p>When I feel that there are too many unanswered questions surrounding my product, I use this “Key Uncertainties” exercise as a method to reduce uncertainty, and more clearly discover and state my remaining key uncertainties.</p><h3>1. Choose Your Topic</h3><p>Getting started is as easy as posing a question. What’s the big question you want to address? Write it at the top of a whiteboard, or a big sheet of paper.</p><p>In the past, I have run the exercise on topics like:</p><ul><li><strong>Business strategy</strong>: <em>e.g. What kind of business should we strive to be in 5 years’ time?</em></li><li><strong>Customer definition</strong>:<em> e.g. Who are our key customer personas?</em></li><li><strong>Product strategy</strong>: <em>e.g. Should our product remain B2B or offer a lightweight B2C version?</em></li><li><strong>Product definition</strong>: <em>e.g. What is this new product going to offer users to delight them?</em></li></ul><p>For this article, I’m going to explore the question “What do kids want in a social experience”, which is a real example of a time when I used this technique at SuperAwesome to explore and reduce the uncertainty around a key product question we had at the time.</p><p>Write the topic at the top of a piece of paper or whiteboard:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8tRjn6q-qJmpwO2q" /><figcaption>A big question.</figcaption></figure><p>We want to jump straight to user testing to figure out from the users directly, but the problem space is too vast. If we want to <a href="https://hackernoon.com/the-mvp-is-dead-long-live-the-rat-233d5d16ab02">test our riskiest assumption</a>, we have to discover what our assumptions even are.</p><h3>2. Identify Your Uncertainties</h3><p>Next, start expressing questions about your topic as little spectrums. What are you unsure about? Ask: are we X or Y? Are we more THIS or THAT? Draw a line, write THIS at one end and THAT at the other. The answer is rarely black and white, hence drawing the questions as axes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cX2S61VnM3aAp-NG" /><figcaption>Uncertainties</figcaption></figure><p>Do it fast. Don’t get hung up on whether the poles of your axes are actually binary or whether you are duplicating questions. Ask as many questions as you can about your topic and draw them all as axes.</p><p>You should quickly end up with a page filled with uncertainties. Do we build things or buy things? Do we care more about growing revenue or users right now? Do we want our users to invent stuff of remix things? Should we go global or just stay focused on a local market? Should we be amazing in one thing or generalists across a range of connected things?</p><p>I find this part of the process both fun and cathartic. A chance to take all your secret worries and spread them all out in plain view.</p><p>As the brainstorm starts to lose speed. Access the axes you have and look for proxies and clues to other hidden questions. As an example, you might have a wordy axis that asks:</p><ul><li><em>“we provide value to our customers by integrating the best tech ←→ we build unique tech that is easy to integrate”.</em></li></ul><p>We might try to break in up into simpler axes:</p><ul><li><em>Integrate ←→ Innovate</em></li><li><em>Systems Integrator ←→ Supplier</em></li><li><em>Turnkey ←→ Specialists</em></li></ul><p>You are looking for opportunities to restate or simplify axes in a way that hopefully reveals lower-level questions that provide more granularity.</p><p>Similarly, there is likely to be axes that are actually proxies for something else more fundamental. Here, you are just looking for opportunities to restate or simplify axes in a way that reveals the high-level questions provide more strategic context.</p><p>Essentially, you are looking at each axis a second time and asking: what other uncertainties does that dichotomy suggest?</p><p>An example might be:</p><ul><li><em>Great documentation ←→ No need for documentation</em></li></ul><p>This is an interesting question, but it perhaps suggests a deeper uncertainty about what success truly feels like to you. Perhaps this axis is actually a proxy for something like:</p><ul><li><em>We focus on powerful features ←→ We focus on ease of use</em></li></ul><p>If you find more fundamental axes, write them down.</p><h3>3. Calibrate</h3><p>You should now have a ton of little horizontal axes. Look at them all, like slides on a giant mixing board for our problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iFyqcL7BAC1Pc5r1" /><figcaption><a href="https://www.pexels.com/photo/black-disc-jockey-music-pad-159206/"><em>More cowbell</em></a><em>.</em></figcaption></figure><p>Now, we start mixing.</p><p>Pick any axis at random. Draw a dot on the line at the point you believe most accurately defines how your product, customers or company either fits or wants to fit with the question. This is the little knob of your mixing slider for this uncertainty.</p><p>If you find you can’t easily pick the right spot on your axis for the dot, that’s great! You might just have found one of your Key Uncertainties! (More on these in a moment).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*osvGJI9jVYf34fpb" /><figcaption>Calibration</figcaption></figure><p>If it is pretty obvious to you where on the spectrum your little control knob should be for this question, that’s great too! You have found something that you ACTUALLY KNOW. Draw the dot in the right place and never worry about this question again. You just eliminated some uncertainty from your life.</p><p>I find this part of the process exhilarating. You can see the shape of your problem being revealed, as the terrain behind the fog of war. On each axis, you either discover something specific you need to know more about or something that you realise you’ve known all along.</p><h3>4. Prune and De-dupe Proxies</h3><p>The next step is to reduce the noise, in search of our most uncertain questions. We start crossing out axes. We are going to:</p><ol><li>Cross out any duplicate axes. Just keep the best phrased one.</li><li>Cross out every axis you were able to calibrate. These are low uncertainty.</li><li>Cross out any axes that you actually don’t care about the answer to. These are low impact.</li></ol><p>By the end, the picture might look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BCDD_hcg-VieCU-H" /><figcaption>Pruning</figcaption></figure><p>To get here, we look across the axes with a critical eye.</p><p>There will be axes that are duplications of each other. Perhaps something was important, so the brainstorm returned to it several times. One will be phrased best, so choose that, or write a better one to summarise the different versions. Cross out the duplicates.</p><p>There will be axes that, on second look, aren’t that important. The answer to the question they pose doesn’t really matter in a big way. You don’t really care what the answer is. These are of low impact. Cross them out.</p><p>By now. you should have a bucketload of uncertainties. Most of which have been crossed out. The ones that remain are candidates for our Key Uncertainties. Your Key Uncertainties are the fundamental questions that underpin the whole topic. If you knew (or could agree) the correct calibration of those Key Uncertainties, you could confidently orient your team, your customers or your company towards that as a <a href="https://medium.com/superawesome-engineering/how-to-find-the-biggest-possible-question-part-two-f40e7e3b5abf">north star</a>.</p><p>At this point, let’s clear the whiteboard and re-draw what we know so far:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mYsmIBAUSeupcWcW" /></figure><p>In the example above, I have summarised those axes that I was able to confidentially calibrate. These are my knowns. I feel confident that these assumptions hold water. I don’t have to worry about these right now, they are swept to the side of my analysis space, leaving me to focus on my key uncertainties, on the right.</p><p><em>At this point, a fresh cup of coffee is well earned. In </em><a href="https://medium.com/superawesome-engineering/how-to-find-the-biggest-possible-question-part-two-f40e7e3b5abf?postPublishedType=repub"><em>Part Two</em></a><em>, I’ll show you how to take these Key Uncertainties and create a focused set of Alternative Futures, (our “scenario”) in a simple visual that will make you look like you have Your. Shit. Together.</em></p><p><strong>&gt;&gt;&gt; </strong><a href="https://medium.com/superawesome-engineering/how-to-find-the-biggest-possible-question-part-two-f40e7e3b5abf"><strong>Turn to Part Two</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cc6da5c9216" width="1" height="1" alt=""><hr><p><a href="https://medium.com/superawesome-engineering/how-to-find-the-biggest-possible-question-part-one-1cc6da5c9216">How to find the biggest possible question — Part One</a> was originally published in <a href="https://medium.com/superawesome-engineering">SuperAwesome Engineering</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 implemented kid-safe analytics with Amplitude]]></title>
            <link>https://medium.com/superawesome-engineering/how-we-implemented-kid-safe-analytics-with-amplitude-e1d923ab953d?source=rss-348af2fe9556------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1d923ab953d</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[kidtech]]></category>
            <category><![CDATA[kids]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Mike Hutchinson]]></dc:creator>
            <pubDate>Fri, 31 May 2019 14:06:51 GMT</pubDate>
            <atom:updated>2019-06-03T09:01:01.182Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WgEjs5MOgZkCekwpRl8Aww.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@patrickian4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Patrick Fore</a> on <a href="https://unsplash.com/collections/4697687/work/b2e74dc5b3413066e28246a57c88a0af?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><a href="https://www.popjam.com/">PopJam</a> is a social platform that is <a href="https://www.superawesome.com/popjam">built from the ground</a> up to be safe, appropriate and fully anonymous for kids. It’s a safe, moderated community for kids to engage with their favourite content and brands, designed specifically for the safety and data privacy requirements (COPPA, GDPR-K) of the under-13 audience. Because it is aimed at an audience of 7–12 year olds, we take both privacy and compliance extremely seriously.</p><p>A critical concern for any platform is the product analytics you use to measure and learn. This is never a trivial thing to get right. Deciding what to measure, and how, requires careful thought, but at least you have a massive array of products and solutions to choose from, often with fully-featured SDKs to make implementation quicker and easier.</p><p>Not so in the kids digital ecosystem.</p><p>When making apps for kids you have an additional set of concerns and constraints. Were you to simply plug in an off-the-shelf analytics SDK, you would very likely find that analytics SDK broadcasting personally identifying data (as defined by COPPA) from your client application and recording it server side. This is standard for analytics platforms made for the grown-up internet and enables those platforms to provide richer insights, such as geographical heat-mapping. However, this is something we take every precaution to avoid across the PopJam platform, be it web or mobile, as a stand-alone product or embedded in customers’ products.</p><p>As you consider your options in this space, allow me to reflect on the journey we went through on PopJam, to illustrate a couple of possible approaches.</p><h3>Roll Your Own</h3><p>We all know the cheap/fast/good triangle. In the PopJam team, we started with a solution that we rolled ourselves. We span up an <a href="https://aws.amazon.com/redshift/">Amazon Redshift</a> database, put the open source query runner <a href="https://redash.io/">Re:Dash</a> over the top and got to work on defining and implementing our own analytics event infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*NvOYDPZMRV80XX4N" /></figure><p>We created our own client-side SDKs to broadcast product analytics events to our own analytics API, making certain not to pass any data that could be used to identify or fingerprint the user. Our events service then carefully discarded any remaining PII, such as the IP address and user agent in the request and wrote the event into a raw database for overnight processing.</p><p>We then painstakingly constructed our ETLs, analyst schemas and metric definitions by hand in raw SQL, using Re:Dash to schedule and run those queries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EJx7YPjeEF_NCGL6" /></figure><p>Initially, it seemed like a great solution. Cheap (built on open source and internally-build tools), fast (we controlled the scope and the roadmap) and good (we knew it was compliant, and we had full visibility and control over our data). However, it didn’t take long for the cracks to appear.</p><h3>Not So Cheap</h3><p>While relatively cheap to run, from an infrastructure point of view, it was far from cheap to operate and maintain. Our overnight batch jobs, Redshift, Re:Dash, all proved to be somewhat unstable, and days a month of our tech lead’s time were lost to restarting, debugging, recovering lost data, responding to disgruntled business users and generally keeping the product analytics alive. When it failed, all kinds of business functions were affected, as we had built things like campaign reporting, community management dashboards and marketing attribution on top of the data in it.</p><p>It also took a ton of time from our product managers, who had to build every metric, graph, dashboard, reporting tool and query manually, learning as they went. Mistakes were made, which in turn took more time to undo.</p><h3>Opportunity Cost</h3><p>All this effort was not just time-consuming, not to mention frustrating for the team, it also represented a huge opportunity cost. With our product manager sometimes spending two whole days a week arms-deep in SQL, they were less able to focus on the job of discovering an awesome product. Questions raised during discovery took much longer to answer, further slowing the iteration cycle, and often we did not have the skills to be able to fully answer our own questions, having to fall back on simpler analysis instead.</p><p>In addition, any improvements we wanted to make to our analytics, analysis or visualisation toolkit would require prioritisation within our backlog. We were getting nothing over time unless we put the grunt in. No-one was moving us forward if we weren’t.</p><h3>Not Good Enough</h3><p>While Re:Dash worked tolerably well, there were a few downsides, even beyond the reliability (which very likely could have been resolved if we had prioritised the time to invest in it). Our key problem was our reliable on our own statistical analysis and query crafting skills within the team. The product manager (me!) was not a data scientist. We didn’t have a dedicated data analyst in the business.</p><p>While we were able to self-serve on the basics, and do a reasonable amount of discovery within the data, there was a universe of more advanced analytics techniques and approaches that were closed to us. We needed an analytics platform that could actually lift us up, above our own skills, and supercharge our ability to truly understand what our data was telling us about our users and customers use of the PopJam platform.</p><h3>Levelling Up</h3><p>As we started to push more frequently against the limits of our skills, we went in search of some experts who might have the solution to our problem. We knew that more advanced solutions existed, as many of us had used them in previous roles. We needed richer insights to continue to improve our product development process.</p><p>We tried a few different analytics platforms before selecting <a href="http://amplitude.com/">Amplitude</a>. We were blown away by their user interface, which was totally dedicated to product development. The Amplitude platform contained a host of incredibly powerful and easy to use analytics tools that we just had no practical way of making ourselves in our previous solution.</p><p>One of the most impactful improvements was the ability to <a href="https://amplitude.zendesk.com/hc/en-us/articles/231881448-Behavioral-Cohorts">define cohorts</a> from any data point, using <a href="https://amplitude.zendesk.com/hc/en-us/articles/236032527-Amplitude-2-0-Microscope">Microscope</a>. As well as giving the product team the ability to easily dig down to understand the behavior of those users that (for example) comment most regularly and see what else they do, the marketing team were also able to make immediate use of this feature to understand how engaged a cohort of users that joined as a result of a particular marketing campaign were, and asses if that tactic brought in the “right” kind of kid.</p><p>Another tool that we could not have dedicated the time to create ourselves is <a href="https://amplitude.zendesk.com/hc/en-us/articles/360020765372-Impact-Analysis">Impact Analysis</a>. Using this analysis tool we were able to reveal and explore the hypothesis that encountering and enjoying a personality quiz early on in your PopJam journey has a big impact on how you perceive the product and how much you go on to engage and retain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TmUS3BOAWJEMEtYy" /></figure><h3>Migration</h3><p>Migration to Amplitude was simple. We kept our existing kid-safe events pipeline, and client code, but piped all the events from our events service into Amplitude via their HTTP API. This ensured that we remained in full control of what data leaves (or more importantly doesn’t leave) the kid’s device. We continued to use our bespoke client SDKs, rather than Amplitude’s client SDKs, as this kept us in full control of the data leaving the child’s device. We maintained our event service, which served to ensure (a) we remained de-coupled from any specific analytics platform, and (b) we were in full control of the privacy of data prior to piping it to Amplitude.</p><p>The result was that we could get all the benefits of Amplitude’s powerful front-end tools with full confidence that Amplitude contained absolutely zero personally identifying data from our users.</p><p>While more expensive than our previous solution, we have reclaimed focus on our ability to innovate and iterate our products and platforms, which is invaluable.</p><h3>Kid-safe Analytics</h3><p>The toolset we have now is light years ahead of what we were able to achieve internally, in terms of analytical sophistication, provided a depth of insight and guidance for product iteration that we would never have got anywhere near to. The team and the business trust the numbers now. We have rolled Amplitude out across multiple non-product teams in SuperAwesome because the UI is intuitive and non-threatening (goodbye SQL!).</p><p>Scarlett Cayford, Head of PopJam, heads up a team of strategists, designers and ad operations executives, all of whom regularly use Amplitude to analyse data in different areas of PopJam.</p><p>“While our own set of tools were workable, it meant we were restricted in what we could measure and were completely reliant on the product managers to build out new queries. Amplitude is simple enough that we can construct our own queries, and breaking out that data into different time frames and geographical regions is extremely simple. The adoption of Amplitude gave us autonomy as well as authority and has enabled us to react much faster.”</p><p>Moving from an internally-developed, open source based analytics solution to <a href="http://amplitude.com/">Amplitude</a> was a great choice for us. We were able to find a setup that allowed us to use Amplitude in a way that continued to protect the data privacy of our under-13 users whilst giving us a sophisticated toolset for understanding how our product is used.</p><p>We don’t worry about analytics anymore. We get constant improvements to our tools and new capabilities because there is a whole other business thinking about that problem-space. We no longer have to be experts in a domain that has nothing to do with making the internet safer for kids.</p><p><strong>If you’re interested in staying on top of technology and kidtech news, we publish several kids industry </strong><a href="https://content.superawesome.com/superawesome-newsletter-sign-up"><strong>newsletters</strong></a><strong> which now have over 10k subscribers reading monthly. </strong><a href="https://content.superawesome.com/superawesome-newsletter-sign-up"><strong>Sign up now</strong></a><strong>!</strong></p><p><a href="https://www.linkedin.com/in/crikeymiles/?originalSubdomain=uk">Mike Hutchinson</a> is Chief Product Officer at SuperAwesome</p><p><em>Originally published at </em><a href="https://blog.superawesome.com/2019/05/31/how-we-implemented-kid-safe-analytics-with-amplitude/"><em>https://blog.superawesome.com</em></a><em> on May 31, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1d923ab953d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/superawesome-engineering/how-we-implemented-kid-safe-analytics-with-amplitude-e1d923ab953d">How we implemented kid-safe analytics with Amplitude</a> was originally published in <a href="https://medium.com/superawesome-engineering">SuperAwesome Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Regaining Focus: Moving to an iPad Pro Full-time]]></title>
            <link>https://medium.com/@crikeymiles/regaining-focus-moving-to-an-ipad-pro-full-time-8686385d52ff?source=rss-348af2fe9556------2</link>
            <guid isPermaLink="false">https://medium.com/p/8686385d52ff</guid>
            <category><![CDATA[ipad-pro]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Mike Hutchinson]]></dc:creator>
            <pubDate>Tue, 28 May 2019 11:28:16 GMT</pubDate>
            <atom:updated>2019-05-28T14:37:50.785Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X-ggMAvnQh_J5xHpveWnQA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/QEShRYXOs60?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daniel Korpai</a> on <a href="https://unsplash.com/collections/4697687/work/b2e74dc5b3413066e28246a57c88a0af?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Can you use an iPad Pro as your main computer? Can replace your laptop completely, and move to iOS full-time? Is this inevitable? Are the days of desktop operating systems numbered?</p><p>I’m about a week into my experiment to shift to an iPad Pro full-time. I’ve had to open my MacBook three times since I started, and one of those times it turned out to be Barclaycard’s website that was done, not the iPad playing up. I have a 2019 12.3” iPad Pro with the Apple keyboard case and the Apple Pencil.</p><h4>The Good</h4><p>I’m going to be honest here. The only reason I’m trying this whole thing is that: The. New. Apple. Macbook. Keyboards. Suck.</p><p>I loved my MacBook Air keyboard. That thing is a total joy. The keys have individual space to themselves. The arrow keys are sensibly laid out. There is no hideous touchbar to accidentally pause the song that’s playing every time you type the number 8. It doesn’t double-fire a’s and s’s constantly, and its. keys don’t get stuck in auto-fire loops that force me to hard reset my laptop twice a day. Grr.</p><p>That start of this journey was the search for a keyboard that doesn’t make me want to throw my computer out of the window, but having begun, I am quite interested to see how viable this full-time shift to mobile computing is in 2019.</p><p>The <a href="https://www.apple.com/uk/shop/ipad/ipad-accessories/keyboards">Apple keyboard case</a> isn’t too bad. I dared not risk moving to an iPad Pro without trying the keyboard, and so I went to the Covent Garden Apple Store (I work just round the corner) and spent about 20mins with one. It’s not too bad. A bit squidgy, but nothing like a bad as the MacBook Pro keyboards. The keys get enough space to themselves and they feel like that move a bit when you hit them. I tried out another keyboard case whilst I was there, a Logitech, and preferred the Apple one. It’s not bad.</p><p>The next stage in my search for keyboard nirvana is to see whether a massive and loud mechanical keyboard is the solution can be made to play nicely with the iPad. I’m considering a <a href="https://www.razer.com/gb-en/gaming-keyboards-keypads/razer-blackwidow-elite">Razer Blackwidow Elite</a>, which has a piece of (Windows-only) software that would allow me to re-map the CMD and ALT keys, as now Mac user should have to endure an ALT button next to the spacebar. I’ll need to find a setup that brings the iPad as close as possible, to reduce the distance I have to move to poke the screen.</p><h4>The Bad</h4><p>I mentioned above, in the first week of this experiment I have had to scuttle back to my MacBook Pro twice for real. The first time was to work on a pivot table in Google sheets. The Google Sheets app is a total joke, unfortunately. It’s basic in the extreme and the combination of missing features and very weak keyboard support make it practically unusable. Due to the limitations of Safari, it’s not possible to use the browser version on iPad, so you are stuck with the sucky app version. God it’s terrible. Apple Numbers is no better. I need to try Microsoft Excel next.</p><p>The lack of a “real” Photoshop is also pretty limiting. Apparently, an iOS version of Photoshop is <a href="https://www.theverge.com/2019/5/14/18623055/adobe-photoshop-ipad-creative-cloud-beta-test-applications">in the pipeline</a>, and I’m very much looking forward to trying that. There are a host of little apps from Adobe, but the lack of support for nudging things around using the arrow keys is very hampering. Initially, not having a sensible image processing workflow was a pain, but I just figured out how to do what I wanted using Apple’s amazing Shortcuts app. I think I have a lot more to explore with that app.</p><h4>The Meh</h4><p>The Apple Pencil. I dunno. I can’t see the point of it (boom). It’s just a pain in the ass to hold it in your hand while typing, and simply more comfortable (and just as accurate) to give the screen a quick poke with your finger.</p><p>I’ve used it a bit while doing fiddling graphical things, like LucidChart and <a href="https://itunes.apple.com/gb/app/adobe-photoshop-mix-cut-out-combine-create/id885271158?mt=8">Photoshop Mix</a> (I’m actually finding <a href="https://itunes.apple.com/us/app/vectornator/id1219074514?mt=8">Vectornator</a> to be more fun), but in 90% of cases, it’s more awkward to hold it and type at the same time, and I didn’t abandon my trackpad to have to pick up a damn pencil everything I want to “move the mouse”.</p><p>Always, it stores itself on the side of the iPad, so it always falls off when I put my iPad in my rucksack. If I had my time again, I’d probably (probably…) save my money. Jury’s still out a bit, I might yet find my groove with it.</p><h4>The Awkward</h4><p>A slight niggle with the Google Docs app is the lack of control over styles and paragraph spacing. As I’m a bit of a “clean typography” nerd, (one of the reasons I enjoy typing in <a href="https://itunes.apple.com/us/app/bear/id1016366447?mt=8">Bear</a>, as I’m doing now), I find a calming effect of having good line spacing and chunky paragraph spacing. It seems to give words space to settle and room to place them. I dunno. It works for me.</p><p>One of my rituals at the start of composing a new Google Doc is to set-up my styles how I like them. I really wish Google Docs provided the ability to set defaults for this. Because I can’t do this, I had to find a workaround. As with a couple of things in this journey, finding the “workaround” seems to have actually led me to a workflow optimisation, leaving me better off than when I started…</p><p>I dug out a recent Google Doc with my styling set up just how I like it, and I made a copy. I deleted all the content and renamed it “Mike’s Template”. Now, when I want to start a new document, I search for “template” and click “make a copy”. I get a blank document and as soon as I start typing, everything is laid out beautifully. I no longer spend the first 4mins of a new document poking around the line spacing settings. Win!</p><p>The Google Calendar app is a fail for me. Predominately, this is done to a single missing feature: I cannot “find a time” by looking at everyone’s calendars in one view. This feature is totally essential if you don’t want to be a calendar douche, and splat meeting invites over the top of other people’s already-booked slots. Happily, the mobile browser version of Google Calendar has this feature and has no problems of any kind, so I’m using that. The only niggle is the mental tick of having to open my browser to view my calendar when literally everything else on my iPad is a dedicated app.</p><h4>The New</h4><p>Honestly, I thought losing the trackpad was going to be the killer here. I dumped my mouse in 2011 when I got a MacBook Air, and I’ve never looked back. I love the fact that my hands have barely left the keyboard for eight years, and the trackpad felt so natural and nearby that I really thought the change to having to lift my hands from the keyboard to poke the touchscreen was going to drive me barmy.</p><p>In fact, an odd thing happened. Not only did my brain instantly and seamlessly make the transition, when I did bounce back onto my laptop to check how a backup was processing, I was actually *annoyed* when I had to reach for the trackpad. This was after just 48 with the iPad. It was a totally natural shift, and I think one of the things I’m enjoying the most (along with the much nicely keyboard, and the newly enforced rigour in my personal workflow).</p><p>Documents by Readdle is pretty neat. I made the switch to a purely online file system three years ago, with all my files in Dropbox, all my documents in Google Drive, and (the most recent addition to my workflow) all my notes in Bear.</p><p><a href="https://itunes.apple.com/gb/app/documents-by-readdle/id364901807?mt=8">Documents by Readdle</a> provides a centralised view on most of my cloud files. It’s not perfect. It’s not able to launch documents from Drive in Google Docs oddly, it opens them as read-only in a webview, which really limits it’s potential and means I still have to use the Google Drive app. This niggle means I can’t use it as the single launch pad for my work, rather it provides something else. A sort of psychological safety blanket. I can see all my files in one place. I can refresh my mental model of where all my work is. It’s harder to feel lost and disorientated, which I think is a genuine hurdle one needs to overcome making this transition away from a desktop operating system. With Readdle’s Documents app at my side, I can feel calm that, should I lose something, I can find it again.</p><h4>The Surprising</h4><p>The most obvious “down-side” of working on iOS is the reduced ability to multitask. You can’t have tons of windows open and move information between them, or refer to them, as easily. You can work in split screen, and have a sort of floating overlay thing that you can swipe in and out, but I’m still getting the hang of it.</p><p>Oddly, I’m starting to feel that this restriction is actually the most powerful and positive aspect of the move to iPad.</p><p>The fact it is more difficult to multitask combo’s really nicely with the lack of distracting toolbars and status bars and other random shit to make an extremely uncluttered and focused working environment. I have disabled all my notifications, pretty much (and certainly all the interruptive banners). When I am in Bear, or in Google Docs, or in Google Slides, there’s nowhere else to go. Nothing is winking in the corner of my eye. Even the clock is tiny and hard to see. It’s amazing. I’m less distracted than I’ve ever been.</p><p>It’s harder to multi-task, so I find myself actually having to finish things before I move on. There are fewer distractions, so I don’t context switch as often. It’s great!</p><p>Along with less “unintended” context switching, it’s also physically more difficult to flick between open applications and work on three things at once. You can do it, but it doesn’t feel right. As it is less easy to context switch and return, I’ve had to adopt a “hub and spoke” mental model, returning to an anchor point which links out to work. Right now, that anchor point is a Trello board. When I’m lost, I flick back to Trello and find out what my top priority was. I crack on, finish that, and then archive the card. Next job.</p><p>The fact you can’t see all the other windows and applications I’ve got open appears to have forced me to be more disciplined about my process, which is a very surprising side-effect.</p><h4>Week One</h4><p>One week in and I’m pretty happy. I have only encountered one real blocking problem (with spreadsheets). Outside of that, I can do my whole job on an iPad, and I’ll be damned if I’m not actually more productive on this thing, thanks to all the weird new approaches I’ve had to develop.</p><p>As a benchmark, I now have zero browser tabs open multiple times a day, which is absolutely unheard of for me prior to now. It turns out all those open tabs were either a task to complete or a thing to read later and now they end up in Trello or Pocket inside.</p><p>There are niggles, no question, but the more I get into this, the more I wonder what the fundamental advantages of a desktop operating system really are. Will I really miss my local file system? Will I really miss my window frames, taskbars and endless visual distractions?</p><p>I’m excited to find out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8686385d52ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning from Demoing]]></title>
            <link>https://medium.com/planet-smasher-games/learning-from-demoing-18f7eeeaa524?source=rss-348af2fe9556------2</link>
            <guid isPermaLink="false">https://medium.com/p/18f7eeeaa524</guid>
            <category><![CDATA[games-design]]></category>
            <category><![CDATA[tabletop-gaming]]></category>
            <category><![CDATA[gasland]]></category>
            <category><![CDATA[miniature-wargaming]]></category>
            <dc:creator><![CDATA[Mike Hutchinson]]></dc:creator>
            <pubDate>Tue, 28 May 2019 09:40:55 GMT</pubDate>
            <atom:updated>2019-05-28T11:33:28.707Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*trVzFE3PbrZxI5MKjFbEyg.jpeg" /><figcaption><em>Photo by </em><a href="https://unsplash.com/photos/UGdjUaYkwH0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Victor Xok</em></a><em> on </em><a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Unsplash</em></a></figcaption></figure><p>I’ve probably demoed <em>Gaslands</em> to two hundred people at this point. After demoing the game that many times, you get a very strong sense of what order to present and explain its concepts to potential players to show them the best of the game as quickly as possible.</p><p>The objective of the demo is to hook the audience in with something exciting, then get them up and running on their own as quickly as possible. As situations emerge on the tabletop, you get the chance to introduce additional concepts or rules. The hope is that they are having some measure of fun by that point and are invested enough to want to listen to the next rule. Ideally, by the end of the demo, they are actively asking about the deepest or most complex parts of your rules and delighted to find they exist.</p><p>This is very linked to the “ <a href="https://gaslands.com/progressive-sophistication/">progressive complexity</a> “ approach I explored in a previous article, but at the demo table, you get a chance for very immediate and visible qualitative feedback on whether your ordering of concepts is working. Get it right, they buy the book and the dice, get it wrong, they don’t.</p><h3>Don’t Push It</h3><p>As an example, during a player’s first activation, I will explain the different faces on the skid dice. I will rarely mention the “Push It” rule at this point. I will let the players experience the peril and triumph of the skid dice first, then the first time a player rolls a really unfortunate set of skid dice results I introduce the “Push It” rule. They already understand why resolving skid dice well matters, experience a moment of panic and peril when they realise the dice have turned against them, and then a moment of delight when I give them a way to escape this peril.</p><p>This contextualises the rule in a way that makes this rule seem intuitive and exciting, rather than fiddly and unnecessary complexity, which it might have felt like if I had explained it before the players even knew how the cars moved on the table. It’s also much more likely that the player will remember the rule in future, and indeed come away from the demo with a sense of excitement about the game.</p><h3>You Didn’t Tell Me That!?</h3><p>For many years now, I have been the “rules explainer” in whatever board game group I end up in. I like collecting games, and so am often the person bringing the game to the table. I’ve learnt from years of explaining board games that a 20min pre-game rules explanation is like fun-poison to me, and I actively disregard games that I can’t figure out how to just “get going” with at the table. (I will never be the guy bringing Eclipse to your house.</p><p>Quite often, people get annoyed that I didn’t explain such-and-such tiny rule before we started (I would have done my turn totally differently!”), but I mostly think they wouldn’t have enjoyed a 20min upfront rules dump, and I bet they wouldn’t have remembered the rule anyway, until they’d seen it in context and why it mattered. I guess this experience has carried over into demoing at conventions, and the question is why I never really used it as a structuring device for the rulebook!</p><p>Collisions is another good example. I never describe these rules before the game starts, even if someone asks. I will only talk through those rules the first time a collision happens. Sometimes players need to know those rules on the first or second activation of the game (seriously, what is it with you people!?) but often everyone is getting used to the movement system and can go a gear phase or two without one.</p><h3>Explaining Gaslands, Mark II</h3><p>With the progressive sophistication structuring pattern, the lessons learned from demoing the game become valuable editing hints. I know now that I can hold back rules like Push It and collisions until the rulebook has explained how to drive in a straight line, change gear and machine-gun someone.</p><p>The act of demoing the game has taught me which parts of the game you need to know immediately to get moving, and which parts are secondary to the initial buzz of excitement needed to get you hooked. It’s going to be interesting to see how well this translates on to the page. At the worst, it’ll at least be different…</p><p><em>Originally published at </em><a href="https://gaslands.com/learning-from-demoing/"><em>https://gaslands.com</em></a><em> on May 28, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18f7eeeaa524" width="1" height="1" alt=""><hr><p><a href="https://medium.com/planet-smasher-games/learning-from-demoing-18f7eeeaa524">Learning from Demoing</a> was originally published in <a href="https://medium.com/planet-smasher-games">Planet Smasher Games</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 overcome location bias when brainstorming with remote teams]]></title>
            <link>https://medium.com/superawesome-engineering/how-we-overcome-location-bias-when-brainstorming-with-remote-teams-21f3721fc27c?source=rss-348af2fe9556------2</link>
            <guid isPermaLink="false">https://medium.com/p/21f3721fc27c</guid>
            <category><![CDATA[location-bias]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Mike Hutchinson]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 15:08:46 GMT</pubDate>
            <atom:updated>2020-03-13T06:55:19.935Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ibnfzRqKjE7XC3iXJ_oaA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/26MJGnCM0Wc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kaleidico</a> on <a href="https://unsplash.com/collections/4697687/work/b2e74dc5b3413066e28246a57c88a0af?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Whiteboarding and brainstorming when you are working from home</h3><p>Working at <a href="https://www.superawesome.com/">SuperAwesome</a> often means working with super talented people based thousands of miles away from you (we have offices in London, NYC, Chicago and LA, as well as joint ventures in Singapore, Australia and LatAm). We try to remove location bias in all that we do, but it’s not always easy, especially in the context of meetings and brainstorms.</p><p>Different teams and different product managers have different ways of approaching these issues, but all agree that a degree of visualisation is key to success. If you can’t see it, you can’t understand it. And if you don’t all have access to the same whiteboard with post-its and pens, then you need to find a digital way to whiteboard.</p><p>In this piece, our Chief Product Officer, <a href="https://medium.com/@crikeymiles">Mike Hutchinson</a>, and Product Manager for Kids Social, <a href="https://medium.com/@blainejoubert">Blaine Joubert</a>, explain which tools they use when whiteboarding to bring their concepts to life for remote teams.</p><h3>Mike</h3><p>I run a lot of collaborative sessions with team members in different offices. I’m always surprised when I tell people we are going to use Google Slides as our digital whiteboard and their eyes widen. I don’t feel like this is a revelatory idea, but if I must play the part of Blake and bring visions of product management heaven to the worthy, so be it.</p><h4>The Big Idea</h4><p>If you are planning any sort of collaborative meeting or workshop, with either internal or external folks, as you create the meeting invite you should also create a new Google Slides document. Set it to “Anyone with the link can edit”. Copy the link into the meeting invite, saying something like “Digital whiteboard link here”.</p><h4>The Set-Up: Google Presentation</h4><p>Preparation is everything. If you go into the meeting with your methodology all mapped out, your team will fall into utilising your methods much more smoothly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DOihMcSWgLpJEoKP" /></figure><h4>Make the canvas really big</h4><p>Go into File &gt; Page Setup and make the paper really big. If I’m doing something epic, like a user story map (thanks for teaching me those, Blaine) I’ll use 130&quot; x 60&quot;. For something more modest, I’ll maybe use 40&quot; x 25&quot;.</p><p>You’ll have to make font sizes a little bigger, but this will make everything easier to manage.</p><h4>Learn the keyboard shortcuts</h4><p>I won’t lie, moving around a big canvas in Google Sheets is a pain, particularly if you are used to a sensible product that expects you to scroll around.</p><p>There are some canvas zooming keyboard shortcuts hidden in the menus that make life less painful. You’ll want to get familiar with Alt+Cmd+”+” and Alt+Cmd+”-”.</p><h4>Make a couple of pre-styled post-it notes</h4><p>A few moments of preparation before the workshop is all it takes. Find the shape that is a box with a corner clipped off. Make it a nice pastel yellow colour. Orange outline. Change the font size. Choose a cheesy marker pen font. I swear, ten minutes into the workshop, people will have totally tuned out the fact that the post-it notes aren’t physical.</p><h4>Alt + Drag things to duplicate them</h4><p>This is the fastest way to fling post-its across your digital whiteboard. Select a post-it note or three, hold down the “ALT” (PC) or “OPTION” (Mac) key and drag. It will be duplicated rather than moved, and this trick will speed you up a lot.</p><p>Before anyone flames me: yes. There are MUCH better tools that Google Slides for this task. You can look at InVision, Figma, RealtimeBoards, and loads more. But you know what? Google Slides is free, works fine, and everyone already knows how to use it.</p><p><a href="https://docs.google.com/presentation/d/15MDxFyrmSzdo-3C4mnyrL_JpR5OZDZ_UaKXnPXDoW4U/edit#slide=id.g3c2529e154_8_6">Here’s</a> a template you are free to borrow. Click “make a copy” to have it.</p><h3>Blaine</h3><p>On my team, we’ve started experimenting with other products, including <a href="https://realtimeboard.com/">Miro</a> (formally RealTimeBoards).</p><p>To get the most out of a virtual whiteboard, one thing I’ve learned is to spend time before the workshop outlining a basic skeleton of ideas as post-it notes. Never start with a blank canvas and just ask people for ideas.</p><p>Once the end-to-end skeleton is created it’s very easy for the team to jump into the verticals. Send the link around, and everyone can connect to the virtual whiteboard and start throwing their own post-it notes in. The benefit of having a virtual whiteboard is that it’s easy to just pick up where you left off without having to get everyone back into the same meeting room and hoping no one has removed your post-it notes.</p><h4>Dot Voting</h4><p>Once you have your ideas down, Miro has a great feature for traditional dot voting. You click the thumbs up icon, select the area of notes and allocate votes per person and a time limit. Once time is up it will show you the top ideas. This anonymous voting really helps to remove “in the room” bias and gives everyone an equal say in ideas we want to prioritise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/591/0*1gZLwyMlzTqeKvfA" /></figure><h4>Effort VS Value</h4><p>There are many ways to prioritise ideas but as a starting point, we like to use a simple effort vs value matrix to quickly remove unrealistic ideas, which is easily achieved in Miro.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/649/0*1o4VUh_A6AjK25zf" /></figure><p>Miro has many pre-made templates for common product needs; for example, we love using user story maps to really flesh out our prioritised ideas into shippable MVPs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/0*ZwbNccaz73b_JiaO" /></figure><h4>JIRA integrations</h4><p>Once our MVPs are set up and agreed upon, Miro has useful add-ons like JIRA integrations which allow teams to replace user story cards with JIRA tickets that then automatically update when tickets are closed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/0*OZoXJhagVhmGOMyJ" /><figcaption>Mike: “Man, this is so much swisher than my Google Slides…”</figcaption></figure><h4>Wireframing</h4><p>We have even gone as far as using Miro’s whiteboards to collaboratively wireframe future products. Miro has some premade wireframe kits to rapidly sketch out ideas:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/0*5fcra6Qy_2A3vQPs" /></figure><p>With the exception of fridge magnets, if you can do it on a physical whiteboard, then you do it in Miro. Miro really seems to have you covered in all aspects of the product life-cycle and we are even starting to add moodboards and finished designs so we have an end-to-end virtual project war room.</p><h3>How do you whiteboard?</h3><p>With all the templates and shortcuts it’s actually more efficient for us to run virtual whiteboarding sessions rather than physical ones now.</p><p>Have you got your own methodologies for holding remote whiteboarding sessions? Or anything at all that helps remove location bias when trying to ideate the early stages of a project? We’d love to hear them.</p><p>If you want to whiteboard remotely with Mike or Blaine, check out our <a href="https://www.superawesome.com/careers">open jobs</a>!</p><p><strong>If you’re interested in staying on top of technology and kidtech news, we publish several kids industry </strong><a href="https://content.superawesome.com/superawesome-newsletter-sign-up"><strong>newsletters</strong></a><strong> which now have over 10k subscribers reading monthly. </strong><a href="https://content.superawesome.com/superawesome-newsletter-sign-up"><strong>Sign up now</strong></a><strong>!</strong></p><p><a href="https://www.linkedin.com/in/crikeymiles/?originalSubdomain=uk">Mike Hutchinson</a> is Chief Product Officer at SuperAwesome, while <a href="https://www.linkedin.com/in/blainejoubert/?originalSubdomain=uk">Blaine Joubert</a> is Product Manager for Kids Social.</p><p><em>Originally published at </em><a href="https://blog.superawesome.com/2019/04/24/how-we-overcome-location-bias-when-brainstorming-with-remote-teams/"><em>https://blog.superawesome.com</em></a><em> on April 24, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21f3721fc27c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/superawesome-engineering/how-we-overcome-location-bias-when-brainstorming-with-remote-teams-21f3721fc27c">How we overcome location bias when brainstorming with remote teams</a> was originally published in <a href="https://medium.com/superawesome-engineering">SuperAwesome Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>