<?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 Megan Williams on Medium]]></title>
        <description><![CDATA[Stories by Megan Williams on Medium]]></description>
        <link>https://medium.com/@meggywil?source=rss-fcd39695741c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-WSfUcTor9DrxnK7.</url>
            <title>Stories by Megan Williams on Medium</title>
            <link>https://medium.com/@meggywil?source=rss-fcd39695741c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:51:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@meggywil/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[Understanding problems till we’re blue in the face]]></title>
            <link>https://medium.com/@meggywil/understanding-problems-till-were-blue-in-the-face-69c7b243609e?source=rss-fcd39695741c------2</link>
            <guid isPermaLink="false">https://medium.com/p/69c7b243609e</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[problem-definition]]></category>
            <dc:creator><![CDATA[Megan Williams]]></dc:creator>
            <pubDate>Tue, 05 May 2020 11:32:04 GMT</pubDate>
            <atom:updated>2020-05-05T19:56:30.396Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TyZEj6n3fse0EWIc272R1Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@epicantus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daria Nepriakhina</a> on <a href="https://unsplash.com/s/photos/problem?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>Understanding gnarly problems</strong></h3><p>“If I had an hour to solve a problem I’d spend 55 minutes thinking about the problem and five minutes thinking about solutions.” — Einstein</p><p>Sometimes in our work we come across problems that have been hanging around for a long time. Decades in fact. People think “that’s just the way it is here.” We’ve tried some things, and they haven’t stuck. We muddle on. We live with it, like a stone in our shoe. It’s difficult, we work around it, it’s in the too hard basket. And when pushed, we quickly jump to what we think will be the easiest way to solve it, from a limited tally of possible solutions, and from our own limited view of the problem. Do what we have always done. Adopt our pet ‘go to.’ A website. A toolkit. A how to guide. A site champion. We get tunnel vision.</p><p>I know because I’ve been in teams making all of these things at some stage in my career. But often, this doesn’t really cut through the problem — it’s a temporary solution, a band-aid if you will. Alternatively, we ignore the problem and hope it goes away. Thinking someone else will deal with it. Seldom it does. Through adopting either of these mindsets, we could be further entrenching this problem for years and generations to come.</p><p>My dear friend, if you are like me and are in this situation, you have no doubt uncovered one of the gnarlier problems — a systemic problem in fact. This problem needs untangling with some different ways of thinking. The great scientist Albert Einstein believed the quality of the solution you generate is in direct proportion to your ability to identify the problem you hope to solve. But is design more than just understanding intellectually a problem? It is also about learning by doing, testing and trialling things to understand.</p><p>Our job as service designers is to firstly seize that problem and wrestle it to the ground. It’s been around for years, decades — so don’t be deceived. If it was easy, it would have been solved by now. Do your problem justice. Size it up. Examine it’s many facets through talking to people outside your organisation. Use techniques that unpack and iterate your problem definition throughout your piece of work. Describe it, and test your definition. If your problem is gnarly, ensure that when you are designing your approach — account for slightly more of your time here, in problem definition than you might normally.</p><p>Then, apply different frames to solving it. And people in our organisation, who like to rush in with their off the cuff, tried and true ideas, would do well to stop, and suspend judgement. Hold up the hand, accompanied by a “whoa nelly.” Allow a creative response to emerge. Allow for a moment that feeling of lack of control. That eeiry feeling that you might not have the entire answer to this annoying, and stubborn problem. Embrace the pregnant moment of opportunity.</p><p>Then, try some new different techniques for solving the problem. There is a technique for creative problem solving in service design called <a href="https://www.designkit.org/methods">analogous situations</a>. This means looking around at what other industry might have a similar problem, (an industry unlike, and dissimilar from your industry) and seeing how they solve it. This may throw up completely different ways of solving it, that you may never thought of.</p><p>You may of course meet with resistance if you suggest doing this. Many people believe that their own industry knows the answers fair and square. How would others understand? They haven’t had to deal with X, or Y, like us here? This is a common fear response to the unknown. You think to yourself, how did design suddenly become confrontational? Evangelical even?</p><p>Or you can reframe the problem from your customers perspective or even better, examine the frame (or box) that has created the problem in the first place. By examining the belief systems that underlie this problem can lead to truly breakthrough innovation. For an exceptional post on this topic follow @Sebastian Vetter or read his <a href="https://www.hackingculturalbeliefs.com/post/everyone-says-we-need-to-think-out-of-the-box-to-innovate">blog</a></p><p>So next time, you think you have the quick answer, or are feeling yourself pressured to come up with the quick answer — pause, take the time to explore what it could be. You could be cutting your organisation short of a fundamental shift towards that ambitious system change only dreamed about, and a wholly alternative universe to the one you have come from.</p><p>This article explains the analogous method of problem solving in more detail: <a href="https://hatrabbits.com/en/problem-solving-look-outside-">https://hatrabbits.com/en/problem-solving-look-outside-</a> industry/</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69c7b243609e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>