<?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 Joshua Rogers on Medium]]></title>
        <description><![CDATA[Stories by Joshua Rogers on Medium]]></description>
        <link>https://medium.com/@rogers.josh?source=rss-1b37c212fe21------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Hca5qfdAa-z7OW2dDQfeFw.jpeg</url>
            <title>Stories by Joshua Rogers on Medium</title>
            <link>https://medium.com/@rogers.josh?source=rss-1b37c212fe21------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:56:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rogers.josh/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[Eight habits great designers do]]></title>
            <link>https://medium.com/@rogers.josh/eight-habits-great-designers-do-14e36b5b4489?source=rss-1b37c212fe21------2</link>
            <guid isPermaLink="false">https://medium.com/p/14e36b5b4489</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Joshua Rogers]]></dc:creator>
            <pubDate>Fri, 12 Jun 2020 00:45:25 GMT</pubDate>
            <atom:updated>2020-06-12T01:31:51.433Z</atom:updated>
            <content:encoded><![CDATA[<h4>Abilities to look for in a designer</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RdBJR_3EqkXBaQce7NGFVg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@medbadrc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Med Badr Chemmaoui</a> on <a href="https://unsplash.com/s/photos/design?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Starting a Multimedia company after completing College may have been a bold move, venturing into the unknown and starting from a zero base.</p><p>I was young and wildly inexperienced. An enthusiastic 22-year-old startup looking to make the world a better place, one design at a time.</p><p>I understood it was going to be a tough and slow-paced venture to establish a healthy clientele base early. Especially true in the early years.</p><p>It took me many years and countless mistakes to become better at being a designer. I’m in my mid 30’s now and have since been recruited as a designer at <a href="https://medium.com/u/c4944b3eb26">Enabled Solutions</a>. Through my learnings, I have identified eight-core design principles that have become a part of my ethos.</p><h3>Don’t have a style</h3><p>Many successful creative designers have a clear and identifiable style. Potential clients can easily recognize their work, and their style may become iconic in certain circles or communities.</p><p>Having a personal style is a great way to get new clients quickly. If you’re lucky, you can take off and become wildly successful and in high demand in a really short period of time.</p><p>Just like fashion styles come and go, last year’s design trends may now be passé. Having a distinguished style can certainly make you stand out from the crowd. However, a great designer will possess the ability to become a chameleon, knowing how and when to reinvent themselves to stay ahead of the curve. Always looking for new ways to visually communicate, instead of relying on the old trick of the hat.</p><p>It’s okay to reuse a style or a look every now and then — if it fits the brief. Other than that, a great designer’s signature is their diversity, not the ability to repeat oneself.</p><h3>Ask early, ask often</h3><p>Ask the obvious and uncomfortable questions, constantly. This part is key when you’re starting the design process.</p><p>A great designer gives their clients what they want. But here’s the catch: what clients ask for hardly ever is what they really want.</p><p>It’s the job of a designer to find out what it is that a client essentially wants. By asking the uncomfortable questions early, they can avoid venturing down the wrong pathway.</p><p>As a designer, it’s good practice to keep asking questions — but make sure they are the right ones. Your client may <em>say</em> that they want such and such, but why do they say that? Throughout my years I’ve developed a set of framing questions to help identify what my clients are looking for. What are you trying to achieve? What is the underlying problem you’re trying to overcome? What do you need? What is the<a href="https://youtu.be/JJ4s9-zHb44"> job to be done</a>? When do you need it by? How much time do you think this will take? What is your MVP?</p><blockquote>If you’re going to solve a problem, you want sufficient information to solve it.</blockquote><p>Finding answers to those questions puts you in good stead in providing your client with what they want. Spoiler alert: it hardly ever resembles what they initially asked for.</p><h3>Explain, explain, explain</h3><p>As a young designer, I kept to myself a lot. I was often secretive about my creative process. Believing that if a process that works well — it isn’t to be tinkered with.</p><p>It took me some years to realise that one of the most vulnerable things designers can do is to be completely transparent about their process, the choices they make, and the doubts they have.</p><p>I discovered that transparency is one of the habits great designers do well: they explain.</p><p>A great designer should explain why they make certain choices. Explain what they tried. Explain what didn’t work, and why. Explain what their uncertainties are.</p><p>Being good at explaining why you work the way you do achieves two things. Firstly, it forces you to continually review your process, which makes it easy to spot inaccuracies or false assumptions. Secondly, it helps clients relive your train of thought, making them more likely to understand where things come from. Showing <a href="https://www.instagram.com/p/B7FcfDxAaHn/?utm_source=ig_web_button_share_sheet">empathy and understanding</a> your client’s needs can go a long way.</p><p>Your goal, as a designer, is to put yourself in the shoes of the people you’re designing for to truly <a href="https://www.instagram.com/p/B-tdumSAXwb/?utm_source=ig_web_copy_link">understand the problem</a> you are trying to solve.</p><p>Learning to explain yourself will make your work more solid and coherent, and help clients understand how beautifully orchestrated the things you make are.</p><h3>Options aplenty</h3><p>As a designer, it’s easy to become fixated on an idea or layout. As a rule of thumb, I try to provide at least three options that have been well considered. Providing multiple options is a useful discussion tool with the client. It opens a new line of dialogue, showcases your decision making and helps explain your design process to the client. Some designers prefer to provide the one option to pitch — this is okay too, after all, we are the experts, right?</p><p>In the past, I’ve used the <strong>Crazy, Medium Safe</strong> rule to help provide my clients with options and items to consider in their project. Providing a crazy “out there” design, an in-between and a safe design option, is a good way to show the extremities of what the client might be looking for. Additionally, this practice can help rein in client expectation, helping you steer them in the right direction.</p><p>For a designer, the <a href="https://designsprintkit.withgoogle.com/methodology/phase3-sketch/crazy-8s"><strong>crazy eights</strong></a><strong> </strong>design method<strong> </strong>is a nice way to move past that layout or idea that you may have fixated on in your mind right from the early pitch meeting. Putting yourself through this process can provide insight into building additional concept options for the client to consider.</p><h3>Assume nothing</h3><p>An essential for every great designer is to assume nothing — especially when it comes to creativity.</p><blockquote>Assumption is the mother of all mistakes — Eugene Lewis Fordsworth; Philosopher</blockquote><p>See, a great designer solves problems. To be able to solve a problem accurately and gracefully, you cannot make any assumptions. You need to know exactly what the variables are, and what the desired outcome is.</p><p>Only then can you start working on a solution. This is why a great designer does not jump to their tools right away. The first phase of any task, no matter how small, is always to ask questions. Do large amounts of research. Understand the product. Define the variables.</p><h3>Be kind</h3><p>Customer satisfaction depends a lot on the interaction between your staff and your customers.</p><p>Signs that a designer that shows genuine interest is a key indicator to determine whether the outcome will be a great result. An individual working purely for money shows through in the work. Genuine human characteristics in a designer is a strong quality to have, often resulting in strong relationships and positive interactions.</p><blockquote>A great designer will show kindness, be compassionate and will empathise.</blockquote><p>Kindness becomes contagious, which can often lead to a better outcome. Customer satisfaction can happen when all stakeholders are happy with the result.</p><blockquote>“Kindness doesn’t cost a penny, but its value is beyond measure to its recipient.” — Chris Holmes</blockquote><h3>Become a therapist</h3><p>I was once approached by a client that said “Our UI just isn’t cracking it — we are just not getting the conversions we thought we’d get. We need to re-do this whole UI. The UX probably needs some re-working as well. People seem to be confused; they are not sure exactly how to get through the product.”</p><p>So my team and I took a step back and said: “Okay well that’s interesting. Maybe that’s what we’ll have to do, but first, let’s think about what the problem really is”.</p><p>So I started to call their prospects and their customers and asked: “so what do you think about their product?” The common consensus was “It’s great; we love it! We have no idea what the company does though.”</p><p>From that, we were are able to determine it wasn’t so much a product problem — it was a value proposition problem.</p><p>I think this is at the core of a lot of failures. You can’t put the onus on the product.</p><p>That’s like saying your child is doing an awful thing. Raising a child and raising a product — ultimately the responsibility is with the parent and the creator of that product. You can’t blame the product. The product isn’t the thing that’s failing.</p><p>For my team and I, this opened our eyes as to what was actually going on behind the scenes. That’s when you realise you are more than a designer/product person, you are also a therapist. A lot of the work you are doing is indirectly unrelated to the product itself.</p><p>The questions that you ask as a designer aren’t so much about “Is this the right colour? Is the typography right?” it’s more about “Why did this problem happen in the first place? What kind of decisions drove the outcome?”</p><h3>Never stop learning</h3><p>The design world is an ever-evolving fast-paced industry.</p><p>To strive to become a high-end designer, it’s important to have a strong desire to improve. Try to maintain a never stop learning mindset. Try<a href="https://maketime.blog/"> to make time</a> to do so.</p><p>Find a curiosity for something that matters, and then above all else, do something with it. Because while learning is invaluable, if you have all the knowledge in the world and do nothing with it, you’ve squandered the most valuable opportunity available–to make a difference.</p><p>These are eight core values I like to keep in my designer toolkit. Not only have they proven successful with clients and projects time and again, but they also keep me engaged in the design world, doing the work I love.</p><p><strong>As a client:</strong> Working with a designer should be an enjoyable experience. If you can find a designer to work with who shares these core values, it will hold you in good stead for a healthy and enjoyable working relationship.</p><p><strong>As a designer:</strong> Try to work with clients who treat you with respect and understand the value of your design — clients who understand your value holistically and what it can bring to their product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14e36b5b4489" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to prepare a User Testing Report for your Client]]></title>
            <link>https://medium.com/@rogers.josh/how-to-prepare-a-user-testing-report-for-your-client-2ad899afad08?source=rss-1b37c212fe21------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ad899afad08</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Joshua Rogers]]></dc:creator>
            <pubDate>Tue, 10 Dec 2019 06:58:33 GMT</pubDate>
            <atom:updated>2019-12-12T04:52:23.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OFRGP4jrkR0i9ODcI1Eaow.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@headwayio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Headway</a> on <a href="https://unsplash.com/s/photos/design?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Over many years I’ve been working in the industry as a designer in the UI / UX space. I’ve run various user tests over my time, each unique and tailored to best fit the clients’ needs. Through this experience, I’ve learned that these sessions offer the most benefit to the client when you can follow up with a clear and concise User Testing Report to communicate your findings and key action items.</p><p>User tests are a great way to find out how people behave when interacting with a website or app.</p><p>I prefer to run remote user testing sessions as in my experience users feel less pressured to provide biased answers. Sometimes I conduct the sessions with user testers on my own, and sometimes with the client’s UX team. <a href="https://medium.springboard.com/a-guide-to-the-art-of-guerrilla-ux-testing-69a1411d34fb">Guerrilla User Testing</a> is another testing option; this method often leads to interesting feedback. Both testing options benefit from a document to share with your client and internal team.</p><p>Whilst running a user testing session is important, you also need to record the results. Not only is it impossible to keep all of your findings in your head, but you may also have a different recollection of events after the fact. Without capturing the results, you may end up with unintended bias or misrepresentation in your results.</p><p>You need to be careful about how you prepare a User Report. Creating a big report can result in a document that no-one reads. Creating one that’s too minimal, runs the risk that it may not be taken as seriously; resulting in the client not taking onboard your recommendations to the potential changes that need to happen.</p><blockquote>“I’ve taken a brief look at the report — can you give me a quick run down on the results?” — Client</blockquote><p>It’s important to keep your report lightweight and follow <a href="http://www.agilemodeling.com/essays/agileDocumentationBestPractices.htm#BestPracticesSimplification">lean design principles</a> so that it doesn’t slow down your process. After all, the tests are just a means to an end of improving your site experience.</p><p>Based on my experience I try to keep my report to under 10 pages, with clearly defined sections whilst using a key bullet point structure. Keeping the document clean and concise helps the user easily digest the findings.</p><p>Here’s a guide to making a comprehensive but light user testing report, with a rough indication of how big each section should be.</p><h3>Introduction</h3><h3>Summary of key findings</h3><p>Whilst aiming to keep the report short, it’s a good idea to make room for an executive summary. Including this slide right at the start, shows your client the most pressing two or three issues that came from the round of testing. Even if a client or the stakeholders read nothing else, they still learn this key information.</p><p>Aim to identify the pressing issues that came from the testing, If you were to advise only one change to improve life for the users — what would it be? By deriving this at the summary it will help focus your findings.</p><h3>Who you tested with</h3><p>Summarise the demographics of the users you tested with and how many there were. Usually, I try to capture as much information as possible that I feel the client and stakeholders may find useful.</p><p>Initially, I ask many introductory questions to the user testers — many of which don’t make it into the report. I do this to help calm the user and to build a friendly rapport with them, before delving into the user flow.</p><p>The data that does make it into my report is usually, user testing participants, age demographic and everyday iPhone / Android user. If you wish to include additional screener questions into your report, feel free to do so.</p><h4>Conduct five test sessions</h4><p>The rule of testing with <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">only five users</a> is a solid one that has always stood me in good stead. Testing five users will help you find up to 85% of the core usability problems in your product. You learn a lot from the first person you talk to, a little less from the next, and so forth. After the fifth user, you’ll observe the same findings repeatedly, but won’t necessarily learn anything new.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/1*Zyk_6E-Bh5U18q_Zdr5RDA.gif" /><figcaption>You only need to talk to five users to find 85% of the core usability problems.</figcaption></figure><h3>User Story Tasks</h3><p>Once identifying who you tested with, I usually identify the tasks that the users tested from. If working with a client it’s good practice to run this by your client beforehand — I usually share a Google Doc with my client early in the piece to ensure they are kept abreast on the evolving user flow script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*a2YNQDSUs_FqiwCkZgKFrQ.png" /><figcaption>An easy to comprehend visual aid will help your client interpret your findings</figcaption></figure><h3>Key Issues and Takeaways</h3><p>The main focus of this report is to identify key usability issues. Items that make this list are usually tasks that caused the most frustration to the user — you may find these items are reported more than once.</p><p>Aim to identify the issues almost as a bullet point like list, including a clear statement explaining the problem, possible solutions and client feedback on particular usability issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*IPG9YFCSMIeGRduFhov2Hw.png" /><figcaption>Identify your bugs and usability issues and order them by severity</figcaption></figure><p>Ideally, bugs should be found during QA and not during user testing but it’s hard to catch everything: things can break over time and users can do things you just didn’t plan for. I aim to capture bugs into this Key Issues and Takeaways section.</p><h3>Top user likes vs dislikes</h3><p>Whilst conducting a user testing session, a variety of odd bits, bugs and usability problems can arise that hadn’t been accounted for. It’s good practice to additionally capture this feedback — especially positive feedback as it’s easy to get lost in the problems and negatives!</p><p>Ending with some positives is a nice touch, and this slide can also be used to include suggestive feedback from your users that perhaps the design team, client or stakeholders hadn’t considered.</p><h3>Additional Advice</h3><h4>Pre-test questions (optional)</h4><p>Additionally, a lot of remote user testing platforms offer the opportunity to survey participants before (or even after) the test. These questions can be of varying usefulness, but any chance to gather a bit of extra detail from real-world users should be taken. Use it as an opportunity to find out a bit more about them.</p><p>As I mentioned earlier I usually try to establish a friendly dialogue pre-test to help calm the user. This especially helps when the user may be of a unique age demographic or unfamiliar with a different testing device.</p><h4>Capture each user session</h4><p>Recording each session is a great way to capture accurate results. I usually set up a small tripod with a mobile phone/camera. This way I can refer to the footage at a later date to double and triple check on each users findings. As I mentioned earlier- it’s almost impossible to keep all of your findings in your head.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*KIOuurEnZmwwZK-woAdrPw.gif" /></figure><p>Explain the purpose of recording the test, and mention you’re recording the testing of the product, not them.</p><blockquote>“I’m recording the testing the of product, not you. No need to worry about making any mistakes. And please don’t worry about our feelings. We want to improve our product and we need to hear your honest reactions.”</blockquote><h4>Follow ”Think Aloud Protocol”</h4><p>When moderating the testing, always ask the participant to think out loud. The think-aloud method is critical for getting inside the user’s head. It means asking the user to speak out loud everything they are thinking, so you can gain insight into the thought process behind the user’s actions.</p><p>As the participant uses the product, you should encourage them to think out loud and share their thoughts and ideas with you. Since talking while doing isn’t typical for people, you should ask them to do it:</p><blockquote>“While you’re using the product, I would like you to think out loud. Just say what you’re thinking, what you’re trying to accomplish, what you expect to happen after an interaction, and so on.”</blockquote><p><strong>Tips:</strong></p><ul><li>Don’t hesitate to ask test participants questions like, “What are you currently thinking?” “What do you think will happen next?” or “Is that what you expected to happen?” during the testing session to stimulate them to verbalise their thoughts and feelings.</li><li>Even when people are thinking aloud, sometimes they experience problems with verbalising their thoughts. That’s why you should ask clarifying questions if something seems unclear or you think there’s more information a test participant can share.</li></ul><h3>Get the template</h3><p>If you are interested in seeing a real client User Test Report of mine, I’ve included the PDF report and the Sketch working file, <a href="https://gum.co/WWGev">which you can get a hold of here</a> and customise as much as you’d like.</p><p>Thank you for reading! 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ad899afad08" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>