<?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 Dr Ziwei Wang on Medium]]></title>
        <description><![CDATA[Stories by Dr Ziwei Wang on Medium]]></description>
        <link>https://medium.com/@dr-ziwei-wang?source=rss-58c2fcf9ea8d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1MATzycV6nGfSc6YZE-q8g@2x.jpeg</url>
            <title>Stories by Dr Ziwei Wang on Medium</title>
            <link>https://medium.com/@dr-ziwei-wang?source=rss-58c2fcf9ea8d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:35:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dr-ziwei-wang/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[We’re here now. 来都来了. Might as well do a little bit of good.]]></title>
            <link>https://dr-ziwei-wang.medium.com/were-here-now-%E6%9D%A5%E9%83%BD%E6%9D%A5%E4%BA%86-might-as-well-do-a-little-bit-of-good-a8a45105c47a?source=rss-58c2fcf9ea8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8a45105c47a</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Dr Ziwei Wang]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 07:26:01 GMT</pubDate>
            <atom:updated>2026-10-09T07:26:01.706Z</atom:updated>
            <content:encoded><![CDATA[<p>There is a popular Chinese phrase: 来都来了.</p><p>Literally: “Well, we’re already here.”</p><p>It often describes something quite stupid: you’ve already travelled this far, spent this much money or put this much effort in, so you might as well carry on.</p><p>Basically, the sunk cost fallacy in four Chinese characters.</p><p>But recently I’ve started thinking it can be a rather lovely way to live.</p><p>I’m cooking a meal anyway. Why not cook it properly?</p><p>I’ve come to this conference. Why not actually talk to a few people?</p><p>I have to do this job. Why spend all day being angry about office politics and whether I’ll get the reward I deserve? 来都来了. Do it well. Learn something. Make something useful.</p><p><strong>I’m alive already. Might as well have a good time.</strong></p><p>That thought became more real yesterday when I visited an old graveyard.</p><p>Some gravestones had skulls and crossbones carved into them. They looked surprisingly sinister, so I looked up what they meant.</p><p>They weren’t simply trying to be macabre. The message was essentially:</p><p><em>This person is dead.</em></p><p><em>You aren’t.</em></p><p><em>So make something of your life before you are too.</em></p><p>What a lovely thing to put on a gravestone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LhzfQqGWm63jAB6unWSMvg.png" /></figure><p>And I think there’s a version of 来都来了 for UX too.</p><p>Most of us don’t work under perfect conditions.</p><p>The stakeholder has already decided the feature needs to exist. The technology is already chosen. The deadline is ridiculous. You’re redesigning a page when you know the real problem is the service behind it.</p><p>You can be completely right about all of that.</p><p>But the user still has to use the thing.</p><p>来都来了.</p><p><em>If we’re making the page anyway, why not make it easier to understand?</em></p><p><em>If the feature has to exist, can we at least add an explanation?</em></p><p><em>If we can’t redesign the whole journey, can we make this one moment less annoying?</em></p><p><em>Can we write an error message that doesn’t make someone feel like an idiot?</em></p><p><em>Can we put a little bit of joy into an otherwise boring interaction?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZhPbQoVVwJXkfiyaef6Mvw.png" /></figure><p>UX people can become very good at explaining why something is wrong: bad process, bad stakeholder decision, not enough research, technical debt, organisational politics.</p><p>And sometimes we should fight those things. <strong>Sometimes the right answer really is: don’t build it.</strong></p><p>But being right about something is bad won’t make the situation any better.</p><p>You wouldn’t have chosen this situation.</p><p><strong>But you’re here now.</strong></p><p><strong>来都来了.</strong></p><p><strong>Might as well add a little bit of good.</strong></p><p><em>Have you ever tried adding a bit sparklings to the boring work you have to deliver?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ionWt4dr-C7cd6gXpvhlA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8a45105c47a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI is not UX’s Magic Pill]]></title>
            <link>https://dr-ziwei-wang.medium.com/ai-is-not-uxs-magic-pill-2279ada73c78?source=rss-58c2fcf9ea8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2279ada73c78</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Dr Ziwei Wang]]></dc:creator>
            <pubDate>Sat, 03 Oct 2026 23:08:38 GMT</pubDate>
            <atom:updated>2026-10-03T23:08:38.646Z</atom:updated>
            <content:encoded><![CDATA[<p>I listened to two podcasts recently.</p><p>One was about concussion. The other was about inflammation. Two completely different problems, but at some point both scientists ended up talking about surprisingly similar things: sleep well, eat well, exercise.</p><p>And I thought, isn’t it crazy how boring the answer is?</p><p>We already know these things are good for us. The problem isn’t that nobody has told us to sleep properly or exercise. The problem is that doing them is hard.</p><p>Running is hard. Eating well every day is hard. Sleeping properly somehow becomes hard too.</p><p>We’d much rather discover something new that will fix everything.</p><p>I think UX has exactly the same problem.</p><p>Before AI, it was Figma.</p><p>For a while, being good at UX design seemed dangerously close to being good at Figma. Even then, people complained about designers making beautiful things without talking enough about what user problem they were actually solving.</p><p>But at least we were still talking about users.</p><p>Then AI came along and everything took a bit of a nosedive.</p><p>Go to LinkedIn, conferences, design communities: AI, AI, AI. AI agents. AI prototypes. AI research. AI workflows.</p><p>Sometimes I wonder if UX people talk about users anymore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k7zSjytIMczITDchL-psqg.png" /></figure><p>Even the title “UX designer” isn’t fashionable now. Everyone is a “product designer”. Conveniently, we managed to remove the word <em>user</em> from the job title too.</p><p>I don’t think this is because Figma or AI is bad.</p><p>I think it’s because tools are easier.</p><p>You can learn enough Figma to start making things in days, and become pretty comfortable with it in months.</p><p>AI is even more extreme. AI as we know it has barely existed for a few years and we already have endless AI experts. You can spend a few weeks building one thing with AI and give a talk about how to build things with AI.</p><p>Again, I’m not saying being genuinely good at these things is easy.</p><p>I’m saying they’re easy <em>compared with becoming knowledgeable about your field</em>.</p><p>Try learning psychology.</p><p>Behavioural science. Consumer psychology. Research methodology. Decision-making. Cognitive biases. How people actually behave rather than how we imagine they behave.</p><p>That takes years. Probably decades.</p><p>“We don’t have that long.”</p><p>So let’s learn another AI tool instead.</p><p>It’s basically the UX version of knowing we should exercise but continuing to look for the magic pill.</p><p>And AI actually makes this problem more important.</p><p>If everyone can generate ten decent-looking prototypes in a day, generating prototypes isn’t particularly valuable anymore.</p><p>Knowing <strong>which one is actually good</strong> is.</p><p>Knowing why someone would use it. What problem it solves. What behaviour you’re trying to change. What evidence you have. What you’re assuming. What you’ve completely misunderstood.</p><p>That’s the difficult bit.</p><p>So yes, learn AI. I use it constantly.</p><p>But maybe read a psychology book as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GvGikMCsb-jzQfrvsz3WAQ.png" /></figure><p>Leave a comment if you’ve actually read <em>The Design of Everyday Things</em> — and, even better, any psychology or behavioural science book that wasn’t written for UX designers.</p><p>I just hope Claude Design has been trained properly on behavioural psychology.</p><p>Otherwise, good luck with your ten fancy, average-looking prototypes made before lunch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2279ada73c78" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fixing a Broken “Live Survey” Report]]></title>
            <link>https://dr-ziwei-wang.medium.com/fixing-a-broken-live-survey-report-a374f8dec6cc?source=rss-58c2fcf9ea8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a374f8dec6cc</guid>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[quantitative-research]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Dr Ziwei Wang]]></dc:creator>
            <pubDate>Thu, 07 Aug 2025 17:54:39 GMT</pubDate>
            <atom:updated>2025-08-07T18:01:00.127Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>A practical case study for researchers who inherit bad analytics</strong></p><p><strong>TL;DR</strong></p><p>In 2023 I inherited a 46-slide deck that exaggerated tiny changes, mixed unlike users, and used inconsistent time windows. In 2025 I rebuilt it into a two-layer system: <strong>monthly windows, correct scales, segmentation that matters, a simple sentiment index, a survey drop-off analysis, and delivery via a Miro scan board + Excel source book</strong>. Senior leaders now use this pack in decision meetings. I’m not claiming impact beyond that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uaRFkWP7SvCV1AlSU_11vQ.png" /></figure><h3>Signs a reporting can’t be trusted</h3><ol><li><strong>Zoomed axes</strong> (e.g., SAT 2.5–3.5 instead of 1–5; SUS 48–64 instead of 0–100) exaggerate minor variations, making small changes appear significantly larger than they actually are.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/1*8s0EdlHxa1LyLpt5vfYrog.png" /></figure><p>2. <strong>Inconsistent periods</strong> (“August” is actually a Jun–Aug average). You should have consistant intervals on the X-axes. The naming of the point should represent what the value indicates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*3fWikZrd45Ct3a96Kdw4vw.png" /></figure><p><strong>3. “Better/worse” claims without stats or minimum-n rules.</strong></p><ul><li>Aggregation crimes (current + prospective students lumped together).</li><li>Manual word clouds + cherry-picked quotes.</li><li>Five dots per chart, no true trend view.</li></ul><h3>What I inherited (May 2023)</h3><p>Site-wide banner survey (Hotjar): user type → SUS → SAT → reaction cards → free text.</p><p><strong>Reporting</strong>: 46-slide PPT every ~8–9 weeks; five data points per chart; variable averaging windows; zoomed axes; subjective quote selection; manual word clouds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JygpvMF6OBUtf9xC4UIiow.png" /></figure><p><strong>Result</strong>: Misleading point-to-point variations, lacking longitudinal accuracy and provenance, resulting in inconsequential insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IP42WzSutoTjsp07ZNtlCg.png" /></figure><h3>What I built (Jan 2025) — minimum that actually fixes it</h3><h4><strong>Time windows &amp; scales</strong></h4><ul><li><strong>Monthly windows</strong> across everything (not just averaged groups).</li><li>SUS 0–100 (with bands), SAT 1–5.</li><li>Drop “better/worse” unless justified; add min-n flags and “do-not-compare” rules.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8y3TCQTstYQT1zx3OUeBCg.png" /></figure><h4><strong>Segmentation that matters</strong></h4><ul><li>Current vs. prospective students (non-negotiable). And levels of study.</li><li>Home vs. international within each.</li><li>IP: UK vs. non-UK as context only (IP is noisy).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t00uWk7EAusBK32gVRbu1A.png" /></figure><h4><strong>Sentiment without drama</strong></h4><ul><li>Use Hotjar’s Positive/Neutral/Negative labels.</li><li>Yearly <strong>sentiment index</strong> = (+1×pos + 0×neutral + −1×neg) / total.</li><li>Directional, not diagnostic.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*071Bbaw5BnF-UZefTBzMyw.png" /></figure><h4><strong>Survey performance (funnel)</strong></h4><ul><li>Step-level completion + drop-offs.</li><li>Identify top 2 question fixes; estimate recovered completion.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oqoG57o1DyRjN3emcPfpgA.png" /></figure><h4><strong>Delivery model (because reporting is a product)</strong></h4><ol><li><strong>Excel “report book”</strong> (source of truth): one sheet per audience with scores → trends → hypotheses → recommendations → caveats, plus a Changelog.</li><li><strong>Miro “scan board”:</strong> all charts tiled; each tile links back to its exact Excel tab.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ue1A33ClXkxidpoGnFrgbw.png" /></figure><h3>Architecture: before vs. after</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lq_Nm5rBGv8qiBoVRYMTiQ.png" /></figure><h3>What changed (and what didn’t)</h3><p><strong>Changed</strong></p><ul><li>Senior meetings now use this pack when survey results are discussed.</li><li>Stakeholders can see cross-year and monthly trends quickly and trace them to source.</li><li>Aggregation masking is gone (current ≠ prospective; home ≠ international).</li><li>Word clouds kept but clearly marked illustrative, not evidence.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Lbw9UuULvyHML9HmGYR-A.png" /></figure><p><strong>Didn’t</strong></p><ul><li>It’s still a voluntary banner survey (convenience sample).</li><li>IP geolocation is noisy (context only).</li><li>Auto-sentiment is directionally useful, not clinical truth.</li><li>Some steps remain manual (exports; Miro updates).</li><li>No formal significance testing yet.</li></ul><h3>Reusable guardrails (steal these)</h3><p><strong>Minimum-n rule (tune for your context)</strong></p><ul><li>Main Users: warn/suppress when <strong>n &lt; 30</strong></li><li>Secondary Users: warn/suppress when <strong>n &lt; 20</strong></li></ul><p><strong>Caveat blocks (paste on every chart)</strong></p><ul><li><em>Sampling:</em> “Voluntary banner survey; use for service quality trends, not population KPIs.”</li><li><em>Small n:</em> “Low sample; compare with caution or don’t compare.”</li><li><em>Sentiment:</em> “Auto-classified; suitable for directional trends only.”</li><li><em>IP:</em> “IP location is approximate; context only.”</li></ul><h3>Dates &amp; adoption (exact)</h3><ul><li><strong>Oct 2024:</strong> legacy audit.</li><li><strong>Jan 2025:</strong> cross-year (2022–2024) + 2024 monthly trends.</li><li><strong>Q1 2025:</strong> two-layer delivery rolled out; used in senior meetings.</li><li><strong>Aug 2025:</strong> Report called to departmental strategic review. old decks showed up in ~5% of senior meetings; The new pack is now <strong>requested and used</strong>.</li><li><strong>Now:</strong> ongoing optimisation.</li><li><strong>Decision impact:</strong> Ongoing, informing website redevelopment direction.</li></ul><h3>What I’d add next (if allowed)</h3><ul><li>95% CIs/bootstrapped bands on monthly means.</li><li>Automated refresh (scheduled export → Power Query).</li><li>Light manual sentiment validation.</li><li>A governed BI surface (Looker/Power BI) if policy allows.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a374f8dec6cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Research case study on cross-team UX audit]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://dr-ziwei-wang.medium.com/user-research-case-study-on-cross-team-ux-audit-faf26279df4f?source=rss-58c2fcf9ea8d------2"><img src="https://cdn-images-1.medium.com/max/2600/1*0Qsk8iPhe7qtL4ZVsxK6Fw.png" width="3708"></a></p><p class="medium-feed-snippet">Highlight efficient review on a large amount of competitors.</p><p class="medium-feed-link"><a href="https://dr-ziwei-wang.medium.com/user-research-case-study-on-cross-team-ux-audit-faf26279df4f?source=rss-58c2fcf9ea8d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://dr-ziwei-wang.medium.com/user-research-case-study-on-cross-team-ux-audit-faf26279df4f?source=rss-58c2fcf9ea8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/faf26279df4f</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[competitor-analysis]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-review]]></category>
            <category><![CDATA[uxaudit]]></category>
            <dc:creator><![CDATA[Dr Ziwei Wang]]></dc:creator>
            <pubDate>Thu, 19 Sep 2024 19:08:41 GMT</pubDate>
            <atom:updated>2024-09-19T19:08:41.265Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Analyse usability testing better and faster than AI]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/design-bootcamp/analyse-usability-testing-better-and-faster-than-ai-08549fe0a117?source=rss-58c2fcf9ea8d------2"><img src="https://cdn-images-1.medium.com/max/1441/1*kB0--VV7bM9-P-KeduAU0w.png" width="1441"></a></p><p class="medium-feed-snippet">Practicing Collaborative User Research</p><p class="medium-feed-link"><a href="https://medium.com/design-bootcamp/analyse-usability-testing-better-and-faster-than-ai-08549fe0a117?source=rss-58c2fcf9ea8d------2">Continue reading on Bootcamp »</a></p></div>]]></description>
            <link>https://medium.com/design-bootcamp/analyse-usability-testing-better-and-faster-than-ai-08549fe0a117?source=rss-58c2fcf9ea8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/08549fe0a117</guid>
            <category><![CDATA[research-methods]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[presentation-tips]]></category>
            <dc:creator><![CDATA[Dr Ziwei Wang]]></dc:creator>
            <pubDate>Sat, 10 Aug 2024 19:30:40 GMT</pubDate>
            <atom:updated>2024-08-11T16:26:49.167Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[An Advanced UX Knowledge Base Built in Miro — User Goals Framework]]></title>
            <link>https://medium.com/design-bootcamp/an-advanced-ux-knowledge-base-built-in-miro-user-goals-framework-a806479c8bc2?source=rss-58c2fcf9ea8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a806479c8bc2</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Dr Ziwei Wang]]></dc:creator>
            <pubDate>Sun, 07 Jul 2024 15:42:47 GMT</pubDate>
            <atom:updated>2024-07-07T16:26:58.953Z</atom:updated>
            <content:encoded><![CDATA[<h3>An Advanced UX Knowledge Base Built in Miro — User Goals Framework</h3><h4>A better user knowledge base built on top of the user needs collection.</h4><p>In a <a href="https://medium.com/@dr.ziwei.wang/preserving-user-knowledge-building-your-user-knowledge-base-with-miro-b1f57b4edf2c">previous article</a>, I demonstrated how to store user knowledge in user needs format and utilise the user needs table as the knowledge base.</p><p>However, user needs is not the sole method for storing user knowledge, nor is it the most efficient or space-saving way to do so. I aim to minimize the size of the knowledge base without compromising our understanding of the user. <strong>One simpler alternative to user needs is user goals</strong>.</p><h3>Why Using User Goals Framework?</h3><p>The user needs to follow the format ‘I need…, so that…’ This format leads to repetitions:</p><p>you <em>need A so that B</em>, you also <em>need B so that C</em>. And then you <em>need C so that D</em>, you <em>need E so that D</em>, and you <em>need F so that C</em>.</p><p>The researcher has to write their Cs and Ds multiple times, which can make it difficult to see the relationships between the needs. All the user needs must be connected somehow, and there must be an overview of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0tm0h8XNX_IpHGSkxPaJA.png" /></figure><p>That is where a user goals system come into the play. All your ‘I need’s are goals, and all your ‘So that’s are also goals, just at different levels. You fulfil multiple lower-level goals to achieve higher-level goals. Achieving higher-level goals let you achieve even higher goals. So, why not visualise this multi-level user goals map?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FvseIPGPfrvTgxLRjHg0Rg.png" /></figure><h3>How to build a user goals framework?</h3><p>I have written an article discussing the creation of a user needs table to store user knowledge. You may wonder why I chose to firstly demonstrate how to build a user needs framework when I consider the user goals framework to be superior. Why not simply bypass user needs and delve into user goals directly?</p><p>To develop a user goals framework, it’s important to first extract the goals or organise the materials in a way that makes the goals easily visible. Since user researchers typically don’t code their findings, it can be challenging for non-technical individuals to extract goals directly from a written report. Therefore, it’s necessary to document the user needs before visualising the goals. Additionally, in some organisations, user needs are also essential for communicating with developers.</p><h4>Step 0</h4><p>The first step in creating your user goals map is to have your user needs table ready. Here’s an example of a user needs table <em>(all user needs here are generated by ChatGPT)</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gc888CTBLrszSUQ9jYApbQ.png" /><figcaption>Example User Needs Table</figcaption></figure><h4>Step 1–4: Copying and write High Level Goals</h4><p>The first 4 steps involve copying and pasting to <strong>build a mind map named after the user group</strong>, in this case, ‘Young professionals’. Here are the steps:</p><p><em>Step 1: </em>Copy over your <strong>epic user needs</strong> as the first level of nodes under the map named by your user group.</p><p><em>Step 2:</em> <strong>Extract high-level goals</strong> from the epic user needs as your next level nodes, representing the high-level user goals (temporary).</p><p><em>Step 3: </em>Copy over your ‘<strong>so that’s as the Mid-level goals</strong> (temporary).</p><p><em>Step 4: </em>Copy over your <strong>‘I need’s as the low-level goals</strong>, positioning them behind the ‘so that’s they are related to (temporary).</p><p>Don’t worry about formatting the text for better readability now; we will revisit it later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aPmqoBNkTEu4Mby8f66Ggw.jpeg" /></figure><h4>Step 5: Rewrite Mid Level Goals</h4><p>After copying everything from your user needs table, you can begin organizing it. <strong>Revisit your temporary mid-level goals</strong>, and consider shortening, merging, rewriting, or moving them. Here’s an example of how to rewrite the content you copied from the user needs table:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wmWFBHNayXCMtRWxw6DcfA.jpeg" /></figure><p>After step 5, your map should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5hp_4TmOuCVWEykjq4fUjA.jpeg" /></figure><h4>Step 6: Rewrite Low Level Goals</h4><p>Now it’s time to <strong>review low-level goals</strong>, and consider shortening, merging, rewriting, and reorganising them. Here’s an example of how to organise your low-level goals:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hKhTBIKFWn0NXp8qc_qF-Q.jpeg" /></figure><p>After step 6, your map will look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3adwCSiFKsCkRkcy_oc6nA.jpeg" /></figure><h4>Step 7: Rewrite High Level Goals</h4><p>Now that you have restructured your mid and low level goals, it’s important to also <strong>revise the high level goals</strong> to align with the changes made.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pVSt4Q2N9B6K1W2T_F1_XQ.jpeg" /></figure><p>After Step 7, your map may look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DEdz8kEfP14etzHQf0t63w.jpeg" /></figure><h4>Step 8: Rewrite Epic User Needs</h4><p>Now that everything your epic user needs to cover has changed, it’s important to <strong>rewrite the Epic User Needs</strong> to reflect all the changes made. Ensure that each Epic User Need summarises all the goals it’s related to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b_QFh62ex5tH8ZAUWG4p_A.jpeg" /></figure><p>After step 8, your map may look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mONgYezFkejOukgtu9pQpw.jpeg" /></figure><h4>Step 9–10: Add Tasks and Links</h4><p>Now that you have created your user goals map, you can add links to the reports where you identified the goals. You can expand the map to include the design actions you will take to address specific user goals. Then, you can link your design file to this task. For example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eGp-XHiUzcrZd978nFoFEw.jpeg" /></figure><h4>Final Presentation</h4><p>Finally, you can display your user needs table and user goals map side by side. Like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_8XTllxhibNrgig5zO2HAw.jpeg" /></figure><h3>Make use of the User Goals Map in your stakeholder communication</h3><p>With this user goals map, you can communicate to your developer and stakeholders like this:</p><blockquote>We aim to “add a calendar view” (task) to facilitate “convenient booking” (low-level goal), in order to provide “speedy service” (mid-level goal) and enable young professional users to “manage their busy schedules and get their pets groomed without interrupting their work” (high-level goal).</blockquote><p>It will be difficult to decline your proposal because the logic is sound and the stakeholders can see it.</p><p>If this article has helped you, please click ‘Clap’ a few times!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a806479c8bc2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/an-advanced-ux-knowledge-base-built-in-miro-user-goals-framework-a806479c8bc2">An Advanced UX Knowledge Base Built in Miro — User Goals Framework</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Preserving User Knowledge: Building your user knowledge base with Miro]]></title>
            <link>https://dr-ziwei-wang.medium.com/preserving-user-knowledge-building-your-user-knowledge-base-with-miro-b1f57b4edf2c?source=rss-58c2fcf9ea8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1f57b4edf2c</guid>
            <category><![CDATA[market-research-reports]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Dr Ziwei Wang]]></dc:creator>
            <pubDate>Fri, 28 Jun 2024 07:12:43 GMT</pubDate>
            <atom:updated>2024-06-28T07:12:43.779Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Structured Approach to Storing and Leveraging Research InsightsThe Background</h4><p>In the world of research, managing and storing the vast amount of acquired knowledge can be a significant challenge for many professionals. Whether you are a UX researcher, a market analyst, or a product manager, the problem of “disposable research” is one that is all too familiar.</p><h4>Challenges of Storing and Preserving Research Knowledge</h4><p>Researchers often face the challenge of managing and storing a vast amount of knowledge generated through their work. If you don’t perceive this as a problem, you may be engaging in what is known as “disposable research.” This occurs when you undertake research projects at the request of a product manager, often as short-term or mid-term initiatives. Once the research is completed, you write a report or create a presentation deck, and then file it away in a folder, never to be revisited. The insights and knowledge gained from these projects, especially the information that has not yet been applied to the product, are often forgotten and wasted.</p><p>A year later, particularly when a new researcher joins the team, the process may be repeated, with the new researcher generating the same knowledge that was previously obtained, but at the cost of additional company resources. To ensure the sustainability of your UX research, the first and crucial step is to focus on effectively preserving your accumulated knowledge.</p><h4>Existing Research Management Tools and Their Limitations</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RSNehtnC6aTSd853URqTwg.png" /></figure><p>Many UXers have explored approaches to solve the problem of “disposable research.” One of the most successful examples in this regard is <a href="https://dovetail.com/">Dovetail</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oze865KIEe9qElvj2Utksg.png" /></figure><p>For academics, two well-known research management and data analysis tools are <a href="https://lumivero.com/products/nvivo/">Nvivo</a> and <a href="https://www.maxqda.com/">MaxQDA</a>. These tools offer a robust coding approach and analysis capabilities for those conducting in-depth qualitative research. However, these tools have not been widely adopted in the commercial sector. The reasons for this include:</p><ol><li>They are designed for the time-consuming, scientific approach to qualitative data analysis, which may not suit the needs of UX researchers (although market researchers also do coding, so they may able to pick it up quicker).</li><li>There is a lack of marketing and outreach to communities outside academia, limiting their awareness and adoption.</li><li>These tools are not as visually appealing or optimized for presentability, which may not align with the aesthetic preferences of UX professionals.</li><li>Mastering the extensive functionality of these tools requires a significant time investment, which can be a deterrent for some.</li></ol><h3>‘User Needs on Miro’</h3><h4>Centering User Needs as the Foundation for Knowledge Storage</h4><p>The system I propose for user knowledge storage begins with a fundamental concept in UX: user needs (UN).</p><p>User needs are widely used in the UX field to guide direction and inform projects. The term “user needs” is familiar to developers and serves as a common language between UX and other disciplines.</p><p>What many UXers may not have noticed is that all user knowledge, including pain points, personas, and user journeys, can ultimately be translated into user needs. At the core of the decisions made about a service are the users’ needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ji0HsttAbsRFLo6Y_zbzhQ.png" /><figcaption>An example of turning a pain point to user need</figcaption></figure><p>Be cautious, basing your service on the incorrect user need or non-specific user need could prevent your business from succeeding.</p><h4>Limitations of Existing Approaches to Storing User Needs</h4><p>The Government Digital Service (GDS) provides guidance on documenting user needs through user stories. In this framework, user stories capture the essence of a user’s need in the format “As a [user], I need [something] so that [outcome].” Acceptance criteria are then specified to clearly define the conditions that must be met for the user story to be considered complete. Epics are used to represent larger user needs that require more extensive development efforts.</p><p>While the GDS approach of storing user stories on individual cards has merit, this method does not offer a comprehensive system for organizing and preserving the full breadth of user knowledge. User needs often exist at varying levels of granularity and are interconnected, necessitating a more structured way to manage this information. Simply compiling a collection of user stories fails to provide a holistic overview of the accumulated user insights. To effectively leverage this knowledge, a more robust system is required to capture, categorize, and maintain user needs in a way that reflects their complex, hierarchical relationships.</p><h4>Organizing User Needs with a Visual Table Approach</h4><p>Traditionally, UXers have stored their user needs in spreadsheets. For those who love spreadsheets, this approach can be effective, as it allows for the addition of numerous filters, making it easy to navigate even lengthy sheets. However, not everyone finds spreadsheets easy to read, and many actually dislike this format.</p><p>Another limitation of the spreadsheet approach is that it does not readily allow for the organization of user needs into different levels. To address these challenges, an alternative solution emerges — using a table in a visual collaboration tool like Miro.</p><p><strong>This table-based approach</strong> preserves the neat, organized view of a spreadsheet, while making the information more visually appealing and easy to zoom in and out. Although you may lose the advanced filtering capabilities, the tabular format allows for simpler categorization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FNR3YxDBIKG9hifi-HXnuw.png" /></figure><p>Generally, this table consists of three main sections: the user group, the titles, and the user needs (UN) themselves. Within the UN section, you can further break it down into three parts:</p><ol><li>Keywords: This replaces the filters, providing a quick way to identify key elements.</li><li>UN body: This is divided into two parts — the narrative (what the user needs the service for) and the goal (why the user needs it).</li><li>High-level UN: This covers similar user needs, providing an overarching summary.</li></ol><h4>Constructing the Visual User Needs Table</h4><p>To build the visual table for organizing user needs, you first need to <strong>have your research findings ready</strong>. These findings can encompass a wide range of insights, such as issues with the product, the strengths of the service, the difficulties users encounter, or the emotional needs of your target users.</p><p>If the findings are not specific to particular user groups or are about mixed groups, you should separate them into findings for each distinct user group. Then, for each finding, rewrite it in the format of “I need [what the user can use the service for] so that [why the user needs it].” This <strong>translates the findings into clear user needs statements</strong>.</p><p>If your findings are already structured into sections, maintain that organization by <strong>keeping the user needs under their respective sections</strong>. When importing the user needs into the table, use the section titles as the starting point for the keywords. This is a simple way to initiate the table structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jBQXr9FJxP1b_4isd_6zWg.png" /></figure><p>To enhance the readability and visual clarity, <strong>assign a different color to each section</strong>. This separation of the “I need” and the “so that” allows you to easily see the relationships between the various user needs.</p><h4>Refining the User Needs Table through Grouping and Abstraction</h4><p>Now that you have filled the user needs table, the next step is to revisit the content and start <strong>rearranging the user needs to group similar ones together</strong>. You may wonder why this is necessary, as the user needs are already organized into sections. However, without having them in a standardized format like this table use, you may not always notice the similarities between certain user needs.</p><p>One pattern you may observe is that many user needs share the same “why” or goal (the “so that…” part). These can be grouped together within a section to form more cohesive subgroups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uLVW4p18xwvK17gk4jGbDQ.png" /></figure><p>After completing the reorganization. Write more overarching user needs that encompass multiple individual user needs, especially those that share the same underlying goal. This process of abstraction will make your sections even clearer and more coherent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c0C3kjT98PPRiA5kktEJ3Q.png" /></figure><p>This refined, hierarchical structure allows you to better understand the relationships between user needs and make more effective use of the user knowledge. You can reference these high-level user needs in various contexts, such as end-of-quarter reports, to provide a comprehensive and meaningful representation of your user research insights.</p><h3>Updating and using your User Knowledge Base</h3><h4>Incorporating New User Needs and Maintaining the Table</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9yzQYEl9xjyJn0QQ4RSbTw.png" /></figure><p>One of the advantages of the user needs table approach is the ease with which you can add new user needs. For example, let’s say you have a new user need:</p><blockquote>“As a young professional, I need grooming staff trained in handling and grooming pets with special needs or disabilities, so that my pet can receive the specialized care they require.”</blockquote><p>To incorporate this new user need into the table, you would first identify the most suitable keyword from the existing sections. In this case, it could be “Efficient and Personalized Service.” Then, you would examine the “so that” part of the new user need and see if it is similar to any existing ones. You can confirm if this is indeed a new user need and add it to the appropriate section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mh2LiOuFx4pH9sEzWrA-Ug.png" /></figure><p>After adding the new user need, you should review the overall user needs and determine if any rewriting or refinement is necessary. Sometimes, adding a new user need may not significantly impact the high-level, overarching user need if the new need is closely aligned with the existing ones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RBVoFxqBl8hqYLSB5egTKg.png" /></figure><p>This flexibility to easily incorporate new user needs, while maintaining the coherence and structure of the table, is a key strength of this approach. It allows you to continuously evolve and expand your user knowledge base without compromising the clarity and usability of the information.</p><h4>Leveraging the User Needs Table for New Projects</h4><p>When starting a new project, the user needs table is an invaluable resource. Refer to the table to locate relevant user groups and review keywords to identify applicable user needs. Then, examine the general user needs to confirm their relevance for shaping your project outline.</p><p>This approach is particularly effective for projects involving different user groups. The structured table allows quick navigation to extract necessary user knowledge for your new initiative.</p><p>If organizing by user groups isn’t suitable, you can structure the table based on different service parts, such as buying, long-term renting, or short-term renting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p65gw64uG1f9bJs-o-uQPw.png" /><figcaption>Examples of different types of keywords you can use</figcaption></figure><p>The keywords section is highly customizable. You can use user need categories, service features, or any organizational schema that fits your preferences and workflow.</p><h4>Iterating and Updating the User Needs Table</h4><p>As you develop your user needs table, you may find that your themes and structure need to change as you gain a deeper understanding of your users. This is a positive sign of growth. Update the table as needed to reflect new insights and ensure it remains an accurate representation of user needs. Embracing flexibility and adaptability is essential to maintaining a valuable and up-to-date knowledge base. This iterative process demonstrates your commitment to continuously improving your understanding of users.</p><h4>Linking User Needs to Original Research Resources</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TLfMkHCSrBNHsxg8vp5oog.png" /></figure><p>You can enhance the user needs table by including links to relevant resources, providing direct access to original reports or materials. This allows users to easily navigate back to the source documents for deeper context and details behind specific user needs. These resource links enhance the table’s value as a comprehensive knowledge repository, enabling seamless cross-referencing between user needs and primary research data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FWkwS7HllDPtwsAs4zAYQg.png" /></figure><p>*Data in this article is generated by ChatGPT</p><p>Click clap many times if you find this article useful, and leave your comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1f57b4edf2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rethinking Responsibility: Designers, Users, and the Path to Sustainability]]></title>
            <link>https://medium.com/design-bootcamp/rethinking-responsibility-designers-users-and-the-path-to-sustainability-76014a6af9fc?source=rss-58c2fcf9ea8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/76014a6af9fc</guid>
            <category><![CDATA[dark-patterns]]></category>
            <category><![CDATA[sustainable-design]]></category>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[sustainable-ux]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Dr Ziwei Wang]]></dc:creator>
            <pubDate>Mon, 03 Jun 2024 11:42:47 GMT</pubDate>
            <atom:updated>2024-06-11T22:02:00.898Z</atom:updated>
            <content:encoded><![CDATA[<h4>UX and Environment Sustainability</h4><p><em>Reflection on [UX Edinburgh] x [People Pint Planet] Meetup event.</em></p><p>As UX designers, we often discuss the concept of “dark patterns” — design choices that manipulate users into doing things they don’t intend. We acknowledge our responsibility as the creators of these products, recognising that we have the power to shape user behaviour.</p><p>Yet, when it comes to environmental sustainability, we seem to take a different stance. We expect users to dutifully recycle, reduce their carbon footprint, and adopt sustainable habits — often without considering the very real barriers and complications they face.</p><p>The truth is, recycling is far more complex than many of us realise. Juice boxes need to be rinsed and flattened, paper can’t be recycled if stained, and each municipality has its own varying policies. Even simple items like cooking pans may or may not be accepted. How can we reasonably demand perfect recycling behaviour from people who are already stretched thin, working long hours or juggling caregiving responsibilities?</p><p>The disparity becomes even more stark when we look at sustainability efforts across cultures. In the UK, we want people to bike and use public transit, despite lacking the necessary infrastructure. In China, where buses are affordable and reliable, and electric vehicle charging stations abound, sustainable transportation is far more accessible.</p><blockquote>Chinese people are living the green way because it’s the easier way, it’s not a conscious decision, and it never should be.</blockquote><p>The common thread? Sustainability has to be the easier, more convenient choice. Asking individuals to make drastic lifestyle changes, when the systemic support isn’t there, is both “naive and arrogant.” The onus should be on designers, policymakers, and businesses to make sustainable living the default, not the exception.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ex99RqJTLTnss1YF" /><figcaption>Photo by <a href="https://unsplash.com/@focusbyanders?utm_source=medium&amp;utm_medium=referral">Anders J</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Just as we in the UX field have accepted that “user errors” are actually design failures, we must extend that same mindset to environmentalism. Designers and governments have a responsibility to make sustainability effortless — through clear labeling, intuitive recycling systems, and accessible green alternatives. <strong>Only then can we reasonably expect users to do their part.</strong></p><p>This isn’t to say users bear no responsibility. But the ratio should be tilted heavily in favour of those creating the products and systems. <strong>Designers should strive for 80% of the solution, while users contribute the remaining 20%. </strong>After all, we wouldn’t blame users for filling out forms incorrectly if the instructions were unclear.</p><p>Sustainability is a complex, multi-faceted challenge. But by embracing a shared sense of responsibility — one where designers, companies, and policymakers do the heavy lifting — we can make real progress.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76014a6af9fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/rethinking-responsibility-designers-users-and-the-path-to-sustainability-76014a6af9fc">Rethinking Responsibility: Designers, Users, and the Path to Sustainability</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analysis & Ideation in 2 hours — A super fast way to analyse your usability testing notes]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://dr-ziwei-wang.medium.com/analysis-ideation-in-2-hours-a-super-fast-way-to-analyse-your-usability-testing-notes-ada3b5ece0a9?source=rss-58c2fcf9ea8d------2"><img src="https://cdn-images-1.medium.com/max/2600/1*dJ-GWPRbvSq3fhyCUtoQLg.png" width="3148"></a></p><p class="medium-feed-snippet">NID Method&#x200A;&#x2014;&#x200A;for conducting fast and high-quality team analysis (invented by Dr Ziwei Wang)</p><p class="medium-feed-link"><a href="https://dr-ziwei-wang.medium.com/analysis-ideation-in-2-hours-a-super-fast-way-to-analyse-your-usability-testing-notes-ada3b5ece0a9?source=rss-58c2fcf9ea8d------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://dr-ziwei-wang.medium.com/analysis-ideation-in-2-hours-a-super-fast-way-to-analyse-your-usability-testing-notes-ada3b5ece0a9?source=rss-58c2fcf9ea8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ada3b5ece0a9</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[usability-testing]]></category>
            <dc:creator><![CDATA[Dr Ziwei Wang]]></dc:creator>
            <pubDate>Tue, 02 Apr 2024 17:23:10 GMT</pubDate>
            <atom:updated>2024-04-03T14:36:35.923Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Practical Way to Take Notes in Miro Whiteboard]]></title>
            <link>https://medium.com/design-bootcamp/the-practical-way-to-take-notes-in-miro-whiteboard-dd964361974a?source=rss-58c2fcf9ea8d------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd964361974a</guid>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[research-methods]]></category>
            <dc:creator><![CDATA[Dr Ziwei Wang]]></dc:creator>
            <pubDate>Mon, 01 Apr 2024 08:47:23 GMT</pubDate>
            <atom:updated>2024-04-02T00:26:48.840Z</atom:updated>
            <content:encoded><![CDATA[<p>For the best note taking approach for usability testing, go to the end of this this article.</p><h3>The traditional note types</h3><h4>Note type 1</h4><p>Today, many people still take digital notes in the same way as they would on a notebook, resulting in a list of sentences. For example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*68E-RR3ZSZ-b66_J7AVBuw.png" /></figure><p>This type of note poses challenges when it comes to digital analysis on a whiteboard, as it requires highlighting to identify key themes. However, it can be easily analyzed on paper using a structured coding system. Nevertheless, this approach may be too complex for non-academic researchers.</p><h4>Note type 2</h4><p>The next approach is to break down the note into individual stickies, which is a common approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pGW912y2tF4vj0wqEXt0Yg.png" /></figure><p>The challenge in analysing these notes is that you may not know which object the notes are referring to. It requires strategic importing of the notes onto the whiteboard and remembering the content of each note during the process.</p><h4>Note type 3</h4><p>The enhanced notes will now include a timestamp, participant name, question name, and the actual notes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vy4vjX5qFuCZGBxF3CX2ew.png" /></figure><p>The issue with these notes is that they are very hard to read. Additionally, it’s not possible to organise the notes by time, question, or participants, as the information is only displayed for presentation purposes and not for grouping.</p><p>You can colour code the notes by participants:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-CMGq6kve9FVlId2vlmc8Q.png" /></figure><p>But as you can see below, it isn’t very helpful, especially when you have 200 stickies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2J1_dvPpWa0y8H1C_F9Cig.png" /></figure><p>It is very difficult to figure out where to start looking.</p><h4>Note type 4</h4><p>To tackle the problems of above note types, I used to take notes like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9c36eXvEH54a13Cefl9IBA.png" /></figure><p>For this type of notes, you have to take notes on the white board directly.</p><p>The template is pre-populated with clear indications of the app or web page/task/question, the session it pertains to, and the specific participant involved. Each participant’s notes are assigned a unique colour, and the task number is displayed as a tag, such as the red ones shown above.</p><p>Before conducting analysis, you have the option to <strong>group the notes by tags</strong>. This allows for a <strong>more focused analysis</strong>, either task by task or page by page. The use of colour coding and manual timestamps further assists in locating specific information within the recordings.</p><p>I always manually type timestamps in the format of 01&#39;34&#39;’ on the note, which helps with refining the notes if needed. This practice is also helpful for some organisations in obtaining recording clips.</p><p>This is still not the most convenient type of notes. Because you still end up with this for each task:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kd18rgLPasflZpAOiFWcLw.png" /></figure><h3>The ultimate note format for usability testing</h3><p>After years of note-taking, I have developed the following approach for creating the most effective notes for usability testing sessions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RDwEmmgCcJUSaQps16XtHA.png" /></figure><h4>Notes in seven colours</h4><p>In general, there are following 7 types of notes to take:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jVtWx_TAVQti5sKafNg6yw.png" /></figure><p><strong>Click path notes</strong> are important because they help us discover users’ task flows and page flows. This information can assist us in designing a smoother experience to reduce the drop-off rate and increase meaningful session time.</p><p>Splitting <strong>observation notes</strong> into negative, positive, and neutral categories provides a quick overview of both positive and negative experiences.</p><p>Adding designated quote notes makes it easy for us to compile engaging reports later.</p><p>In this design, there are two types of quantitative notes. The first type is the <strong>Task Completion Score</strong>, which uses a scale of -1 for “participant could not complete the task without the facilitatorâ€™s instruction”, 0 for “participant could complete the task on their own, but experienced obstacles during the process”, and 1 for “the participant completed the task with no problem”. After all sessions, the mean score for each task is calculated. By simply determining if the score is negative or positive, we can instantly assess the quality of the design.</p><p>The second number is the <strong>Ease of Use Score</strong>. This score was designed to align with the industry standard measure of usability, ranging from 0 to 10. This allows for easy comparison of each page and helps in identifying which page presents the most significant challenge to address.</p><h4><strong>Tagged notes</strong></h4><p>As seen in the photo, each note is labeled with the participant code, note taker’s name, and task number.Â</p><p>While a time stamp is not necessary, you can use the participant code and task number to find the recording clip. The note taker’s name allows you to ask for clarification on the notes, and the task number makes it easier to organise the notes for analysis.</p><h4>Additional non-task notes</h4><p>Not all of your notes will pertain to tasks. Throughout your testing, you may have additional questions before or after completing tasks. Following the testing, you may also have general observations to add from observing a few sessions. Therefore, I have also included space for these types of notes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YMLt0yUNLEiaXe2hfL-6Gw.png" /></figure><h4>The final template</h4><p>Check out this final template that increases how much you can learn from usability testing:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wDADtKN2ZKqG5SnHFOfFrg.png" /></figure><p>Go ahead, try this template, and explore the best way to take notes for your own project.</p><p>You can find this template on Miro: <a href="https://miro.com/app/dashboard/?miroversePath=%2Fnote-taking-for-usability-testing%2F"><strong>Note Taking Template by Dr Ziwei Wang</strong></a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u051nga0DiKlpRZ2wk2J3g.png" /></figure><p><em>*all notes used in this article are generated by ChatGPT.</em></p><p>If this article helped you, please click clap many times!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd964361974a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-practical-way-to-take-notes-in-miro-whiteboard-dd964361974a">The Practical Way to Take Notes in Miro Whiteboard</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>