<?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 Matteo Cavucci on Medium]]></title>
        <description><![CDATA[Stories by Matteo Cavucci on Medium]]></description>
        <link>https://medium.com/@MatteoCavucci?source=rss-3a3941635fa1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_lScj9d56FiNhu_L.jpeg</url>
            <title>Stories by Matteo Cavucci on Medium</title>
            <link>https://medium.com/@MatteoCavucci?source=rss-3a3941635fa1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:20:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@MatteoCavucci/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[Do designers dream a digital factory?]]></title>
            <link>https://medium.com/@MatteoCavucci/do-designers-dream-a-digital-factory-a53258869cc2?source=rss-3a3941635fa1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a53258869cc2</guid>
            <category><![CDATA[codesign]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Matteo Cavucci]]></dc:creator>
            <pubDate>Fri, 02 Sep 2016 15:12:45 GMT</pubDate>
            <atom:updated>2016-09-04T15:37:32.738Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fZzNnvRA1ha5DgaDhITaFg.jpeg" /></figure><p>This morning I was reading this article from Smashing Magazine,<a href="https://www.smashingmagazine.com/2016/08/pixel-perfect-specifications-without-the-headaches/"> Pixel perfect specifications without the headaches</a>. As usual for Smashing Magazine, it’s a very well documented article. The author examines three different tools for making detailed design documentation: <em>Avocode</em>, <em>Sympli</em> and <em>Zeplin</em>. While I was reading the article, a lot of questions came to mind.</p><h3>Should we need such kind of detail?</h3><p>The first question was about the purpose of these tools. Why do people need such detailed programs when working on a design document? Because, I imagine, they need to communicate their work to other people, like stakeholders, project managers and developers. That’s a worthy goal: be transparent, expose what you’re doing and engage quick feedback loops is actually a good idea. But why such level of detail? What do they need to communicate?</p><p>I have the suspicion that those tools are made to give the illusion of control. One of the most common frustrations for UI designers is having their work badly executed. But, for many reasons, what seems a well designed interface on a mock-up, end up being an ugly and unusable product. Technical constraints, as well as time or budget, can force the original idea to compromises, which will affect the perceived quality. So, ok, it looks like there is a problem. And the proposed solutions is… just add more documentation. Uhm, really?</p><h3>Design as blueprint?</h3><p>For many people, the word “design” have very different meanings and nuances. In this specific case, “design” seems to mean the act —and sometimes, even the outcome — of a blueprint creation. Blueprints are detailed specifications that are pretty common in industrial design. They act as references for the production. Actually, every object is created two times: once on the blueprint, representing the final state; another one on the assembly line, where the actual object becomes real.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gHWZMtTf-CuIqzzTWuY0XQ.png" /><figcaption>Don’t you dare make the button 60pt!</figcaption></figure><p>Is it actually the same in the digital space? As far I know, there’s no such a thing like an assembly line here. Where you have people performing repetitive tasks in order to produce a large number of pieces reducing defects, here you have highly educated people trying to solve complex problems in a uncertain market. The production phase is operated by machines, “building” products just-in-time at user request. I’m wondering how many companies who are proclaiming to be “Agile” know what the Manifesto says about documentation.</p><h3>Is that waste?</h3><p>Taiichi Ōno, the Japanese engineer behind the Toyota production system, introduced the concept of three kind of waste: “<a href="https://en.wikipedia.org/wiki/Muri_(Japanese_term)">Muri</a>”, “<a href="https://en.wikipedia.org/wiki/Muda_(Japanese_term)">Muda</a>”, “<a href="https://en.wikipedia.org/wiki/Mura_(Japanese_term)">Mura</a>”. The second one is particularly interesting here: “Muda” is any activity or process that does not add any value; a physical waste of your time, resources and ultimately your money.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*6_tgSVhyg35H03v80tix7Q.jpeg" /><figcaption>“That’s exactly the tool I was waing for my micromanagement tasks!”</figcaption></figure><p>Over-detailed documentation,unnecessary management overhead, and excessive reporting are some common examples of “Muda” waste. From my prospective, those tools looks more an invite on spending time on describing details, than an effective communication platform. Are discussion over a tone of color really useful for the product success? Is the client engagement something that sounds like micromanagement and art-direction? Are feedback ultimately discussion over pixel-perfect positioning? Do the people using this product really care about that perfect shade of orange?</p><p>Spoiler: no.</p><h3>Are designers alone?</h3><p>If I consider that all those products have actually a market, I cannot avoid the image of a lone designer which can communicate only via deliverables. But we have to remember how different is a shared document from a shared understanding. Increasing the amount of detail most of the time doesn’t create more understanding. It produces specification books that usually nobody wants to check. It creates hand-offs, increasing the number of misalignment, and making the change process more painful. Again: it consider the creative act finished, while a lot of things can sill happening through the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*uonQKsjStmHTQBQJ4n3CkA.jpeg" /><figcaption>A shared document, like an order sheet, is definitely not a shared understanding…</figcaption></figure><p>Feeling this frustration, many people switched to another way of thinking about requirements: user stories. Those are actually the opposite: natural-language narratives that describes the user behavior (not the product) intentionally avoiding details. User stories are based on the inclusion of different people: business, tech, research, style, quality, and also users. When domain and technical knowledge is spread among different people, a discussion between those people often leads to good questions, options, and product ideas. It keeps the innovation cycle always open.</p><h3>Why people prefer new tools to new mindset?</h3><p>It’s definitely hard to invest on creating new product and services in a space where everything changes so quickly. Where customers are completely different from the traditional idea of passive message receiver. Create something is easy, but creating the right thing is definitely one of the hardest thing. Still, I see people approaching those problems with a traditional mindset, where tools can solve problems as new machines can increase production and reduce defects.</p><p>I believe digital space require a new way of approaching problems. New century organizations are powered not by tools or specific technologies, but before all by their ability of creating and managing conversations. A paradigm shift is required in order to enable people to solve a new set of problems. Instead of specifications or hand-offs, real value is generated by effective co-creation in short feedback loops.</p><p>As the digital space becomes ever more central to our lives, the design of its interfaces become more important to people’s quality of life. Design teams needs to respond to changes and generating value aggregating inputs from all the ecosystem. I believe a new process of continuous design can enable companies to identify, keeping and evolving their interaction with customers. Continuous design practices can transform the process of idea generation and definition into a more resilient, efficient flow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a53258869cc2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>