<?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 Magdalena Pituła-Szpakowska on Medium]]></title>
        <description><![CDATA[Stories by Magdalena Pituła-Szpakowska on Medium]]></description>
        <link>https://medium.com/@magdalena.pitula?source=rss-2349e7cac6c3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*GTEqREuKmMpUiHqgNgOKrw.jpeg</url>
            <title>Stories by Magdalena Pituła-Szpakowska on Medium</title>
            <link>https://medium.com/@magdalena.pitula?source=rss-2349e7cac6c3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:50:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@magdalena.pitula/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 we created a professional usability testing lab in a day]]></title>
            <link>https://medium.com/netguru/how-we-created-a-professional-usability-testing-lab-in-a-day-6a695b41beb5?source=rss-2349e7cac6c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a695b41beb5</guid>
            <dc:creator><![CDATA[Magdalena Pituła-Szpakowska]]></dc:creator>
            <pubDate>Mon, 20 Jan 2020 10:46:00 GMT</pubDate>
            <atom:updated>2020-02-24T16:30:55.787Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A group of people at a table in a workshop room watching streaming at a screen." src="https://cdn-images-1.medium.com/max/1024/1*Gd2Qhj5imhKMxvf_MJhARg.jpeg" /></figure><p>Professional usability testing is often associated with a full-blown lab, a two-way mirror, fancy device mountings and multiple monitoring screens capturing every word and nuance of a respondent’s behaviour. It is definitely a huge advantage to be able to access this kind of a facility anytime a need for user testing comes up.</p><h3>The challenge</h3><p>But of course, it is not always the case that usability testing is planned ahead in full detail. One situation I have recently had like that was during workshops with a client. The goal of the workshops was to refine the final feature set for a mobile application, which would act as a supporting platform for an already existing, quite complex web application. Testing the mobile app prototype with users seemed like a perfect opportunity to validate the idea we would come up with during the workshops.</p><h3>Figuring out the approach</h3><p>We knew we had a few respondents coming in for the final day of the workshops. What we did not know, but worked out during the first few days of the workshops was that the client would be thrilled to see for themselves how real users interacted with the initial prototype of their product.</p><p>What we did not want to do though was to place the respondents in front of a committee observing their each and every move. It would have for sure put way too much pressure on them and most likely distorted the results of the study. But we definitely wanted to pamper our client and let them see the magic behind the curtains.</p><p><strong>Mocking up a lab</strong></p><p>Needless to say, we did not have a professional usability testing lab at hand. We had to think of a solution that could be set up in a very short amount of time and would still be effective and most importantly, glitch-proof. We decided to go with the tools we use everyday and mix them up a little bit to reach the solution we were aiming for.</p><p><strong>Rolling up our sleeves</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fk4-yG4gPbqQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dk4-yG4gPbqQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fk4-yG4gPbqQ%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/873d82b1964f69056679d67cc14977cc/href">https://medium.com/media/873d82b1964f69056679d67cc14977cc/href</a></iframe><p>As the prototype we were going to test was of a mobile application, we needed to record the screen of a smartphone, and at the same time cast it on a laptop screen. To do that we chose a standard recording software built into the computer by connecting the phone to the laptop with a cable and selecting the right source settings.</p><p>Why did we want the smartphone screen to be visible on the laptop screen? Because we wanted to do some live streaming to another room so that the client could see exactly what was going on. We did that by connecting with the client’s team via a popular online conferencing software and sharing the screen — with the mobile view on it — so that everyone could see, which screen of the mobile app was being discussed. The team in the control room cast their screen on a TV as well, so that everyone could sit comfortably in their chairs and watch the show.</p><p>Apart from that, we also thought it would be nice to have a full recording of the session, including the way the respondents hold the smartphone and which parts of the screen they tap and swipe with their fingers. To have it covered, we used a camera on a tripod. The recordings were obviously a life-saver in the data analysis phase, too.</p><p><strong>A glitch-free run</strong></p><p>It all turned out really nice and smooth. We did not experience any glitches or problems during our sessions, as we only chose familiar tools that we use on a daily basis in our work as designers. In total, we employed:</p><ul><li>1 smartphone;</li><li>2 laptops;</li><li>1 camera;</li><li>a TV.</li></ul><p>The “lab” really did look professional and made a great impression on the client. Could it have been done another way? Most definitely — yes. It would have probably been easier and require less creative technological effort had we used a dedicated lab, but it proved to be as effective. So cheer up, get creative and remember that usability testing can be easy, fun and experimental even if you do not have a fancy lab at your disposal. If you want to know more about the technicalities of this endeavour, feel free to get in touch.</p><p><em>A big kudos to </em><a href="https://medium.com/u/b5d90e0484d9"><em>Wojciech Wasilewski</em></a><em> for huge help with this endeavour.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a695b41beb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netguru/how-we-created-a-professional-usability-testing-lab-in-a-day-6a695b41beb5">How we created a professional usability testing lab in a day</a> was originally published in <a href="https://medium.com/netguru">Netguru</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 things you didn’t know about Voice User Interface]]></title>
            <link>https://medium.com/netguru/8-things-you-didnt-know-about-voice-user-interface-83f9ba85193b?source=rss-2349e7cac6c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/83f9ba85193b</guid>
            <category><![CDATA[vui]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[vui-design]]></category>
            <dc:creator><![CDATA[Magdalena Pituła-Szpakowska]]></dc:creator>
            <pubDate>Fri, 27 Dec 2019 13:43:40 GMT</pubDate>
            <atom:updated>2019-12-27T13:44:56.550Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Google Home on a kitchen rack beside jars with pasta" src="https://cdn-images-1.medium.com/max/1024/1*gEHCZjZuXuSKaa1xX8IJiw.jpeg" /></figure><p>With voice assistants getting more and more popular each year, we start considering them regular everyday companions. According to <a href="https://www.emarketer.com/content/us-voice-assistant-users-2019">eMarketer.com</a>, it’s estimated that 111.8 million people in the US alone will use a voice activated device at least once a month, and the number is growing. For many of us, talking to an assistant, or, putting it more technically, interacting with a Voice User Interface (VUI), has become a natural solution to handle various tasks.</p><p>Apart from the unavoidable occasional, slightly awkward misunderstandings, when talking to a voice assistant we get the impression that we’re talking to an intelligent being who can hear us, understand our needs and fulfill our requests. I would even go so far as to say, companions such as Alexa or Siri can become like a friend or family member to some. This may be partly due to our natural tendency to anthropomorphize entities around us but could also be explained with John Searle’s <a href="https://en.wikipedia.org/wiki/Chinese_room">Chinese Room argument</a>, which is cleverly referred to in <a href="https://www.amazon.com/Designing-Voice-User-Interfaces-Conversational/dp/1491955414">Cathy Pearle’s book</a> on VUI.</p><p>It’s our job as designers to make interactions with voice assistants seem natural, smooth and human-like. Obviously, nowadays we achieve quite impressive results with that — just take a look at <a href="https://www.mediapost.com/publications/article/326999/84-of-amazon-echo-users-satisfied-73-for-google.html">some stats</a> about user satisfaction in this matter. But that doesn’t mean that the assistant behind the VUI actually <strong><em>is</em></strong> intelligent or does any thinking at all. In fact, it usually doesn’t even have to — which is just an example to show you that in order to design a good VUI and have a successful voice control product, you should be aware of a few important things:</p><h3><strong>1. Most likely, the voice assistant doesn’t actually “understand” what you’ve just said</strong></h3><p>Well, at least not entirely. The speech recognition mechanism often uses the so-called N-best lists. When you say a voice command to your assistant, it transcribes your words into phrases to interpret them, just as if you were dictating something. But what actually happens is that It doesn’t just “write down” one version of what was recorded, but several versions of it. The versions of what you said, are then being ordered by likelihood and assigned a confidence score. The one with the highest score wins and you may feel understood even if the backstage transcript confused some words. So, as you can see, it’s more or less like the Probability theory in action.</p><h3><strong>2. The voice assistant may do what you ask even though it didn’t understand you</strong></h3><p>Depending on the confidence score of the best matched option, the voice assistant can act in different ways:</p><ul><li>It may simply respond to you and fulfill your request;</li><li>Repeat what you said and ask for a clarification;</li><li>Admit that it didn’t understand you at all (meaning: was not able to match the phrase to anything in the database it operated on) and ask you to repeat what you’ve just said.</li></ul><p>So, as you can see, the way you handle the N-best lists may have a great impact on how the assistant will behave.</p><h3><strong>3. You may feel heard and empathized with by your voice assistant even though it has a limited set of responses available</strong></h3><p>If you ever designed a VUI you know that predicting every possible phrase a user might say to the voice assistant is virtually impossible. Attempting to do so requires an immense amount of work and is thus very time-consuming. There is a way to address this problem.</p><p>You can do it by designing not only for words and phrases, but for clusters of categories with words likely to appear in relation to an interaction. This way, your assistant just needs a limited set of responses, where each response refers to a proper category and this way seems appropriate and logical to what has just been said, no matter what words were used exactly.</p><p>Let’s say the assistant asks you how your holiday was, it just needs to know how to react to an array of responses categorized as “good” or “bad”. No matter if you put it as <em>“It went great!”</em> or <em>“Fabulous!”</em> or even <em>“Quite ok”</em>, the response will be the same, as it all falls into the same category — “good”. The user won’t notice and the assistant will seem skilled at small talk.</p><h3><strong>4. To make the VUI “understand” you better, you should not be too specific</strong></h3><p>When you talk to a voice assistant and the worst case scenario happens: it says it didn’t understand you, your first instinct might be to repeat the key word of your statement, perhaps a little louder. At least that’s what you’d normally do in a regular conversation with a human being. The issue with VUIs is that it doesn’t really need you to speak louder — unless of course you were too far away or there was some interference, but this isn’t the case we’re focusing on here. The truth is the VUI often handles short phrases quite poorly, because it means there is less data to compare with what’s in the database. So it’s better to say <em>“Yes, I do”</em> instead of just <em>“Yes”,</em> to give the VUI more to chew on. With this in mind, it might sometimes be a good idea to design the dialogue inducing longer responses from the user.</p><h3><strong>5. The conversation with a voice assistant may seem strange to you, because it’s not actually a conversation</strong></h3><p>Not all VUIs are conversational. Well then, how come we are having conversations with them? When we want our voice assistant to help us with a particular task (e.g. order a pizza) it is usually enough for the VUI to follow a set path of questions to get answers necessary to perform a given task. It’s not the same as a true conversation, in which your interlocutor remembers what you said earlier and can refer to it without trouble, even if, for instance, you decide to use some pronouns not to repeat yourself all the time with the subject of what you’re talking about. You may not believe it, but this is something that is quite challenging to the VUI. That’s why some of your conversations may seem a little strange. But even though they do, the voice assistant can still help you with simple everyday tasks.</p><h3><strong>6. You’re more likely to give in to a voice assistant with an avatar</strong></h3><p>Even though an avatar accompanying voice is not crucial to have a fruitful user interaction with a VUI, some apps do use visual representation to enhance the experience. When done right, an avatar combined with voice has the power to inspire more engagement from the user, because it conveys the VUI’s personality in a stronger manner. Users are more likely to connect and empathize with the voice assistant because they tend to anthropomorphize it. So if you’re looking to influence your users, try to change their views or convince them to assimilate some beneficial changes in behaviour, you might want to give it a go and combine the voice assistant with an avatar. Use it to do good, not evil, though.</p><h3><strong>7. Testing a VUI design can be much like a theatre rehearsal…</strong></h3><p>Testing a VUI is full of challenges — it’s actually much more difficult to prototype voice in the way that doesn’t seem fake without doing some programming at the same time. The problem is that saying something to a mocked-up VUI can’t cause a reaction on a prototype, just like clicking a button would do in a graphical interface prototype.</p><p>So to test a VUI well, you need to apply some practices other that for standard interface testing. One of the simplest, least costly and time-consuming ways is playing out a dialogue designed for the VUI with a colleague, where one of you plays the role of the voice assistant and the other, of the user.</p><p>When you write out all possible paths a conversation can go, it’s not only worth reading it to yourself but also to actually speak it out loud with another person to check what is sounds like, just as if you were having a rehearsal before a theatre play. By doing that, you can realize which parts of the dialogue seem natural and which don’t. You can also verify if the verbiage used by your colleague is included in the possible responses set.</p><h3><strong>8. …and also like the Wizard of Oz</strong></h3><p>When your VUI design is a little more advanced, you might want to try to test it with users by presenting them with a working prototype. You then try to be like the Wizard of Oz from the children’s story — someone who can do some magic even though he’s not a real wizard but just a regular guy. Instead of waiting for the VUI to be fully implemented, you place a helper behind the scenes, who will (just like the Wizard), press the proper button to play a recording with the voice assistant’s response adequate to what the user has just said. This way you get the chance to see the user reaction to the product you’re designing in an almost real context.</p><h3>Designing a Voice User Interface — takeaways</h3><p>As you can see, the VUI often makes a poker face… or rather a poker voice. And this is just the tip of the iceberg of surprises you can stumble upon when designing VUIs. It’s obviously good to know the intricacies associated with VUIs and to use them best for the benefit of a great user experience.</p><p>Remember it’s always a good idea to:</p><ul><li>Keep in mind how technology behind the VUI works;</li><li>Aim for a natural, human-like outcome;</li><li>Come up with an efficient way to test your VUI design before releasing it.</li></ul><p>Do you have any stories about VUI design? Or are you thinking of building one? Let me know!</p><p><em>This post has been inspired by the book “Designing Voice User Interfaces” by Cathy Pearl.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83f9ba85193b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netguru/8-things-you-didnt-know-about-voice-user-interface-83f9ba85193b">8 things you didn’t know about Voice User Interface</a> was originally published in <a href="https://medium.com/netguru">Netguru</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When surgery meets military aviation — the design challenges]]></title>
            <link>https://medium.com/netguru/when-surgery-meets-military-aviation-the-design-challenges-1684455ec02e?source=rss-2349e7cac6c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1684455ec02e</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Magdalena Pituła-Szpakowska]]></dc:creator>
            <pubDate>Fri, 11 Oct 2019 13:53:21 GMT</pubDate>
            <atom:updated>2019-10-15T10:49:37.973Z</atom:updated>
            <content:encoded><![CDATA[<h3>When Surgery Meets Military Aviation — The Design Challenges</h3><figure><img alt="A surgeon looking at the Nodus Medical application on a screen in an operating room while performing a surgery." src="https://cdn-images-1.medium.com/max/1024/1*QWKO7581tAdZOijKAr9DsA.png" /></figure><p>A few months back I had the opportunity to be a part of a project in which the goal was to <a href="https://www.netguru.com/services/product-design">design an app</a> helping surgeons perform operations. The app was unique in that it adopted the rigid checks and procedures used in military aviation.</p><p>Behind this idea, there is a very interesting story of how the founders of Nodus Medical came up with <strong>combining the worlds of medicine and jet piloting.</strong> You can read all about it <a href="https://www.netguru.com/blog/nodus-medical-interview">here</a>. Nodus was not supposed to be just an app, but a whole digital assistant making the surgeon’s everyday life less stressful, starting from the stage of planning the operation, through performing it in the operation room, and supporting (or rather being a relief form) the paperwork that comes after.</p><p>So, what did being part of this project mean to me?</p><p>I simply love taking part in <strong>building products with a big mission</strong>, and helping save lives is certainly one. When you realize that, as a designer, you are the one to shape the way the product will work, how usable it will be, and what consequences it may bring if it isn’t — you get a great sense of both pressure and responsibility. This is why I treated this challenge with the utmost respect and diligence.</p><h3>The challenge</h3><p>As described to us by the Product Owner, the Nodus Medical app was supposed to <strong>serve as a digital assistant to surgeons</strong>, supporting the efficiency of performing their surgeries and relieving them of unnecessary stress. It was also meant to improve communication in the surgical team and significantly reduce formal procedures and paperwork around surgeries.</p><figure><img alt="Mockup of a screen from the iPad application." src="https://cdn-images-1.medium.com/max/1024/1*ts3XxlLCOOgpgCm5jEfPeQ.png" /><figcaption>Image credit: Przemek Kowal</figcaption></figure><h3>Problems to solve</h3><p>Thanks to the initial research done on the client’s side, we knew the key problems that needed to be addressed:</p><h4><strong>The cognitive load of remembering detailed procedures by surgeons, serious consequences in case of errors, and the surgeon’s stress around the process.</strong></h4><p>Did you know that <strong>up to 40%</strong> of post-surgical complications are avoidable?</p><p>You might wonder — do experienced surgeons really happen to forget sometimes one or two main steps during the surgery?</p><p>Well, I believe that it’s not about forgetting, but about allocating precious cognitive energy to recalling the next step of the procedure instead of being fully focused on the body part that is being operated on. Surgeons perform many different surgeries each day and <strong>medical knowledge advances all the time</strong>, causing the procedures to change.</p><h4>Distributing information among the team members and efficient communication</h4><p>Surgeons have their own way of organizing medical equipment, favourite instruments — each muscle memory is unique. It’s important that the medical staff (who changes all the time from one surgery to another) supporting the surgery know how to prepare the operating room and when to pass each instrument. The knowledge about which step comes after which is highly helpful in that process.</p><h4>Time-consuming administrative tasks and paperwork — mandatory post-surgery reports</h4><p>Each surgery needs to be followed up by <strong>proper documentation</strong>. A detailed report about the course of treatment, the methods used, and patient care recommendations need to be recorded. It takes a lot of precious time for both the surgeon, who needs to dictate the report, and the medical nurse who needs to transcribe it.</p><h4>Restrictions of the specific context of the operating room</h4><p>This was by far the most interesting of all the challenges in this project.</p><p>Why not just use a regular <a href="https://www.netguru.com/services/ios-mobile-development">iPad app</a>? Obviously, the surgeon’s hands are busy during the surgery. This makes it <strong>impossible to use a touch screen in a traditional way</strong>, not to mention that the environment is sterile and the surgeon’s full attention needs to be directed towards the operating area.</p><p>The lighting conditions during different surgeries may vary and reading distance has to be taken into consideration as well as other medical equipment which might interfere with the target device.</p><p>Not to mention the fact that it would be convenient for the equipment to be set up in no time so that it didn’t cause any additional hassle during the necessary medical setup of the surgery.</p><p>Apart from all those issues, other factors had to be taken into consideration, such as <strong>security and anonymity of the patient data</strong> as well as <strong>stability and efficiency of the software.</strong> A scenario where the app crashes during surgery was simply unacceptable.</p><p>So, as you can see, there certainly was a lot on the designer’s plate. How do you tackle such a challenge? How do you even start?</p><h3>The process</h3><p>Well, the answer to this is the right process tailored to the stage of the product development and to what’s already in front of you.</p><p>We had a lot of data delivered to the team by the product owner on Nodus Medical’s side. A great part of research had already been done, and we were able to use the expertise of a surgeon available to us throughout the whole project, so what we started with was <strong>a synthesis of the data to form conclusions, which were then crystallized into the product concept.</strong></p><p>In practice, we based it on the result of stakeholder interviews, personas, user journey maps, competition analysis, some interface benchmarks, and observations drawn from initial prototype testing.</p><p>It’s not every day that a <strong>client is aware of the value of the right approach and how defining the basics</strong> — who the product is for, what are the target users needs and problems and what context they operate (no pun intended) in — can influence the product and its further success in the market. Not to mention patient care.</p><p>In Nodus Medical’s case we were lucky to have a client who believes in such an approach and it made me more confident in proceeding with the project knowing that we were building the product on solid foundations.</p><h3>Searching for answers</h3><p>We knew that choosing the right type of interface would determine the shape of the product and both the design and development phases.</p><p>After the initial data synthesis we knew what the main features of the app should be and that the best medium for the app during surgery would be <strong>an iPad placed next to patient body function monitors.</strong> That’s why we did another round of research, this time a more technical one, to establish what options we had to control the interface using input methods other than touch.</p><p>To me, this was the most fun part of the research, but also the most difficult one. It involved creativity in searching for sources of state-of-the-art devices and weighing the pros and cons of each of the options, sometimes with scarce evidence of the device’s success in various contexts.</p><p><strong>The options we were considering were:</strong></p><h4>External button controls, e.g. foot pedal, hand remote control</h4><p>A foot pedal was a device that had already been tested by some surgeons. There were quite a few disadvantages to it though, such as complicated setup or the confusion between which button on the pedal evokes a particular action.</p><p>All in all it added to the cognitive load which was supposed to be reduced in the final product. The case with a hand remote control seemed similar, but additionally raised the question of the surgeon’s hands being occupied with medical instruments. We had to look further.</p><h4>Remote gesture interface</h4><p>The necessity to keep the surgeon’s hands free brought us to another device. The idea with gesture control would be to use a device which enables connecting the interface to a band which is worn on the user’s arm and, thanks to muscle movement detection, enables controlling the interface.</p><p>There were some questions around this one — could the device be kept sterile? Would the calibration be reliable enough? Could it be seamlessly integrated with the iPad?</p><h4>Eye-tracking interface</h4><p>Famous thanks to both gaming and user research, we thought of an eye-tracker.</p><p>The use of an eye-tracker makes it possible to control an interface by focusing one’s gaze on certain UI controls. The device needs to be calibrated to the user’s eyes and works within a distance up to 1 m. This sounded more promising, but still not perfect.</p><p>Again, the question was if the eye-tracker could be kept sterile and also whether it would not interfere with other operating room equipment. We also had to keep in mind the possible problems with performance outside the distance range of the device.</p><h4>Brainwave interface</h4><p>A brainwave interface requires a device in the form of a headband which catches and recognizes the type of brainwave activity of the user.</p><p>It enables controlling the connected device interface by focusing attention on UI controls and blinking to perform actions. The brainwave controller can be connected to the iPad by using Bluetooth.</p><p>Although it brought to mind an SF movie, apart from the problem of being kept sterile, it looked quite promising. Given that surgical equipment does come in the form of headsets, it would seem quite natural to the surgeons.</p><h4>Voice interface</h4><p>We considered a voice interface for the scenario where the app would read aloud the steps of the operation displayed on the iPad screen during the surgery, but also for one where the surgeon’s speech would be recognized and actions on the iPad would be performed based on the meaning of the phrase.</p><p>We were looking at a customizable wake-up word for the interface, speech recognition, and possibly <a href="https://www.netguru.com/services/natural-language-processing">natural language processing</a> for open commands.</p><p>We also had to bear in mind that a relevant technological approach needed to be determined for poor internet connection scenarios. We had to explore how the variety of accents would influence the interface on giving speech commands and keep in mind the noise disturbance in the operating room due to face masks and medical conversations being conducted.</p><h3>And the winner is…</h3><p>In the end, though definitely a challenge from a technological standpoint,<strong> the voice interface option</strong> was given a go as the most natural one for the users and leaving the most potential for further development of the product.</p><p>It was certainly not the end of the design challenge.</p><p>The iPad alone needed a sterile sleeve to be kept in the operating room, but luckily it turned out that it wouldn’t obstruct the use of the app. We had the precious <strong>Human Interface Guidelines</strong> to lean upon, but even the advised font sizes and styles had to be reconsidered because of the unusual distance of the iPad from the surgeon using the app with a patient in between.</p><p>We needed to decide if we were going with a light or a dark mode for the app for the operating room where lighting conditions could be changing.</p><p>We kept working through these challenges and tackling them one by one. We had a strong foundation of well-conducted user research and a technical background taking into consideration the specifics of the context and the users.</p><p>The project wasn’t easy — it was filled with the awareness of the gravity of each decision and no straight answers. But we all worked hard for it to be well-structured, precisely described at all stages, and thought through. This is how we kept it all so exciting and exceptionally fulfilling. You can see the results <a href="https://www.nodus-medical.com/">here.</a></p><figure><img alt="Mockup of a screen from the iPad application in dark mode." src="https://cdn-images-1.medium.com/max/1024/1*anPMfW0Y3RBFuLCpZmcpRw.png" /><figcaption>Image credit: Przemek Kowal</figcaption></figure><p><em>Originally published at </em><a href="https://www.netguru.com/blog/surgery-military-aviation-design-challenges"><em>https://www.netguru.com</em></a><em>. Also check out the </em><a href="https://www.behance.net/gallery/83294015/Nodus-Medical-The-Forefront-of-Surgical-Intelligence"><em>Behance case study</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1684455ec02e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netguru/when-surgery-meets-military-aviation-the-design-challenges-1684455ec02e">When surgery meets military aviation — the design challenges</a> was originally published in <a href="https://medium.com/netguru">Netguru</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[11 Common Critical User Experience Mistakes and How to Avoid Them in Your Design]]></title>
            <link>https://medium.com/netguru/11-common-critical-user-experience-mistakes-and-how-to-avoid-them-in-your-design-476317e12cb2?source=rss-2349e7cac6c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/476317e12cb2</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-mistakes]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Magdalena Pituła-Szpakowska]]></dc:creator>
            <pubDate>Mon, 12 Aug 2019 10:46:49 GMT</pubDate>
            <atom:updated>2019-08-13T12:57:44.619Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9MiQ3K8kPd5ZMkokYs1KLw.jpeg" /></figure><p>UX design is like with safety. Passengers won’t notice the lack of accidents, but they certainly will remember a bus collision, and even more so a train going off the rails or a plane crash. People will notice a <a href="https://www.netguru.com/blog/how-not-to-design-an-interface-for-your-mobile-app">lousy user interface design</a> much more often than appreciate an outstanding one.</p><p>The conclusion for both designers and product owners is simple — first, do no harm. Avoid the most annoying mistakes. This should <a href="https://www.netguru.com/ux-techniques-ebook">improve your website’s or app’s user satisfaction rates</a>.</p><p>Here’s a list of common design mistakes prepared for you by the Netguru team. Make sure you or your <a href="https://www.netguru.com/services/ux-design">UX design agency</a> don’t make any of them.</p><h3>1. Difficult to understand navigation patterns</h3><p>It’s a common mistake that is quite easy to avoid, yet <a href="https://www.netguru.com/blog/10-ux-tips-to-improve-website-navigation">hard-to-find navigation or menu buttons have always been typical UX flaws</a>. Although the term <a href="https://en.wikipedia.org/wiki/Mystery_meat_navigation">mystery meat navigation</a> was coined 20 years ago for describing navigation links that are not visible unless you hover the cursor over it, the mistake can still be found even in recently redesigned websites, of which the worst examples were usually built with Adobe Flash.</p><p>You can imagine how annoying this may be on mobile devices, where you don’t even have a cursor to move. You can see some recent examples <a href="http://www.webpagesthatsuck.com/mysterymeatnavigation00.html">of mystery meat navigation here</a>.</p><h3>2. Hidden value proposition</h3><p>Apart from being beautiful and impressive, websites and landing pages should do their main job — show the value proposition. While your team may be really into advanced features or the captivating product story, “what does it do for me?” is the most crucial question for the customers.</p><p>Make sure that the main headline explains the value and is visible at first glance. Your visitors have no time to search for it. If you are lucky enough, they clicked your ad or just found you in Google — don’t waste this opportunity. That’s why it’s so important for your visitors to learn what you do from the first impression.</p><p>There are many other ways to present your value proposition. You may add a video explainer or show the benefits of using your product with drawings or icons. If you’d like to play it safe, take a look at the market leaders in your sector and follow their example.</p><h3>3. Crouching “log-outs” and hidden “delete account” buttons</h3><p>This is very frustrating. Of course, you want your visitors to sign up for your product. That’s why you make it as easy as possible to register. However, you need to treat your customers with respect. You need to make logging out and deleting your account equally easy.</p><p>Hidden “exit” buttons are an effect of the designer’s negligence or the product owner’s greed. Whatever the motive, angry users will blame the latter. They will think you want to keep their data or pump up your stats on their expense.</p><p>Make sure you don’t make this cheap impression on anybody and remember about providing a comfortable way out of your app.</p><h3>4. Top bar navigation on mobile design</h3><p>Even if you are building your product for a very conservative or professional audience that uses mostly desktop devices, your web application has to work on mobile properly!</p><p>And this means replacing top bar navigation with a slide in the menu.</p><h3>5. Unnecessary animations that take too long</h3><p>Software users have always been anxious. They are getting even more anxious now. A lag hurts them. If an action takes too long, it means the software is crappy or the device is outdated. Each one is quite infuriating. Make sure you don’t make this kind of impression by making your UX animations too slow.</p><p>Research shows that the optimal speed of interface animations is somewhere between 200 and 500 ms, while all movements below 100 ms are just unnoticeable for the human eye. The new mobile generation needs applications to work even faster.</p><p>The animation speed should adjust to what the users are accustomed to, so it’s a good idea to track not necessarily your competition, but the most popular apps among your target audience — be it Facebook, Messenger, Instagram, Gmail, Slack or Snapchat.</p><h3>6. Underestimating the power of spacing</h3><p>The rule is called <a href="https://en.wikipedia.org/wiki/Principles_of_grouping">the grouping principle or the Gestalt law of proximity</a> and was formed by the Berlin School of experimental psychology. It’s quite straightforward — whenever you place objects relatively close to each other, our minds will consider them a group.</p><p>This is a dominant tendency. The Gestalt law works even with objects that have different shapes, sizes or colors — if they are close to each other, the brain will consider them a group.</p><p>Some beginner designers don’t know the rule and will try to override the spacing with shapes or colors. This will create chaos in most users’ brains. Remember to use spacing wisely. You can read more about <a href="https://medium.muz.li/gestalt-principles-in-ui-design-6b75a41e9965">the proximity principle and other Gestalt laws in this post</a>.</p><h3>7. Pesky newsletter pop-ups</h3><p>Once again, we have the product owner’s (or some other party’s) greed taking over. Of course, you’d like to maximize the conversion each visit. But you don’t want to sabotage the product at the same time.</p><p>You need to set your priorities accordingly. First of all, the product should be useful and appealing to the target group. Maximizing the promotional capacity is a secondary objective.</p><h3>8. Broken form validation</h3><p>A quality digital product needs an excellent database that stores clean records, as well as good protection against spam. Both goals are achieved by form validation, which is such an important question from the backend point of view that the UX is often neglected.</p><p>There are some validation errors that not only make it difficult but often impossible to use a service. I have encountered such a bug recently and it cost me 2 hours to perform an easy task in Polish e-bureaucracy. It was an infuriating experience.</p><p>Make sure your validation works appropriately. In more complex forms, the validation shouldn’t just appear when you click “Submit,” because it doesn’t help the user. Inline validation is a much better solution. However, it should work with some delay. Give your users some time before communicating the error. Use microcopy (small text explaining what input to type in) whenever necessary and communicate the errors in a clear but very polite way. Use words like “please” a lot ;)</p><h3>9. Overusing transition elements</h3><p>Functional animations are a great way of communicating actions to the user. Motion is understood intuitively and analyzed by different parts of the brain than static text, shapes, and color, which dominate interfaces. It also gives a real-life feeling to the digital world, as traditional buttons and switches move and click when we interact with them.</p><p>However, when using animations and moving elements, you need to be careful not to make any of these common mistakes:</p><p>A fade in animation is considered a good way of attracting attention to a headline or an image. It also shows continuity between the state before and after the action. However, you should be very careful not to overuse it. The content should be presented in a static form to be readable.</p><p>Each browser provides the user an option to scroll the viewable rectangle. Usually, you scroll from top to bottom, but at times you’ll also need this to move sideways. Often these elements are not very beautiful, which is why many designers try to replace them with custom scrollbars. Don’t do it. Your users are used to the scrollbars they have in Safari, Chrome or Firefox. It is unnecessary.</p><h3>10. No clear feedback on an action</h3><p>This is big. Your users need to get clear feedback whenever they add a product to their cart, rate something, add to favorites, copy a link to clipboard, or unsubscribe from a list. Not getting it will undoubtedly confuse, provoke additional customer service inquiries, and even make some of the users hate you when they find out that a meaningful action was not performed.</p><h3>11. Lack of a proper information architecture</h3><p>This a mistake that is the most difficult to avoid, since it’s not so easy to come up with a well-organized information hierarchy. However, taking some time and thinking about it is already a step in the right direction.</p><p>That is why you should think about it at the earliest stages of the <a href="https://www.netguru.com/blog/design-process-for-pros-our-live-ebook-launches-today">design process</a>. Information architecture (IA) is a complex science, and it’s much more challenging to fix an already broken IA in a working app than to build a healthy one from the start.</p><p>Your IA should put user satisfaction at the top — this is your primary business goal — provide the best value to the customers. If this works well, everything will come naturally.</p><p>Choose carefully if you’d like to use a hierarchical, sequential or a matrix IA; think about whether you’d like to group information by audience, topics, chronologically or just alphabetically.</p><p>Once you decide what system you’d like to use and what are your priorities for communication, you can adjust the navigation and search system.</p><p>That’s it. These are the 11 most crucial mistakes you should avoid. They may look obvious, but I bet that eliminating all of them will automatically put you in the top 20% of the best-designed websites or applications in your category. Take this list and walk through your plan, MVP or working product to check if you are making any of these mistakes.</p><p>If you need any additional help, contact Netguru, and we will happily help you with your <a href="https://www.netguru.com/services/ux-design">UX design</a>.</p><p><em>Originally published at </em><a href="https://www.netguru.com/blog/11-common-critical-user-experience-mistakes-and-how-to-avoid-them-in-your-design"><em>https://www.netguru.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=476317e12cb2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netguru/11-common-critical-user-experience-mistakes-and-how-to-avoid-them-in-your-design-476317e12cb2">11 Common Critical User Experience Mistakes and How to Avoid Them in Your Design</a> was originally published in <a href="https://medium.com/netguru">Netguru</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How User Research Can Improve Internal Communication]]></title>
            <link>https://medium.com/netguru/how-user-research-can-improve-internal-communication-242ddd19fe3a?source=rss-2349e7cac6c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/242ddd19fe3a</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Magdalena Pituła-Szpakowska]]></dc:creator>
            <pubDate>Mon, 17 Jun 2019 12:54:08 GMT</pubDate>
            <atom:updated>2019-06-17T13:05:07.387Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hPLIUCQysiRTvAfqH6kwSA.png" /><figcaption>Image credit: Paweł Szymankiewicz</figcaption></figure><p><a href="https://www.netguru.com/blog/how-to-incorporate-ux-design-into-your-product-design">User research</a> is the foundation of building new products or updating existing ones. It’s a powerful tool to <a href="https://www.netguru.com/featured/meet-temi-a-personal-assistant-robot">better understand the market, the users</a>, and their needs. It comes in handy with <a href="https://www.netguru.com/services/ux-design">building actionable user stories</a> in a very short period of time, helping you adjust the product to your audience. We leveraged it in one of Netguru’s internal projects, called Netguru Software Radar, so our team could take the most out of it. Here is how it went.</p><h3>What is Netguru Software Radar?</h3><p>Netguru Software Radar is an internal company service showing the <a href="https://www-netguru-co.sandbox.hs-sites.com/services">tools, technologies, and methods that we deal with at Netguru</a>. It distinguishes the ones that we use on an everyday basis, the ones we experiment with, and those which we find outdated. The radar helps tech leaders discover areas where we should invest and determine the direction the company should follow to stay on top of things.</p><p>The Radar was created a few years ago and in its first version the goal was very simple — to picture all the technologies in our stack on a map in the form of a radar, so that our team members could have a good visual overview of the technology that we work with as a company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Q-lXzWmYRRREZqTM.png" /><figcaption>Image credit: Paweł Szymankiewicz</figcaption></figure><h3>Why change it?</h3><p>Over time, we have noticed that there was still loads of potential left in the tool. We knew that many team members, especially newcomers, did not know about its existence and that knowledge about new technologies (which changes dynamically) was scattered across different channels, mostly on Slack, instead of being shared within the Radar map. The team was basically looking for people who were experts in a <a href="https://www.netguru.com/services/bespoke-software-development">particular technology stack</a> and asking them questions. Because the questions were spread across different channels, the same ones were being asked over and over again and we felt this was not the most effective way to manage internal knowledge.</p><h3>Our approach</h3><p>With all these problems in mind, we felt that a good starting point would be to get a full picture and gather real data about why and how our team members use information regarding our technology stack. We were interested in how they obtain it and what are the most common obstacles they come across while doing so. We also wanted to find out to what extent the Radar was being used and whether it was considered useful by the team. We surely had many hunches and assumptions about the outcome , but the point was to start building a better product based not only on intuition but above all on facts.</p><h3>The research issue</h3><p>The first step was to structure the above research goals and put them into questions:</p><ol><li>What tasks require information about the technology stack in order to be carried out properly?</li><li>In what situations and how often does the need for such information occur?</li><li>By what means is this information gathered?</li><li>What are the alternative actions when this information cannot be found?</li><li>What are the most common problems with gathering this information?</li><li>To what extent does the current version of the Radar meet the team’s needs and what could be improved?</li></ol><h3>The method</h3><p>Apart from what had already been done (the observation of messages exchanged in public channels of our company chat, which captured a variety of situations regarding the knowledge about technology stack), the obvious method to answer the questions above was to conduct in-depth interviews (IDIs) with stakeholders from different teams within our company. Given the availability of our team members, it seemed like the most valuable source of first-hand insights we could get.</p><p>We were hoping to identify needs and goals underlying the use of technology stack knowledge and come across ideas for improvements stemming from the nature of the most commonly encountered problems.</p><h3>User interviews</h3><p>We wanted to keep the user research phase short and actionable, and so we conducted a total of 6 interviews with team members from different departments, with different tenure and scope of expertise, to get the widest perspective possible. The interviews lasted no longer than 45 minutes each, given that we did not want the respondents to be away from their everyday duties for too long.</p><p>Each interview consisted of</p><ul><li>an introduction,</li><li>several open questions based on the research issue,</li><li>and a wrap-up.</li></ul><p>Because of each team member’s different background, every interview turned out to be a little different, as we let the conversation flow its own course depending on the respondent’s story. As the nature of the study was for an internal project, we did not feel that recording the interviews was necessary. However, we did keep detailed notes in order not to miss any important information.</p><h3>Analysis of the results</h3><p>After the interviews, we analysed the responses we got. The analysis was qualitative, so it was about categorising answers and looking for patterns in the different answers. We prepared a matrix with all the responses and labelled them with corresponding user needs or encountered problems so that it would be easier to aggregate them. We ranked the findings taking into account the frequency in which they came up, but also the emotional load that the respondents gave to them. As a result, we had a list of the most important needs and problems that the Radar should address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BOniwgK5m2cBZgOg.png" /></figure><h3>The output</h3><p>After the analysis, equipped with a list of tangible needs and problems related to the use of knowledge about different technology stacks, we proceeded to ideating how the Radar could meet the needs and relieve the pains of our target user group. We had a solid, fact-driven foundation to come up with solutions and enough data to prioritize those solutions. Instead of writing a full report (which we normally would have done when cooperating with an external client), we decided to write <a href="https://www.netguru.com/blog/doing-features-and-user-stories-the">user stories</a>, which allowed us to translate the ideas for solutions into <a href="https://www.netguru.com/services/custom-software-development">software features</a>. Some of those features included being able to:</p><ul><li>Identify the history of handling a given technology stack in our company,</li><li>View previous projects and expert team members in particular technologies,</li><li>Find sales information related to a technology stack,</li><li>Share information with clients in an easy way,</li></ul><p>…and many more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sBf2rA4IRybViO31.png" /></figure><h3>Conclusion</h3><p><a href="https://www.netguru.com/services/product-design-review">Designing digital products</a> based on research does not have to be time consuming, costly or complicated. It can be conducted in various ways and it always depends on the context of the idea for a product. It is never set in stone, but it always adds value to the product — it makes design and development decisions more <a href="https://www.netguru.com/services/ux-review">user-centered</a> and thus more likely to be successful. The investment of resources compared to the benefits is definitely worth it. Thanks to the user research we did for Netguru the Software Radar, by the time we started writing user stories we were fully convinced that we were heading in the right direction and planning a product which would be relevant and usable.</p><p>And now? After the round of user interviews we did at the beginning, and then further into the project, a working group among our team members gathered for regular meetings in order to track the performance of the Radar and talk about possible improvements. The group is cross-functional and new features are being implemented according to priorities agreed by the team. Stay tuned for the next news about our Radar!</p><p><em>Originally published at </em><a href="https://www.netguru.com/blog/how-user-research-can-improve-internal-communication"><em>https://www.netguru.com</em></a><em>.</em></p><p><em>Thanks for all the help in making this case study happen: </em><a href="https://medium.com/u/78f3aa4a5f7b"><em>Anna Borysiewicz</em></a><em>, </em><a href="https://medium.com/u/999feaae6626"><em>Natalia Chrzanowska</em></a><em>, </em><a href="https://medium.com/u/c61e1558ed16"><em>Paweł Szymankiewicz</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=242ddd19fe3a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netguru/how-user-research-can-improve-internal-communication-242ddd19fe3a">How User Research Can Improve Internal Communication</a> was originally published in <a href="https://medium.com/netguru">Netguru</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>