<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chiara Torti on Medium]]></title>
        <description><![CDATA[Stories by Chiara Torti on Medium]]></description>
        <link>https://medium.com/@ChiaraTorti?source=rss-e9d9c06ae481------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*qF9xPmIYnXsP66yD.jpg</url>
            <title>Stories by Chiara Torti on Medium</title>
            <link>https://medium.com/@ChiaraTorti?source=rss-e9d9c06ae481------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:14:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ChiaraTorti/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[4 complaints you may encounter while proposing a Design Thinking approach and how to respond]]></title>
            <link>https://medium.com/eni-digitalks/4-complaints-you-may-encounter-while-proposing-a-design-thinking-approach-and-how-to-respond-df872458116?source=rss-e9d9c06ae481------2</link>
            <guid isPermaLink="false">https://medium.com/p/df872458116</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-culture]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <dc:creator><![CDATA[Chiara Torti]]></dc:creator>
            <pubDate>Fri, 02 Dec 2022 08:55:30 GMT</pubDate>
            <atom:updated>2022-12-02T08:55:30.463Z</atom:updated>
            <content:encoded><![CDATA[<h3>4 complaints you may encounter while proposing a Design Thinking approach and how to respond to them</h3><p><em>An experience from an in-house design studio and how to foster design methodology from the inside</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z9QPvup19Ainp3xCB-NtlA.png" /></figure><p>One of the challenges a designer could face is that after a pitch illustrating the design approach shaped for the specific brief the client asked us for, you won’t see happy and welcoming faces but silence and dumbfoundedness. <br>This situation is very familiar when as an in-house designer in a non-design corporation where the methodology is quite new and revolutionary, you approach your colleague-client to expose how you will like to collaborate with them during the job following the design thinking principles. On paper, when you explain those principles many managers agree with them, nobody will say to you that it is wrong to listen to final users to design a solution, but when those final users are in the team and you are asking to involve them in new activities such as workshops, the most common reactions we receive are as follows:</p><p><strong>1. “We don’t have time!”</strong> — the evergreen of excuses! One of the best explanations in every field and corner of the world since we were kids and our mum was asking you to tide up our room: we didn’t have time. I love this excuse because it gives me the chance to talk about one of my favorite benefits of design thinking: collaboration. It’s true that when you are asking to jointly have a team of people in one room (physical or digital) for a workshop session that at least lasts 2 hours in a traditional manager’s mind that is used to meetings, a long session required too much of their time. But workshops are not meeting, everyone is working at the same time to reach a common goal during a fixed time frame. Everyone is involved in the creation and knows what is happening in the room. It means that you won’t need other meetings to share the output and explain it. The team is already aware of the output and ready to go on with a buy-in.</p><p><strong>2. “I already know what to do, just do it”</strong> — some managers don’t see collaboration as a key element for a better result, but mostly as a time-consuming activity. But sharing is not just only caring, but it also ensures that, along the journey of the project, different nuances of the system are considered as a result of collaboration with different experts, who bring their own unique set of skills and experiences. The result will be for sure richer and more complete than a solo performance. Do you truly believe that a single person can have the knowledge and all the skills needed to solve the design problem alone? It is very unlikely to happen, and at the end of a long project journey, your users or key stakeholders could reject the project, or worse, sabotage it. Collaboration is one of the wise elements and assets to entrust a long and prosperous life to your projects.</p><p><strong>3. “It doesn’t need to be beautiful, it just needs to work”</strong> — this kind of complaint is typical when you are applying the methodology to improve internal processes that don’t have a customer-facing side. It makes me sad because it means that we, as employees, do not see the worth of having valuable solutions designed for us, around our needs and our context of work, that take into account usability. As customers we are exposed to beautifully designer products and services, so why do we set our expectations to lower results in a work environment? We deserve to work better, and it starts with us deciding to serve better ourselves. Usually, a well-designed internal product or service means less time spent understanding how to interact with it and concentrating on results and their quality. In a design project, beautiful is a concept mixing 3 different aspects: usefulness (it solves an actual need), usability (it is easy to interact with), and desirability (I will keep using it and promote it).</p><p><strong>4. “We are not creative people, you won’t have much from us”</strong> — the classic example of a bias that is not empowering people. Everyone could be creative if put in the right condition. Design Thinking and designers are there to facilitate the condition where everybody can feel confident in their creativity in an open and safe environment as workshops are designed for. <br>Those were the main excuses or biases we have listened to during years of practice and as an in-house design studio we constantly operate to create the best environment possible for Design Thinking to be known and used as a key tool for transformation (digital and not) inside Eni. <br>If you are in a similar condition here are our two cents from our experience.</p><p><strong>If you are in a similar condition here are our two cents from our experience.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RKsAk7HkPTLOuusGAOaTZw.jpeg" /><figcaption>© <a href="https://stock.adobe.com/contributor/202206661/tierney?load_type=author&amp;prev_url=detail">Tierney</a> — stock.adobe.com</figcaption></figure><p><strong>Be colleague-centric:</strong> be humble and remember that everybody is different and has had a different life path within the company and works in a very diverse environment that is not just an office building. That should be valued no matter what. Listen to them and their complaints because they can give you hints and elements to find the best way to adjust your design approach without compromising on principles. You should be the first one to be creative and design the best approach possible for the specific colleagues you are facing.</p><p><strong>Arise awareness and share:</strong> any moment counts to talk about Design Thinking, its principle, and its benefits. You should structure formal moments to explain it through different corporate media and then use wisely the time you spend with businesses in meetings and workshops. At the beginning of each project use a few slides to explain the principles of the methodology and why you decided to apply it to that specific challenge. Be repetitive, during workshops too, and keep explaining the link with the methodology in every activity the team is facing.</p><p><strong>Education:</strong> it is useful to train colleagues on the methodology and its principles, so they know what to expect when involved in a design project. If you have a specific target of colleagues that are keen to use the methodology you can create a more practical course to give them tools to be independent on specific design thinking tasks.</p><p><strong>Feedback:</strong> the best way to understand how to improve the way you are spreading and using the methodology is to ask for feedback and be open to accepting them. Let’s then ask for feedback proactively, to understand what worked and what didn’t, so we can gather insight and have a sentiment on how to adapt and change our work to better serve our colleagues.</p><p>In conclusion, spreading and adopting the methodology in a big company is not an easy challenge and we, as designers, should embrace it with patience and humbleness. Give yourself goals and define a roadmap of activities to reach them, but be flexible to change while working with your colleagues to find the best way forward for the specific environment you are working in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df872458116" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eni-digitalks/4-complaints-you-may-encounter-while-proposing-a-design-thinking-approach-and-how-to-respond-df872458116">4 complaints you may encounter while proposing a Design Thinking approach and how to respond</a> was originally published in <a href="https://medium.com/eni-digitalks">Eni digiTALKS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>