<?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 Simone Ferraro on Medium]]></title>
        <description><![CDATA[Stories by Simone Ferraro on Medium]]></description>
        <link>https://medium.com/@simoneferraro?source=rss-5dd5a8e79bb2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*laFXMUmwOLgRzP4RvHxJmA.jpeg</url>
            <title>Stories by Simone Ferraro on Medium</title>
            <link>https://medium.com/@simoneferraro?source=rss-5dd5a8e79bb2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:10:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@simoneferraro/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[How co-design can shape big companies from the inside]]></title>
            <link>https://uxdesign.cc/how-co-design-can-shape-big-companies-from-the-inside-3e52fd609ced?source=rss-5dd5a8e79bb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e52fd609ced</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Simone Ferraro]]></dc:creator>
            <pubDate>Fri, 22 Nov 2019 16:23:14 GMT</pubDate>
            <atom:updated>2019-11-29T22:30:12.037Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QZjWG121zZ894YJE6NdDag.png" /></figure><p>This is the transcript of a talk I gave in October 2019 in Bologna for the <strong>XIII Summit Italiano di Architettura dell’Informazione, </strong>organised by <a href="https://medium.com/u/c6c2994f2326">Architecta</a>.</p><p>The main topic of the conference was “Designing for Communities” and I was invited along with my <strong>Creative Director </strong>at the <strong>BBC</strong> <a href="https://medium.com/u/44c1b36a36ce">danramsden</a> who presented the talk “<strong>Two heads are better than one</strong>”.</p><p>My contribution to the talk consisted of a set of case studies, focused on central topics such as collaboration between interdisciplinary teams and design approaches and techniques.</p><p>I explained through a set of <em>real working life </em>scenarios how I managed to help people to bridge the gaps between disciplines, to build a good shared understanding and to communicate effectively. I stressed the concept of how important is to pick the most effective tool at any time to communicate across disciplines.</p><p>I explained how to make possible a collaborative design approach in such a complex organisation like the BBC.</p><p><em>Please note: The information in this case study is my own and does not necessarily reflect the views of the BBC.</em></p><h3>Presentation</h3><p>I work at the <strong>BBC</strong> in S&amp;SD (<strong>System and Service Design</strong>) as <strong>UX Architect</strong>.</p><p>I work on the design and the user experience of the tools used internally by the BBC, trying to make complex things more meaningful.</p><p>We can say that, in a way, in S&amp;SD we take care of everything behind the scenes.</p><p>For example, just to quote a few of them, in our team we work on the CMS used by journalists in <strong>BBC News</strong> all across the world, on many different web-based video editors and on commissioning and scheduling softwares for Radio and TV. We deal both with the final users and the stakeholders.</p><p><strong>There are literally hundreds of internal tools, used by hundreds of teams and thousands of people.</strong></p><p>I’m going to talk about organisational silos, reusability and scalability.</p><p>We’ll see how a good reflective practice can help in the design process. We’ll see how important is to pick the most effective tool at any time to communicate across disciplines, to build shared understanding and connect effectively.</p><h3>Organisational silos and everyday life</h3><p>Big companies are prone to a so called “silo mentality”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vT8P-Jq5uD6gsd_W2Z2T2w.png" /></figure><p>It refers to an organisation that is made up of divisions that operate independently and avoid sharing information.</p><p>Silos can affect both the communication between entire departments and the communication between small groups of people within a single team.</p><p>Why this happens?</p><p>There are several reasons for this. The reason can be “political”, but it’s quite often psychological.</p><p>While preparing this talk, a colleague of mine, a Senior Product Manager, popped up at my desk because he needed to ask some questions about a project we are working on together. He saw me reading an article on my computer about organisational silos.</p><p>He went “<em> Oh, I love silos!”</em>. He was joking, of course, but I’m sure that, in a way, he meant it.</p><p>Why am I saying so?</p><p>Let’s have a look at the Maslow Pyramid of needs. An all time classic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d53joQ_v1TXUzeTkC5ZcHw.png" /><figcaption>Maslow’s hierarchy of needs</figcaption></figure><p>The pyramid is the graphical representation of Maslow’s hierarchy of needs, a theory in psychology proposed by Abraham Maslow in his 1943 paper “<em>A Theory of Human Motivation</em>”.</p><p>Needs lower down in the hierarchy must be satisfied before individuals can attend to needs higher up.</p><p>As you can see the very basic needs are physiological. Fair enough. Not going to argue about that.</p><p>But security, safety… they reside just right above and have definitely to be considered among the most relevant needs for any human being.</p><blockquote>That’s essentially why people love <em>silos</em>. They feel safe inside!</blockquote><p>The thing is that they can provide benefits in some contexts and be harmful in others. Especially when it comes to <em>agile</em> environments.</p><p>At the BBC we constantly try to mitigate the way silos impact everyday working life.</p><p>Most companies nowadays work with cross-functional teams (a group of people with different functional expertise working toward a common goal), and it’s important to find a way to remove any obstacle to collaboration.</p><p>That’s why we tend to adopt a collaborative, workshop-based approach to achieve this:</p><ol><li>Aligning people and raising awareness of the common benefits in sharing technology and best practices.</li><li>Create a meaningful network of people across teams.</li><li>Validate some hypotheses and assumptions we might have.</li></ol><h3>The Tools Framework Case</h3><p>Speaking of silos let’s have look at the Tools framework case</p><p>Content silos are evident in our tools, making it difficult for producers and product teams to discover, share, and reuse content. Not to mention that content silos drive to the increasing of software development costs.</p><p>Considering that several users’ tasks are rarely confined to a single tool, some years ago the BBC developed the <em>Tools Framework</em>, which is a set of libraries and API driven services that aims to provide a way for task-focused web activities to interact and collaborate with each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z9T4xhV4exzX8ltfX5bYHw.png" /></figure><p>It is essentially a framework to create and manage reusable components that can be used by the developers in order to allow them to just call the element they needed when building a new tool.</p><p>It revolves around the concept of activities, borrowed from the Android Activity Model.</p><h4>The Activity Model</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S3HWlpcO0pQw2SXR-Ii53A.png" /></figure><p>An activity (in the <em>Android</em> world and in the <em>Tools Framework</em> sense) is a screen or series of screens that satisfy the intent of a user to perform an action.</p><p>An activity could be for example “<em> Browse/list articles</em>” or “<em>Add image</em>”.</p><h4>The Workshop</h4><p>Cool! We had our framework and it sounded amazing. But something didn’t work.</p><p>People were not using it consistently. We wanted to discover why. We had some hypothesis and we wanted to validate them.</p><p>One of the strongest assumptions we had was they essentially were using another open source framework (<em>React</em>) instead of our internal framework to perform their tasks.</p><p>We wanted to validate our hypothesis using a human centred approach.</p><p>That’s why we decided to run a workshop with some key stakeholders (12 people) in order to learn more.</p><p>Adopting a diverge/converge design thinking approach, we asked the attendees to assess the positives and negatives of using <em>Tools Framework</em> and <em>React</em> in relation to their specific tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tobY8z4b8Sx_escoB4R_nw.png" /></figure><p>Attendees discussed all positives and negatives established for both options and grouped all comments into common themes with an affinity diagram.</p><p>They then dot voted which of the grouped themes they wanted to talk about in the final discussion, what we called the “Roundtable”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SVwyBSc60L70ZFhHB-aJEQ.png" /></figure><h4>What we found</h4><p>What emerged was that Tools Framework didn’t work well.</p><p>It relied on obsolete technologies (still too many <em>iframes!</em>), there was not enough shared support, it was not scalable and flexible enough…</p><p>Someone could say that we killed an idea. I’d prefer to say that we discovered it had to be radically reframed.</p><p>But — most importantly — we contributed to get the stakeholders in the same room working in a collaborative way on something. We got them aligned.</p><p>We worked with the developers using a human centred approach.</p><h3>Reusing components is easier said than done</h3><p>As you might have noticed from the <em>Tools Framework</em> case, reusability is a core concept.</p><p>Every developer and every designer should be committed to reusability, and most companies are working in that direction, either building a new framework (at the BBC the <em>Tools Framework</em> project is going in that direction) or adopting existing ones like <em>React</em>.</p><p>Reusing Components, avoid duplication…that’s not easy.</p><p>We need to work on our culture, attitude and strategy: reusability has not to be seen just as a set of tools and standards, but rather as a development strategy which goes far beyond mere technical aspects.</p><p>Striving towards reusability means allowing the teams to think of everything they build as something that can serve other people and parts of the product.</p><p>At the BBC we are committed to create the right environment for a more efficient workflow, and as UX practitioners we use our expertise to put in place strategies to foster the communication between people and teams, and promote the adoption of shared standards.</p><p>That leads us to the next case study.</p><h3>The Partner Platform Case</h3><p><em>Partner Platform</em> is the tool developed by the BBC to manage the authentication to our systems for both employees and external collaborators and contractors.</p><p>Like we said, at the BBC we have hundreds of internal tools and an effective system to grant or revoke access to users is vital.</p><p>These days, the team behind Partner Platform are working on boosting up the system, turning it into a proper <em>Authentication as a Service </em>system, enabling simple and secure access to the BBC’s systems and resources for internal and external users with a self service approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-FUMRIGPETyacbjns4j4Ag.png" /></figure><p>It is a big change of mindset to them (before they add to enter manually the data).</p><p>They asked SSD to help them finding a way to keep the momentum and making it clear among all the members of the development team what this goal means and how they can achieve it.</p><h4>The Workshop</h4><p>We wanted to question, push and validate the new model underlying the new <em>Authentication as a Service</em> system, using a collaborative approach and getting all the members of the team involved. We recruited 10 people between developers and technical architects.</p><p>The aim of the exercise was to move from a higher level of abstraction (the logical model itself) to a set of actionable and potentially reusable activities.</p><p>This process would have helped the team to design a more effective system architecture and efficient reusable UI components.</p><p>Before running the exercises, we drafted with the help of a couple of senior members of the <em>Partner Platform</em> team a set of statements according to the new logical model. We tried to translate into statements some aspects of the model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*csQ85PksokzWtZTFIrYTdQ.png" /></figure><p>Considering that the logical model shows the concept of “group” of users with specific capabilities as core concept, an example of statement could have been:</p><ul><li><em>“A group contains people”</em></li><li><em>“A policy allows a group to access a resource”</em></li></ul><p>We then printed all the statements, sticked them on the wall and we asked participants to write down on posits what activities (in the Tools Framework sense) would be needed in order to make the model statement a reality for users.</p><p>After less than one hour we had a set of actionable activities on the wall!</p><p>We ended up with a wall like this (this is the final deliverable, the digitised version of the wall with post its notes)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bF6AVEaYRAA519HwIymzeg.png" /><figcaption>For the statement “A group can contain zero to many users” activities as these were added: “Add/Remove Users from Group”, “Create/Edit Group”, “Browse all Groups”</figcaption></figure><p>We then moved to the next exercise.</p><p>Before the session we produced 5 scenarios and 5 <em>proto-personas</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bI2f4OkZoDGGvGi_cJt2HA.png" /></figure><p>We split the participants into 5 groups and we asked to test the model statements against each scenarios and to create a storyboard (they had to use the post its with the activities previously created)</p><h4>What we found</h4><p>Different teams came up with a slightly different workflow / model for their scenario, which was fine because it fostered a final discussion about to which model works best and why.</p><p>The work we did together let us identify how much flexibility the model enables, and made the team feel more aware of the importance of taking into consideration reusability and scalability since the very early stage of the design process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e52fd609ced" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-co-design-can-shape-big-companies-from-the-inside-3e52fd609ced">How co-design can shape big companies from the inside</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Please, stop designing just for users]]></title>
            <link>https://uxdesign.cc/please-stop-designing-just-for-users-5d72114c870d?source=rss-5dd5a8e79bb2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d72114c870d</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Simone Ferraro]]></dc:creator>
            <pubDate>Wed, 03 Apr 2019 17:42:26 GMT</pubDate>
            <atom:updated>2019-04-07T22:49:12.168Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kGqMs1YROwsuP4HpQ0smaA.jpeg" /></figure><p>As a UX Architect at the BBC in London, I’ve been working on a set of API driven services that aims to provide a way for task-focused web activities. It allows modular, flexible workflows to be composed and used across different tools and products.</p><p>This job led me to think more in depth about the role of human activities in the design process.</p><p>Most items in the world have been designed without the support of any user study and they still do quite well.</p><blockquote>Human-Centred Design has become such a dogma that we automatically apply it.</blockquote><p>Take a look around and think of an <em>ancient</em>, major technology designed with a straight <em>user-first</em> approach in mind: kitchen tools, furniture, clothing, music instruments, writing systems themselves…these things and many others haven’t been originally designed that way. Some of them were not even properly <em>designed</em>, they just evolved and improved with time.</p><p>Why do they work so well, then? Because they were designed just keeping in mind the activities that were to-be performed.</p><p>Think about the telephone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gv_mkBn4fttELJqoPt6AWg.png" /></figure><p>The device wasn’t designed putting the user first. It was pretty difficult to use if you had never seen one, indeed!</p><p>You had to compose a sequence of numbers on the rotary phone dial. The digits were arranged in a circular way on a finger wheel.</p><p>To make a call you had to:</p><p>1. Keep in mind the sequence of digits you had to dial<br>2. Put your finger into the hole corresponding to the number you wanted to dial. <br>3. Rotate the wheel from the position of each digit to a fixed stop position<br>4. Wait for the finger wheel to get back to its original position.<br>5. Repeat the process for every digit of your sequence.</p><p>I’m pretty sure that this user flow wouldn’t have passed easily any user testing.</p><p>Again, let’s pretend you live in a remote village, somewhere on heart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SySCuYCwgFZ7nwtZDiyimg.jpeg" /></figure><p>If you need to move quicker from village to village you need to learn how to ride a bike.</p><p>The learning curve could be steep because nobody designed the bike intending to make it seamless for people learning how to ride it. Yet, once you know how to, the benefits in terms of gaining time and efforts are invaluable!</p><p>The HCD mantra say: “<em>Understand your user first</em>”, “<em>Technology should adapt to people</em>”. Is that really true?</p><p>What if it was different? What if it was something like “<em>Understand the activity first</em>” or ”<em>People should adapt to the technology</em>”.</p><p>These thoughts made me starting to investigate about the topic, and I discovered more about a thing called “Activity Centered Design”.</p><p>Well, the overall point is, in fact, that well designed devices should be the ones that seamlessly support the requirements of the underlying intended activity!</p><blockquote>Well designed devices should be the ones that seamlessly support the requirements of the underlying intended activity.</blockquote><p>Don’t misunderstand: activities are things that humans do, so a deep understanding of people is important.</p><p>Human Centred Design leads to better products. It can fix and improve existing things and it can make them more effective and usable.</p><p>User testing, along with a structured approach to iteration and many other Human Centred Design practices can definitely make the difference. I always believed that and I still do.</p><p>But are we sure that Human Centred Design alone can guarantee good products?</p><p>Are we really sure that listening to users should be the very first aim of our design process?</p><p>Understanding our users is important. Understanding activities and technologies maybe even more.</p><p>Like Don Norman states: “<em>The individual is a moving target. Design for the individual of today, and the design will be wrong tomorrow</em>”.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d72114c870d" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/please-stop-designing-just-for-users-5d72114c870d">Please, stop designing just for users</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>