<?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 Davey van der Woert on Medium]]></title>
        <description><![CDATA[Stories by Davey van der Woert on Medium]]></description>
        <link>https://medium.com/@dpwoert?source=rss-111c6bc27fd9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kGIDAWphLfV5M_kwGND8ng.png</url>
            <title>Stories by Davey van der Woert on Medium</title>
            <link>https://medium.com/@dpwoert?source=rss-111c6bc27fd9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 02:48:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dpwoert/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[Why play can improve the interdisciplinary collaboration in your team]]></title>
            <link>https://uxdesign.cc/why-play-can-improve-the-interdisciplinary-collaboration-in-your-team-8d7fd1ce32f8?source=rss-111c6bc27fd9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d7fd1ce32f8</guid>
            <category><![CDATA[interdisciplinary]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[play]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Davey van der Woert]]></dc:creator>
            <pubDate>Tue, 12 Sep 2017 02:46:28 GMT</pubDate>
            <atom:updated>2017-09-17T20:26:34.836Z</atom:updated>
            <content:encoded><![CDATA[<h4>Improving collaboration by learning from playful behavior</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b04h3q-s765aLMmOUppkeA.png" /><figcaption>This interdisciplinary <a href="http://www.imdb.com/title/tt4574334/">team</a> uses play to collaborate and solve their problems. (photo copyright <a href="https://www.google.co.uk/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=1&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwj3rMLJt4bWAhXpKcAKHeLPBDIQFggpMAA&amp;url=https%3A%2F%2Fwww.netflix.com%2Fnl%2Ftitle%2F80057281&amp;usg=AFQjCNGCoGlGm3iK263llZWe7Ck9Mav1ZA">Netflix</a>)</figcaption></figure><p>A year ago I started writing my thesis for my study at Hyper Island. I choose to research the collaboration between developers and creatives, since reflecting on my own history, the collaboration between creatives and developers has always been an uneasy one. Even though it can result in amazing outcomes, it often feels as an incredible struggle. It often feels easier and better manageable to just prevent those two disciplines from collaborating at all. Let creatives be creative, and let developers do their thing. Don’t play with fire.</p><p>My background is in being a developer, but also in being creative. This all works really well when working alone of course, since there is nobody there to hold you back (except yourself). Working on creative technology projects in university was like a dream came true. Soon after my bachelor, when working in the real world, it became clear to me that working as a cog in a bigger team isn’t easy. You’ll face a lot of complexities due to the collaboration with others. This means that interdisciplinary synergy is often lost. You have to fit a label, you are a strategist, designer, developer or a project manager, you can’t be all right? This meant I became a developer. And all of a sudden the possibilities of me being creative felt lost behind a lot of different stakeholders and complexities.</p><p>I want to see that interdisciplinary synergy happening. Not only because I feel this is limiting me personally, but by creating those silos it can limit the possibility of all teams. Interdisciplinary collaboration is hard, therefore I went back to a school. To one that is known for their unorthodox, holistic and pragmatic style of education; <em>Hyper Island</em>. To me their biggest attraction was learning their vision on how to nurture and develop creative collaborative environments. My thesis is heavily inspired by this ‘Hyper Island’-thinking. The full thesis can be read <a href="http://thesis.dpwoert.com/">here</a>, and dives deeper into creatives and developers but for this blogpost I am going to keep it shorter and only going to focus on the most important learning of my thesis: <em>play is effective in creating &amp; nurturing an interdisciplinary collaborative team culture</em><strong>.</strong></p><h3>Play, as in learning by doing</h3><p>So let’s look at what <em>play</em> is first. In this case play is not seen as leisure or distraction, rather it is the work of working something, of figuring out what it does and determining how to operate something. Play is not the same as games, although play lies at the heart of games. Play is a deeper, more instinctual trait, like young animals using play to learn and get familiar with new abilities. In our culture play is seen as a child-like behaviour, not to be expressed by mature professionals since it involves intuition, rather then rational behaviour.</p><blockquote>“But I do want to keep this idea of imagination in mind that the thing that humans are doing, especially young humans are doing, when they play, is imagining. They’re learning to imagine. They’re learning to think about how other worlds could be. You think about this world by imagining alternatives to it. And you think, of course, about futures by imagining how the world could turn out.” — Brian Eno (2015)</blockquote><p>So play is tinkering, trying out things, failing, and succeeding. Play thus comes with a bit of (calculated) risks, there is always the <em>uncertainty</em> to ‘lose’, outcomes are not predefined. Losing is not necessarily a bad thing, since it gives the player the option to reflect, learn and be better next time. Play is thus intuitive, but also <a href="https://uxdesign.cc/pragmatic-design-how-does-design-thinking-fit-into-the-real-word-3ec55c9d97cb">pragmatic</a> in learning from practice not from theory.</p><p>Johan Huizinga, one of the most important scholars in the academic field of play, observes that play is <em>meaning</em> giving. When playing there is a relationship between a players actions and the system outcomes. This system is the fictitious reality where a player emergences himself in. This world is called the <em>magic circle</em> by Salen &amp; Zimmerman. In this space the normal rules and reality that guard normal life are suspended. Rules when playing aren’t laws, they only apply when playing and are make-believe in players’ heads. The relationship between this fictitious world and the real world is porous, there is always a relationship between the two. Rules governing that fictitious world can therefore vary, evolve, and adapt to fit to circumstances. When playing with a football, a player needs to pretend and imagine that a goalpost has a meaning in his act of playing since it doesn’t have that in real life. If there are no goalpost in a players environment, it isn’t a far stretch to pretend other objects that are at hand can have that same meaning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d6OtwWUG2Zmnp7fl8tysxw.png" /></figure><h4>Play is more than an individual act</h4><p>Play is about action and reaction. Something happens and a player has to respond to that, onto which another thing happens. A player kicks a ball against a wall and has to anticipate it bouncing back to kick it again. Play goes back and forth. This is also true when playing with others. There is always a relation between a player’s moves and another player’s counter-moves. A player has to be emphatic to other players, to learn to understand how they will behave so one can act accordingly. One way to do is by learning through <em>mimicry</em>. Mimicry is pretending you’re something or somebody else. It is therefore not only used to understand people, but also understand others aspects of life. Imagine a kid pretending to be a formula one driver, he is imagining what it is like to drive a car and how a person who does would feels like.</p><p>Even though play can be done with others, play is an individual and subjective experience. You can play with others but every player will have it’s own unique view on that happening. One player might win, and another would lose. Those players therefore have another qualitative experience. The reason to play is this experience itself, to be fully immersed in this is its own justification. The goal of playful behaviour is not achieving some subsequent ending. Play is not about acquiring beneficial gains. Those beneficial gains might happen, but those were not the aim for showing playful behaviour.</p><p>Huizinga suggests that play is primary to and a necessary (though not sufficient) condition of the generation of culture. Huizinga states that in human evolution play was eventually transformed into culture. He argues that many of the valuable aspects of human culture are formed by human cravings for those playful experiences, rather then by rational thinking.</p><h3>Why interdisciplinary collaboration is needed</h3><p>In interdisciplinary collaboration experts from different fields of expertise are challenged to work together in order to succeed in solving the tasks at hand. Collaboration can not be seen separate from culture, since culture shapes views towards collaboration. Interdisciplinary collaboration can liberate a group from previous <em>cultural restraints</em>. “This is how we do it” is not always improving end results. If a culture is not open enough for outside influences tunnel vision can arise. Team members can then act in ways that are harmful or dangerous to themselves, or others due to <em>cultural limitations </em>in their scope of view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fcgiQl-qn1Ynel9hewIFxg.png" /></figure><p><em>Immigrants</em> play an important role in culture, since they can bring fresh insights and methodologies from their previous disciplines, while seeing cultural aspects which are invisible to the natives. To improve interdisciplinary collaboration, both disciplines must value this diversity, develop the capacity for self-assessment, work towards understanding one’s own disciplinary culture, and be sensitive to the dynamics inherent when cultures interact. Cultures must get used to collaborating with other cultures. Every <em>cultural encounter</em> could broaden their view. These collaborating cultures must therefore want, not be mandated to engage in the process of becoming culturally aware, knowledgeable, skillful, and familiar with cultural encounters.</p><p>Each discipline has it’s own background, which has shaped their culture and language, which may be conflictful when collaborating. Teams must therefore recognise the potential for miscommunication. Team members must therefore start learning to speak the language of disciplines it collaborates with, while being mindful and aware of their own language.</p><h4>Be open to learning</h4><p>It is important that cultures are really open for hearing, and acting upon each others inputs. This collaboration should be desired by the whole team, not put up as a symbolic act. Representation does not mean inclusion. Important for inclusion is the willingness to share power, otherwise <em>tokenism, </em>the symbolic effort of giving a few people from a minority a say to make them feel more inclusive, might occur. Tokenism is likely to be found wherever a dominant group is under pressure to share privilege, power, or other desirable commodities with a group which is excluded. This tokenism can lead to experience substantial performance pressure, heightened awareness of boundaries, and perception of entrapment in this role for those excluded members of the team.</p><p>This is part of a bigger learning process of understanding each others disciplines better in order to collaborate more successfully. These disciplines have a complementary expertise for the tasks at hand, by possessing relevant knowledge the other discipline does not have. This creates a relationship where both disciplines are an expert in their own domain, while being a novice in the other. When collaborating each party becomes the ‘teacher’ for their own domain, while being the ‘pupil’ in the other domain at the same time. For both creatives and developers this process should feel familiar, since both disciplines already require individuals to dive deep into the problem domain to better understand the problem, and provide a successful solution.</p><h3>Collaboration as an act of play</h3><p>After my period at Hyper Island I’ve seen that creating interdisciplinary collaboratives cultures are not only possible, but more successful. In my year at Hyper Island we had 60 students with 27 nationalities, and even more diverse backgrounds. And I think this is because Hyper Island teaches methods, tools and ideas that cunningly use elements of play to create and maintain cultures.</p><p>One can learn from play that every situation is unique, like no act of play is the same or completely predictable. You can’t oversee every aspect of what is happening. All teams are made out of different people, in different roles, with different backgrounds and with different goals to achieve. There is not such a thing as an archetype for any discipline. Some patterns emerge everywhere but it is hard to generalise these patterns. It will be hard, or even impossible to create an easy roadmap to fix collaboration for everyone and in every situation. The solution for improving the collaboration is not in being dogmatic, rather in having a pragmatic and holistic mindset. Improving interdisciplinary collaboration is only possible when all actors involved ‘buy into’ changing their mindset. There is no way to change one’s mindset if that person does not intrinsically believes in it.</p><p>To create that mindset team members have to be immersed into creating a joint culture. Like with play, the goal shouldn’t be about personal gains but about the experience itself. These gain might (and in the case of collaboration, should) happen, but those gains are secondary to the experience. Think about professional athletes, during the game they will be completely immersed into the game, even though the gains after might be huge. Losing that focus and immersion can be devastating to them. When playing those gains are secondary, and going completely in to the experience is the only thing can counts.</p><h4>Using the magic circle</h4><p>At Hyper Island everyone was continuously talking about the ‘hyper bubble’ we were constantly creating. In hindsight I think that was the <em>magic circle </em>we were experiencing. We were in such an immersed collaborative state that the normal rules and reality that guard normal life were partly suspended, which gave people the possibility to collaborate beyond the normal barriers of their backgrounds. It therefore makes sense to keep that magic circle or bubble alive during the collaboration. One thing you learn, and hear a lot at Hyper Island is “trust the process”. You’ll hear this so much, after a while it will even get annoying. But it serves a purpose, it keeps this immersion alive I believe. When playing we all know what we’re doing is make-believe. When you start questioning those make-believe elements that porous magic circle is easily broken and the immersion lost. Trusting the process enforces focussing on the experience rather then the gains.</p><p>Why “trusting the process” will get annoying at times it can feel like a thought-terminating cliché. It might suppress being reflective, because “this is just the way it is”. Collaborative teams have to be reflective too, teams can’t just use this as an excuse to always continue what they’re doing. Hence team members should be involved in giving each other feedback, doing reflection and sharing the previously hidden, yet influential, thoughts and feelings. Teams have to understand that we all have individual experiences, we’re not always feeling the same emotions during the duration of a project.</p><h4>Keep on tinkering</h4><p>Not only individuals can improve, but the group process itself can be continuously improved. Think about the tinkering aspects of play, teams needs to start tinkering their processes continuously. Trying something, reflecting on it and than adapting and tailoring their processes to fit the demands and needs required. This is a continuous and messy process since the world we live in is in an constant unpredictable flux too, teams continuously have to respond to this. It is a constant state of action and reaction.</p><p>To create better collaboration teams also have to push their disciplinary boundaries in a playful way. Teams can only push those constraints if they have a basic understanding of where these constraints actually are. One should be interested and open to learn from the other discourse since this will provide a basic understanding of the constraints involved. Like when playing, collaborators have to be empathic to each others. It’s not just about learning how another team member completes his tasks, It is also about learning about other values and ways of thinking that might conflict with ones own. Like kids that shown <em>mimicry</em>, we have to put ourselves in the shoes of others to understand their thinking.</p><p>It’s not just about learning, it is also about acting after, which is easier said than done. The disciplinary teams need to be continuously aware of their mutual relationship. Play comes with risks. It is not about preventing conflict, it is about acknowledging it will happen, so you are ready to deal with it when it does. Both discourses will enter an unsafe situation where everything could happen. Trying to plan everything ahead will feel safe, but prevents improving the collaboration since the status quo will stay the same, or possible even deteriorate. It will prevent playfulness and a magic circle from happening. Playful collaboration will lead to unexpected results. Sometimes good results, yet not always. A team thus needs to know how to deal with failure when it happens.</p><h4>Use facilitation to ensure ‘fair play’</h4><p>A good referee understands the game, and will bend the rules whenever possible to keep the experience as smooth as possible while still keeping the game a ‘fair play’. We need that too for collaboration to succeed. At Hyper Island we therefore learned to value facilitation and facilitation tools to improve collaboration. A facilitator is not a leader, it’s a dedicated role that enables collaboration to be playful. This role is not fixed, every team member can take this role at times. The facilitation tools are playful ways of getting team members to facilitate their own processes. These tools should help teams get insights in their collaboration process, and help teams in dealing with conflict. These tools should improve communication between all actors involved in a project. These tools shouldn’t feel ‘big’, there shouldn’t be much of a training process for using these tools. The aim is to use tools that facilitate in a way that is non-obtrusive and collaborative for group members. Teams must decide themselves which tools work best in which situations. There is a multitude of ‘toolboxes’ available online like the one of <a href="http://toolbox.hyperisland.com/">Hyper Island</a> onto which teams can get inspired to use, or make own of tools. By doing so, teams will start creating their own toolbox. This process of tinkering should be lead by team members, not from management higher up.</p><p>The most important phase in a group process is the starting phase. In here the environment for collaboration has to be created so the group can enter their magic circle. To do so I think it is important to use tools to kick start this process, so a group can break the ice. These <em>ice breakers</em> try to break elements like egos, hierarchies and over-rational professionalism from blocking a group from being playful. Put your team in fun situations so they can enter their magic circle. Put them in challenging situations so that magic circle get less porous.</p><p>One challenging tool that was successful at Hyper Island was the “s<a href="http://toolbox.hyperisland.com/stinky-fish-13d9ce8d-e64f-4085-8a06-8d212c627788"><em>tinky fish</em></a><em>”</em>. In here everyone has to tell about their stinky fish: “that thing that you carry around but don’t like to talk about; but the longer you hide it, the stinkier it gets”. The purpose of this is not to shame people, rather the opposite will happen. This will affirm the group that we’re all human beings since no matter which background you have everyone has fears, anxieties and uncertainties. You better be open about those. To create fun situations you can for example use “<a href="https://issuu.com/hyperisland/docs/energizerbible"><em>energizers</em></a><em>”</em> as an ice breaker. In here you play small (dorky) mini games with a group that last only a few minutes. Or why not organise a dinner together for some group bounding?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jb8ssJXbmwAqM2v8aqDZxQ.jpeg" /><figcaption>At Hyper Island we organised a dinner party together as an ice breaker (photo by <a href="https://www.instagram.com/p/BAzNoRgCYqx/?taken-by=hyperislanduk">hyperislandu</a>k)</figcaption></figure><p>The final reward of play is fun. Successful collaboration will result in fun too. The process of play and collaboration itself encompasses many more emotions then just fun. Fun shouldn’t be mandated, you can’t enforce fun all the time. A group will go through various stages, and not all of them are fun. A group is not always winning, sometimes it is though. Every situation is unique. Every team has to improve the collaboration in their own way, as long as it feels ‘right’. Most important is to start doing. Talking about collaboration will not solve your problem, you need to get your hands dirty. It will definitely not be an easy process. There are no good or bad ways to improve team collaboration. What works for one team might not work for others.</p><blockquote>As a team you should decide what is working, and what is not. As a group make your own magic circle.</blockquote><p><em>Feel free to contact me on </em><a href="https://twitter.com/dpwoert"><em>twitter</em></a><em> or here on medium</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*aNPBhln7iDMY8qRcmoyCfA.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d7fd1ce32f8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/why-play-can-improve-the-interdisciplinary-collaboration-in-your-team-8d7fd1ce32f8">Why play can improve the interdisciplinary collaboration in your team</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic design: how does design thinking fit into the real word?]]></title>
            <link>https://uxdesign.cc/pragmatic-design-how-does-design-thinking-fit-into-the-real-word-3ec55c9d97cb?source=rss-111c6bc27fd9------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ec55c9d97cb</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Davey van der Woert]]></dc:creator>
            <pubDate>Fri, 12 Aug 2016 13:29:18 GMT</pubDate>
            <atom:updated>2016-08-23T11:20:39.121Z</atom:updated>
            <content:encoded><![CDATA[<h3>Pragmatic design: how does design thinking fit into the real world?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NYDwyQkkI4O90biIOOiyYQ.jpeg" /><figcaption>this design team is <a href="https://en.wikipedia.org/wiki/Lost_(TV_series)">lost</a>, let’s use design to feel less lost when trying to solve problems.</figcaption></figure><p>Last 6 months I’ve studied a MA at <a href="http://www.hyperisland.com/">Hyper Island UK</a>. Here at hyper I’ve learned so much more than I thought I would learn. I’ve started thinking differently about design, and think I’ve got a more complete view of design now. I am therefore writing this article to concretise my learnings from the last 6 months at Hyper Island. Initially just meant for myself, but hey why not share this? Others might learn something as well!</p><p>In our fast and ever changing world where everything is connected and nobody lives in a bubble anymore, we need better ways to look onto the world when trying to be innovative. The old methods of applying research to create innovative products or services are no longer sufficient enough. Expectations of users are higher then ever before, we no longer allow the products and services we use to be imperfect. We crave ‘experience’ in this world where everything is about ‘the self’ and individualism. We therefore need a paradigm that allows us to move out of the vacuum created by our own environment and opinions, to create products and services that truly serve a purpose to its users.</p><blockquote>“Design is way too important to be left to designers” — Tim Brown (creator of Design Thinking method)</blockquote><p>I think the principles behind design can provide us these paradigms for creating innovation. The principles behind design should not be limited to the traditional design principles, since innovation should take place on all levels of a company or team to be effective. Therefore <a href="http://designthinking.ideo.com/"><em>Design Thinking</em></a> became popular. <em>Design thinking</em> democratized design and made it available to non-traditional designers, therefore uses a broader range of backgrounds to find solutions, as well as defining the real problems.</p><p>The most famous implementation of<em> design thinking</em> is the one of IDEO. This method consists of <strong>5 stages</strong>. This process should be repeated multiple times, since it is an <strong>iterative approach</strong>. Every iteration acts like an improvement of the previous.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*Mt6xSg_nwhiei7S72bTwEw.jpeg" /><figcaption>5 stages of Design Thinking (IDEO)</figcaption></figure><ol><li><strong>Empathize</strong>: Try to empathize with your user first. Get to their level, learn how to think like your user, learn how to behave like your user, learn about their needs. Do this by interviewing, observing etc.</li><li><strong>Define</strong>: The problem needs to be redefined again, and again. By better understanding the playing field and users you can better understand the real problem that needs to be faced.</li><li><strong>Ideate</strong>: The stage were creativity comes in. By using previous learnings try to come up with new solutions for the problem.</li><li><strong>Prototype</strong>: Make a minimal version of your solution you can test with your users. The later iteration you are, the more fidelity a prototype will have.</li><li><strong>Test</strong>: test your prototype with your users. Use these learnings to start the new iteration.</li></ol><p>This matches the widely used <a href="http://www.designcouncil.org.uk/sites/default/files/asset/document/ElevenLessons_Design_Council%20(2).pdf">double diamond</a> method from the <a href="http://www.designcouncil.org.uk/">British Design Council</a>. This method describes the design process in 4 phases. It maps these phases to either convergent or divergent thinking, which therefore makes the two distinct diamond shapes. Like the IDEO design thinking method, this method is meant to have multiple iterations (but this model might over simplifies itself by presenting it too linear/fixed).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wuKkoPegua5RCUvrWWiW3A.jpeg" /><figcaption>4 stages of design (double diamond)</figcaption></figure><p>The 4 stages are as followed:</p><ol><li><strong>Discover</strong> (divergent): The start of the project, it often starts with an initial idea or inspiration. In this stage of the design process the team is asking a question, posing a hypothesis or identifying a problem by analysing market data, trends and/or user needs. The goal of this phase is too get a broad perspective.</li><li><strong>Define</strong> (convergent): The learnings of the discovery phases are analysed and synthesised to a clear definition of the problem(s) and a brief/plan for how to address this through a design-led product or service.</li><li><strong>Develop</strong> (divergent): During this stage the team will refine one or more concepts that will address the problems or issues identified during the Discover and Define stages. In this stage methods like brainstorming and prototyping take place to get to a well enough defined concept that is ready for delivery to production.</li><li><strong>Deliver</strong> (convergent): In this stage the final concept is taken through final testing, signed-off, produced and launched.</li></ol><p>These methods are all nice explaining a subset of design, but they formalise design too much. I think design is something easier and more hackable than this. I have been working on multiple aspects of design; graphic design, software (architecture) design and design for innovation and in my opinion all these design disciplines can be boiled down to a really simple core principle, which can be traced back to philosophical ideas of <em>pragmatism</em>. It is the notion that you can only see the effects of <em>something</em> when you put that <em>something</em> into the real world. The idea that theory follows practice, instead of the other way around.</p><p>At the heart of pragmatism lies the idea that the the world is always in flux and will never reach a fully finalised state. The <a href="http://www.asatheory.org/newsletter/the-pragmatic-maxim"><em>pragmatic maxim</em></a> states that the meaning of our conceptualizations of the world should constantly be evaluated on the basis of their practical consequences. This means that theory and practise are connected, theories are made through practise and must be judged upon practise. According to the famous pragmatist John Dewey everything in the world is connected and thus everything in the world has an interaction which each other.</p><blockquote>“Everything that exist in as far as it is known and knowable is in interaction with other things” — John Dewey</blockquote><p>Since everything is connect Dewey states that everything is <em>situated</em>, By which he means that things can only be understood by its connection to the contextual whole. This means it is not possible to think or act on an abstract representation of something, it will always be situated within a certain context. This context is not predetermined or eternally stable, but can always be changed through human practices (as in humans using design!). This means that a situation that is thought of as being problematic can be transformed to be temporarily stable.</p><p>In pragmatism this is called the <em>inquiry</em>. An inquiry is the mode of thinking and acting to transform an unstable situation. An inquiry is not a way of finding the truth, it is the means or method to reduce doubt and to restore balance to a problematic situation, to let you get on with the task at hand. With an inquiry a person will first try to identify what causes the unstable situation. This person will then try to form conceptualizations which need to be put into practice in the real world. If these conceptualizations fail, they are not suitable and the person will try to make new hypotheses to test again. Sounds a lot like design (thinking) right?</p><p>So I see design not as a discipline or a skill set, rather a way of looking at the world. It is an extension of pragmatism. It uses the the ideas of pragmatism, and then adds a lot of method &amp; tools on top. These methods &amp; tools aim to help teams/individuals in their process of inquiry when creating services or products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WZ055SkoXX1IgjQ9I7jMCQ.jpeg" /><figcaption>design toolbox</figcaption></figure><p>So basically design is a toolbox. On the left side is the pragmatic design process of <em>inquiry</em>. On the right side we have tools to assist the design process. The design process is limited in time, so we need to have <em>time management</em> tools to get to the most suitable answer within the given time. Since design is mostly done by teams, we can only succeed if the team works together collaboratively. Therefore group development is often needed for successful design.</p><h4>Try/do</h4><p>Design is about making stuff, we make stuff to test our hypotheses. We can do this from very low-fidelity to very high-fidelity. It’s not only about prototyping, even brainstorming with post-it’s on a wall is putting something in the real world. It externalises information and other group members will have to possibility to evaluate (and improve) it. The later you are in the design process, thus the more iterations there have been taken place, the higher fidelity the outcomes will be.</p><p>Methods and tools you might use:</p><ul><li><a href="https://hbr.org/2012/09/the-secret-phrase-top-innovato">How Might We?</a></li><li>Brainstorming</li><li>Storyboarding</li><li>(Paper) prototyping</li><li>Wireframing</li><li>Deskresearch</li><li>…</li></ul><h4>Learn</h4><p>Everything you try and do should have a method of learning attached to it. There is no point in doing something, when you can not learn from it. Most of these methods need to include potential users, since they are the biggest unknown factor in most design projects of course.</p><p>My personal learning about users is that they can only verify your wrongdoings and successful solutions (although watch out for the <a href="http://momtestbook.com/">Mom test</a>!), they will not provide you concrete solutions. You will probably need your creativity and problem solving abilities to transform your learnings into new iterations. This is also the hardest part of design, nobody will give you ready solutions. You always need to set the right course yourself. Design is always on the edge of ratio and intuition.</p><p>Methods and tools you might use:</p><ul><li>Interviewing</li><li>Downloading method(IDEO)</li><li>Questionnaires</li><li>A/B testing</li><li>Technical feasibility test</li><li>…</li></ul><h4>Time management</h4><p>Every design project has to deal with a process over time. Not a single design process is the same, or requires the same approach. There are multiple ways to approach the time management of a design process. Not every project requires the same phases, or order of phases. It is up to the team to decide how they want to spent their time to solve a problem. They can use, hack and combine a range of methods and tools.</p><p>Team members need to keep in mind that they need to be flexible when planning. Time might be linear, a design process is not. A design process is iterative and learnings might change the whole project. Team member need to follow their intuition to keep within time. Design is an adventurous journey, it’s not possible to know beforehand how a design process will behave. Let’s be honest, most of the time we have the feeling of being lost during the design process, and these methods and tools provide us a sense of direction.</p><p>Methods and tools you might:</p><ul><li>Design thinking phases</li><li>Double diamond</li><li><a href="https://medium.com/@dpwoert/re-booting-our-startup-fb4770a25942">1–10–100 method</a></li><li><a href="http://www.designkit.org/human-centered-design">Human Centered Design</a> (IDEO)</li><li><a href="https://developers.google.com/design-sprint/">Design Sprints</a> (Google)</li><li>Scrum or other agile methodologies</li><li>…</li></ul><h4>Group development</h4><p>Since design thinking is no longer a paradigm exclusive to those from the traditional design world, design has become an interdisciplinary field of work. At Hyper Island, we were with 60 students, with 27 nationalities, with an even wider range of backgrounds. Working in interdisciplinary teams was therefore a given and we needed to focus a lot on improving our team work. This resulted in interdisciplinary projects with fresh and unexpected insights.</p><p>When disciplines collaborate conflicts will naturally arise. These conflicts are threats and opportunities at the same time. To conquer and come out stronger of these conflicts we must recognize that cultural differences exist between, and within, disciplines. To work together successfully each individual must improve in self-assessment, must learn to better understand his own disciplinary culture and be open to learn from other disciplinary cultures.</p><p>Methods and tools you might use:</p><ul><li><a href="http://theteamcanvas.com/">Team canvas</a></li><li><a href="http://toolbox.hyperisland.com/principles-of-effective-feedback">Feedback</a> and <a href="http://toolbox.hyperisland.com/reflection-individual">reflection</a></li><li><a href="http://toolbox.hyperisland.com/check-in-check-out">Check-in &amp; check-out</a></li><li>Team activities</li><li>…</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3kns0fGZd3U9z-1buOiKEw.jpeg" /><figcaption>Design is an adventurous journey, where we need to trust our team because the conditions are hard</figcaption></figure><p>Since design is such an adventurous journey, where we are unsure what we are actually building and feel lost so much, we need somebody to guide the team. This is the facilitator. His/her job is not to lead the group, but to assist the team in keeping the journey as stable as possible. The facilitator can help with his knowledge of the design process, by proposing (not dictating) methods and tools to use. A good designer is therefore somebody who can lead the design process properly.</p><p>To become a better designer one needs to increase his design toolbox. Learn more methods and tools, learn how to hack them and learn how to make methods &amp; tools yourself. A good designer acknowledges the fact that he needs to act in the real world to learn. Learnings from a book are only useful when used, tested and learnt from by yourself. A good designer will always revaluate his learnings later on since the world is constantly changing. Design is pragmatism, accepting that the the world is always in flux and will never reach a fully finalised state.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ec55c9d97cb" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/pragmatic-design-how-does-design-thinking-fit-into-the-real-word-3ec55c9d97cb">Pragmatic design: how does design thinking fit into the real word?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>