<?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 Sonja Bobrowska on Medium]]></title>
        <description><![CDATA[Stories by Sonja Bobrowska on Medium]]></description>
        <link>https://medium.com/@SBobrowska?source=rss-a6135d4ae422------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7GxCAgIEoy_Yp1z08pwpGw.jpeg</url>
            <title>Stories by Sonja Bobrowska on Medium</title>
            <link>https://medium.com/@SBobrowska?source=rss-a6135d4ae422------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:19:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@SBobrowska/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How do user research findings contribute to developing a strategy?]]></title>
            <link>https://medium.com/@SBobrowska/how-do-user-research-findings-contribute-to-developing-a-strategy-d12fee0a8b97?source=rss-a6135d4ae422------2</link>
            <guid isPermaLink="false">https://medium.com/p/d12fee0a8b97</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sonja Bobrowska]]></dc:creator>
            <pubDate>Fri, 06 Jan 2017 20:37:26 GMT</pubDate>
            <atom:updated>2017-02-14T07:59:37.278Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve worked in the UX field for several months now. During this time I realised that the design process is not as straightforward as I’d imagined it to be when I studied the theory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I6ZUtX0Er-xbfdRsZEJrrg.jpeg" /><figcaption>Sometimes making sense of research data feels like wandering inside a labyrinth. It’s such a relief to see the end of the path.</figcaption></figure><p>I got especially confused when I tried to develop a coherent strategy from research findings. First, there is a plenty of choice when it comes to synthesis so it’s hard to choose the “right” method, especially for a beginner. Second, I thought that I might have difficulty explaining my choice to stakeholders who are not familiar with UX thinking. Thus, this project was born.</p><p>I decided to answer this question:</p><p><em>How do user research findings contribute to developing a strategy?</em></p><p>To make it easier for myself, I broke it down into two related questions:</p><p><strong>What methods of research synthesis are used to develop a strategy that serves user needs and drives business goals?</strong></p><p><strong>How well does each method support the development of such a strategy?</strong></p><p>My aim for this project was to research, assess, and form an opinion about these methods. I chose to write about personas, alignment diagrams, and design principles because I’m most familiar with them. Every method has its pros and cons which depend on an organisation’s context, for example, its stage, structure and available resources. But I don’t write about these issues. Also, this isn’t a how-to guide for each method. There are many such guides and I note those that I found most useful during my research. I wanted the article to provoke a discussion.</p><p><em>Disclaimer: </em>I don’t have decades of experience in UX. I built my arguments based on more experienced writers’ perspectives and I chose to include what I found most convincing. I’m open to changing my mind, too.</p><h4><strong>What is ‘strategy’</strong></h4><p>First, I want to explain what I mean by ‘strategy’ in the context of product design. It seems that there are <a href="https://experiencinginformation.wordpress.com/2011/06/19/on-communicating-strategy-for-design/">several layers of strategies</a> which contain each other like a matryoshka. The top layer is the business strategy. It stems from the business model and helps prioritise objectives. It is probably related to profit or an exit, if you work for a startup. Next is the product strategy. <a href="http://www.svpg.com/business-strategy-vs-product-strategy/">This one</a> “speaks to how you hope to deliver on the business strategy” across touchpoints and channels. Finally, there is the design strategy. It provides “a framework for developing design solutions that support a given product strategy.” While the product strategy influences the roadmap, the design strategy influences the interface design. The methods I write about touch on these different levels of strategy to varying degrees.</p><h3><strong>PERSONAS</strong></h3><h4><strong>“We don’t use them”</strong></h4><p>Creating personas might be the most popular or at least the most familiar method to infuse strategy with user research findings. In theory, personas should help design teams and business folks in a myriad ways. They should instil empathy for users, and be a framework for product requirements and a filter for design solutions. And yet, when I conducted an informal (and unscientific) survey about personas in the UX community in Vienna, the overwhelming response from the crowd was, “We have them but we don’t use them.” Perhaps I shouldn’t have been surprised. When I asked for our personas in my first week at work I was presented with a set of no less than 12 “personas.” They were created in an internal workshop 2 years earlier and never used in design.</p><p>When a tool is based on unvalidated assumptions it’s actually safer that way. It’s also for this reason that <a href="https://medium.com/u/15e3d5b240db">Steve Portigal</a> <a href="http://www.portigal.com/wp-content/uploads/2008/01/Portigal-Consulting-White-Paper-Persona-Non-Grata.pdf">discourages</a> the creation and use of personas. I believe his criticism relates to a distortion of the method, whereby personas are created from guesses, and filled with fake or irrelevant data. This is an acceptable exercise only to create a pre-screening survey to recruit research participants. And even so, we should be careful to label it as bullshit personas to make sure we don’t use them for strategy and design.</p><p><strong>Why then are personas misused or underused?</strong></p><h4><strong>The origin of personas</strong></h4><p>Most publications credit <a href="https://medium.com/u/b1fa02015e7f">Alan Cooper</a>’s <a href="https://www.amazon.com/Inmates-Are-Running-Asylum-Products/dp/0672326140"><em>The Inmates Are Running the Asylum</em></a> for popularising the use of personas. Alan described personas as “hypothetical archetypes of actual users” who “represent [real people] throughout the design process.” According to him, a well-developed persona includes a name, a face, and a set of demographic characteristics such as race, gender, and nationality. Those demographics should conform to stereotypes because “stereotypical personas are more effective.” His reasoning is that:</p><p>“As a design tool, it is more important that a persona be precise than accurate. That is, it is more important to define the persona in great and specific detail than that the persona be the precisely correct one.”</p><p>These ideas echo across the web and literature. For example, an <a href="https://www.nngroup.com/articles/analytics-persona-segment/">article on the NN Group blog</a> states that such demographic data helps “to create an easy-to-imagine, relatable character.”</p><p>I believe that personas that adhere to this characterisation don’t aid in the decision-making process, but rather become obsolete as soon as the team moves from research to design.</p><h4><strong>What’s wrong with demographics</strong></h4><p>A key benefit of personas is that they help foster empathy among team members. But when we focus on demographics two <a href="https://medium.com/@indiyoung/describing-personas-af992e3fc527#.b7v4pjpxc">bad things tend to happen</a> according to <a href="https://medium.com/u/7f2b3796beec">Indi Young</a>. First, instead of focusing on motivations, we discuss age and gender. Second, we tend to attribute to personas stereotypical behaviours and attitudes. This can cause conflict within the team because our assumptions stem from different media impressions of and personal experiences with a subgroup of people. Thus, our interpretations of personas’ demographics diverge. Unfortunately, this leads to the development of shallow design solutions. I tend to agree with <a href="http://indiyoung.com/about/">Indi Young</a> that “[c]ognitive empathy requires not a face, not preferences and demographics, but the underlying reasoning, reactions, and guiding principles.”</p><p>The authors of <a href="https://www.amazon.com/Project-Guide-Design-experience-designers/dp/0321815386/ref=pd_sbs_14_t_0/168-0923221-3246110?_encoding=UTF8&amp;psc=1&amp;refRID=M4720FC7GEGR3K7TWFVY"><em>A Project Guide to UX</em></a> follow this type of stereotypical thinking. They write that assigning age and status to a persona is helpful because “[b]ehaviors of a 21-year-old college student and a 34-year-old professional mother are significantly different!” But this might not necessarily be true. For example, with regards to reading habits or fashion shopping these personas could have identical motivations. And so, it’s important to remember: demographics don’t cause behaviour; reasoning, motivations and beliefs do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KvCRr-9uDMXbdEjg." /><figcaption><em>A typical persona deliverable created using </em><a href="https://xtensio.com/user-persona/"><em>Xtensio</em></a><em>, a persona template tool. I think there are better, more narrative ways to communicate personas.</em></figcaption></figure><h3><strong>SUGGESTIONS TO IMPROVE PERSONAS</strong></h3><p>The following suggestions come from my readings around the topic. I must credit Indi Young, <a href="https://www.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed/personas">Lene Nielsen</a> and <a href="https://medium.com/u/8268cafa037f">Cyd Harrell</a> for these ideas.</p><h4><strong>Assign atypical characteristics</strong></h4><p>To diffuse the power of demographics assign your personas characteristics that are atypical or unusual for that subgroup of people. For example, if your persona is a nurturer and always wanted to work as a nurse, make them a 25 year old single man. This tactic helps the team focus on what’s important — behaviours and motivations — rather than on what’s easy to process — age, gender, marital status etc.</p><h4><strong>Write first person narratives</strong></h4><p>My second suggestion is to write persona narratives in the first person. This tactic accomplishes two things. First, it helps the team pay attention to the words they use to describe a persona’s inner world and context. This aids them to create messaging that conveys a deep understanding of users’ situation and problems. Second, simply reading a first person narrative helps us identify ourselves with and appreciate another person’s perspective (Think of the experience of reading a novel written in the first person). This technique like no other helps foster empathy for personas’ motivations.</p><h4><strong>Use descriptive phrases</strong></h4><p>Although my team was reluctant at first, they agreed to give these techniques a try. But my proposal to remove names and photographs from persona documents met stronger opposition. Alan has a particularly strong view about assigning names to personas: “A persona without a name is simply not useful. Without a name, a persona will never be a concrete individual in anyone’s mind” which makes me ask ‘why not?’</p><p>I agree that names and faces can be helpful to a certain extent — for recognition, but not for fostering empathy. Ideally, we would refer to user archetypes in descriptive terms, e.g. “people who treat food as nourishment” as opposed to “those who treat it as entertainment”). But I can imagine that this might become tedious. For the sake of brevity then my suggestion is to use gender-neutral names.</p><h4><strong>Try metaphorical descriptions</strong></h4><p>My second suggestion is a little more creative and comes from Cyd Harrell’s <a href="https://aycl.uie.com/virtual_seminars/using_metaphors_to_create_better_personas">use of metaphors</a> for creating personas. Why metaphors? George Lakoff and Mark Johnson explain in <a href="https://www.amazon.com/Metaphors-We-Live-George-Lakoff/dp/0226468011"><em>Metaphors We Live By</em></a> that we naturally tend to think in metaphorical terms anyway. This shows in our language as in“time is money” or “to win an argument.” If personas are archetypes, the best way to flesh them out might be to assign each persona a symbol (an object or an animal) that represents their motivations. Cyd argues that for recognition and recall of personas metaphorical representations work like a charm. And better than giving them names. That’s because metaphors prompt us to have emotional reactions. We immediately see images in our minds that correspond to personas’ characteristics.</p><h3><strong>ALIGNMENT DIAGRAMS</strong></h3><h4><strong>There are many different kinds</strong></h4><p>Besides personas, the most popular method in researchers’ pockets is what <a href="https://medium.com/u/4b8b911d809b">Jim Kalbach</a> called alignment diagrams. This deliverable is a schematic representation of the relationships between the service provider, the product or service, and the service recipient. It includes service blueprints, customer and user journey maps, experience maps, and mental model diagrams. Some writers seem to mix and match these terms or use them interchangeably. But I believe we should be careful how we label them. Let’s avoid adding more confusion to our field since it brims with undefined terms already. After all, there is a reason we have such a variety of related but distinct diagrams.</p><p>First, despite differences, all alignment diagrams have a common purpose, both strategic and tactical. Jim writes that “value creation lies at the intersection of human interaction with the provider of a service.” As my short definition explained, that’s exactly what alignment diagrams are for. They promote strategic discussions (which hopefully lead to consensus) and also help design teams on the tactical level. By highlighting to moments when the product underwhelms and the recipient experiences setbacks or confusion, they act as a catalyst for creating better solution.</p><p>Alignment diagrams differ when it comes to their focus. There are diagrams that focus on uncovering problems with the organisation’s processes. And then there are those that push the organisation’s product completely out of the picture during research. These differences hint at each diagram’s proper application.</p><h4><strong>Peek behind the curtain</strong></h4><p><a href="https://medium.com/u/99e7e21f8833">Megan Erin Miller</a> clearly <a href="https://blog.practicalservicedesign.com/the-difference-between-a-journey-map-and-a-service-blueprint-31a6e24c4a6c#.m57kp1nrv">explains</a> the differences between a service blueprint and a customer journey map. Essentially, while the service blueprint follows the flow of a customer’s journey, its focus lies on the backstage of the business. What’s important is how the organisation’s actions and actors support the creation of an experience for the customer. Blueprinting is most useful when we’re concerned about improving the business’ internal processes. And to do that, first we need to understand how our employees work together across departments to deliver that experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/0*suDzjS36MAT2bjMw." /><figcaption><em>A service blueprint created by fellow at the Carnegie Mellon University and used as an example on the </em><a href="http://www.servicedesigntools.org/tools/35"><em>Service Design Tools website</em></a><em>.</em></figcaption></figure><h4><strong>Depict archetypal journeys</strong></h4><p>What distinguishes the customer journey map from all other diagrams is its focus on the individual as the customer of a service or product. This customer is typically involved in a purchase decision. Similarly, the user journey map views the individual as the user of a system. The customer and the user don’t need to be the same person. The distinction is important because it determines what sort of behaviours we expect to depict and see in the diagram. These diagrams are useful when we want to understand how a typical customer or user moves through the system we designed to support their goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y0xW_zXaMjCBFt5v." /><figcaption><em>A customer journey map created by Mad*Pow and used by UX Mastery in their </em><a href="http://uxmastery.com/how-to-create-a-customer-journey-map/"><em>how-to article</em></a><em>.</em></figcaption></figure><h4><strong>Place your product in people’s lives</strong></h4><p>The experience map depicts generalised human behaviour in relation to achieving a goal or experiencing a life stage. As Jim <a href="https://experiencinginformation.wordpress.com/2016/03/12/sorting-things-out-customer-journey-maps-experience-maps-and-service-blueprints/">points out</a>, it moves away from the organisation’s product as the focus. Instead, it examines how that offering fits into people’s lives. <a href="https://medium.com/u/d330efe2baff">Chris Risdon</a>’s <a href="https://aycl.uie.com/virtual_seminars/vs89_mapping_the_experience">view</a> is that what distinguishes the experience map from the customer journey map is that it’s generalised. In other words, it helps us understand many customers or users who move across channels and have many goals at different points in time. But the customer journey map is archetypical. It focuses on a typical customer’s emotional responses in relation to a specific goal they want to achieve through our product. Since it’s a subtle difference these two diagrams get easily confused.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/0*a3DvUmldXV0RrvyF." /><figcaption><em>A pregnancy experience map, created by Beth Kyle and used by Jim Kalbach as an example in </em><a href="https://experiencinginformation.wordpress.com/2016/03/12/sorting-things-out-customer-journey-maps-experience-maps-and-service-blueprints/"><em>his articles</em></a><em>.</em></figcaption></figure><h4><strong>Understand people</strong></h4><p>Finally, the mental model diagram is clearly distinct from all of the above. It doesn’t even seek to acknowledge the existence of any particular service or product, at least during research. It’s agnostic about the tools people use. Instead, it concentrates on the broadest human motivations and behaviours. Then, towards the end of the process, we add our existing content and features to the “human” part of the diagram. Thus, we discover gaps in our offering. This is an invaluable perspective to explore for three reasons. First, some teams struggle to even define their user journeys, which is what happened in my team. The mental model then acted as a springboard for articulating such journeys. Second, it allows us to see gaps that we wouldn’t have seen otherwise. If we only focused on the experience that we already provide, we wouldn’t discover goals that are within our scope but which we don’t yet support. Third, it’s useful when we wish to understand how well our offering might work for people who aren’t our customers or users yet.</p><p>Unlike other diagrams, the mental model represents hierarchical rather than chronological relationships. Instead of dealing with sequential steps, it deals with people’s states of mind that come up for them in relation to achieving a specific goal. People can switch between these different states while trying to achieve one step of their journey. Tactically, this is useful when we want to rethink our product’s interactions and information architecture. On the strategic level, we get a unique chance to uncover new opportunities to create value for our users.</p><h4><strong>Design the future</strong></h4><p>These deliverables are called alignment diagrams for a reason. Since they represent the current state of our customers’ or users’ experiences with our product or service, they help align business objectives with people’s needs.</p><p>Users’ pain points in the current journey are the gaps that are waiting to be filled with creative design solutions. Thus, alignment diagrams help us move from the present towards the future. Which gaps we tackle first and which solutions might be successful are questions that are answered best with alignment diagrams. It’s much easier to realise a vision if that vision is explicit and grounded in solid research findings. These diagrams show how the present design falls short of satisfying people’s needs and invites us to imagine what the ideal could look like. There are several ways to flesh out such future visions. These include scenarios, storymapping, and storyboarding. All future-oriented deliverables draw on personas and alignment diagrams for inspiration. They also follow storytelling conventions. <a href="https://medium.com/u/1b382fc24375">Donna Lichaw</a>’s approach to <a href="http://rosenfeldmedia.com/books/storymapping/">storymapping</a> is an inspiring read in that area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1VpCovJwANJs6jhU." /><figcaption><em>A slide from Donna Lichaw’s </em><a href="http://www.slideshare.net/dlichaw/storymapping-the-user-experience"><em>presentation</em></a><em>: Storymapping The User Experience.</em></figcaption></figure><h3><strong>DESIGN PRINCIPLES</strong></h3><h4><strong>More useful than you might think</strong></h4><p>There is another research deliverable that can help teams make tactical decisions and support the strategic vision at the same time. This deliverable is a set of design principles. These short and opinionated statements express some condition that a design must fulfil to achieve its goals. Design principles are not the most common deliverable on any project but they do help with making design decisions. Well-defined principles are like lenses through which we view our designs to pick those that truly stand out. 18F has an <a href="https://pages.18f.gov/design-principles-guide/index.html">excellent guide</a> for defining them. And <a href="https://medium.com/u/b90ef6212176">Jared M. Spool</a> wrote a “<a href="https://articles.uie.com/creating-design-principles/">checklist</a>” for making sure that what we define is up to the task.</p><p>First, design principles must be specific and not vague. Common aspirations like “usable” and “delightful” are too general. They cannot function as decision-making filters because every single design tries to be just that. Plus, what does delight even mean? Similarly, contrasting positive versus negative qualities doesn’t work. Given a statement “beautiful over ugly,” the answer is obvious and it cannot be. The design principles that we use must be unmistakeable for design principles of our competitors, even if we work in the same market. When we look at designs, we must have a way to say “Yes, this is like us” and “No, this isn’t like us at all. It’s them.” Finally, design principles should be open enough to work across projects. Specifying the colour palette or functionality is the domain of style guides and requirement documents. Design principles should be more than that. They should be statements of beliefs that guide our decisions in all design aspects, including copy and information architecture. Take a look at the <a href="http://www.designprinciplesftw.com/">Design Principles FTW</a> website to find more examples of design principles, some better than others.</p><h3><strong>IN CONCLUSION</strong></h3><h4><strong>What it means</strong></h4><p>Every deliverable I described lies at the intersection of research and strategy. Each one uses a different method to analyse and synthesise research data and, as a result, adds a different dimension to that relationship. What method we choose depends on the questions we wish to find answers to, whether about the past or the future of our product. What’s important is not the deliverables themselves but their purpose.</p><h4><strong>Do it too!</strong></h4><p>I must say that this was an extremely useful exercise for me. Exploring this fuzzy area between research and strategy helped me understand not only what methods exist but also what makes each one distinct and better suited for different circumstances. It’s much clearer what methods I should use when and how to explain their value to those who might not be as familiar with them as well.</p><p>Also, I believe that every designer should develop her own perspective. This article outlines my views but I hope it prompts you to find your own!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d12fee0a8b97" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Improving volunteers’ efficiency]]></title>
            <link>https://medium.com/@SBobrowska/case-study-mobile-application-for-noble-box-227f4c02fa6e?source=rss-a6135d4ae422------2</link>
            <guid isPermaLink="false">https://medium.com/p/227f4c02fa6e</guid>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sonja Bobrowska]]></dc:creator>
            <pubDate>Sat, 14 Nov 2015 13:57:14 GMT</pubDate>
            <atom:updated>2017-02-24T12:22:38.951Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Helping </em><a href="http://www.szlachetnapaczka.pl/en"><em>Noble Box Project</em></a><em> volunteers organise an efficient Finale so that they can focus on providing an emotionally gratifying experience to donors and families in need.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DJzL6i7SyMuml61hSJ4ssw.jpeg" /><figcaption>Noble Box (Szlachetna Paczka) is fuelled by the enthusiasm of over 11,000 volunteers in all corners of Poland. This photo was taken in Wrocław, my hometown.</figcaption></figure><h3>Background</h3><p>For over a decade the Noble Box Project (Szlachetna Paczka) has been fighting poverty in Poland by providing direct aid to families who cannot afford a Christmas gift or fulfil their basic needs. In order to enable people to help each other effectively the project connects struggling families with volunteers and donors. Over one weekend in December — the Finale — donors deliver boxes of gifts to a warehouse. Before each box is then delivered to a family, volunteers must record its value, the number of people that helped create it, and the number of individual packets it contains (Each “box” is in fact a collection of packets that often include large household appliances such as fridges or washing machines).</p><h3>Problem</h3><p>Collecting and publishing this data is crucial for Noble Box because it conveys the project’s overall impact and efficiency. However, it is also a complicated process. Data is collected on tiny pieces of paper called questionnaires. After delivering packages and returning to the warehouse, volunteers submit filled-in questionnaires to district leaders. They in turn send the report to the headquarters, where data is entered into the system. Finally, updates appear on the Noble Box website. In other words, the process is inefficient and the data often goes unrecorded or missing.</p><p>Thus, Noble Box partnered with a national digital design agency, Edisonda, who created an <a href="http://konkurs.edisonda.pl/">interaction design competition</a> (Polish) and called on young designers to help solve this problem with a mobile application. This is a story of how I answered their call.</p><h3>Audience</h3><p>Noble Box is a nationwide project and each year its work is supported by 11,500 volunteers, including 670 district leaders who perform managerial functions. Thus, the app needed to support both novice and veteran volunteers with different levels of responsibility.</p><h3>Constraints</h3><h4><strong>Zero experience</strong></h4><p>At the time of the competition, I was still an inexperienced interaction designer. In fact, until then, I had been gathering on my own purely theoretical knowledge about interaction design methods and techniques. Thus, the competition was an incredible opportunity for me. Although I was nervous, I was also excited to discover whether I had what it took to pursue a career in interaction design. Little did I know!</p><h4><strong>Balancing competition requirements with what’s best for users</strong></h4><p>Since this was a competition, I had to fulfil various requirements in order to qualify:</p><ol><li>Submit the concept individually within a one-month deadline</li><li>Create an Android mobile app concept</li><li>Submit deliverables:</li></ol><ul><li>Feature list</li><li>Persona</li><li>Information Architecture</li><li>Three mockups that highlight the best features</li></ul><p>In addition, the brief outlined certain features which the client was hoping to incorporate into the concept. Except for the ability to submit box questionnaires, which was the primary business goal of the app, I decided to treat those as assumptions to be validated.</p><h4><strong>Working remotely</strong></h4><p>Finally, because I was living outside Poland at the time, all the work on the app concept, including user research and client presentation, had to be conducted remotely.</p><h3>Process</h3><h4><strong>Qualitative user research</strong></h4><p>Edisonda offered to connect each contestant with one volunteer to kick-start their user research process. Instantly I knew that interviewing one user would not be enough to get a sense for the complexity of the Finale. Instead, over two weeks I managed to interview five volunteers from different districts and with different levels of experience in Noble Box. It was the right call because it helped me discover the real range and difficulty of tasks volunteers must perform.</p><h4><strong>Analysis</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/403/1*WqfagmVWh2zpeX9cT2pgCQ.jpeg" /><figcaption>Journey mapping exercise helped me define the most promising features.</figcaption></figure><p>I worked on identifying insights from interviews, and transforming them into design solutions over a four-day period. Having collected more than 50 pages of interview transcripts, the analysis was the most challenging (and the most rewarding) step for me. I decided to use the journey mapping exercise and outlined all user’s tasks performed before, during and after the Finale, their goals and pain points, and resources or knowledge they needed access to at each step.</p><h4><strong>Uncovering insights</strong></h4><p>While the journey mapping exercise helped me wrap my head around the kinds of features that could bridge gaps in users’ experience, I still didn’t have a clear persona. For that, I simply categorised each user’s interview quotes under cognitive labels such as behaviours, goals, pain points, and others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d2h29M-5O2NvQ2qhIPBmTA.png" /><figcaption>I analysed user patters in a simple spreadsheet, which helped me create a solid persona.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*CIDI7dWkm8qewQnnWWerog.png" /><figcaption>This persona helped me distill two insights: 1) the Finale was a logistical challenge for volunteers, 2) leaders were already tackling this problem by relying on Google products. (Translated from Polish)</figcaption></figure><p>With the journey mapping exercise completed and a persona defined, I was ready to appreciate the insights this process helped me uncover. First, the Finale was an enormous logistical challenge: managing donor and family visits, managing the warehouse, scheduling and distributing drivers, filling in required documentation etc. In between these tasks, volunteers could hardly find the time to focus on what mattered most during the weekend — creating emotional connections and lasting memories with donors and families. My app could help them do that instead. Second, because most of my interviewees were veterans, I got a valuable insight into how district leaders were currently dealing with this challenge — they simply relied on Google Docs and Sheets.</p><h4><strong>Design exploration</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5OWsNafDqE94l7LT-S6a6g.jpeg" /><figcaption>This sketch shows my early interaction design exploration for various features.</figcaption></figure><p>Armed with the scope provided by the first insight, and the interaction and visual design direction uncovered by the second insight, I dove into exploration. I sketched for quantity over quality because as an inexperienced designer, I wanted to get a sense of the solution space. However, along the way I decided to adhere to Material Design because users were already familiar with and using Google products during the Finale, and I could rely on templates to quickly prototype the concept. This decision provided me with interaction and visual design solutions that I might not have used otherwise.</p><h4>Information architecture</h4><p>Before I dove into wireframing, I turned my attention to the information architecture. Because it was supposed to be a mobile experience, I created a user flow diagram to outline the app’s logic. This was a surprisingly challenging task and the diagram continued to evolve and change in lock step with the wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*cdb5WVckPOLWaHRjQhqwGQ.png" /><figcaption>User flow diagram A showing the functionality of the most important features. (Translated from Polish)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*9-rW7Z2n1TvRiQub-YbqtQ.png" /><figcaption>User flow diagram B showing secondary features.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*kCqr784iCUUSx54wyq3GLw.png" /><figcaption>User flow diagram C showing tertiary features were not prototyped.</figcaption></figure><h4><strong>Interactive prototype</strong></h4><p>The final interactive prototype highlights the three most important features:</p><p><strong>Box</strong></p><ul><li>filling out the questionnaire</li><li>letting the leader know that the box had been delivered</li><li>sending “Thanks” to donors upon delivery</li></ul><p><strong>Schedule</strong></p><ul><li>scheduling donor and family visits</li><li>requesting and scheduling appropriate drivers to deliver boxes to families on time</li></ul><p><strong>Tasks</strong></p><ul><li>distributing items to bring to the Finale among the team</li><li>managing volunteers tasks</li></ul><p>The interactive prototype can be accessed through the InVision App: <a href="https://invis.io/DC3JESV2G"><strong>https://invis.io/DC3JESV2G</strong></a> (Translated from Polish).</p><h3><strong>Retrospective</strong></h3><h4><strong>Yes, I can!</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*yw5y3UNUGvU1Upwau8k4fA.png" /></figure><p>Despite my lack of experience, my concept stood out from among 17 competition submissions and was awarded First Prize. While this makes me very proud, what is more important is that I emerged on the other side with a conviction that experience design is what I am meant to be doing. Throughout the process I felt more invigorated and alive than ever before. I discovered what it means to be in a state of Flow, as described by Mihaly Csikszentmihalyi, and until then, I believed it would never happen.</p><p>I just can’t wait to work more!</p><h4><strong>The hidden value of teamwork</strong></h4><p>I worked mostly on my own, occasionally asking whoever was in my vicinity for feedback. At times I got bogged down in inconsequential details and checking my ideas against other points of view was how I could keep moving forward. Ironically, this is how I discovered the value of teamwork in design. I truly believe that collaboration is indispensable to developing robust solutions and I wish to work on a team that communicates frequently and honestly.</p><h4><strong>User research, exploration and testing</strong></h4><p>Throughout the process I was often on the call with my interviewees, clarifying details and eliciting feedback on my general direction. This was invaluable and it makes me think that co-creation would have been an appropriate technique to try in this challenge. If I had more time, I would have spent it exploring navigation, interaction and visual solutions so that the primary features of the app would be truly highlighted and quickly accessible. On the other hand, the value of design thinking lies in quick prototyping and iteration on ideas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=227f4c02fa6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Enabling young people to become social entrepreneurs]]></title>
            <link>https://medium.com/@SBobrowska/case-study-human-centred-design-95e4c9f8dcbd?source=rss-a6135d4ae422------2</link>
            <guid isPermaLink="false">https://medium.com/p/95e4c9f8dcbd</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[portfolio]]></category>
            <dc:creator><![CDATA[Sonja Bobrowska]]></dc:creator>
            <pubDate>Sat, 14 Nov 2015 13:56:48 GMT</pubDate>
            <atom:updated>2015-11-29T20:06:15.282Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Developing a meaningful solution to a design challenge by following the Human-Centred Design approach.</em></p><h3>Background</h3><p>In order to practise my design thinking skills, I regularly participate in a MOOC developed by IDEO and Acumen+ —<a href="https://novoed.com/hcd-acumen"> Design Kit: The Course for Human-Centred Design</a>. The first time around, May through July, my remote design team and I collaborated on answering a personal design challenge addressing the level of empathy within a family. Unfortunately, the team fell apart before we reached a solution. Between September and November, I took part in the course again. This time, my new team focused on following the Human-Centred Design approach exactly as laid out in IDEO’s readings and workshop guides.</p><h3>Team</h3><p>My remote teammate, a UX designer from Oakland called Wendy, and I shared responsibilities equally throughout the process. We collaborated on transforming the hands-on nature of Human-Centred Design methods to an online environment.</p><h3>Problem</h3><p>Since we were limited to developing a digital solution due to the nature of remote collaboration, we picked a design challenge about social entrepreneurship, i.e. “How might we enable more young people to become social entrepreneurs?”. The project brief highlighted the lack of support and funding as the biggest barriers for young people seeking to establish social enterprises. However, from my personal experience of growing up and being schooled in Poland, I knew that this was an assumption that needed to be tested as I expected more fundamental awareness-related barriers to exist.</p><h3>Constraints</h3><p>Although working remotely within the Human-Centred Design approach was certainly a challenge, our bigger concern was the cultural divide that separated experiences of our target users in two geographically distant countries.</p><h3>Audience</h3><p>Young people are a diverse group in general. In addition, the cultural, social and economic differences that exist between Poland and the US are enormous, especially concerning awareness of entrepreneurship. One can say that Poland and the US are on polar opposites. While young people in the US, especially in the Bay Area, are well-aware of concepts such as entrepreneurship, social entrepreneurship and design thinking, young people in Poland have close to zero awareness of and direct experience with those concepts. While it was certainly a challenge to design a solution that worked for both groups of users, it was also an opportunity — one of the HCD research methods focuses on exploring extreme users and we definitely had access to those.</p><p>This is a story of how we tried tackling this design challenge and failed. And then, gave it a second try and fared much better.</p><h3>Process</h3><h4><strong>Take one</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aivZae1WsROtpvcOapKHXQ.png" /><figcaption>We conducted our “Download” session in Trello.</figcaption></figure><p>During the Inspiration phase, we conducted 14 interviews with nine potential users (including a Noble Box volunteer), one young representative of a social cooperative, and four experts from social entrepreneurship and education organisations. Although the range of experiences was as diverse as it could be, we managed to identify the following insights:</p><ol><li>Young people use social media in all aspects of their lives.</li><li>Because of a lack of role models, young people don’t know that social entrepreneurship is a viable career path.</li><li>Entrepreneurial skills are easier to teach than social sensitivity.</li><li>More privileged young people have to set aside their guilt and learn about more disadvantaged communities in order to help.</li><li>Young people like being taught through engaging, participatory means.</li></ol><p>From these we developed three actionable How Might We questions to guide us through the Ideation phase:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/1*0I63Kh0qqV-fU-xHw-l_jg.png" /><figcaption>Our brainstorming session, where we tried to answer the first How Might We question.</figcaption></figure><ol><li>How might we bring the experiences of successful social entrepreneurs to young social workers?</li><li>How might we teach young people to see societal problems within their own communities?</li><li>How might we create ways to teach young people about social entrepreneurship through engaging and participatory means online?</li></ol><p>Following the brainstorming session and after having selected the most promising idea, we dove into storyboarding. That’s when things started falling apart. We realised that the solution we created was too broad, too complicated and had no clear end-goal for the user. It was not going to work! You can access our <a href="https://docs.google.com/document/d/14yAEEEE4jIJUG3LoOWlv9OecRjikWubPx8MeEvSwQPM/edit?usp=sharing">first working document</a> and leave us feedback in the comments on where you think we started losing ground.</p><p>This was the turning point where we had two options. One, we could give up and submit what we had for assessment. Two, we could focus, go back to the drawing board and commit to developing a working solution. Because we valued gaining experience more than a course certificate, we opted for the latter.</p><h4><strong>Take two</strong></h4><p>We scraped our ideas and returned to our interview data. This time around, we knew what tools we were missing: a clearly defined persona and a framework for becoming a social entrepreneur. We developed both.</p><p>Having identified patterns and synthesised insights gathered during interviews, we finally knew who our target user was: a socially minded student who lacked entrepreneurial and design thinking skills, but who desperately wanted to make a positive impact on the world, whilst also making a living. This focus was what we were missing all along! Having created an empathy map for our persona, we knew that we had to target our users at a point in the framework where we could have the most impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2P3OJxpdrMtadhaW641JdA.png" /><figcaption>This is a walk-through that accompanies our visual storyboard (below).</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/475/1*B93ipVBqxGmzW83d5UXI2g.jpeg" /><figcaption>This storyboard helped us define the vision around our solution.</figcaption></figure><p>The solution—called CityHELP—addresses both, the old and the newly developed How Might We question: “How might we show young people how they can take action right away to become a social entrepreneur?”. It focuses on enabling young people to address problems existing in their local communities through the power of Human-Centred Design and design thinking. Through an online platform, young people would access local design challenges sponsored by organisations, businesses and the municipal government. Then, they would collaborate in person on developing meaningful solutions that address real problems. The teams responsible for top ideas would receive access to funding and guidance provided by design challenge sponsors. Although this is an ambitious solution, there exist several working predecessors, including the OpenIDEO platform as well as the examples of Global Service Jam and Startup Weekend communities.</p><p>In order to test the desirability and viability of our idea, we decided to prototype three touch points. First, I created a simple paper prototype to test the onboarding process — the first interaction between the user and our platform. We wanted to know whether the design challenge and team presentation answered users’ expectations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KPxrAbVzBMewFHqrSMpTug.png" /><figcaption>This simple paper prototype helps us test the interaction between our users and the platform.</figcaption></figure><p>Second, Wendy wrote a <a href="https://docs.google.com/document/d/1fQklaR1rmErLtUqvZArgSj5Xxt6nKcZvkg5P9AAkRCo/edit?usp=sharing">newspaper article from the future</a>. This way we could text users’ and organisations’ excitement about the impact our solution could generate in the local community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*BzBt92dF_JHRQzeh1bPj-Q.png" /><figcaption>The Facebook event helps us test the idea with our target users — we’re trying to meet them where they are — on social media.</figcaption></figure><p>Third, I created a fake Facebook event to gauge young people’s interest in participating in design challenges which address their local community problems.</p><p>Our initial feedback from users revealed that we could make improvements to the app onboarding process, and tweak how CityHELP positions itself vis-a-vis the target audience.</p><p>People appreciate that CityHELP could help in real-life situations. For example, several potential users pointed out that many European cities are faced with a challenge of accommodating a large influx of refugees and CityHELP could help bridge the gap between young city-dwellers and migrants.</p><p>Currently, we are in the process of iterating on our designs based on feedback. You can review our work in progress in the <a href="https://docs.google.com/document/d/1Ys-e09-_wfcjnjVotNMcoyjWeEnbFzoU9wNtyH0BI4c/edit?usp=sharing">second working document</a> and also leave us your feedback in the comments.</p><h3><strong>Retrospective</strong></h3><h4><strong>Identify Human-Centred Design methods that work for your team</strong></h4><p>It was interesting to have followed the Human-Centred Design approach as laid out in the course guides and discover that it was lacking, at least in our experience. By adhering only to the methods prescribed in the guides, we missed out on a large chunk of analysis and synthesis work that turned out to be invaluable. If I could do things differently, I would have followed my instincts and included the methods I found most helpful from the start, e.g. personas and journey mapping.</p><h4>Be aware of cultural differences</h4><p>While I have always been sensitive to cultural differences, having studied Japanese Studies and lived in four countries, throughout this Human-Centred Design process I have learned to appreciate that cultural differences can have a huge impact on the conceivable design space. In order for design solutions to be meaningful to target audiences, designers must make explicit the assumptions that exist in users’ cultures, whether they permeate whole countries or individual organisations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95e4c9f8dcbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>