<?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[Service Design Notebook - Medium]]></title>
        <description><![CDATA[Travel journal of my journeys in service design and design thinking. - Medium]]></description>
        <link>https://medium.com/service-design-notebook?source=rss----82eab1ca5829---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Service Design Notebook - Medium</title>
            <link>https://medium.com/service-design-notebook?source=rss----82eab1ca5829---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:03:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/service-design-notebook" 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 Would Anyone In Their Right Mind Talk To Their Users Anyway?]]></title>
            <link>https://medium.com/service-design-notebook/why-would-anyone-in-their-right-mind-talk-to-their-users-anyway-efc1869ce907?source=rss----82eab1ca5829---4</link>
            <guid isPermaLink="false">https://medium.com/p/efc1869ce907</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Dennis Hambeukers]]></dc:creator>
            <pubDate>Wed, 13 Nov 2019 06:30:27 GMT</pubDate>
            <atom:updated>2019-11-12T20:25:46.348Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ULPgfU4_6DDEHDLDCdUMKQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@nickxshotz?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Nicholas Green</a> on <a href="https://unsplash.com/s/photos/crowd?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>When you are developing a new product or service or when you are updating an existing one, talking to your users is one of the scariest and at the same time potentially most valuable things you can do. It’s an investment, no doubt about that, but it’s one that has a huge return if you do it well. Involving your users can lead to higher quality products and services and reduce risk.</p><p>A valuable design for a product or service is one that meets three requirements:</p><ul><li><strong>Feasibility</strong>. First of all the idea needs to be doable. It must be technically and organizationally possible to produce the product or service. If not, you need to invest in that area.</li><li><strong>Viability</strong>. On top of that, the idea has to generate value for your organization. All things that are possible do not automatically generate value. The product or service must fit the long term strategy of your organization about how it intends to create value.</li><li><strong>Desirability</strong>. And, last but not least, the idea must fit the needs of your users. If no-one is excited about your product or service, you are not creating value for your organization.</li></ul><p>The first two are <em>internal affairs</em>. What makes the third so tricky is that you have to step outside your organization for that. And there can be many reasons why this is difficult, scary or downright impossible. It can be difficult to contact your users. Or maybe you want to target a new demographic and you don’t know exactly who is in it. Or your users are reluctant to invest time in talking to you about new products and services. Maybe you are working on top-secret stuff that nobody outside your organization can know about. Often it is also very scary to talk to users because they might say things you don’t want to hear.</p><p>About that last thing, I can reassure you. When you talk to users, you don’t have to do everything they say. You also have your own strategic vision and technical and organizational conditions that have to be met. The input of the users is just one of the factors that impact the decision-making process.</p><p>When it’s really impossible to talk to your users, there is also the middle way of the user persona. A persona is a fictional description of a user. If you start thinking about who your users are and what their needs are and you try to empathize with that, you will already get some new insights.</p><p>But the insights and confirmation that you get from interacting with real users are far more valuable. Because next to using the perspective of the user to get a fresh view of your product or service, you can get way more from that interaction:</p><ul><li><strong>Test assumptions.</strong> Maybe one of the most important things you can do during the development of products and services is finding out whether your assumptions are right. Often we don’t even know we are making all kinds of assumptions when we think about our products and services. There are bound to be numerous assumptions in both your problem description and in your solutions. Testing assumptions will only work if you are talking to real users. Making wrong assumptions creates the risk of developing solutions that will not work for your target audience.</li><li><strong>Collect valuable insights</strong>. Users can not only help you identify your assumptions but also with uncovering the right questions and the finding of new solutions. When you know what troubles your users, when you know exactly what problem they are trying to solve, when you know precisely why they use your product or service, you can better serve them. Often users bring you questions you have never thought of yourself.</li><li><strong>De-risk.</strong> The development or improvement of products or services is a risky operation. If you fuck it up, your investment is lost or users turn away from you. In each step of the development process, you have to make choices. If you involve users, you can validate those choices each step of the way. By using prototypes, you can test whether you are making the right choices. This way you can take away the risk in your project and prevent costly mistakes.</li><li><strong>Grow ambassadors.</strong> When you involve users, they usually appreciate that very much. If they can help to design products and services they care about, they like that. It’s innovative and creative work. You not only project an image of an open, modern, innovative organization but the users you involve can turn into ambassadors and share their experience in their network. This way you can build social capital.</li><li><strong>Motivate your team.</strong> Most people are motivated by doing something good for others. But the reality in most organizations is that most people are too far removed from the users they work for. By bringing employees closer to the user, you can increase their level of motivation. When they see why they do their work, that can be very inspirational.</li><li><strong>Stakeholder alignment.</strong> Putting the needs of users central in your project can help to solve differences of opinion between stakeholders. If you make the user the judge of what works and what doesn’t, you can create a central focus point to create a shared vision and common goal.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XUsVMVciYdOwJ_2KqJSElQ.png" /><figcaption>Benefits of user involvement</figcaption></figure><p>All these benefits not only go for involving users but for everyone. For a successful project, you need to engage all stakeholders. Not only is the support of all stakeholders a critical success factor, but they can also provide valuable knowledge and insights for your project. All of this takes time and money. But think about how valuable it could be if you could prevent costly failures, make a higher quality product or service, create a support base for your project, have a motivated team, and spend less time on support because your users better understand your product or service. Investing in involving your users will yield returns on multiple levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/0*A0p-Fw9ceNXLODe1.jpeg" /></figure><p><em>Thank you for taking the time to read this article. I hope you enjoyed it. If you did, don’t forget to hit the clap button. I will dive deeper into the topics of Design Leadership in upcoming articles. If you follow me here on Medium, you will see them pop up on your Medium homepage. You can also connect with me on </em><a href="https://www.linkedin.com/in/dennishambeukers/"><em>LinkedIn</em></a><em> to see new articles in your timeline or talk to my bot at </em><a href="http://dennishambeukers.com/"><em>dennishambeukers.com</em></a><em> :)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efc1869ce907" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-notebook/why-would-anyone-in-their-right-mind-talk-to-their-users-anyway-efc1869ce907">Why Would Anyone In Their Right Mind Talk To Their Users Anyway?</a> was originally published in <a href="https://medium.com/service-design-notebook">Service Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should You Make One Customer Journey For Your Entire Organization?]]></title>
            <link>https://medium.com/service-design-notebook/should-you-make-one-customer-journey-for-your-entire-organization-3d2b3855ddd3?source=rss----82eab1ca5829---4</link>
            <guid isPermaLink="false">https://medium.com/p/3d2b3855ddd3</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[customer-journey]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[customer-journey-map]]></category>
            <dc:creator><![CDATA[Dennis Hambeukers]]></dc:creator>
            <pubDate>Thu, 01 Nov 2018 11:07:53 GMT</pubDate>
            <atom:updated>2018-11-01T11:07:42.256Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*464eKImbR4lVQv991VHJ1g.jpeg" /></figure><p>Yesterday I was one of the speakers at a little seminar on customer journeys. We discussed, studied and learned from each other around the customer journey mapping tool. Over the years, more and more projects started to use the tool in the organization. This, and the strategic goal to put the user at the heart of services, led the board of directors to state that the use of the customer journey tool should be one of the primary tools within the organization. The question we focussed on was: how do we do that? how do we make sure more people use it? how do we benefit from this tool? can it be more than just a tool?</p><h4>More than a tool</h4><p>A tool is just a tool. The underlying goal is to make the organization more customer centric and the customer journey map is a great tool to:</p><ul><li>look at your services through the eyes of the <strong>user</strong>,</li><li>see the <strong>bigger picture</strong> of the services your organization provides,</li><li><strong>align</strong> stakeholders and departments,</li><li>focus on <strong>tasks</strong>,</li><li>create a <strong>common language</strong>,</li><li>uncover new insights and <strong>opportunities</strong>,</li><li><strong>share</strong> insights,</li><li>and <strong>validate</strong> ideas.</li></ul><p>A customer journey map can be so much more than just a tool. It can be a way to:</p><ul><li>enhance <strong>engagement</strong> and energy,</li><li>to make your organization more <strong>agile</strong>,</li><li>to focus and set <strong>priorities</strong>,</li><li>and to introduce a new, customer centric, <strong>way of thinking,</strong></li><li><strong>change</strong> the organization.</li></ul><h4>Do your job better</h4><p>To move from ownership of processes to ownership of journeys, the customer journey map can be a great tool, mental model and way of thinking. But to let the customer journey tool be more than a tool, you have to discover how using it can help you do your job better. Just drawing a customer journey map will not help you do your job better, you have to understand how it can help you do your job better. So one of the questions that we discussed is how to use the insights you get from mapping to take a next step. How to make the most of the organizational effects like engagement, alignment and user centric mindset. Some of the uses of the tool came up:</p><ul><li>The customer journey map can help you see the most crucial areas of the service. This helps in <strong>prioritizing</strong> efforts.</li><li>The map can help you uncover new elements of the service that you didn’t see before. This helps in <strong>improving the service</strong>.</li><li>The map can help you to uncover elements of the service that do not provide any value to users. This helps in making your operation more <strong>lean</strong>.</li><li>The map can be a good starting point for prototyping. If you use prototyping to dive deeper into elements of your service you can drill down to the specifics of the problems you need to solve and learn about <strong>how to best solve</strong> them.</li><li>If you map front and back-end services and systems to the journey you can start seeing the relations between organizational processes, systems and the journey of the user. This creates <strong>new perspectives for decisions</strong> on systems, different discussions on more relevant topics.</li></ul><h3>One journey</h3><p>The question I brought to the discussion at the end of my presentation was:</p><blockquote>“Should we make one customer journey for the entire organization?”</blockquote><p>One the one hand it looks like people in the organization are doing work that has already been done. If everybody is drawing similar customer journey maps, should there just be one map that everybody can use? On the other hand, the process of making the maps has ripple effects on the people in the projects that you miss if you just use the corporate map and don’t draw one yourself.</p><h4>One way of thinking, seeing and communicating</h4><p>We quickly came to the conclusion that there is no such thing as one customer journey map for an entire organization. Each map is draws from the perspective of a different user, is drawn to answer a specific question and is the result of the input of different stakeholders. There are bound to be some overlapping pieces but each project will need their own map. But it’s good to at least have one way of thinking, seeing and communicating. So maybe you don’t need one map, but one way of doing would be great. Especially to enhance communication between and across projects. If everybody makes maps, everybody is starting from the user perspective.</p><h4>One method</h4><p>There are many ways to draw customer journey maps. If you look into it, you’ll find multiple ways to structure a map, but also multiple visual representations. So to help sharing and to get off to a quick start, it would be a good idea to at least use one method to draw the maps. This way people from other projects can quickly read your map. And you can also learn from other projects more easily. You can see what others have done and start from that. You could build up a library of maps that other projects have drawn to learn, see connections, draw inspiration etc.</p><h4>One tool</h4><p>One part of the effort to use one method is to use one tool. There are many tools out there that can help you draw your maps. Starting with simple tools like a pen and paper to cloud computing tools that let you collaborate and offer templates. One of the tools I like, and is free for education institutions, is <a href="https://mural.co/">Mural</a>. This tool offers templates and collaboration and has a specific graphic style that allows you to quickly read maps once you are used to it. It’s also a platform to save maps so you can back to them later and see other people’s maps.</p><h4>One journey</h4><p>At first the idea of one corporate journey was rejected in our discussions. But talking about the one way of thinking, one method and one tool, the one journey idea came back up. Because if each map is draws to investigate a specific question, there is also a specific question that could be investigated with a meta/über corporate map. On strategic level there is also:</p><ul><li>a need for <strong>overview</strong>,</li><li>a need for a way to <strong>prioritize</strong> and <strong>monitor</strong> investments,</li><li>a need to get everybody in the right <strong>mindset</strong>, and</li><li>a need for a way to have the <strong>right discussions</strong>.</li></ul><p>If putting the user in the center is a strategic goal, using a customer journey map on a strategic level would be a great idea. In the end you want all the effort and investments to have an effect on the overall customer journey of the services your organization delivers. A journey on a strategic level could be a great frame for discussions, monitoring and decisions. The meta map could be fed with insights from the project maps. Like all maps it would be a living document that could also track the history of effort and results, create continuity between projects and strengthen relations. Tools change behaviors and the customer journey map can be a great tool to change communication, mindsets and definitions of success.</p><h4>Journey of journeys</h4><p>Even if you have a different question that drives the drawing of the map in your project, even if you have a different user, even if there are different stakeholders involved, the journeys in an organization will touch each other. Projects can not only benefit from the bigger picture in a project, but also from the bigger picture of the relations from your project to that of others. Journey maps can help break people from their silos. But changing ownership from processes to journeys can create new silos. On different levels the touchpoints between journey maps can facilitate cross journey communication, strengthening the organization. The meta journey can be a place where the relations between journey can be mapped to create a journey of journeys.</p><h3>The journey continues</h3><p>Using customer journey maps shouldn’t be forced onto people and projects. It only works if people see the benefits. To achieve this you have to:</p><ul><li><strong>educate</strong> people on the tool, the use and benefits,</li><li><strong>lead by example</strong>: use the tool on key projects and on strategic level,</li><li>provide <strong>tools</strong>,</li><li>keep the <strong>discussion</strong> alive.</li></ul><p>A mini seminar like this is a good way to get the discussion started and to share insights. I’m curious to see where the journey of the journey maps takes us. It’s great to see so many people get exited about the benefits, the effects this tool can have on an organization. The tool in itself is simple, but like any tool, the benefits don’t come from the tool but from the people using it, their goals, their questions, their skills. Tools like the journey map can be a catalyst for change. The discussions around the tool are equally, if not more, important than the tool itself. If you can change people’s mindset just a little, if you can enhance communication just a little and if you can uncover little areas to improve your service, you’re already winning.</p><blockquote>“We become what we behold. We shape our tools and then our tools shape us.”</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d2b3855ddd3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-notebook/should-you-make-one-customer-journey-for-your-entire-organization-3d2b3855ddd3">Should You Make One Customer Journey For Your Entire Organization?</a> was originally published in <a href="https://medium.com/service-design-notebook">Service Design Notebook</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 Get From Design To Deliver And Beyond]]></title>
            <link>https://medium.com/service-design-notebook/how-to-get-from-design-to-deliver-and-beyond-507e32dbc4bd?source=rss----82eab1ca5829---4</link>
            <guid isPermaLink="false">https://medium.com/p/507e32dbc4bd</guid>
            <category><![CDATA[strategic-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-conference]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design-leadership]]></category>
            <dc:creator><![CDATA[Dennis Hambeukers]]></dc:creator>
            <pubDate>Fri, 06 Jul 2018 09:36:54 GMT</pubDate>
            <atom:updated>2018-07-06T09:52:25.065Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/717/1*PY2bDJbC1_A594PxSKg7JA.jpeg" /></figure><h4>Looking forward to the Service Design Global Conference 2018 in Dublin.</h4><p>One of the themes that emerged from the 2017 Service Design Global Conference in Madrid was the gap between design and business and the difficulties service designers were experiencing when it came to implementing the services they designed. The theme of the 2018 conference addresses this theme: D<em>esigning to deliver</em>. In the run up to the conference, I thought it would be a good idea to reflect on this question on how to get to delivery.</p><p>If you missed my reflection on the SDGC17 conference in Madrid, you can find it here:</p><p><a href="https://servicedesignnotebook.nl/mind-the-gap-4b061256eabc">Mind the gap — reflections on the Service Design Global Conference 2017 in Madrid</a></p><h3>Innovation theatre</h3><p>Service design designs new services or improves existing ones. So most of the time service design is about innovation. Innovation is a hot topic these days and service design offers very useful tools, mindsets and skills to innovate. Lots of companies want to innovate so they deploy the tools. They organize design thinking workshops and hackathons, do user research, draw journey maps and service blueprints. This all looks and feels very innovative and it produces ideas, but in a lot of cases this does not actually produce results and impact. Innovation gets stuck in the superficial aspects. All the post-its, sketchnotes, prototypes and lego bricks make it look like innovation, but it is just theatre. This not only is a waste of resources, but it also disqualifies the tools as a fad. The challenge for both service designers and the organizations that want to innovate is to come up with an innovation pipeline that produces results.</p><blockquote>“Ideas are easy. Implementation is hard.” — Guy Kawasaki</blockquote><h3>Ideas</h3><p>Innovation is not about ideas. It’s about good ideas. It’s about ideas that move people. Sure, ideas are easy, but good ideas are not. Good ideas are the ones that create a platform for people, interest, departments and technology / resources to come together. Good ideas create synergy. Good ideas create a new frame, a new way of thinking about the problem. Good ideas open up new possibilities. Good ideas take the complexity of the problem into consideration and create a new order. Good ideas make complex problems simple. Good ideas are the ones that embrace the constraints of the organization and the technology.</p><blockquote>“If I had an hour to solve a problem I’d spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.” — Albert Einstein</blockquote><h3>The right problem</h3><p>And good ideas are ideas that solve the right problem. You can come up with a brilliant solution, but if it solves the wrong question it’s worthless. One of the key elements of design-based problem solving is that you use solutions, ideas, to uncover the problem. I believe that is where the real power of design-based problem solving approaches like service design is located.</p><p>But it’s not only about finding the right problem to solve. If you want to design something that actually gets delivered, it’s also important to find an area in your organization that is dealing with an urgent, relevant problem with a lot of impact on the organization. And it also has to be an area where there is a sense of urgency. People have to be fed up with the current way of working, the current systems and services. Otherwise your project won’t get funded.</p><h3>A pro-active approach</h3><p>For your project to succeed, for your design to get delivered, it’s not enough to find the right problem in the right part of the organization. The right problem, the pain and the sense of urgency are not givens. Setting your project up for success means being able to drill down quickly to the real problem underneath, pushing on the pain and nurturing the sense of urgency. There might be relevant problems and some sense of urgency, but people naturally resist change. You need to sell the change and continue doing so during the entire project.</p><h3>Think ahead to the delivery phase</h3><p>So even in the first stages of your project, the discovery and design phase, you need to think ahead to the delivery phase in order to design things that have a chance. That creates a good base. But in innovation projects that succeed, the discover and design phase is just a small part of the entire timeline. Most of the work is done in the delivery phase. And if you continuously develop the service, this phase is stretched well beyond the MVP. If your solution is flexible enough to accommodate new insights, your design will just be a starting point and will evolve through numerous iterations. The design principles that are in your design have more value than the actual design in the delivery phase. When your design meets with the reality of the business, it needs to be flexible and have a strong foundation of principles.</p><h3>Things to do in the delivery phase</h3><p>The things you need to do during the delivery phase span a wide spectrum of hard and soft skills. If you have set up your design right, if you found the right problem and context, if you have created a knife that will cut through the complexity, if you have created a platform that will bring stakeholders together and have defined some solid design principles, you will have a good starting point for delivery. Then the real hard work starts. Here is a selection of the things I learned are important in the delivery phase.</p><ul><li><strong>Sales</strong>. You need to be constantly selling. It’s not just in the beginning when you sell your big idea. It’s also not about black hat sales tricks and puffed up marketing, these things will bite you in the butt. People make the project and they need to be engaged. If you have a good design, this is the starting point, the base for engagement. But the initial enthusiasm will meet with reality and disappointment is lurking.</li><li><strong>Constantly be designing.</strong> The ultimate sales technique of a designer is his designs. Once you hit a bump, once you design runs into a wall of restrictions within the organization or technology, you need to redesign. Based on your design principles, you need to come up with a different solution that honors the same principles. A design is just one possible manifestation of an idea or design principle. You will run into conflicts that will slow down, deteriorate or even kill your project. You can use redesigns to resolve conflicts. Use the conflict and disappointments as new input into your design. Design is creative conflict solving.</li><li><strong>Tell stories.</strong> Storytelling is one of the most powerful tools to create engagement and convince people. If you can base your stories on your designs, your stories become super powerful. This way people don’t only hear your stories, but they can also see them.</li><li><strong>Connect strategy, tactics and operations.</strong> One of the biggest problems in organizations is the disconnect between strategy, tactics and operations. Strategist have no clue about the reality of operations and the tactical people are caught in the middle. Because design operates on all abstraction levels, design is in a great position to connect these layers in an organization. If you can show how a strategy translates to an operational service and draw out a roadmap of how one might get there, you are connecting. If you use the insights you gained from researching operational problems to inform strategy and tactics, you are connecting. If you can use your designs to give tactical people the tools to sell to strategy and engage operations, you create enormous value. Strategic alignment is crucial for the success of your project.</li><li><strong>Communicate.</strong> You might think all things are clear to all stakeholders. But this is not the case. You need to explain and repeat your message to all stakeholders. If you are not explaining your project in a presentation at least twice a week to different groups of people, you are not communicating enough. If you don’t have a project website with updates or an place on the intranet, you are not communicating enough. If you are not doing regular showcases of your project, you are not communicating enough. If you don’t have a big launch party for your MVP, you are not communicating enough.</li><li><strong>Defend the user.</strong> You are the guardian of the users. User centered thinking is new to organizations. They might be sold on the idea initially, but tend to forget as time progresses. Keep the focus. Keep involving the user and keep urging people to think from the user. Also make sure that the user centeredness is not going overboard. It’s not like the user holds all the answers. There are other things to consider.</li><li><strong>Defend the design principles.</strong> Another things that tends to be forgotten over time are the design principles, the reasons why, the bigger goal. It’s your job to remind people of the principles when they are forgotten. It’s your job to think up new solutions based on the same design principles. But it’s also your job to pivot the principles if there are new insights. Have strong principles, but hold them lightly.</li><li><strong>Be creative in the project management.</strong> Agile is cool, but don’t get caught in the trap of all the rules and tools. I have seen so many people doing Agile in a rigid way. And that way it only makes things worse. Adhere to the principles formulated in the Agile Manifesto, but don’t get caught up in the theatre of Scrum. Sometimes you need some waterfalls or a Gantt chart, sometimes you need to create your own project management tools and process. Try to see what the situation needs and be creative in combining different project management tools. Creativity in KPI’s is also crucial. Progress or success in innovation projects might not show up on the radar if you use traditional KPI’s. Create and sell new one, create a new frame and mindset around success.</li><li><strong>Keep your business case Agile.</strong> Most people understand that your process should accommodate new insights, that your design should be flexible, but the business case needs to be as well. Most projects are governed by time, budget and functionality. In most projects time and budget win and functionality looses. But during the project you will uncover new insights on how to create value. You should use these to update the business case. Opportunities for value creation open up during projects, that couldn’t be imagined up front. Treat the initial business case as a first, rough idea, not as something that is set in stone. Also be prepared to lower the ROI predictions. Honesty will build trust and trust is needed to break open the business case. Stakeholder validation and engagement are excellent currency in business case negotiations.</li><li><strong>Keep discussions concrete. </strong>A lot of conflicts arise from abstract discussions. If things are abstract it’s easy to hide behind abstract words. It’s easy to disagree when the terms of discussion are not clear to all. People often disagree because they have a different understanding of abstract concepts. Design can make things real, concrete. This helps a lot in discussion. Because everybody understands and sees what is discussed, the disagreements are resolved far quicker than in abstract discussions. So always put the designs on the beamer when discussing user stories.</li><li><strong>Document the learnings.</strong> During innovation project you collect insights all the time. These are hard to document. If you put them in text documents, they become hard to read after time. If you incorporate the useful insights into the design, the design becomes the documentation. Create versions of the design. This will create a historic document of the insights and how they sparked new solutions. This will also create an easy access database of all the ideas that did not make it into the MVP, but can be explored further in future iterations.</li><li><strong>Facilitate co-creation.</strong> Because design makes things concrete, it can be a great platform for people to come together and communicate. Everyone understands designs and everyone can reverse engineer what his department needs to do to make it happen. But this requires the design process to be open to the input of all stakeholders. If someone has a great idea, use it. Don’t be “the designer” and openly discuss the options. People need to have the idea that the designs are not set in stone and they can have input. The designer also has to be perceived as open and in touch with the reality of the organization, not a know-it-all that wants to push unrealistic things, but an expert with an open mind.</li></ul><h3>Relevant, credible and visible</h3><p>There are many more things to consider and do, but the main thing is that you keep your projects relevant, credible and visible. Communication, alignment, problem finding, flexibility all help to achieve that. Design is a catalyst for these processes, but it’s complex. And it doesn’t end with delivery. Innovation is iterative process of constant delivery.</p><p>The conference title <em>Designing to deliver</em> for me has two meanings. First it’s about creating a good solid foundation in the discover and design phase that already anticipates and looks forward to the delivery. But it also means that you keep on designing during the delivery phase, that design can be a catalyst for the delivery phase of the innovation process. I’m curious to see how the speakers at this year’s conference address these topics.</p><p>If you want to know more about the Service Design Global Conference 2018 in Dublin, you can visit the website of the Service Design Network:</p><p><a href="https://www.service-design-network.org/sdgc/2018">SDN | Service Design Global Conference</a></p><p>If you want to read my article in the Touchpoint magazine of the Service Design Network about the Service Design Global Conference 2017 in Madrid, you can read it here (pages 12–14):</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=%2F%2Fe.issuu.com%2Fembed.html%230%2F62893594&amp;url=https%3A%2F%2Fissuu.com%2Ftouchpoint_journal%2Fdocs%2Ftouchpoint_vol9_no3-issuu&amp;image=https%3A%2F%2Fimage.issuu.com%2F180426102441-be8ecef7c199cd52c8d54a0d0b464cf3%2Fjpg%2Fpage_1_thumb_large.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=issuu" width="525" height="792" frameborder="0" scrolling="no"><a href="https://medium.com/media/f2f54233f98b931ee8a230ee6b72b9d6/href">https://medium.com/media/f2f54233f98b931ee8a230ee6b72b9d6/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=507e32dbc4bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-notebook/how-to-get-from-design-to-deliver-and-beyond-507e32dbc4bd">How To Get From Design To Deliver And Beyond</a> was originally published in <a href="https://medium.com/service-design-notebook">Service Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 ways to design if your aim is not ease but excellence]]></title>
            <link>https://medium.com/service-design-notebook/did-technology-make-us-happier-10ad50c127b7?source=rss----82eab1ca5829---4</link>
            <guid isPermaLink="false">https://medium.com/p/10ad50c127b7</guid>
            <category><![CDATA[happiness]]></category>
            <category><![CDATA[effort]]></category>
            <category><![CDATA[dont-make-me-think]]></category>
            <category><![CDATA[technology-and-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Dennis Hambeukers]]></dc:creator>
            <pubDate>Thu, 26 Apr 2018 07:29:41 GMT</pubDate>
            <atom:updated>2018-05-07T11:00:26.846Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*rN1rdUEQOVDnrKtnRyI6Qw.jpeg" /><figcaption>Source: statera.com</figcaption></figure><h4>Now that we have an app for everything, a lot of things are easier. The effort is taken out of a lot of our daily activities. But are our lives better? I believe effortlessness has a negative impact on our happiness. And the promise of effortlessness that is not fulfilled is one of the greatest irritations. Maybe understanding the dualities around effort and efficiency can help us design better technology.</h4><h3>Hurdles and quality</h3><p>A few weeks ago I was in a meeting with some people from <a href="https://usabilla.com/">Usabilla</a>. Usabilla is a user feedback tool. They introduced themselves as Customer Success Managers. You can dismiss this as newspeak, but I believe it puts people in a nice mindset of what their job is.</p><p>At first I was very critical about the user experience of the Usabilla tools. In my opinion they did not follow best practices when it comes to creating a good user experience for the end user. Their interface required too many clicks for my taste, putting to much cognitive load onto the user. As an exercise and a tool for discussion, I built a prototype of a new interface for their tool that reduced the amount of clicks of the user by 75%.</p><p>When we talked about my solution, they were impressed by the User Experience ingenuity. But in the discussion that followed I learned a lot about quality of feedback. Although they recognized the improved User Experience, my design allowed them to articulate their own philosophy to user feedback very clearly. They learned that slowing down the user a little bit, forcing them to think a little bit longer, requiring them to put in a little more energy resulted in higher quality feedback. Maybe some people will drop out of the feedback process because it takes to many clicks and requires to much effort. But their aim is quality, not quantity. They believe that for an organization to be successful, it is much better to have lower quantity in feedback and a higher quality.</p><p>This also ties back into their job titles of Customer Success Managers: their end goal is success of the organization that uses their tools and the best way to do this is by quality feedback. And there are also other feedback tools in the market place that might have a focus on high quantity. So their positioning is clear.</p><blockquote>“In our complex world, efficiency should not be the ultimate goal.” — General Stanley A McChrystal, Team of teams</blockquote><p>I quite like the idea that introducing some hurdles to activities increases the quality of the work. This is the opposite of mainstream User Experience thinking. Normally we think that reducing hurdles creates more quality, but slowing down can sometimes be more helpful then rushing through things. It has to do with the attention we give to things, the focus.</p><h3>False promises and irritation</h3><p>Modern technology holds a promise. It promises to make our tasks easier. And this is true. A lot of tasks that took our parents or grand parents a lot of effort are now effortless. Because of that our productivity is much higher. A lot of tedious tasks are automated and other task don’t take as much effort. The effort that is reduced is on many levels:</p><ul><li>the tasks take <strong>less time</strong>,</li><li>we <strong>don’t have to think</strong> about them so hard and</li><li>our <strong>performance</strong> is measured immediately.</li></ul><p>When my father had to look up information, he had to go to the library, search though a cabinet of index cards, go though several books and write down the information on a piece of paper. Now we can do a Google search and the result is presented to us in a fraction of a second:</p><blockquote>About 2.680.000.000 results (0,45 seconds)</blockquote><p>Google even has algorithms in place that tell you which of the 2.7 million results is the best. It’s fast, you don’t have to think and performance indicators are at the top of your screen. But what if you can’t find what you are looking for? What if your search query requires you to go through pages and pages of search results and then you still don’t find it? You never learned how to do complex queries and never studied document and knowledge management strategies. You are unable to formulate and execute a complex search strategy. You are unable to tap into the advanced features of the Google search bar. The promise of easy is broken. You get irritated. To top it all off, you are in a bubble controlled by algorithms that determines what information you can and cannot find.</p><h4>Failing in the UX game</h4><p>Similar false promises and irritations apply to bad UX. The UX expectations bar on modern applications has risen dramatically over the last years. We expect every app to work effortlessly and be perfectly tailored to our personal needs at any particular time. Big corporations spend a lot of time and money on creating engaging User Experiences, because that is where the battles of competitive advantages are waged and won today. Everybody expects Google-level-of-search on each website and application, Netflix-type-of-personalization and Zappos-type-of-service levels of each technology. But this is difficult. This involves doing user research right, asking the right questions, letting go of your cherished assumptions, pushing design best practices to the next level, matching design specs to back-end systems, engaging stakeholders, building a business case, restructuring your organization, etc. This is extremely complex and very difficult to get right. A lot of companies are in this game, but not all succeed. The market share of Apple is built largely on their excellence in getting the UX right, but it also has cracks. We have grown to expect so much, that it’s becoming impossible to live up to our standards. There is so much irritation when things are not perfect.</p><p><em>I once heard a story about Wifi on airplanes. It was a story about the first time an airline was able to put Wifi on a plane. They announced it at the beginning of the flight. People were over the moon with happiness. They were relieved from the strain of not being able to read their Facebook time during flight. They were in heaven. People started to applaud, shout and cry of happiness. 4 minutes later the Wifi crashed and never gut up during the flight. People were devastated. This was the worst airline ever, they were robbed, they asked for their money back and trashed the airline on social media once they landed and got their Wifi back.</em></p><p>That is how quickly our expectations shift from being exited in heaven to being irritated because we feel entitled.</p><p>It’s a tightrope. <strong>Expectation management</strong> is tough. And when marketing comes into the game, it gets even more difficult to live up to expectations. Marketing lives of off inflated expectations.</p><h4>The value of effort</h4><p>The story we live in is that technology is going to make everything quick and easy. Technology is going to take over more and more. Our narrative is made up of the idea that there should be an app for everything, that AI and robots will take over more and more of the tasks that take us a lot of effort. What doesn’t fit into this story is that idea of putting effort into something leads to more focus, satisfaction and happiness. Technology is helpful in a lot of areas, but it also disconnects us from the reality we live in. More and more people are spending more and more of their time in the virtual reality. The Matrix is becoming reality. We are moving away from the here and now. And research shows that this is not making us happier. All the comfort and all the ease make people feel empty and disconnected. The privacy we gave up didn’t give us in return what we expected. We want a lot of things, but are more and more unwilling to do what it takes to get it.</p><blockquote>“Everyone wants to go to heaven, but nobody wants to die.” — Unkwown</blockquote><p>I for one started an experiment last year. I started to introduce more and more discomfort into my life. Basically I’m taking the long hard stupid approach to more and more things. And it turns out that the more long, hard and stupid things I do, the more fulfilling my activities become, the more focus I have, the more connected I become. I’m not here to recommend this to anyone. I just want to point to the other side of effortlessness. If we look at things from a happiness point of view, less effort doesn’t necessarily lead to more happiness. Especially if we look at things on the long run. There is a difference between short term joy and long term fulfillment. When you start to think about it, there are a lot of things that lead to short term joy but to long term emptiness.</p><blockquote>“But ease isn’t the goal; excellence is.” — Ed Catmull, Creativity Inc.</blockquote><h4>How we should design</h4><p>If we agree on the value of effort, the question is how can we incorporate this into design. If think there are a couple of things you can do:</p><ul><li><strong>Incorporate</strong> <strong>speed bumps</strong> into your flow. If every step is fast and easy you loose focus and attention. To some things you don’t want to pay attention, but to some you do. Sometimes an extra click serves a purpose.</li><li><strong>Add a little slowness</strong> to communicate security and trust. Some processes in apps have complex back end processes that should be handled with care. Even if you are able to present the user with immediate results of their action, taking some time to show them the result can tell them that you take the security in their process seriously.</li><li><strong>Making task a little difficult </strong>to raise engagement. I once read a study about Facebook likes. The researchers compared like buttons on webpages to posting something on Facebook the long, hard, stupid way: copying the link from you browser / opening Facebook / then pasting the link to create a post. Not surprisingly the people who took the long road were far more engaged and were far better ambassadors then the “cheap” clicks on a like button.</li></ul><h3>Walk the extra mile</h3><p>If you want to engage people on a deeper level, it’s okay to ask a little bit more of them. Just like people are willing to walk an extra mile for a better cup of espresso, people are willing to click an extra time if they really dig your service. Extra clicks have to make sense of course. Eliminate all unnecessary actions and focus on meaningful actions. I’m all for simplicity, but it mustn’t become a fetish, a KPI. If people have to put in a little extra effort, their fulfillment will be higher as well. When you have to walk that extra mile to your favorite espresso bar, the effort and engagement alone will make the coffee taste much better. If you take a shortcut and use the time you save to do something meaningful and fulfilling, that’s cool. But if you spend your days taking shortcuts to other shortcuts, that probable won’t lead to heaps of happiness.</p><h4>A little thinking</h4><p>There is a classic book all User Experience Designers should read called <a href="https://www.amazon.com/Dont-Make-Me-Think-Usability/dp/0321344758">Don’t make me think</a>. It’s a book on usability and tells you to eliminate all unnecessary interactions. It doesn’t tell you how to create meaningful interactions. Stopping and thinking once in a while can also be useful, even on the web.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10ad50c127b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-notebook/did-technology-make-us-happier-10ad50c127b7">3 ways to design if your aim is not ease but excellence</a> was originally published in <a href="https://medium.com/service-design-notebook">Service Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why tools and diagrams are detrimental to your creative problem solving capacity]]></title>
            <link>https://medium.com/service-design-notebook/why-tools-and-diagrams-are-detrimental-to-your-creative-problem-solving-capacity-a68cc0b831c4?source=rss----82eab1ca5829---4</link>
            <guid isPermaLink="false">https://medium.com/p/a68cc0b831c4</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[strategic-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[diagrams]]></category>
            <dc:creator><![CDATA[Dennis Hambeukers]]></dc:creator>
            <pubDate>Fri, 30 Mar 2018 09:08:56 GMT</pubDate>
            <atom:updated>2018-05-18T10:50:17.065Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gSLYMaq_iq1MwrLulWSYpQ.jpeg" /></figure><h4>I love Service Design, but I don’t use a lot of tools. That might sound like heresy to a lot of Service Designers, but it shouldn’t. To much focus on tools and diagrams turns Service Design into something instrumental. It suffocates three important strategies for innovation.</h4><p>I once met a Design Thinking student that carried <a href="https://www.amazon.com/Design-Thinking-process-methods-manual/dp/0988236249">a book of more than a hundred tools</a>. She treated it like her bible. For her Design Thinking equalled tools. That was how it was taught to her in school. Also the book <a href="http://thisisservicedesignthinking.com/">This is Service Design Thinking</a>, that was one of the first books to explain the field of Service Design, consists mainly of tools.</p><p>If you see Service Design and Design Thinking as a collection of tools, it’s easy. Easy to learn, easy to apply. Anyone can do it. Which is cool. Service Design and Design Thinking are hot and it lowers the barrier of entry. The problem however is that these tools all work. They produce results. If you do a creative exercise, if you fill in a diagram together or crack open a box of lego, you arrive at ideas, solutions and directions. And any ideas, solution or directions might be better than none at all. But it’s important to realize that you are not operating in reality. You are solving problems within the boundaries and mindset of the tool you are using. Just as an IQ test doesn’t measure how smart you are, but how good you are in taking IQ tests, solving a problem in a tool is not solving a problem in reality. This means that if you use a tool, you arrive at a solution that works in the tool. Any tool and diagram is an abstraction of reality, only showing you a part or maybe a different reality all together. They can be used to uncover new insights, but the translation to reality is the hardest part. You have not solved a problem in reality. The distortion of your view of reality and the real problems therein is detrimental to your problem solving capacity.</p><h3>Creativity killers</h3><p>Most tools and ready-made diagrams force you into a straight jacket that will suffocate creativity. Your problem solving capacity revolves around three things that are killed by tools and diagrams:</p><ul><li><strong>Connection to reality is lost.</strong> As stated above, you want to solve problems in reality, not in your diagram. What might work in your diagram, might not work in reality. Reality is far more complex than your diagram and staring too long at it blinds you from the complexity of reality in which your solutions have to perform. It also blinds you from the possibilities and ideas that reality can provide. You become deaf to the solutions that reality can hand you.</li><li><strong>Improvisation is boxed out.</strong> Tools and diagrams have strict rules. To use them means to abide by their rules. They only work if you follow the rules. These rules might pull you out of your comfort zone far enough to get some new ideas. But they allow little room for improvisation, coloring outside the lines, play. This is the fabric creativity is built from. Filling in a diagram or using a tool usually boxes in any improvisation. And improvisation and playing around is the best way to discover new solutions that work.</li><li><strong>Intuition is suppressed.</strong> Buddhists refer to the rational mind as the “small mind” and intuition as the “big mind”. Intuition is far more creative than ratio. Anyone who relies on his creativity knows they have to foster their connection to their intuition. Tools and diagrams most often put you in a rational state from which it is very difficult to access and thus develop your intuition.</li></ul><h3>There is another way</h3><p>Using a lot of tools and diagrams is a valid way to practice Service Design. I believe it is important to realize the limits and dangers of them. I also occasionally use them, but I am following a different path. My strategy is to stay as close to reality as possible. I found that if you are able to talk to real users and work with prototypes as soon and long as possible, you are creating an environment where the three strategies for creative problem solving I mentioned above can flourish.</p><p>It’s hard to disagree with a diagram. It has its own rules and it operates on a level of abstraction in which it’s hard to see flaws. It’s easy to argue with a prototype. Anyone can understand it. Anyone can reverse engineer what is needed to get there. Anyone can make a suggestion on how to improve it. And you can test it easily in reality. Diagrams and tools have a lot of assumptions baked into them that you might not see. And assumptions are the enemy of good solutions. You want to test your assumptions as soon as possible. I use a Lean Startup approach to Service Design. Build, measure, learn. You can learn a lot more from a prototype than from a diagram. It’s much easier to communicate about a prototype than about a diagram. It’s much easier to involve and inspire people with a prototype than a tool. It’s much harder to provide a false sense of security with a prototype than with a tool.</p><h3>Ripple effects</h3><p>The effect something has is much more important than the thing itself. I think it is important to think about the ripple effects of diagrams and tool. To think about what mindset and culture they create in a project, what image of reality and the process. I have seen to many occasions where diagrams put the project members in a mindset that limits their creative problem solving potential more than it enhances it. I have seen to many occasions where people are very happy that they used a tool to come to a solution that is to hard to translate into the reality in which it has to live. The initial excitement has a tendency to die quickly with this approach.</p><p>Maybe my one tool approach (just prototype and talk to people) is too extreme and also has its downsides, but drowning in hundreds of tools and diagrams is the other extreme. Mastery of the Service Design tools to me means not only knowing how to fill out a the next cool canvas, but to know what the ripple effects on the problem solving capacity, quality of solutions and long term engagement of stakeholders are. Studying the limits, power and effects of any tool, diagram or solutions is the core of strategic design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a68cc0b831c4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-notebook/why-tools-and-diagrams-are-detrimental-to-your-creative-problem-solving-capacity-a68cc0b831c4">Why tools and diagrams are detrimental to your creative problem solving capacity</a> was originally published in <a href="https://medium.com/service-design-notebook">Service Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your diagrams are not innocent]]></title>
            <link>https://medium.com/service-design-notebook/your-tools-are-not-innocent-a8c71aaab47e?source=rss----82eab1ca5829---4</link>
            <guid isPermaLink="false">https://medium.com/p/a8c71aaab47e</guid>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Dennis Hambeukers]]></dc:creator>
            <pubDate>Thu, 15 Mar 2018 09:59:00 GMT</pubDate>
            <atom:updated>2018-03-15T11:34:23.789Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xTtPSNlrHUAOJfbTlcTrHQ.jpeg" /></figure><h4>One of the things approaches like Service Design and Design Thinking introduce is new tools. These tools are more visual and easier to use. Therefor they enhance communications between all stakeholders. For a long time I thought that the communications aspect of these tools were the largest benefit. That all changed when I was confronted with traditional business/IT analysis tools in a project again. I hadn’t seen these tools being used in projects for a long time. But when I did I realized that the biggest benefit of Service Design tools lies in the mental image and mindset they create.</h4><p>I love tools and diagrams. When I was studying IT, making Data Flow Diagrams, Entity Relationship Diagrams and State Transition Diagrams was one of my favorite things. Making a diagram forces you to think deeply about processes, relationships and structures. They are abstractions you force onto reality to see things that you might otherwise miss. They deconstruct reality into the smallest elements and their relations. They provide a mental model to understand, to analyse and to solve. Apart from all that, they are necessary first steps towards the functional and technical design that is needed to build IT applications. The diagrams are of benefit to the business (to analyse) and to the IT developers (to start specifications). This makes them the ultimate tool for business consultants working in IT.</p><p>At least until Service Design and Design Thinking started introducing new tools. A lot of IT projects just don’t “work”. They have trouble creating real value to users, have very limited room to incorporate progressive insights during a project and always end up costing more than is good for you. And I think a lot of these problems are a direct result of the tools that are used. It’s important to realize that the tools you use are not innocent. With the benefits also come downsides. Some of the downsides of traditional diagrams are actually starting to hurt more than they help.</p><h3>The technocratic mindset</h3><p>The first and biggest downside of traditional analysis tools is the mindset it gets you in. Because the diagrams are so abstract, so technical, they put all the people interacting with them in a technocratic mindset. That might seems the logical mindset to be in in an IT project, but that is a misconception. If IT projects are about IT, they are going to fail. IT projects should be about people. They should about how people work, how people interact and in what state of mind people should be while they do that. If you focus on those things, value creation, performance and risk management follow naturally. If you don’t, these things become problems you need to solve in your project.</p><p>I learned about the prison of the technocratic mindset in a recent project I did. The project started in true Service Design fashion with user research workshops and prototyping. But when we had a design for the new service, a traditional IT development company came in with their business analyst. He cranked out his traditional IT analysis diagrams and tooling. At first I thought that was a good idea. I loved these tools in school, so I thought that they might be a nice addition to the project and the Service Design toolkit. I was wrong. It forced the whole project into the left side of the brain, into the technocratic realm. Because these diagrams and tools have their proven track record and seem to fit naturally into IT projects, they come with a certain “logicalness”. They quickly seem like the right thing to do. It’s hard to argue with them, also because they are needed to make the specifications for the programmers later on. The problem arises when you see the user experience, service quality and engagement you built up in the project evaporate. The challenge then is to try to bring those things back. Then you see all the things that are lost and how the diagrams form a huge obstacle to bringing these things back:</p><ul><li><strong>User centered design becomes more difficult</strong>: it’s much harder to keep the focus on the user. The user is not in the diagrams. He might be in some of the boxes or swim lanes, but he is drowning in business processes and back end systems. When you stare at diagrams, you don’t see what the user sees. And because the user is just one of the many parts in the whole system, he is more easily lost.</li><li><strong>It’s harder to make IT projects about people</strong>: not only the user gets lost, but also the people working on the delivery of the service. In diagrams, all elements are just parts of a system. In a diagram, all parts are equal. In diagrams, there are no people. So if you stare at them long enough, you have a much harder time seeing the people. You get into a systems view mindset that makes it harder to value people over IT.</li></ul><h3>The blindness</h3><p>One of the crucial elements of a project is to focus on the right things, doing the right things. You want to see what the issues are that need addressing. In diagrams, you don’t see these things. In a project you want to discover the right questions. If you don’t analyse and work with the actual matter, interfaces and interactions in the case of IT projects, it’s really hard to find the right questions, to learn from the designs you made. It’s really hard to see mistakes in diagrams. In a diagram everything looks logical, looks right. The simple fact that something is in a diagram, gives it an aura of logical, of right. But all diagrams are abstractions, they only show you a small part of reality and in a distorted way. You can use that to analyse, but if you put to much faith in it, it’s distorted, limited view of the world will make you blind. Blind to opportunities, blind to mistakes, blind to false assumptions.</p><h3>The i<strong>nflexibility</strong></h3><p>Diagrams are also incredibly inflexible. They might not look like that at first. Especially if you have good tooling. You can move boxes around, draw new arrows and stuff like that. You can change diagrams in tools. The problem however is overview. If diagrams become complex, and they will become complex in any IT project, they become hard to read. It’s really hard to keep a mental image of a really complex set of diagrams. The solution could be to also include higher level diagrams, but that just adds to the inflexibility because of the need to change things in multiple places. Diagrams show relationships between things, but these relationship are so abstract that you always need to do mental steps in your head to check for dependencies and other implications. Where making a diagram might seem a helpful exercise at first, changing a complex diagram is a recipe for diaster. If you want to change something in the service, you first have to locate the elements and relations that are affected. Then have to figure out how to change them and all the implications the change has to the rest of the system. Here the layers of abstractions and complexity start to quickly become detrimental.</p><h3>The complexity</h3><p>One of the challenges of larger IT projects and services is dealing with complexity. Complexity puts a strain on decision making, communication and engagement. When diagrams become complex it’s hard to see the issues and solutions. It also becomes hard to talk about things. Especially when you are a stakeholder that only comes in once in a while: you quickly loose overview and understanding, it’s hard to spot changes. And when the complexity of the problem is only enhances by the complexity of the diagrams, people have a harder time engaging in a project.</p><h3>The communication issues</h3><p>The confrontation with traditional diagrams and analysis tools showed me the enormous power of the Service Design and Design Thinking tools. It’s not just about communication. They offer a total reframing of what IT projects should be about. They put people involved in totally different mindset. They analyse the problem in a totally different way. I also found that it is really hard to keep the Service Design mindset in a project once you introduce traditional tools and thinking. I even wonder if they can coexist. In other projects where traditional IT tools were used, they were more invisible to non-IT project members and that worked better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8c71aaab47e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-notebook/your-tools-are-not-innocent-a8c71aaab47e">Your diagrams are not innocent</a> was originally published in <a href="https://medium.com/service-design-notebook">Service Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design thinking is a mental revolution]]></title>
            <link>https://medium.com/service-design-notebook/design-thinking-is-a-mental-revolution-684c5cfe3e66?source=rss----82eab1ca5829---4</link>
            <guid isPermaLink="false">https://medium.com/p/684c5cfe3e66</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[revolution]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Dennis Hambeukers]]></dc:creator>
            <pubDate>Sat, 17 Feb 2018 07:45:23 GMT</pubDate>
            <atom:updated>2018-02-17T07:45:13.426Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nkARDRVDJaB9bKN0Po53-g.jpeg" /><figcaption>Source: Zybra</figcaption></figure><h4>Design thinking requires no technological breakthroughs and no development of new skills. It is a purely mental revolution. Design thinking is not post-its and lego bricks. Design thinking is making anything concrete that people can use to uncover the fundamental questions of a problem for the purpose of solving those problems quicker, cheaper and faster.</h4><h3>The value proposition</h3><p><strong>Design thinking enables people to think more creatively and connect better to the creative powers of others to enhance the overall problem solving capacity of a group of people.</strong> There are many different types of design thinking. It vary from a simple, crude sketch on the back of a napkin in a meeting in a restaurant to a hi-fi prototype of a new motorcycle on a motorcycle show. Anything concrete that organizes your own thoughts in a new way and lets you connect to other people with clarity and conviction is design thinking. The goal of design thinking is not to design a solution, that is design. The aim of design thinking is to find the right question. That is the really hard part of creative problem solving and innovation. Once you have found the right question, the answer is relatively easy. The answer can be designed.</p><h3>The trick</h3><p>The trick that design thinking uses to find the right question is a reversal of traditional thinking. Traditional thinking tries to think through the question and then come up with a solution. <strong>Design thinking turns things around. </strong>Design thinking starts coming up with solutions quickly to learn about the problem and to uncover the right question that needs answering. Design thinking doesn’t spend too much time trying to get a complete picture of the problem before getting into solutions because it knows that this is not an effective way to solve problems. Trying to get a complete picture of a problem before designing solutions involves abstract discussions based on incomplete information, opinions and previous or analogous solutions.</p><p>Abstract discussions:</p><ul><li>allow people to talk about different things while they think they talk about the same,</li><li>allow more space for personal opinions that are not necessarily rooted in reality,</li><li>exclude people who do not master the jargon.</li></ul><p>And innovation is the opposite of using solutions you already know.</p><h3>The process</h3><p>Design thinking makes things concrete first and draws lessons second. <strong>Design thinking starts designing before you think you are ready.</strong> It acknowledges that the information is incomplete at the start of a project. But it doesn’t make decisions on that incomplete information, but makes designs to uncover more information. It uses this new information to enhance the design and keeps on doing this. The cycle never stops. Design thinking recognizes that innovation doesn’t happen in one big bang, but in small iterations. When a solution is implemented, this is the beginning of a new cycle. Implementation offers the chance to learn from actual use that can feed back into the solution. The most important learnings are new and better questions you uncover.</p><h3>The effect</h3><p>Design thinking has a couple of effects that contribute to the performance of a project or organization. It starts with individual creativity. And its aim at finding the right questions adds performance. There is nothing so ineffective as finding fabulous answers to the wrong questions. Because it creates focus and links people’s minds, it adds even more to the performance. And finally it is more fun, more human than the traditional methods. The engagement that this creates is the fourth performance booster. There is a meme going around that if you want a project cheaper, faster and better that is not possible. Well, <strong>design thinking is a universal medium of communication that enables people to get to better solutions faster and cheaper</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=684c5cfe3e66" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-notebook/design-thinking-is-a-mental-revolution-684c5cfe3e66">Design thinking is a mental revolution</a> was originally published in <a href="https://medium.com/service-design-notebook">Service Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The difference between wanting and needing: the biggest philosophical question of our time]]></title>
            <link>https://medium.com/service-design-notebook/the-difference-between-wanting-and-needing-the-biggest-philosophical-question-of-our-time-94affe0aefac?source=rss----82eab1ca5829---4</link>
            <guid isPermaLink="false">https://medium.com/p/94affe0aefac</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[bad-habits]]></category>
            <category><![CDATA[philosophy]]></category>
            <dc:creator><![CDATA[Dennis Hambeukers]]></dc:creator>
            <pubDate>Sat, 10 Feb 2018 16:43:00 GMT</pubDate>
            <atom:updated>2018-02-12T08:11:43.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pxooHbSmqYDin-wl8CDCcg.png" /><figcaption>The “I want this weeks” campaign of Tele2.</figcaption></figure><p>Yesterday evening I was sitting on the couch with my wife. We wanted to watch a movie together. After going through some trailers on the iTunes store, we decided to go for a romantic comedy. We watched “<a href="http://www.imdb.com/title/tt6964966/">Valentine’s again</a>”. On the surface this looks like a female version of “Groundhog day”. A woman who has trouble finding a mate, is put under a spell to relive Valentine’s day over and over until she finds her perfect life partner. What started out as a mind numbing badly acted B movie turned into a story about one of the most fundamental philosophical questions of our time. The woman that put the main character onder the Groundhog-day-spell told her that she could only find the perfect life partner if she stopped thinking about what she wants and starts paying attention to what she needs. The difference between our wants and needs is a quintessential question. Not only for the field of Service Design, where you can have far more impact and create far more value if you provide what people really need instead of what they want. But also in a larger context of our lives, the planet, our future.</p><h4>We know what’s good for us, but why don’t we act accordingly?</h4><p>This theme is what also stuck with me from this years two traditional new year’s conferences on Dutch TV. Both conferences were very different, but they shared one theme. They both talked about how we know we are doing all the wrong things that are destroying our health and our planet, but we still continue. We know going on a holiday by plane is ruining the planet, but we still do it. We know that if we eat too much sugar we wil get ill, but we still do it. We know that spending too much time on Facebook is detrimental to our mental health, but we still do it.</p><h4>Why do we want this?</h4><p>It might me just me, but this tension between knowing what is good for us (what we need) and wanting all kinds of things we know are not good is approaching a peak. My son is at an age where he starts questioning things. He asks himself (and me) questions like: “Why do I want this?”. If you look at this in a systems thinking way, you see that there are all kinds of elements in play that tap into all kinds of human weaknesses. On a mental level there are elements of status anxiety, group pressure, wanting to belong that make us do things that are not good for us. We believe in stories about successful and good life that were made up by people who are in it for the money. But also on a physical level there are basic human mechanisms that we brought with us from times when the human race as we know it evolved. The sugar, fat and salt additions we developed all stem from a time when these goods were scarce and binging on them had a purpose for our survival. Our physiological system is not well adapted to the abundance we find in our stores today. These are just some examples. I think we all instinctively know what is good and what is not good.</p><h4>What’s the role of business?</h4><p>Many of our bad addictions are created by businesses. Consumerism is a corporate invention. Creating a want for something we don’t need is a craft. It’s called marketing. Our addiction to sugar feeds huge corporates in multiple industries. But business is also where my hope lies. In my Service Design work I see that catering to real needs is far more valuable than satisfying wants of users. More and more organizations are waking up to this fact. Helping people with real needs is a more sustainable business model than feeding addictions and tapping into weaknesses in human nature. This week I heard about Facebook changing its algorithms to better serve humanity. More and more people are comparing the Facebook feed to smoking. One of the risks threatening the future of Facebook is that more an more people are considering their Facebook addiction as a bad habit that has a negative impact on their lives. More and more people wake up to the fact that Facebook is deliberately designed to make you addicted by tapping into basic human weaknesses. More people see that Facebook taps directly into the chemicals released in your brain with their status updates, likes and mentions to force feed you advertisements and other useless information. More and more people realize that the medium Facebook is not as innocent as it seems. It changes your behavior and perception of reality. Apparently Marc Zuckerberg realizes this threat and announced a major overhaul of Facebook’s News Feed algorithm that would prioritize meaningful social interactions over relevant content, one week after he <a href="https://www.theguardian.com/technology/2018/jan/04/facebook-mark-zuckerberg-new-years-resolution">pledged</a> to spend 2018 “making sure that time spent on Facebook is time well spent”.</p><h4>We have a choice</h4><p>I believe the difference between what we want and what we need is one of the fundamental questions of our time. We have a choice here. In our own lives, but also in business. If Service Design is done well, it uncovers user needs instead of wants and builds services on top of that. Those services will sustainably add more value. That is good business. So I would like to add something to one of my favorite business quotes from Thomas Watson Jr, “Good design is good business.”. I think the quote for our time should be:</p><blockquote>“Good ethics is good business.”</blockquote><p>Maybe in the future we’ll see more products that fill our needs instead of the campaigns like Tele2 is running (see image on top), which seem to solely focus on satisfying our wants. Understanding deep human needs will help us more than cleverly playing into our superficial wants.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94affe0aefac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-notebook/the-difference-between-wanting-and-needing-the-biggest-philosophical-question-of-our-time-94affe0aefac">The difference between wanting and needing: the biggest philosophical question of our time</a> was originally published in <a href="https://medium.com/service-design-notebook">Service Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Failing to learn in the Design Sprint]]></title>
            <link>https://medium.com/service-design-notebook/failing-to-learn-in-the-design-sprint-3c7fe91254bd?source=rss----82eab1ca5829---4</link>
            <guid isPermaLink="false">https://medium.com/p/3c7fe91254bd</guid>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[sprint]]></category>
            <dc:creator><![CDATA[Dennis Hambeukers]]></dc:creator>
            <pubDate>Wed, 31 Jan 2018 20:20:44 GMT</pubDate>
            <atom:updated>2018-02-05T20:49:30.040Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*87ez8A-TjNE2J2j6slTs1A.png" /></figure><blockquote>“The only way to truly learn something is by doing.“— Naval Ravikant in Tribe Of Mentors</blockquote><p><strong>If anything, the Design Sprint method from Google Ventures is a tool for learning.</strong> The subtitle of the SPRINT book is “Solve big problems and test new ideas in just five days”. I think this is a little misleading:</p><ul><li>Big problems are not solved in five days.</li><li>And new ideas can be tested in less days with less people.</li></ul><p>So on the one hand the subtitle is way to big and on the other hand way to small. As the Design Sprint is just a tool, a method, an approach, it is only as good as the reason you use it and the things you do with its outcomes. Clearing agenda’s and working together for 5 days with a group of around 8 people is a big investment so expectation management is crucial. Not only before, but also during and after the Design Sprint. If you are coming into the Design Sprint believing you are going to solve big problems, you might get disappointed. If you just want to test new ideas (that you already have?), I would suggest a simple(r), standard usability test. When you think you will have a prototype that is ready for development at the end, you missed the whole point.</p><h3>The link between big problems and testing ideas</h3><p>The big problems that need to be solved and the testing of ideas are linked. Understanding this link is understanding the essence of the Design Sprint. To understand this link you have to understand the two main concepts on which the Design Sprint is built:</p><ul><li><strong>Design Thinking</strong>. This approach uses the fact that you can learn about a problem by doing, by making possible solutions. You know your first solutions will not be the best solution, but by failing, you learn and improve. So you learn by doing. On top of that, making things enables you to better communicate with stakeholders. You let concrete objects and others be your teachers.</li><li><strong>Lean Startup</strong>. This basically uses the same iterative approach as Design Thinking, but looks at this proces with scientific rigor. This allows you to improve the questions you are asking. It is aimed at testing your assumptions. You identify them and then think of a way to test them. The learning is directed at the assumptions that you have in your head that are keeping you from seeing the best solutions.</li></ul><p>Both approaches use learning by doing as their main problem solving method. They don’t break down the big problems into smaller ones. They tackle the whole beast as a whole, but they do so one step at a time. Each step is both a solution but equal parts a way to learn. If your solutions works, you take one step further in that direction. If you solutions doesn’t work, you take one step further in a different direction. In the end you will arrive in the place you need to be. Wherever that is. You do and learn.</p><h3>What’s next?</h3><p>Learning is also the goal of a Design Sprint. At the end of the SPRINT book, the authors say “At the end of the Sprint you know what to do next.”. You have knowledge and that knowledge will help you on your way to solving that big problem. The big problem will not be solved, but if things go well, you will have had a breakthrough. You will have gathered valuable insights. Actionable insights. You will have tested ideas. But not to see if they work, but to learn about what how-and-if-they-work can teach you about the big problem you have to solve. The ideas you tested are not nearly as valuable as the things they can teach you about your big problem. Ideas are easy. Any old brainstorm session will produce lots of them. But co-created, co-owned ideas that are crafted to answer specific questions, turned inside-out by the Sprint Team and fed by external experts are far better ideas. And the reactions to those ideas are far more actionable.</p><h3>Learn to learn</h3><p>If you fail, you learn. But the learning itself is not so easy. To identify what you have learned and how those learnings can be put into action is not so easy. Everyone looks at the Sprint with their own eyes. Everyone learns something else. Sharing the learnings and making the next move is crucial. The period after the Sprint is a tough part. The Design Sprint and all the things you have to do are laid out in the SPRINT book. But what to do after the Design Sprint is not in the book. You have to turn the learnings into action while they are hot. This takes time and energy and creativity. Not everyone is in a learning mindset, not every organization is a learning organization. I think learning needs to be learned. Just like in school: you learn about things, but you also learn to learn. In organizations this is not so evident, there is not so much space. To me the Design Sprint is about learning about your big problem, but also about learning to learn. If you don’t learn to learn, you fail to learn and the Design Sprint as a tool is not as useful as it could be.</p><p>I for one am still learning. The Design Sprint to me is a super powerful way to learn about lots of things.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c7fe91254bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-notebook/failing-to-learn-in-the-design-sprint-3c7fe91254bd">Failing to learn in the Design Sprint</a> was originally published in <a href="https://medium.com/service-design-notebook">Service Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design thinking werkt, maar hoe?]]></title>
            <link>https://medium.com/service-design-notebook/design-thinking-werkt-maar-hoe-6fc08fa948e?source=rss----82eab1ca5829---4</link>
            <guid isPermaLink="false">https://medium.com/p/6fc08fa948e</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[impact]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Dennis Hambeukers]]></dc:creator>
            <pubDate>Thu, 25 Jan 2018 16:04:42 GMT</pubDate>
            <atom:updated>2018-01-25T16:21:07.181Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In de laatste editie van de </em><a href="http://bno.nl/abonnementen/dude"><em>DUDE</em></a><em> van de BNO staat een interessant stuk van </em><a href="https://twitter.com/jeroenjunte"><em>Jeroen Junte</em></a><em> over de impact van design. Zijn stuk inspireerde deze reflectie.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TGBfBxZTn4RCfGYlMMSEcQ.jpeg" /><figcaption>Het artikel van Jeroen Junte in de DUDE</figcaption></figure><p>Design thinking, en daarmee design, zit in de lift. Geïnspireerd door succesverhalen uit Silicon Valley en ook steeds meer in eigen land, investeren steeds meer bedrijven in design. Traditionele IT and management consultancy bureaus kopen design bureaus op om design kennis te integreren in hun diensten. De mogelijkheden voor designers om impact te hebben lijken toe te nemen. Designers krijgen de kans om aan tafels te zitten waar ze voorheen geen toegang tot hadden. Het interessante is dat deze nieuwe belofte van design zorgt voor een tweedeling onder designers. De ene groep springt in de nieuwe ruimte die er ontstaat voor designers and de andere groep vindt dit maar raar gedoe allemaal.</p><p>Om gebruik te maken van de nieuwe mogelijkheden die er ontstaan voor design — nu traditionele aanpakken voor innovatie en problemen oplossen beginnen te kraken — moet design, de designer zich namelijk aanpassen, zich zelf opnieuw definiëren. Om de impact te hebben die de nieuwe ontwikkelingen beloven, moet design zichzelf verbinden met andere vakgebieden. Design kan de meeste impact hebben als het uit haar bubble stapt en in samenwerking met andere disciplines aan de oplossing van problemen gaat werken. Embedded design is veel effectiever dan design vanuit de gesloten studio. De kracht van design ligt namelijk in de katalyserende werking die design kan hebben in projecten. Design kan processen en projecten versnellen, het probleemoplossend vermogen van groepen mensen vergroten en het risico van investeringen helpen te verkleinen. Dit kan alleen als design onderdeel is van het process. Dit kan alleen als de designer de grootte van zijn ego niet langer koppelt aan de schoonheid van zijn design, maar aan de bijdrage die hij levert aan de kwaliteit van de oplossingen en het proces.</p><h3>Wil ik dit?</h3><p>Veel designers vinden dit zweverig geklets. Dat snap ik ook wel. Deze impact van design is namelijk lastig te zien in tentoonstellingen of in magazines. Betere oplossingen die efficiënter zijn gecreëerd en die meer waarde toevoegen voor zowel klanten als de bedrijven zien er namelijk niet perse mooier uit dan andere designs. Aan de buitenkant kun je er niks aan zien. Het werk dat een designer doet om het proces van innovatie te verbeteren zie je niet aan de oppervlakte. Dat design ervoor heeft gezorgd dat projecten de juiste vragen oplossen en dat mensen beter samenwerken en met meer enthousiasme kun je niet zien aan de user interface. Maar die dingen hebben wel veel meer impact dan de dingen die in musea staan en die in design showcases staan. Die dingen hebben veel meer waarde voor bedrijven dan design awards. Die impact zie je in de KPI’s van bedrijven, in de Net Promotor Scores en in de Employee Satisfaction Indexes. Veel minder sexy, maar veel waardevoller voor bedrijven. De vraag is waar je je op wil richten als designer: wil ik dit?</p><h3>Kan ik dit?</h3><p>Daarbij moet je als designer snappen hoe dit in zijn werk gaat. Er zijn al designers die op deze manier waarde toevoegen. Deze designers hebben de mechanismen van projecten en strategieën in een business setting bestudeerd. Ze hebben ontdekt hoe de vaardigheden, mind- en toolset van designers waarde kan toevoegen in deze projecten. Ook al is dit misschien niet voor alle designers zichtbaar, het gebeurt al. Naast de moeilijkheid om dit werk te laten zien in tentoonstellingen, helpen de verhalen over hoe design de opwarming van de aarde en het oprukken van populisme kan oplossen helpen ook niet echt in de beeldvorming. Maar het feit dat dit onzinnige exercities zijn, betekent nog niet dat design geen grotere impact op de wereld en op de processen in bedrijven kan hebben. Met alleen visualiseren en dingen <em>voelbaar</em> maken komen we er ook niet. Als je de impact wil hebben waar het bij design thinking en strategic design over gaat te hebben, zullen designers zich moeten verdiepen in zakelijke processen, problemen en waarden. Dit staat ver af van de meeste designers, maar je kunt ook geen grote impact verwachten met een kleine inspanning. Er zijn geen afkortingen.</p><p>Mocht je hier wat meer over willen leren als designer, kijk dan eens naar de MOOCs van de TU Delft als “<a href="https://online-learning.tudelft.nl/courses/design-leadership-and-innovation/">Design leadership en innovation</a>” en “<a href="https://online-learning.tudelft.nl/courses/design-practice-in-business/">Design practice in business</a>”. Dat heb ik ook gedaan en kan ik van harte aanbevelen :) Lees ook gerust eens <a href="https://servicedesignnotebook.nl/design-leadership-and-innovation-4e5e2cd92d25">mijn eerdere blog</a> over wat ik leerde in deze MOOCs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fc08fa948e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/service-design-notebook/design-thinking-werkt-maar-hoe-6fc08fa948e">Design thinking werkt, maar hoe?</a> was originally published in <a href="https://medium.com/service-design-notebook">Service Design Notebook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>