<?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 Ligia Fascioni on Medium]]></title>
        <description><![CDATA[Stories by Ligia Fascioni on Medium]]></description>
        <link>https://medium.com/@ligiafascioni_8056?source=rss-186b178fc420------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GQ4iXxNjTM6Pw8hxSGnPYA.jpeg</url>
            <title>Stories by Ligia Fascioni on Medium</title>
            <link>https://medium.com/@ligiafascioni_8056?source=rss-186b178fc420------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:46:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ligiafascioni_8056/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[The collaborative habit]]></title>
            <link>https://medium.com/@ligiafascioni_8056/the-collaborative-habit-f3314871c3c9?source=rss-186b178fc420------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3314871c3c9</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[collaborative-learning]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <dc:creator><![CDATA[Ligia Fascioni]]></dc:creator>
            <pubDate>Mon, 04 Dec 2023 11:37:57 GMT</pubDate>
            <atom:updated>2023-12-04T11:37:57.389Z</atom:updated>
            <content:encoded><![CDATA[<p>Review of the wonderful book ‘The Collaborative Habit’ by Twyla Tharp, where she talks about leadership without using that word even once. It’s about the leader who understands that leading is collaborating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H7OE6LCZO5lzrNevTGhieA.jpeg" /></figure><p>I decided to buy this book because I had really liked ‘The Creative Habit’ by the same author. So, ‘The Collaborative Habit’ by Twyla Tharp was a natural follow-up, right?</p><p>Actually, more than a natural sequel, the reason is that I increasingly realize that collaboration is the most important thing a human being can learn.</p><p>There’s another book, one of the best I’ve ever read, called ‘The Illusion of Knowledge’ (Steven Sloman and Philip Fernbach), which supports the idea that individual intelligence is overestimated; the ability to collaborate is much more important.</p><p>Twyla doesn’t use the term ‘leader’ directly, but that’s exactly what she does, as there is no collaboration without leadership.</p><p>But first, let’s introduce this wonderful woman and her background, in case you haven’t read her previous book.</p><p>Twyla is one of the greatest American choreographers in history: she choreographed the sensational performance where the Russian dancer Mikhail Baryshnikov dances with the master of American tap dance, Gregory Hines, in the unforgettable movie ‘White Nights’; she designed all the dances for the legendary musical ‘Hair’ by Milos Forman. Later, she worked with the same director on the film ‘Amadeus.’ She also did numerous works for the theater, collaborating with musicians like Bob Dylan, Abbot Costello, and Billy Joel. In short, if there’s someone who understands collective building, it’s her.</p><p>Twyla is a leader, but she defines herself as a professional collaborator (which is not wrong, as leaders also collaborate).</p><p>I like to use the definition that says a leader is someone who needs help to accomplish something. Of course, because if they can do it alone, they are not a leader; they are an executor. When things are bigger or more complex than what one person can handle, they need collaborators to help.</p><blockquote>A leader is someone who needs help to accomplish something. [Ligia Fascioni]</blockquote><p>And that’s what Twyla does: she can’t dance alone in a performance that requires dozens of dancers, musicians, assistants, lighting designers, producers, costume designers, and many other professionals. So, she seeks help. And makes it happen.</p><p>In this book, she gives some tips that worked for her and uses her own professional life as an example to show how she arrived at the conclusions she shares.</p><h3>WHY COLLABORATION IS IMPORTANT</h3><p>In the first part, she explains why collaboration is so important, reinforcing the arguments of the authors I mentioned earlier. But she draws attention to a fact that I hadn’t realized until then.</p><p>Despite collaboration bringing us to this point, most of us grew up in an environment where only individual achievements were celebrated. I don’t know about you, but I grew up in a quite competitive school environment, where individual grades were much more important than teamwork.</p><p>People celebrate entrepreneurs, scientists, artists, and politicians as if their achievements were individual and the result of their own talent, not the result of teamwork.</p><p>Now, it seems that things are starting to change (because people realized that in this model, most collaborators can’t reap the rewards of their work, and only a few get the credit and profits).</p><p>The buzzword is collaboration. And people need to learn how to do that after so much time competing.</p><p>Twyla says you can’t force people to collaborate. You can share the office or studio, be a colleague on a committee or board, be on the same team — but if the heart isn’t in it, the process is like a dry shell and doesn’t flourish, doesn’t bear fruit. It’s purely bureaucratic participation.</p><p>According to her (with which I totally agree), collaborators are not born; they are built and educated, one day at a time, through practice, attention, discipline, passion, commitment, and, above all, HABIT. At the same time, we are wired to collaborate, as if it were a second nature that needs to be awakened.</p><p>Another thing I loved was this definition:</p><blockquote>Collaboration is the recognition that there is more life, opportunities, knowledge, and dangers than we can handle alone. [Twyla Tharp]</blockquote><p>Twyla also talks about managing expectations: the best collaboration happens when each person knows what is expected of them. And, more than that, any intelligent person learns more by example than by any other method. So, the leader has to be an example of what they expect from each one, whether it’s kindness, commitment, or respect.</p><h3>INSTITUTIONS</h3><p>She also talks about the difficulty of collaborating with an institution or company, rather than an individual. Before starting any project, the choreographer makes a list of all the resources she needs to ensure that the institution will be able to provide them, for example (it’s the same expectation management applied on a larger scale). Everything must be planned and documented, and you must know and understand well the person who will represent the institution in communications.</p><p>Another thing to keep in mind is that institutions, however open they may seem, have as their intrinsic mission to preserve their survival, and for that, they will defend their status quo as much as they can, shielding themselves from outsiders with challenges and very different ideas. So, communication here is essential, more than in any other situation.</p><h3>FRIENDS AS COLLABORATORS?</h3><p>And collaboration between friends for a project? This is a big question for Twyla, who always avoids working with close friends but often ends up making good friends through collaborations.</p><p>But caution is needed because, as she says, a good collaborator is easier to find than a good friend. In fact, finding a true friend is at the top of the hierarchy of difficult things; so, the best thing to do is protect that rare relationship. Working together can jeopardize that.</p><h3>MILOS FORMAN</h3><p>Twyla presents a series of lessons she learned from the director of ‘Hair’ and ‘Amadeus’. Here are some of them.</p><ol><li>Never shout. Never.</li></ol><p>2. If you’re about to shout, step away and go to sleep (in his case) or exercise (in her case).</p><p>3. Clear, precise communication without room for ambiguity makes all the difference.</p><p>4. Collaborators need attention; gently touching people to enhance connection can show that you really care about what they are feeling.</p><p>5. Listening to suggestions from everyone involved greatly improves the group’s spirit.</p><p>6. Saying ‘thank you’ is never too much. Repeat on every occasion, with every small gesture, until you get used to saying it dozens of times a day.</p><h3>CONCLUSION</h3><p>Twyla also talks about difficult collaborators who challenge the work and make things more complicated, and also about remote collaboration (sometimes there’s no other way).</p><p>This inspiring leader wrote an entire book about leadership without ever using that word and always emphasizing collaboration: she really understood the spirit of it more than any leader I know.</p><p>And to conclude, this sentence that says it all:</p><blockquote>‘Every collaboration is a love story’ [Twyla Tharp]</blockquote><p>And it is.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3314871c3c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design is storytelling]]></title>
            <link>https://medium.com/@ligiafascioni_8056/design-is-storytelling-07766f3278f2?source=rss-186b178fc420------2</link>
            <guid isPermaLink="false">https://medium.com/p/07766f3278f2</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Ligia Fascioni]]></dc:creator>
            <pubDate>Sun, 12 Nov 2023 16:32:42 GMT</pubDate>
            <atom:updated>2023-11-12T16:33:26.397Z</atom:updated>
            <content:encoded><![CDATA[<p>Review of the book &quot;Design is storytelling&quot;, by Ellen Lupton.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEgQvZrWPEi4WkcF5faObQ.jpeg" /></figure><p>This book isn’t just for designers, despite the title; I believe everyone should know a bit about the subject, as design affects everyone’s life, no exceptions. The great thing about well-written books like this is that you don’t have to be an expert to understand them. The author takes the idea seriously that design is for everyone.</p><p>I’ve been following Ellen Lupton’s career for over a decade; the first book I bought from her was “<strong>Thinking with Type</strong>” back in 2006. Lupton is a design authority, the curator of the Smithsonian Design Museum in New York, a university professor, author of several successful books, and the recipient of many awards.</p><p>As if all that weren’t enough, this lovely lady is also really friendly. I haven’t met her in person, but I follow her on Instagram, and you just want to be friends with her.</p><p>So, “<strong>Design is Storytelling</strong>” has been read quite some time ago. This week I needed some ideas and decided to revisit it. It never disappoints. So let’s see what this lady has to tell us that’s so interesting.</p><p>Ellen starts with what we already know: design incorporates values and illustrates ideas. It delights, surprises, and prompts action.</p><p>In this book, she examines the psychology of communication from a narrative perspective, which is a powerful tool for encouraging actions and behaviors. And, as she says, this book is a creativity game; it has tools inside that we can use when we need them (like in my case).</p><p>To make it more didactic, she divided the content into 3 parts: Action, Emotion, and Sensation. So, here we go.</p><h3>ACTION</h3><p>Here, Ellen shows us the basic structure of a story (often called the plot) and the more detailed stages of this structure (which are the actual story).</p><p>Designers also plan structures to tell stories. A classic model, which almost always works and is present in most stories we know, considers the narrative arc, where the hero is exposed to a problem, then action happens, reaches the climax, everything calms down, and it ends. This applies to stories, food, design, and even sex.</p><p>Ellen couldn’t forget to mention the Hero’s Journey pattern. It all starts with the hero being called to something beyond ordinary life; aided by a mentor, they manage to cross the border into this unknown world where they have to fulfill a complicated mission full of obstacles until they reach the final reward.</p><p>We can easily recognize this narrative in movies like <em>The Wizard of Oz</em> or the <em>Star Wars</em> series; even in <em>Barbie’s</em> movie. Take a look, this is the basis for almost all the stories we know.</p><p>But what’s cool is recognizing this journey in everyday design experiences, designed to be exactly this way.</p><p>Ellen uses the example of a person entering any IKEA store, which is a well-designed labyrinth. And here’s a curiosity: labyrinths have existed since the Middle Ages and were created for meditation — a path with only one route, but disorienting; yet, the person always reaches the end.</p><p>On the other hand, a maze is a closed path with an exit, but it’s built in a way that a person can get lost forever inside. So, the story of the Minotaur wasn’t about a labyrinth, but a maze.</p><p>Back to IKEA, the idea of the store being built like a labyrinth is precisely to guide the visitor on a journey, where they first see complete environments, then move on to the small stuff, pass through the warehouse full of treasures, and end up with a hot dog!</p><p>Supermarkets and art exhibitions also have designs that guide the visitor’s journey. Even fast-food joints tell different stories. For example, at McDonald’s, you don’t see the actors making your sandwich; just a bunch of customers in front of you, and boxes mysteriously appearing through the wall. In Subway, you participate in the story by interacting with the person making your sandwich throughout the journey.</p><p>The story is told with the help of colors, architecture, symbols, packaging, logos, signage, social media strategies, and so on — a lot of things involved that need to be part of the same narrative for everything to be coherent, and the visitor doesn’t feel lost or insecure, not knowing where they are.</p><p>I’ve always been bothered by designers (of any kind) who simply complete the requested task without a critical analysis of this narrative.</p><blockquote>What story are we going to help tell? What are its elements? Who are the actors? What sensations do we want the customer/user to feel? What do we want to avoid? How will the interactions be?</blockquote><p>There’s a lot to clarify before the practical tasks of designing a space, a logo, packaging, signage, a website, or an app.</p><p>Still in the first part, the author talks about the usefulness of building a storyboard to communicate inspirations, think about a problem, explore alternatives, test ideas, and empathize with users.</p><p>And then there’s the rule of three, where this magic number helps communicate concepts better and make them memorable, as well as facilitating decision-making processes.</p><p>Look, this lady doesn’t even leave futurism alone! She also talks about scenario planning, the cone of plausibility that we study in futures thinking (the analysis of possible futures that includes plausible, probable, and preferable futures) and tells how we can use these tools using storytelling.</p><h3>EMOTION</h3><p>In this part, Ellen talks about how the experience economy values the feelings and sensations of the user/customer. At this point, she emphasizes that</p><blockquote>&quot;experiences are created when designers shift the emphasis from the object to the action&quot;</blockquote><p>And here we arrive at the emotional journey of the user; what feelings do they experience throughout the entire process of interacting with the product/service? This means that, of course, no one is expecting moments of terror when entering a store or website, but things can’t be dull and monotonous. Some movement needs to be created, and very importantly: the last impression is the one that sticks.</p><p>The final chapter needs to leave a good taste in the mouth. So the whole journey needs to be designed to evoke different feelings, but the last stage needs to be memorable.</p><p>There’s also a section dedicated to the importance of co-creation and, of course, empathy (after all, we’re talking about feelings, so the ability to share mental states is very necessary).</p><p>Ellen also talks about the use of emojis and colors in building a narrative that evokes emotions.</p><h3>SENSATION</h3><p>One important thing to note is that we tend to see what we are expecting to see. Whether in a physical environment, a website, a print, or an app, we simply ignore elements that we are not looking for (as a UX designer, I’ve seen this happen many times in practice — it’s amazing how a huge button can become invisible in usability tests just because it’s not in the expected place).</p><p>So, we have to be aware that excessive elements can become obstacles for a person to find what they were looking for because, as in a story, perception is active and temporal. Users don’t just look; they click, point, drag, and scroll in response to what they are seeing.</p><p>The issue is that our working memory can only manipulate a few objects simultaneously — so we are always looking for a small and selected number of objects that have some meaning in this sea of stimuli in which we live.</p><blockquote>These objects should preferably be important, useful, or dangerous, beautiful, or strange.</blockquote><p>According to anthropologist Tim Ingold, landscapes are defined by paths. And indeed; you can notice: where there are humans, there are also paths (and signs on how to navigate them).</p><blockquote>Designers need to think in terms of paths to help the user on their journey, whatever it may be.</blockquote><p>At this point, there’s an interesting discussion about the fact that exploring the world with our eyes is an active process, and some people have more freedom than others, both to observe and to be observed.</p><p>In the next part, Ellen introduces us to the principles of Gestalt, the concept of availability, behavioral economics (which studies how humans make decisions), and multisensory design.</p><h3>CONCLUSION</h3><p>In the end, Ellen leaves us with some gifts: tips to improve writing, prompts to generate stories, and a checklist for the actions, emotions, and sensations that your design project evokes (or doesn’t).</p><p>In summary: this beautiful book is worth every printed letter. If you’re a designer, you’ll love it. If you’re not, you’ll learn many interesting and useful things in a fun way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07766f3278f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User friendly: The book]]></title>
            <link>https://medium.com/@ligiafascioni_8056/user-friendly-the-book-f32dcba6658b?source=rss-186b178fc420------2</link>
            <guid isPermaLink="false">https://medium.com/p/f32dcba6658b</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-friendly]]></category>
            <category><![CDATA[books-review]]></category>
            <dc:creator><![CDATA[Ligia Fascioni]]></dc:creator>
            <pubDate>Tue, 18 Jul 2023 17:01:52 GMT</pubDate>
            <atom:updated>2023-07-18T17:01:52.984Z</atom:updated>
            <content:encoded><![CDATA[<p>Review of the book “<strong><em>User Friendly: how the hidden rules of design are changing the way we live, work, and play,</em></strong>” written by Cliff Kuang and Robert Fabricant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9iaj2bI6wBPmiiC3" /><figcaption>Photo by <a href="https://unsplash.com/es/@sharisocial?utm_source=medium&amp;utm_medium=referral">Shari Sirotnak</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>At first, “<strong><em>User Friendly: how the hidden rules of design are changing the way we live, work, and play,</em></strong>” by Cliff Kuang and Robert Fabricant, might seem like a technical book that would only interest designers and developers. However, I believe that everyone should know a little about how the objects we use in our daily lives have evolved from a user-friendly perspective.</p><p>Let’s start with the idea of “user friendly”. The American programmer Harlan Crowder, from IBM, was one of the first people to use this term to refer to a computer back in the 1960s.</p><p>He couldn’t accept the tedious process of punching cards (I’ve done that a lot when I was an engineering student) and waiting for the mainframe to process the code for hours, only to find out it all went wrong because of a forgotten comma or symbol.</p><blockquote>In this sense, “user friendly” means that the use of a particular equipment is simple, intuitive, friendly, accessible to anyone, and robust in case of operator error.</blockquote><p>The authors, Cliff Kuang, an award-winning journalist specialized in User Experience and editor of the largest and most important design magazines in the United States, and Robert Fabricant, former creative director of the legendary Frog Design, recount how it all began and why people started to realize the importance of taking this matter seriously.</p><p>Of course, intuitively, there were professionals already thinking about this issue, especially industrial designers who emerged after World War I, like Henry Dreyfuss, responsible for designing a significant number of consumer products from the 1930s in the USA. He understood that things, more than being beautiful, should be easy to clean and intuitive to use.</p><h3>Feedback</h3><p>Kuang and Fabricant recount that the most significant influence for this approach came from very serious accidents, such as the Three Mile Island nuclear power plant accident in 1979 and the deaths of dozens of pilots during World War II.</p><p>In the case of the power plant, operators lacked feedback on what was happening. For example, they would press a button to open a valve, but they didn’t receive confirmation that it had actually opened. Additionally, all the instruments were mixed up, making visualization difficult.</p><p>As for the pilots, they made mistakes because the control panel was also poorly designed.</p><blockquote>My father was an airplane mechanic, and I remember him always saying that this was the safest means of transportation, and accidents only occurred due to human error. The technical people had gotten used to blaming humans when the real problem was poor design.</blockquote><p>During that time, researchers even attempted to classify pilots who made mistakes as a class of people prone to that kind of behavior.</p><p>The idea was to find special individuals with the appropriate profile. Only later did they realize that it was much smarter to redesign the interfaces to fit the way humans think, not the other way around, giving rise to a discipline called ergonomics.</p><blockquote>The principle was that machines should be easy to operate because that would also enhance human performance.</blockquote><p>One of the first professionals to address this issue was the engineer and cognitive scientist Donald Norman, who, incidentally, coined the term “User Experience,”* which went beyond ergonomics, as it considered psychological aspects, not just functional ones.</p><p>The idea was to understand why errors occurred, how humans thought and felt, and how machines could be shaped considering this environment and behavior.</p><p>This line of thinking eventually gave rise to other specialized areas of knowledge, such as behavioral economics, which is concerned with making machines user-friendly while acknowledging that our minds will never be perfect.</p><blockquote>Moreover, it is precisely our imperfections that make us who we are, and we must learn to live with them.</blockquote><p>So, designing in a user-friendly way means adapting the objects around us to how we behave. Design is no longer based solely on artifacts but on patterns of behavior.</p><p>All the intricacies of designing new products can be reduced to two fundamental strategies:</p><ol><li>Identify the causes of our pains and try to eliminate them; or</li><li>Reinforce what we already do with a new object in a way that is so easy that it becomes second nature.</li></ol><h3>Metaphors</h3><p>Another crucial aspect highlighted by the authors is the importance of metaphors. According to linguist George Lakoff, in collaboration with philosopher Mark Johnson, it is nearly impossible to think without resorting to metaphors because they are our most basic mental model of the real world.</p><p>Think about the inbox messages (closed and protected, needing your attention to exist) and the feed (like food), or stream (flow), a conveyor belt of food that keeps going even if you’re not paying attention.</p><p>An essential example of a metaphor is the dashboard of the Ford Fusion hybrid car. The driver needed to pay attention to the battery level and whether the car was charging properly. So, when they applied the brakes and the battery charged through kinetic force, the dashboard emphasized the action. However, this led drivers to brake frequently and abruptly, thinking they were charging the battery (but real efficiency only increased with gentle braking).</p><p>How could this be explained intuitively, without a video or manual?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6Pe5PubhJPI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6Pe5PubhJPI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6Pe5PubhJPI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/378c6738d87aaf60f900f2f1ec5321d5/href">https://medium.com/media/378c6738d87aaf60f900f2f1ec5321d5/href</a></iframe><p>One idea was for the onboard computer to scold the imprudent driver. But who likes to be scolded, especially by a machine? Also, considering the culture, driving a car means having control; having a machine give advice would be a real mood spoiler.</p><p>The solution was to use the color green to indicate that the driver was driving well, meaning they were using resources efficiently (driving at a productive speed and braking smoothly).</p><p>After extensive research, the developers decided to use the metaphor of green leaves (ecology). When the trip was efficient, digital green leaves fell onto the dashboard. When it wasn’t, the leaves disappeared, indicating that the driver wasn’t contributing to the environment’s preservation. The result was incredible; people stopped taking short trips that could be done on foot because they felt guilty “killing” green leaves… even children began to pay attention to how their parents were driving.</p><blockquote>One lesson about metaphors is that people will only understand them if they care about the subject. Those who buy electric or hybrid cars theoretically care about it, at least.</blockquote><p>Metaphors can save lives, as seen in the case of the defibrillator designed by IDEO in the 1990s; any layperson could use it since it only had three described steps and a button next to each, indicating the correct sequence.</p><h4>Desktop</h4><p>We almost don’t pay attention anymore, but one of the most significant factors, besides the invention of the mouse, for the popularization of computers was the metaphor of the desktop, with its folders, trash bin, agenda, and more.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fo897T417h-c&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Do897T417h-c&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2Fo897T417h-c%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0aaa589990427cf2e72ba8f27cef9acd/href">https://medium.com/media/0aaa589990427cf2e72ba8f27cef9acd/href</a></iframe><p>Once the computer object became familiar, the elements no longer needed to be so literal from a graphical point of view; they became more stylized. When Apple implemented the drag-and-drop function to move a file or photo, even children could intuitively use it.</p><p>Amazon’s 1-Click button is one of the biggest revolutions in e-commerce history. Its impact on the Internet is only second to Facebook’s Like button.</p><p>Metaphors are so fundamental that the attempts by major companies like Facebook to provide accessible internet for the entire planet have failed because people in underdeveloped countries with lower education levels do not understand what the internet is. Many people think that the Internet and Facebook are the same thing (I’ve personally heard of some cases), and therefore, they do not take full advantage of the tool.</p><h3>Empathy and Humanity</h3><p>Without stepping into the user’s shoes, there’s no way to design something that excites, motivates, and is intuitive for them.</p><blockquote>That’s why the authors claim that user-centered design is nothing but industrialized empathy.</blockquote><p>They go even further and state that we are better at solving a problem when it is interesting and challenging. Empathy is the key to this because the most interesting problems are not obvious.</p><p>They share the story of a student who went to work for a British government agency. Her mission was to find out why so much money was being spent on people injured by lawnmowers. She delved so deeply into the issue that she discovered the real problem lay in the design of the lawnmowers.</p><p>People became distracted while mowing the lawn because it wasn’t a task that required much attention. As a result, they accidentally ran the lawnmower over their own feet, causing serious accidents. Smartly, she reached out to the manufacturers to suggest improvements, but no one took her seriously (after all, the cost wasn’t their burden, and remember, for a long time, the blame was always put on the feeble-minded human).</p><p>In the end, she ended up at one of the most renowned design studios in the world, IDEO. This company, in addition to the design thinking method, was also responsible for developing the mouse for Apple.</p><h3>Conclusions</h3><p>In addition to great stories, many tips, and curiosities, the book also includes an appendix with a summary of the history of User Friendly, starting in 1716 when Louis XV decided to add arms to the throne’s chair to make it more comfortable.</p><p>In a way, this also contributed to the visual projection of power and privilege. It goes on to mention the invention of the steering wheel for better car control in 1898, the Kodak cameras where you just had to press a button and it did the rest (1900).</p><p>There’s also the involvement of Disneyland, emojis, Alexa, among many other articles, books, objects, inventions, movies, and applications. It concludes with the General Data Protection Regulation implemented by the European Union in 2016.</p><p>I recommend this read for everyone. Nothing to lose, everything to gain.</p><p>— — — — — — — — — —</p><p>*The authors don’t mention it, but there is controversy about whether Norman is actually the original author of the term. In any case, he was the one who made the term widely popular.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f32dcba6658b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we fail]]></title>
            <link>https://medium.com/@ligiafascioni_8056/why-we-fail-deb16352283b?source=rss-186b178fc420------2</link>
            <guid isPermaLink="false">https://medium.com/p/deb16352283b</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[book-recommendations]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Ligia Fascioni]]></dc:creator>
            <pubDate>Thu, 13 Jul 2023 10:14:43 GMT</pubDate>
            <atom:updated>2023-07-13T10:14:43.028Z</atom:updated>
            <content:encoded><![CDATA[<p>Review of the book “<em>Why we fail: Learning from Experience Design Failures</em>” by Victor Lombardi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UND1hycq3R6yWAkc" /><figcaption>Photo by <a href="https://unsplash.com/@jeshoots?utm_source=medium&amp;utm_medium=referral">JESHOOTS.COM</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A well-designed book, with a beautiful cover, and about a subject I love: how to resist?</p><p>I came across “<strong><em>Why we fail: Learning from Experience Design Failures</em></strong>” by Victor Lombardi, with a foreword by none other than Don Norman.</p><p>The author has been working in digital product development for over 30 years. To write this book, he conducted extensive research and selected 10 examples: four websites, two services, one software package, one operating system, and two hardware-based products (likely embedded software).</p><p>I really liked the criteria: <strong>all of them were innovative products</strong> (not trying to copy or improve upon a competitor) and <strong>didn’t fail due to incompetence</strong> (which is very common).</p><p>Right at the beginning, Lombardi makes one important thing clear: in this book, he is only considering failures in customer experience; in other words, the product failed to provide a good experience.</p><h3>Bad experience = poor design?</h3><p>Okay, but isn’t a failure in customer experience just a more recent term for poor design?</p><p>He explains that <strong>it’s not the case</strong>: in the past, when products were simpler, bad design could explain many failures. However, as products become increasingly complex, a product can have good physical design and function perfectly well (like a smartphone), yet it’s no guarantee that the user will enjoy using it.</p><p>The reason is that new products are complex and multifaceted, and our experiences and interactions are emotional and subjective.</p><p>And would the blame for these failures be on poorly trained or incompetent designers? Victor says that nowadays the answer is not so simple.</p><p>A product can be loved by one audience and detested by another. An aspect of the experience that the designer believes to be vital, such as a website always being available, may not surpass a competitor that goes offline multiple times for maintenance. Or two similar products that produce similar experiences, but one fails due to social or cultural issues.</p><h3>First Failure</h3><p>He recounts an experience where, in 2000, he was hired by a digital design agency to create the website for a portal that was supposed to revolutionize financial information research; the target audience consisted of investors from large companies. In the briefing, the client made it clear that they wanted something resembling a Bloomberg terminal (which is an American stock exchange); in other words, multiple screens with colorful numbers on a dark background and constantly moving charts.</p><p>The author and his team suggested something cleaner and friendlier (the dark background made it difficult to read), based on previous experiences with similar products. But the harsh truth is that:</p><p>Neither the development team nor the client had conducted any research to truly understand the user’s perception.</p><p>The result? The client didn’t like it, changed the development team twice, and ended up using off-the-shelf software. An absolute failure.</p><p>It was one of the author’s first projects, and he was somewhat traumatized because <strong>nobody in the company liked to talk about failures</strong>, so they never tried to deeply understand what had actually happened. The easiest, most popular, and conventional way is to blame the client, calling them ignorant.</p><p>He started seeing this story repeat itself many times: projects being canceled, dissatisfied clients, and users systematically being ignored while agencies turned a blind eye. And worse: people focusing on studying successful cases to replicate them, always avoiding discussing failures.</p><h3>Survivorship bias</h3><p>Initially, looking only at what went right seems like a good idea, but it’s not quite the case. To illustrate how this approach can be dangerous, he tells the classic story of the fighter plane during the war (it’s a bit cliché, but there’s always someone who hasn’t heard it yet).</p><p>The B-29 planes returning from combat in World War II always had bullet holes in specific parts of the fuselage. The team’s idea was to reinforce those areas since they were more targeted. But a mathematician on the team noticed that statistically, they were only accessing a part of the sample: the ones that survived and returned. They didn’t know where the planes that crashed were being attacked.</p><p>The conclusion was that, probably, the lost planes were being shot at other parts of the fuselage, causing them to crash. And the surviving planes were precisely the ones being attacked in the areas they were trying to reinforce.</p><p><strong>Conclusion</strong>: reinforcing the rest of the plane, not the most bullet-ridden parts of the survivors, increased the aircraft’s resilience. Perhaps, if they had ignored what is called “survivorship bias,” where we only analyze what succeeded, they would have wasted precious resources without any improvement.</p><p>I distinctly remember many people using this fallacy during the pandemic, claiming that we were only counting the dead, not the survivors.</p><p>In other words, we need to carefully analyze the context in a comprehensive way to avoid failures. The answers to complex problems are never obvious.</p><blockquote>So, the author asks: why do we need a book talking about experience failures when there are so many out there? His answer is quite blunt: because most of those books are about <strong>DESIGN</strong>, not about <strong>EXPERIENCE</strong>.</blockquote><p>Here, he illustrates the difference between failures:</p><p><strong>Engineering failure</strong>: when the product doesn’t work as expected from a physical point of view.</p><p><strong>Design failure</strong>: when the product does work, but it’s so bad that people don’t want to use it. It’s when a disaster happens, and we blame it on “human error” when, in fact, the design led the user to that outcome.</p><p><strong>Experience failure</strong>: the product works, and people can use it, but using it is an experience no one desires.</p><h3>Having the right experience</h3><p>Here, the author provides a detailed account of the launch of the navigation, telemetry, and entertainment system called iDrive, introduced by BMW in 2002 in their flagship model.</p><p>Elegant, with most functions integrated, and few controls, most functions were accessed through a small number of buttons that could be pressed, rotated, or pulled. Simple, clean design, a true dream… that quickly turned into a nightmare!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*defdgI5mHv6Y5DUi" /><figcaption>Photo by <a href="https://unsplash.com/@thenerdymillennial?utm_source=medium&amp;utm_medium=referral">Shashwat Narkhede</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The public hated having to wait for the Windows operating system installed in the onboard computer to boot every time the ignition was turned on. There were a series of alert messages that needed to be acknowledged before everything started functioning. Nobody could understand the logic behind the controls, which left customers extremely irritated. Not to mention that every time the system was updated, the person had to take the car to the dealership. Imagine!</p><p>In truth, telematics and navigation systems in cars continue to be a major challenge. But in 2002, there were fewer resources and perhaps higher expectations. As positive points, it can be said that they succeeded in placing controls in accessible locations for the driver, provided clear feedback (on/off button, active/inactive function), introduced dedicated controls for some functions, made the software capable of incorporating new features, and the design was beautiful and clean.</p><p>However, they made a mistake by introducing unfamiliar controls, providing an excess of information (the driver constantly had to look at and close some warning window on the dashboard, diverting their attention from the road), the way information was organized and grouped was not intuitive, some commands had side effects on the configuration that were not visible, acronyms that made no sense, very slow processing, inefficient controls, and some unnecessary redundancies. In short, it was a horror.</p><h3>Finally, the test</h3><p>The result was that, after all the complaints and uproar, the company finally conducted a usability study with 500 users worldwide. The company made some modifications and improved many things. However, even with these changes, comparative publications with competing systems still consider iDrive a poor experience.</p><p>The end of the story? Between 2002 and 2008, sales of the 7 Series model, which featured iDrive, dropped by almost half and have not recovered to this day.</p><p>Why did it all go wrong? The author diagnoses that the software system, outside the company’s traditional area of expertise (automobiles), was launched with the concept of being a technological advancement, rather than a better experience for customers. There were likely not enough usability tests before the launch, due to the company’s overconfidence.</p><p>In this chapter, he also discusses the case of Google Wave, a collaborative platform for creating documents (similar to the precursor of Google Drive as we know it today), which also turned out to be a major failure due to its complexity; people couldn’t understand how to use it.</p><p>In both cases, the focus was on technological advancement rather than the user experience. It’s a common mistake in startups, but as you can see, it’s not uncommon in large companies either.</p><h3>Other cases</h3><p>The author thoroughly analyzes other famous cases of failure, such as OpenID developed by Yahoo to facilitate account access by remembering passwords and usernames. However, it became too complicated, even for the most technically inclined audience it was designed for, and it became even worse when non-technical users started using it (after all, the idea was good and useful; today it’s what allows us to log in to a website using a social media account like Facebook, for example).</p><p>The rest of the book follows this direction: the context, the history, what went wrong, why it went wrong (the different reasons analyzed one by one), and the lessons learned.</p><h3>Conclusions</h3><p>Lombardi concludes the book by saying that we fail because:</p><p>Experience matters. Three facts need to be acknowledged: accepting that errors happen openly sharing information is essential collecting verifiable data is necessary to correct errors <strong>BUT THEN, HOW TO AVOID FAILURES</strong>?</p><p>The author finally explains the method developed based on these studies that prevents similar failures from occurring.</p><p>It’s essentially the framework of the scientific method, which involves observing, formulating a hypothesis, conducting experiments and tests, and finally interpreting the results. However, it is adapted to the development of new products with a focus on the experience.</p><p>The adapted version would look like this:</p><ol><li>Observe the context (business, technology, and users)</li><li>Develop hypotheses</li><li>Test prototypes with users</li><li>Measure and interpret the results</li><li>Repeat as necessary.</li></ol><p>What did I think? Nothing groundbreaking, but I liked the way he organizes the information and analyses the cases. And more, he recommends some books that are on my reading list waiting for their turn.</p><p>In my opinion, I think it’s an important reference for designers, developers, UX designers, product managers, and everyone involved in the field. It’s easy to read and very enjoyable. Go for it!</p><p>_____________</p><p><strong>NOTE</strong>: This text was originally published in Portuguese <a href="https://www.ligiafascioni.com.br/por-que-falhamos/">on my blog</a> as the basis for an episode of my podcast “<a href="https://www.minhaestantecolorida.com/">Minha Estante Colorida</a>,” which is available on all podcast platforms. If you understand Portuguese, you’re welcome to listen to reviews of over 200 titles on various subjects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=deb16352283b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Red light for UX Design in Berlim]]></title>
            <link>https://medium.com/@ligiafascioni_8056/red-light-for-ux-design-in-berlim-bff2012cb155?source=rss-186b178fc420------2</link>
            <guid isPermaLink="false">https://medium.com/p/bff2012cb155</guid>
            <category><![CDATA[ux-research-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <dc:creator><![CDATA[Ligia Fascioni]]></dc:creator>
            <pubDate>Fri, 16 Jun 2023 11:43:48 GMT</pubDate>
            <atom:updated>2023-06-16T11:59:35.071Z</atom:updated>
            <content:encoded><![CDATA[<p>An innovation in the traffic light system in Berlin is causing controversy (and, in my opinion, rightfully so).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tu82aHd8vgegAlZT" /><figcaption>Photo by <a href="https://unsplash.com/@tungstenrising?utm_source=medium&amp;utm_medium=referral">Tungsten Rising</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I couldn’t find the origin of the idea, but here’s how it works: you’re about to cross the street when the little pedestrian figure on the traffic light turns green. Suddenly, out of the blue, the figure turns red.</p><p>To prevent people from being caught off guard, the transportation department thought, “Okay, let’s put a numerical countdown so that people know how many seconds they have to cross the street, like in many cities around the world.” That would be the most obvious choice, right?</p><p>But here’s the catch: we’re in Germany, and here the obvious doesn’t have much room. Instead of using universally understood numbers, they decided to insert an icon of a fading mini pedestrian crosswalk as soon as the light turns red. The five stripes of the crosswalk fade consecutively.</p><p>The pedestrian will supposedly know that when the last stripe disappears and the pedestrian figure remains red, it means that cars will start moving because the signal has turned green for them.</p><p>Honestly, I don’t even have words to describe how much of a UX (User Experience) Design mistake this seems to be (at least from my point of view).</p><p>Reading the <a href="https://www.rbb24.de/politik/beitrag/2023/06/berlin-verkehr-ampeln-fussgaenger-sicherheit-strassenverkehr.html">article from RBB24</a>, I learned that this system has been tested since 2013, with three traffic lights in the city (I confess I’ve passed by two of them and never noticed). Starting in 2024, the city will make a significant investment to replace all existing traffic lights with this creative and revolutionary system. That’s 2,100 installations scattered throughout the city. Just imagine.</p><p>I’m really curious and would love to have access to the user research. What was the size and profile of the sample? What was the feedback from people? Are there any suggestions for improvement? Is this the final version? Does it truly add value and make life easier or enhance pedestrian safety? Is the code understood without any confusion? Does the investment justify the return in benefits for users or the city?</p><p>So many unanswered questions…</p><h3>WHAT WOULD I DO</h3><p>Criticism is easy, especially when we don’t have access to the behind-the-scenes process. But with the data I have (just the final result, without much clarification), it doesn’t hurt to exercise some thinking.</p><p>If I had to solve this problem (assuming it is indeed a problem), the first step would be exploratory research using various methods such as observation, interviews, and empathy mapping to understand how users interact with this public infrastructure, how they perceive and comprehend its operation, whether it meets their expectations, and whether it enhances safety (or not). I would also listen to drivers since they are also stakeholders in this infrastructure.</p><p>The next step would be to gather all the information obtained in the preliminary research and create an Affinity Diagram to group ideas and identify patterns. This way, we could understand the pedestrians’ pain points and how they think, feel, and act in different situations.</p><p>Visualizing the information in separate groups helps us gain some insights, but they are still just assumptions. We need to validate them with more research (yes, it’s tedious, but necessary. Research is the soul of UX Design).</p><p>During this phase, we would also have enough information to precisely define the problem we are trying to solve (I must say that it’s not uncommon for research to show that what we thought was a problem is not, and the actual issue lies somewhere else we hadn’t even considered).</p><p>Defining the problem correctly is crucial because there are many products being developed for non-existent problems, and there are plenty of failed startups out there to tell their stories.</p><p>At this point, if it helps, we can create personas, which are imaginary users representing groups with similar problems and needs. They help us visualize who we are really working for.</p><p>Now we can start generating ideas to solve the identified problems or improve/facilitate/make the user’s life safer or more comfortable (in this case, pedestrians). There are various ideation techniques and different methods, so we won’t run out of ideas for lack of tools (by the way, I’m curious — did the idea of the crosswalk emerge during this research phase?).</p><p>With many ideas to address the identified problem(s), we begin by selecting a few to test. We can conduct a concept test (explaining the idea to some users and gauging their feedback) or create low-fidelity prototypes (rough and inexpensive, but they help users imagine a situation where they are using the proposed product). In the case of the traffic light, a hand-drawn cardboard with post-it notes representing the pedestrian crosswalks would suffice.</p><p>Then, we test and gather feedback (sometimes we have to discard an idea and try another) and continuously improve the prototype until we reach the final version (according to the information, a real version was installed for testing in 2013 for the traffic lights). If the UX Design methods were indeed applied, it would mean 10 years of research with real users before the decision to implement it citywide.</p><p>Or perhaps they used another method for the intervention?</p><h3>THE SOLUTION</h3><p>Either way, transparency is always the best way to bring people to your side when there is such controversy. The team simply needs to share a summary of their development work, documented research evidence, and the criteria that influenced their decision.</p><p>Let’s wait and see…</p><p><strong>NOTE</strong>: The video shows the reporter interviewing some pedestrians. None of them understand how the system works or what the crosswalk symbol means. A person who passes by the place every day said it took them a long time to understand what the crosswalk meant, but they still have doubts. Click on <a href="https://www.rbb24.de/politik/beitrag/2023/06/berlin-verkehr-ampeln-fussgaenger-sicherheit-strassenverkehr.html">this link </a>to watch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bff2012cb155" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A social network app for FPV drone pilots]]></title>
            <link>https://medium.com/@ligiafascioni_8056/a-social-network-app-for-fpv-drone-pilots-2ddf9011ddcb?source=rss-186b178fc420------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ddf9011ddcb</guid>
            <category><![CDATA[ux-ui-designing]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ironhack-berlin]]></category>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <dc:creator><![CDATA[Ligia Fascioni]]></dc:creator>
            <pubDate>Sun, 19 Mar 2023 18:22:22 GMT</pubDate>
            <atom:updated>2023-03-22T10:52:23.405Z</atom:updated>
            <content:encoded><![CDATA[<p>Final project for Ironhack UX/UI Design Bootcamp</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YjifOObJicOSHYV0" /><figcaption>Photo by <a href="https://unsplash.com/@rgaleriacom?utm_source=medium&amp;utm_medium=referral">Ricardo Gomez Angel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The final project of the Ironhack UX/UI Design Bootcamp was to design a Hi-Fi prototype for a real client. This work was made in collaboration with <a href="https://medium.com/u/b2c836ba6f8e">Natália Galves</a> and <a href="https://medium.com/u/b9cec39633e7">Marcele Mendes de Oliveira</a>, worked for Kwadklub, a small e-commerce company based in Berlin specialized in parts for FPV drone and related products.</p><h3>But what is FPV?</h3><p><strong>First-Person View</strong> (FPV) is a method used to control a radio-controlled vehicle from the pilot’s point of view. To fly FPV drones, the pilot wears a set of goggles that allow him to see what the drone&#39;s camera is seeing.</p><p>This sport/hobby is challenging because it is immersive; the pilot is not aware of the world around him. They can see the environment only through the drone’s camera lens.</p><p>That is why, according to the regulations, the flight must always take place with one more person (called a “spotter”).</p><p>Another issue is about the places to fly. It is not allowed to fly anywhere; they are special places (called “spots”) where the practice is authorized.</p><p>There are three main types of FPV flights: <strong>free style</strong> (where the drone performs radical maneuvers inside or outside an environment); <strong>racing</strong> (where there is a speed competition) and <strong>cinematic</strong> (the objective is to capture original and unusual images).</p><h3>The company</h3><p>Kwadklub was founded in 2021 by Raphael Freitas and Ana Breljak. Raphael is a FPV pilot, digital marketing professional, filmmaker and full stack developer in training. He intends to program the interface.</p><p>Ana Breljak is an Aircraft Pilot, FPV Pilot in training, app monetization specialist and takes care of the company’s operations.</p><p>The company’s goal is</p><blockquote>Create a home for FPV pilots, where they can connect, share their experiences and help each other.</blockquote><p>Kwadklub also want to provide to pilots an opportunity to earn some extra income through safely selling their used gear or providing services. In addition, they also intend to host and sponsor events to build global and local communities of FPV pilots.</p><h3>Secondary research</h3><p>We researched competitors apps that offered ways to connect FPV pilots. We found only two social networks specialized in this audience: <strong>Family FPV</strong> and <strong>Airvūz</strong>.</p><p><strong>Family FPV</strong> is the most complete, with a feed in Tiktok format, a place for conversations and a marketplace. <strong>Airvūz</strong> is just a beautiful collection of FPV winner videos of challenges.</p><p>There are also three more apps dedicated to showing flight spots (<strong>Drone Spot</strong>, <strong>Drone-Spot</strong> and <strong>Spotfindr</strong>) and an app that works as a forum (<strong>IDRL</strong>).</p><p>None of them provide information about the fleet, that is, which model of drone the pilot used to produce the photo/video when posting the content. This is a information that Raphael, as a pilot, misses a lot and would like to include in this project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQpoc6mQKEx7BO9dzSF-9A.png" /></figure><p>As indirect competitors, we found <strong>Instagram</strong>, <strong>Youtube</strong> and <strong>Facebook</strong>, where FPV pilots share their experiences and <strong>Reddit</strong>, to solve technical problems.</p><h3>Survey insights</h3><p>With the time we had to develop the project (less than two weeks), we did not have the opportunity to personally interview the FPV pilots (lack of space in their schedule).</p><p>We had Raphael, but we believed his point of view was biased because he was also our client. So we decided to do an online survey.</p><p>Sharing the Google form in FPV groups on special networks and inviting some of them privately, we got 15 responses from pilots all over the world.</p><p>We got some interesting insights: 100% was male, among 18 and 50 years old. Most of them (46.7%) flight on cinematic mode and only 13,3% racing.</p><p>About 87% customize and repair drones themselves. There is an inside joke that FPV pilots spend 50% of their time flying and 50% of their time repairing equipment. That&#39;s why fleet information and marketplace are so important.</p><p>We asked about the main challenges they face when it comes to FPV drone experiences. The most voted answers (they are open) were:</p><ul><li>finding good places (80%)</li><li>find people in the community to fly together (46.7%)</li><li>safety and regulations (40%)</li><li>find a drone spotter (20%)</li></ul><p>We asked also about what they like to share on social networks (most used were Instagram, Facebook, Youtube and Reddit). The answers were: pictures and videos, tips for beginners, old parts, new tricks, quad builds and specifications (fleet), fails, jokes and sales.</p><h3>User persona and the problem statement</h3><p>Based on the research information, we were able to build the user persona: Lukas Maier, a young FPV pilot, for whom</p><blockquote>“Flying an FPV drone is having the freedom to see the world from another perspective”.</blockquote><p>But at the same time, he feels frustrated because it’s hard to find good places and people to fly with.</p><p>These quotes were adapted from users comments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4wTDxhXW-8anbEVSSMYdCw.png" /></figure><h3>Ideation and solution</h3><p>To solve the user problem, we thought of building a social networking app that also includes forum, events, fleet and marketplace.</p><p>But it was a huge and complex project and we didn’t have time to finish the challenge in time.</p><p>So we decided to provide the basic framework for most of the features, but focus our efforts on completing a flow that solved our problem statement: <strong>find a location and someone to fly with</strong>.</p><h3>Moodboard and Style Tile</h3><p>The Kwadklub’s values are:</p><ul><li>togetherness</li><li>freedom</li><li>creativity</li><li>friendship</li><li>constant learning and improvement</li></ul><p>We tried to translate them building a moodboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u2NSAIbhkQc45bxgVqqPzg.png" /></figure><p>For the style tile, we remind that FPV drones are both a hobby and a kind of game. So we decided to use a drone propeller shape to build a bottom menu; at the same time, it is playful and conveys an idea of brand identity.</p><p>As the brand’s logo is black and white, we chose to keep the palette’s colors in this range, expanding to grayscale. To avoid too much contrast, we used a false white and a false black.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ybUgh64gw5nAMUMvpVESfQ.png" /></figure><p>The shape is not symmetrical (in real life the blades are not) and this feature also conveys the sensation of movement when the user changes menu items.</p><p>We also used blade shapes to indicate the content type at the top of the image content: cinematic, freestyle, racing, or education.</p><h3>Concept and usability tests</h3><p>In the concept test, people liked the idea and thought it could be useful.</p><p>But in the usability tests, once again we couldn’t rely on real FPV pilots. So we did many series of tests with our classmates and teachers using Lo-Fi, Mid-Fi and even Hi-Fi prototypes.</p><p>The focus was on whether people could complete the task (finding a place and someone to fly with when they went to Lisbon, Portugal) and we received a lot of very helpful feedback.</p><p>Based on usability testing, we changed the font family to Fira Sans Condensed (before we used Alumni Sans, but it wasn’t as readable), increased the font size in several places and menus, and chose icons that best communicate the idea.</p><h3>Hi-Fi Prototype</h3><p>Here are some screenshots of our Hi-Fi prototype. The first screen is the main feed (home of social network app), with some posts as example.</p><p>The next screens follow in the bottom menu: Search, Forum, Events and Marketplace. In Search we can see all the information in two ways: maps and lists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pBa1bHWR6pNNM7BelnQgzA.jpeg" /><figcaption>Hi-Fi Prototype Feed and Search screens (the latter in two modes: Map and List)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8L1MFtck3zCzcBitYz-ohw.jpeg" /><figcaption>Hi-Fi Prototype Forum, Events and Maketplace screens.</figcaption></figure><p>This video shows the main flow and the version that we presented to the client.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fcw5IhOWbcew%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dcw5IhOWbcew&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fcw5IhOWbcew%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/542c95c4f838d35bab3036e9dcd258ce/href">https://medium.com/media/542c95c4f838d35bab3036e9dcd258ce/href</a></iframe><h3>Key Learnings and Next Steps</h3><p>This was the most complete project we did in this bootcamp. Of course it needs a lot of improvement, but the experience was very valuable. We learned how to negotiate ideas very quickly (the three of us had different points of view most of the time), the importance of testing and having the customer as a partner.</p><p>In our favor, the entrepreneur Kwadklub really intends to implement our project.</p><p>Fortunately, we will have the opportunity to do a lot more testing, change details, improve functionality.</p><p>Therefore, this case study does not end here.</p><p>Wait for the next chapters…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ddf9011ddcb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EachRun: A Running/Walking App where you have full control]]></title>
            <link>https://medium.com/@ligiafascioni_8056/eachrun-a-running-walking-app-where-you-have-full-control-b62c7c7eee1e?source=rss-186b178fc420------2</link>
            <guid isPermaLink="false">https://medium.com/p/b62c7c7eee1e</guid>
            <category><![CDATA[ironhack-berlin]]></category>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <category><![CDATA[ui-ux-challenge]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[app-design]]></category>
            <dc:creator><![CDATA[Ligia Fascioni]]></dc:creator>
            <pubDate>Sun, 19 Feb 2023 13:46:12 GMT</pubDate>
            <atom:updated>2023-02-20T08:06:08.872Z</atom:updated>
            <content:encoded><![CDATA[<p>Ironhack Ux/UI Design Bootcamp Challenge</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*orLCXZMmkDjnCd_NrQyzjw.jpeg" /></figure><p>The fourth Ironhack UX/UI Design bootcamp challenge was to design a Hi-Fi Prototype for a wellness app. The group, composed by <a href="https://medium.com/u/b2c836ba6f8e">Natália Galves</a> and me, chose a running and walking app.</p><h3>First step: secondary research</h3><p>We researched five direct competitors (Adidas, Strava, Komoot, Nike and Step app/Pedometer) and found some patterns:</p><p>Most of apps provides GPS tracking, Apple Health integration, their own community and custom profile.</p><p>Reading the reviews we could conclude that people really like these apps: they are easy to use, have interesting challenges and the possibility to share the runs/walks on social networks.</p><p>As our intention was create an app which could solve problems and pains that others don&#39;t, we were really interested in negative reviews.</p><p>Actually, many reviews complained about the measurements; they weren&#39;t accurate enough. But we couldn&#39;t solve this problem using UX/UI design tools. Thus, another type of complaint caught our attention: many people were not satisfied with the app&#39;s coach feature.</p><p>See a review about Step app/Pedometer:</p><blockquote>&quot;I downloaded the app 3 days ago. I was curious about how many steps I am doing at my very active job. The app has confirmed that it is a lot, even on a slow day, so sure, it did what I expected. The problem is with the notifications from the app chastising me for failing to meet my ‘goal’ during the time that I literally didn’t have the app. Even if I had had the app and took zero steps, it is appallingly gross to program something theoretically intended as a fitness aid to shame the users.&quot;</blockquote><p>And there are more:</p><blockquote>&quot;VERY discouraging. Is it because I’m elderly (72), have arthritis in both knees and do not dash up the stairs like a 30 year old?&quot;</blockquote><p>We found more reviews talking about the app&#39;s coach feature: the unrealistic goals; the pressure for run/walk faster, longer, harder; the feelings of disappointment and failure when the person fails to reach the goal (because they are sick, did not sleep well or something happened during the activity — like an injury) and the bad feeling of being given &quot;commands&quot;. Some users consider the tone of notifications &quot;passive-aggressive&quot;.</p><p>We also found some comments about the complexity of understanding all the stats data and claiming the Dark Mode option on the screens.</p><h3>User interviews</h3><p>We interviewed eight users and the pressure was also mentioned:</p><blockquote>&quot;All the apps I have they don’t they me what to do. I would say leave me alone. It can be pressure and for instance you are sick you cannot do it and can be pressuring.&quot;</blockquote><blockquote>&quot;They should be motivating even if performance slows down for a while and not create pressure to run faster/longer/more intensely. The focus of the features should be on healthy running.&quot;</blockquote><p>The benefits of having control:</p><blockquote>&quot;I know for instance that on Stepz you choose the amount of steps per day. So you can control it. I like I can change the steps so you can manage according to your routine.&quot;</blockquote><p>But having a careful coach can be a very good thing:</p><blockquote>&quot;For running, the best feature is the audio feedback. Every kilometer or so having an audio feedback with pace, distance and HR is really good. Another feature I use a lot is virtual coaching: either by street runs (with someone on your year telling you to pay attention to your core, head high, breathing, etc) and treadmill runs as well.&quot;</blockquote><p>We also paid attention for this comment:</p><blockquote>&quot;Too much data makes the analysis of my performance too complex and complicated since I am not a professional athlete.&quot;</blockquote><h3>User persona</h3><p>With all this information we were able to build our User Persona.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vdcQbMKOVP5TN4L_PTLewA.jpeg" /></figure><p>We also built a User Journey combined with the Empathy Map, where, at each step, we show what our user persona feels, thinks, does and says.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fxx6ux97UG9Mqe7bTQjkog.jpeg" /></figure><p>At this point, the main issue was clear. Thus we composed our Problem Statement and the How Might We sentences.</p><h3>Problem statement</h3><p><strong><em>Busy users NEED a friendly and pleasant way to keep their running/walking activities on track without feeling pressured BECAUSE they already have a lot on their plate.</em></strong></p><h3>How Might We Question</h3><p><strong><em>HOW MIGHT WE provide people who want to control their running/walking activities a flexible way to achieve goals according to their routines and without pressure.</em></strong></p><h3>Ideation and concept test</h3><p>We did many ideation exercises and used the <strong>Affinity Map</strong> to classify related ideas. We decided to focus on the customizable coach feature and the possibility of setting goals for each new activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KK-ewGtWJCqC1h7AfbI9uw.jpeg" /></figure><p>Thus, we did the concept test with positive results. People got the idea of a feature that provides you full control, not just over the coach, but over each activity. You can set your goal whenever you decide to exercise.</p><h3>Moodboard and brand attributes</h3><p>Once brand building is not a UX/UI issue and requires much more time, knowledge and dedication that we had at the time, we defined some atributes just as a reference for the challenge: flexible, empowering and down-to-earth.</p><p>The moodboard helped us to choose colors based on attributes related scenarios.</p><p>So, we can see below the <strong><em>moodboard</em></strong> and the <strong><em>style tile</em></strong>, used to help us in the construction of the Hi-Fi prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aJzjlNZGrbubXOF1Da2E4w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xO37Id9wBUH527BFTtF7Nw.jpeg" /></figure><h3>Hi-Fi prototype and testings</h3><p>The main reason to build a Hi-Fi prototype is testing. So, we built a first version and tested it with a few people. We received some very useful feedback.</p><p>In order to keep the simplicity, we decided to place all the main control on the first page of the app (inspired by the Nike Run feature). But testers didn&#39;t understand that the full power of customization was there. Thus, we decided to be more explicit: we included the &quot;customize this activity&quot; message.</p><p>The Settings button, on left side, allows user to customize sport type (walking/running), carpeting (indoor/treadmill), countdown (on/off), heart rate (on/off), dark mode (on/off) and coach (on/off).</p><p>The Coach button, on right side, allows user to customize voice (male/female/neutral), tone (friendly/assertive/strict), speak (talkative/concise), receive coach per (distance, duration, peace of last km, calories, current heart rate, activity summary, pause music), besides volume.</p><p>Another suggestion was to put &quot;done&quot; button in two places (beginning and end) on popup customise screens, specially when they scroll. In addition, we also received feedbacks on font sizes (too small), profile picture at first page (feel of personalization) and other details.</p><p>Here is the &quot;before and after&quot; screenshot of the first page of our hi-fi prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TvME6ZciA7powzPxQ6ockg.jpeg" /></figure><p>Follow the video showing the version of hi-fi prototype that we presented in the bootcamp.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYuYOH95SfPM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYuYOH95SfPM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYuYOH95SfPM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fc8bca9cc71a0c78333e95681be9c4cd/href">https://medium.com/media/fc8bca9cc71a0c78333e95681be9c4cd/href</a></iframe><h3>Key learnings and next steps</h3><p>We learned a lot with this challenge and we believe that there are lots of things to improve in our project.</p><p>The main lessons are:</p><ul><li>Competitors reviews are full of insights, especially the negative ones.</li><li>Usability tests are very important to understand what users are thinking. And there are feedbacks that can be provided only on Hi-Fi prototypes (such as colours, font sizes and feelings about the design and information structure).</li><li>Our biggest challenge was to provide full control while keeping it simple. This is very difficult, because being explicit means giving more information and tips and being less clean and minimalist. It is a really though defiance, especially for beginners like us.</li></ul><p>As next steps, in a real project we should:</p><ul><li>to do more tests;</li><li>improve UI design (contrasts, consistence, visibility, information design);</li><li>improve stats screens;</li><li>help the implementation.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b62c7c7eee1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unsolicited redesign: Cat in a Flat app]]></title>
            <link>https://medium.com/@ligiafascioni_8056/unsolicited-redesign-cat-in-a-flat-app-d4b4f948e77b?source=rss-186b178fc420------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4b4f948e77b</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <category><![CDATA[ironhack-berlin]]></category>
            <category><![CDATA[ui-design-for-mobile-apps]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Ligia Fascioni]]></dc:creator>
            <pubDate>Sun, 12 Feb 2023 19:24:08 GMT</pubDate>
            <atom:updated>2023-02-12T20:03:48.888Z</atom:updated>
            <content:encoded><![CDATA[<p>Third Ironhack UX/UI Design Bootcamp Challenge</p><p>The third project at Ironhack UX/UI Design Bootcamp was redesign a real app. The challenge was individual and you would choose an app that you liked, but though you could improve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*MuhhL8NAncSixudYvad8IA.png" /></figure><p>As a cat owner (my husband and I live with Charlotte and Isabel — photo above), we usually hire people to look after my cats while we are away. Last year we discovered the site and app <strong>Cat in a Flat</strong> and loved the idea.</p><p>You can hire cat sitters near your home. They are verified, rated and you can choose them by proximity, price, experience, reviews and if they are also cat owners. You can also apply to become a cat sitter.</p><h3>Competitors analysis</h3><p>I did a research on the App Store and found many pet sitter apps. But most of them are focused on dogs, although some also accept cats and other animals.</p><p>The only cat-specific one was <strong><em>Cat in a Flat</em></strong> and as a cat owner myself, I very much appreciate this distinction because cats don&#39;t like changes in their routine and generally don&#39;t like going out (especially if they live in apartments).</p><h3>Moodboard</h3><p>While I believe that the app has some room for improvement, I like the colors and style. So I tried to keep the color palette; I just changed the proportion among them on my version of app.</p><p>The idea is to communicate <strong>comfort</strong> (because the cat sitter go to your home), <strong>care</strong>, <strong>friendliness</strong>, <strong>safety</strong> and <strong>convenience</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*sXBSvhNaGRDKAcAPgwCUYw.jpeg" /></figure><h3>Heuristic analysis</h3><p>The heuristic analysis for user interface design is based in Jakob Nielsen’s <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 general principles for interaction design</a>. For this case, most problems are about <strong>aesthetic and minimalist design</strong>.</p><p>There are a lot of useful information, but all gathered on the same front page. In addition, the app uses three different fonts (one of them made especially for the company) and faithfully reproduces all the content of the website, including the ad that invites users to download the app.</p><p>See screen shots of parts of the app&#39;s first page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XyQ3AxcJyXD1udha1eU_mQ.jpeg" /></figure><p>One of the things that annoys me the most as a user is the question about my street name keeps appearing even after login (when logged in, they know my address). So I tried to solve this problem in my redesign.</p><h3>Style tiles</h3><p>I built a style tile with the aim of simplifying the visual interface and making communication clearer. Because the time was short, this scheme is very simple.</p><p>I chose the Suculenta typeface because it was the closest to the original custom font. Helvetica Neue was chosen for its neutrality e readability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/1*PH_EEqkwpZ2ZLv-FT3TXbQ.jpeg" /></figure><p>We didn&#39;t have enough time for build a complete style guide, but the style tile helped a lot in building the new version for the app.</p><h3>Redesigned version: first pages</h3><p>I built a new version trying to simplify the flow without losing the company&#39;s identity. To that end, I kept the illustration of the kitten in every possible situation that didn’t jeopardize the flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9SzU_JBpzhx3EH7mqh1Lw.jpeg" /></figure><h3>Next pages and the importance of feedback</h3><p>Before I show you the next pages and flow, I need to say that we had the opportunity to present our redesign to an experienced guest UX/UI Designer from Ironhack and my work received a valuable feedback from <a href="https://medium.com/u/13b98d9153">José Victor Matos</a>.</p><p>The first point was the lack of headings on the <strong><em>Choose the Date</em></strong> page. Now it seems obvious; that&#39;s why it is so important to have your work evaluated by an experienced professional.</p><p>Another observation was about readability. Some texts were too small.</p><p>Finally, as the list of cat sitters was long, I put a navigator for the next pages in a place too noble; this should be at the end of the list.</p><p>Look <strong>before</strong> (the version that I presented to Victor) and <strong>after</strong> (with the suggestions implemented). It&#39;s not yet perfect (I&#39;m still learning), but the improvement is clear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*_0BTd2VAgvJwbKD0extA3g.jpeg" /></figure><p>The same with the cat sitter Ingrid H&#39;s page; the header was added and some texts had larger fonts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*xzUpguvTWjx_fHnnHBkh3g.jpeg" /></figure><h3>The final result</h3><p>The video below shows a flow of a cat owner that choose Ingrid H as cat sitter for a choosen date.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F74aixLzx_Po%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D74aixLzx_Po&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F74aixLzx_Po%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7ed1d58ffd0a924660950aafddb6f1ec/href">https://medium.com/media/7ed1d58ffd0a924660950aafddb6f1ec/href</a></iframe><h3>Key learnings</h3><p>The main lesson from this challenge was how important an experienced point of view is in providing feedback. I&#39;m very grateful for José Victor for the opportunity and insights.</p><p>We didn&#39;t have time (because next challenge is already underway), but in real life, next steps would test the app with potential users and gather feedback to improve the redesign.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4b4f948e77b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clayground: a collaborative ceramic store needs an e-commerce]]></title>
            <link>https://medium.com/design-bootcamp/clayground-a-collaborative-ceramic-store-needs-an-e-commerce-b1cba2bd332e?source=rss-186b178fc420------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1cba2bd332e</guid>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[bootcamp-experience]]></category>
            <category><![CDATA[ironhack-berlin]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ligia Fascioni]]></dc:creator>
            <pubDate>Sun, 05 Feb 2023 17:33:32 GMT</pubDate>
            <atom:updated>2023-02-11T14:47:51.347Z</atom:updated>
            <content:encoded><![CDATA[<p>Ironhack UX/UI Design Challenge</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*4G3Caid8f64Uya3Yo1R_QA.jpeg" /><figcaption>Credits: Clayground-Berlin-©HelenaMelikov</figcaption></figure><p>The second Ironhack UX/UI Design bootcamp challenge was to design an e-commerce for a real business. The group, composed by <a href="https://medium.com/u/c93d1cab9df">Montalt silla Javier</a>, <a href="https://medium.com/u/187107be9af0">Delphine Pezivin</a>, <a href="https://medium.com/u/ee7f0dda6b4f">Claudia Sobral</a> and me, started looking for a store in Berlin that would be willing to give us all the necessary information.</p><p>Claudia remembered a ceramics shop next her house, where she had already participated in a workshop. We talked with Tiziana, one of the owners, and she was completely open to the experience.</p><p>Tiziana told us in an interview that Caitlin, the founder, was preparing to move to Berlin, when she realized that the kind of cozy ceramic studio she used to working in Stockholm didn’t exist anywhere in Berlin<em>.</em></p><p>At these studios, a small group of collaborative potters worked together, becoming friends and helping each other. So she decided starts her own studio in 2019, in a cozy space in Friedrichshain. In her words: &quot;<em>Clayground became the first community ceramic studio in Berlin with flexible studio access for members around the clock</em>&quot;.</p><p>Clayground sells pieces from different crafters associated with the studio, and the perspective to having an e-commerce is very attractive, as it would be an opportunity to increase sales.</p><h3>Research time</h3><p>The next step was to start the research. We found some information about competitors and found that there were more than 30 small ceramic shops in Berlin (direct competitors). Big stores like Ikea and Woolworth were considered indirect competitors.</p><p>Among direct competitors, we found that 10 in 15 (67%) don&#39;t have e-commerce. And of the 5 that have, one used Etsy (an e-commerce platform for crafters). About 53% of the stores offer ceramic workshops and courses. All of them have websites, but some are very simple, with just one page with address and contact.</p><p>We did some interviews with people who used to buy pottery and most of them told us that they preferred to go in person and buy directly in the store because they wanted to see the pieces up close and know a little about their history and context.</p><p>Some of those interviewed told us that the pieces are unique and beautiful, but sometimes a little pricey. One of them showed some concern about the dimensions (personally is easier to get an idea) and three already bought pottery for gift.</p><h3>User persona</h3><p>With this data we were able to create our user persona, who is Giulia, a 35-year-old italian designer who doesn&#39;t usually buy pottery online.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gcw_6gbgrtjCYGuofPUdbA.jpeg" /></figure><h3>User journey map</h3><p>We simulate a day when Giulia needed to buy a gift for a friend; she was working, so she looked online for pottery shops. The experience was frustrating because there was not enough information about the pieces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u29qDzxkXVokbhfhh2PXRA.jpeg" /></figure><h3>Problem statement and How Might We</h3><p>The interviews also gave us elements to identify the problem statement:</p><p><strong><em>A craft lower needs more awareness about pieces because they want to know how the product looks and feels before buying it.</em></strong></p><p>The next step was create some possibilities to meet this need. Our choosen solution was:</p><p><strong><em>How might we provide a way so the costumer has more awareness about the product before they buy it?</em></strong></p><h3>Ideation</h3><p>During the ideation phase we had a lot of crazy ideas: holography, augmented reality, videos showing the pieces in 3D, among others. But the question was that the business was small and these features were unrealistic because they were expensive technologies.</p><p>So we decided to provided detailed information about the product with photos from every point of view.</p><h3>About the branding</h3><p>As a scholar of corporate identity (it was the subject of my doctoral thesis), I know that branding is much more than defining some attributes and designing a logo. We had no further information about the store’s identity other than that provided by Tiziana. The shop also had no logo.</p><p>So we decided not to work with this theme, as we believed that, in addition to not being the role or competence of a UX/Designer (Branding is not a UX/UI design problem), we would not have time for the work.</p><p>We just tried to translate the attributes listed by Tiziana in an interview into a moodboard.</p><h3>Moodboard</h3><p>We created a moodboard considering the brand values according with the owners: cozy, collaborative, natural, simple, functional, clean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mshI2j-XUgCn4b5ELmibZQ.jpeg" /></figure><p>As half of our group (Claudia and Delphine) caught Covid during this week&#39;s challenge, we didn&#39;t have time to test the moodboard with people other than Tiziana.</p><h3>Site map</h3><p>We classified the categories of products using card sorting in order to organize the site map. The main two categories are <strong><em>tableware</em></strong> and <strong><em>decoration</em></strong>. This is the result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1JZ9-ie2CAVBN1jmGDMDPQ.jpeg" /></figure><h3>Prototype and tests</h3><p>We did some low-fi prototypes but, as time was short and we were working with a reduced team, we decided to test directly the hi-fi prototype.</p><p>In the first version, the user could buy an item directly on the first page, by clicking on a product in a photo carousel. They were disoriented with by such a quick and straightforward experience and confused about navigation. That&#39;s why we added an introduction on the shop page to extend the experience. The results were much better.</p><p>This is a video with the simulation of use:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fsg4qzfQefrU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dsg4qzfQefrU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fsg4qzfQefrU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/669f480b00989c936b80272bf7ea9cd0/href">https://medium.com/media/669f480b00989c936b80272bf7ea9cd0/href</a></iframe><h3>Key learnings</h3><p>We learned a lot with this challenge:</p><ul><li>The key is to understand the problem we need to solve (problem statement).</li><li>Tests can change everything: that’s why they are so important.</li><li>Different points of view are a precious resource and we need them to do a good job.</li><li>Never forget that we are here to learn.</li><li>Everyone can work together if there is mutual respect and commitment.</li></ul><h3>Next steps</h3><ul><li>Show the result to the store manager and receive feedback.</li><li>Build more flows and test them.</li><li>Provide information to implementation.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1cba2bd332e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/clayground-a-collaborative-ceramic-store-needs-an-e-commerce-b1cba2bd332e">Clayground: a collaborative ceramic store needs an e-commerce</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</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 make young people go more often to the museums]]></title>
            <link>https://medium.com/@ligiafascioni_8056/how-to-make-young-people-go-more-often-to-the-museums-ae9a7caf0dd9?source=rss-186b178fc420------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae9a7caf0dd9</guid>
            <category><![CDATA[ironhack-berlin]]></category>
            <category><![CDATA[ux-design-thinking]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-design-case-study]]></category>
            <dc:creator><![CDATA[Ligia Fascioni]]></dc:creator>
            <pubDate>Mon, 23 Jan 2023 08:12:30 GMT</pubDate>
            <atom:updated>2023-02-12T12:45:38.806Z</atom:updated>
            <content:encoded><![CDATA[<p>First Ironhack UX/UI Bootcamp Challenge</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z2A8FkkVvEGcAvCB5ufYoA.jpeg" /></figure><p>As first project at Ironhack UX/UI Bootcamp, my team (<a href="https://medium.com/u/ce4b52782c1c">Andreia Salame</a>, <a href="https://medium.com/u/816de138b690">Liliana Zeferino</a>, <a href="https://medium.com/u/521e3d04249e">Stasya Mindlina</a>, Noa Niv) and I chose the wicked problem &quot;Museums and Cultural Heritance&quot;. The briefing was:</p><blockquote><strong><em>CULTURE &amp; HERITAGE</em></strong></blockquote><blockquote><strong><em>Since the 1970s, museums and other public institutions have been suffering a profound crisis. The purpose of this type of institution, is to make heritage accessible to everyone.</em></strong></blockquote><blockquote><em>They build bridges between art and people. </em><strong><em>How Might We help museums and other public institutions fulfilling their mission of preserving cultural heritage while making it more accessible to a wider audience?</em></strong></blockquote><p>The first assumption was that people don’t go to the museums anymore (or not so many often than before).</p><h4><strong>SEARCHING FOR MORE INFORMATION</strong></h4><p>Doing a secundar research, we discovered some articles about millenials and, yes, they like visit museums. But they don&#39;t use to go so often because the competition with digital entertainment and others events is big.</p><p>We choose young people as main public to research because, following this <a href="https://themuseumcreative.com/blog/museums-and-millennials">article</a>,</p><blockquote>(..) Millennials prefer special events, interactive learning, social experiences, and personal approaches they don’t often see happening during a museum visit.</blockquote><p>This showed us a interesting opportunity to attract this people using UX design and design thinking method.</p><p>The next step was a primary research; we interviewed 9 people between 17 and 24 years old.</p><p>With this information we can build an affinity diagram (grouping similar ideas in clusters), and choose the more relevant ideas. We got some insights:</p><ol><li>Most of interviewees like to go to the museum</li><li>They prefer to go to the museum with friends</li><li>They don&#39;t use to go to local museums so often, they go more times during vacation in another cities</li><li>They would like to go to the museum more often</li><li>They don&#39;t think that the price of tickets is affordable, even considering discounts for students.</li></ol><p>Based on this insights, we build our user persona: Isabella, a 20 years old Italian who studies Product Design in Berlin .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kK2CYs3xaQkhtExeIyZ90Q.jpeg" /></figure><p>The user journey helped us to understand better the context of Isabella&#39;s experience.</p><p>We went along Isabella on a saturday. She was running in the park in the morning and saw a street poster advertisement about an exhibition. She went to home, invited some friends to go together. Some of them declined the invitation because the ticket price was high.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GaaQBOw8cNj_ZBtpRs0R1Q.jpeg" /></figure><p>Then we were ready to define a problem statement:</p><blockquote>A young creative student needs to find an affordable way to visit museums because they wants to go there more often.</blockquote><h4><strong>IDEATION</strong></h4><p>So, it was time to brainstorm in search of solutions. We began to use &quot;<strong>How Might We</strong>&quot; tool, which consists of finding creative ways to complete the phrase and solve the problem.</p><p>In this Point, something very important happened. <a href="https://medium.com/u/b44f70ef730c">Dominique Camarotto</a>, our co-teacher, observed that we were trying to solve the problem finding ways to turn the ticket prices more affordable, or even free. But as designers, we don&#39;t have the control of that, because it is not a design problem; it&#39;s a marketing or management problem.</p><blockquote>So we realised that we can&#39;t change the facts, but, as designers, we have the superpower to change the perception of them.</blockquote><p>The concept of cheap, expensive or affordable depends on the user&#39;s perception. Students spend money on parties, games, concerts or whatever else they feel is worthwhile.</p><p>If the user thinks (or fells) that an experience is worth the ticket price, it is not expensive, and it doesn&#39;t matter how much it costs. The same line of reasoning can be used for cheap. If some experience is free but bad, it is expensive (because it costs time).</p><p>The next ideation exercise was about coming up with bad ideas to solve the problem and then turn them into good ideas. It was really fun, because some ideas were really crazy (like hiring actors to scare visitors, giving free drugs to change the visitors&#39; perception or playing loud annoying music).</p><p>We though of creating a &quot;Surprise Day&quot; at the museum, when everything could happen. Maybe parties, maybe performances, maybe games or challenges.</p><p>But we did one more ideation exercise called the Round Robin. It consists of “additive ideation”, where a team can work together in silence. Each one writes a idea on a paper and the next colleague adds something or reshapes the idea.</p><h4><strong>THE SOLUTION</strong></h4><p>Our best idea came from this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AfXEJ-l9YNGbf1ohc8__eg.png" /></figure><p>After this, we decided create an app for museum lovers; we realised that to change a perception of a human being, nothing is more powerful that another human being.</p><p>Actually, we took this phrase from <a href="https://themuseumcreative.com/blog/museums-and-millennials">an article</a> about the relationship betwen millenials and museums:</p><p><strong><em>&quot;Millennials look for special moments to share with their loved ones and want to experience things worthy of their time, energy, and money.&quot;</em></strong></p><p>In fact, we believe that if people had companion to go to museum or exhibition, they might visit these places more often.</p><p>For a first version, we decided to limit the app to the city of Berlin; so the app was called <strong>Berlin Museum Lovers</strong>.</p><p>The next step was do some sketches by designing the flow of information in the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GetJ1skA30ctbuVrHIQWOw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IRyieCmPMLTShybk79VkUg.png" /></figure><p>The first step in the app is to register. There, you can provide information such as your name, age, gender, languages that you speak and interest tags. One photo and that&#39;s it: pretty simple.</p><p>From there, you can look for a companion to go to a museum with you. First of them you choose a date; then the exhibition. Now, you can filter the fellow by age, gender and language.</p><p>From that, you can search for a fellow to go to a museum with you. First of them you choose a date; then the exhibition. Now, you can filter the fellow by age, gender and language.</p><p>Then, you just choose someone and chat with that person to combine details of the visit.</p><p>The wireframe can show it better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZfenhnTfp5ZlkLvijA65hQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*76yHILu4ljqldtChAV-3Zw.png" /></figure><p>Unfortunately we didn&#39;t have time to build a prototype, but we managed to do a concept test using a pitch. We explained the idea for a few people and got some insights:</p><ul><li>Most of people think this app is a good idea</li><li>Got to the museums alone is no problem for people betwen 30 and 40 years old</li><li>Some people loved the idea and suggested versions for other events (concerts, movies, parties, etc)</li><li>Single parents with children loved the idea of being able to go to the museum with other single parents with children</li><li>Apparently, this app can increase how often people visit museums</li></ul><h4>KEY LEARNINGS</h4><p>We learned a lot from this challenge.</p><p>First of all, research can change everything. We began this challenge assuming that people didn&#39;t like to go to museums, especially young people. And talking to some of them, we discovered a different scenario.</p><p>We also understood that we are not the users (all of us in the group love going to the museum and have no problem going alone).</p><p>It is important not to fall in love with the first idea; our very first idea was to build a game inside the museum, with challenges and quizzes about the exhibitions. It was not a bad idea, but we can do a lot more if our mind is open.</p><p>Finally, we learned that the best ideas come from teamwork. It is amazing how rich and creative a collaborative ideation can be.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae9a7caf0dd9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>