<?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 Andrea Lei on Medium]]></title>
        <description><![CDATA[Stories by Andrea Lei on Medium]]></description>
        <link>https://medium.com/@cruxlay?source=rss-3aca94d69267------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*VfzoJ4p-OmEVP64E.jpeg</url>
            <title>Stories by Andrea Lei on Medium</title>
            <link>https://medium.com/@cruxlay?source=rss-3aca94d69267------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:41:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cruxlay/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[认识设计者的自大]]></title>
            <link>https://medium.com/@cruxlay/%E8%AE%A4%E8%AF%86%E8%AE%BE%E8%AE%A1%E8%80%85%E7%9A%84%E8%87%AA%E5%A4%A7-fc15df7071d0?source=rss-3aca94d69267------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc15df7071d0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Andrea Lei]]></dc:creator>
            <pubDate>Tue, 20 Mar 2018 21:06:41 GMT</pubDate>
            <atom:updated>2018-03-20T21:06:41.883Z</atom:updated>
            <content:encoded><![CDATA[<p>凌晨两三点看了一个一席的设计师的演讲，有些感触，记录下来，希望可以跟更多人探讨。</p><p>演讲者是何志森，<a href="http://www.yixi.tv/speech/620">视频在这里</a>。这个演讲讲的是设计师要有一颗柔软细致的心，真正去生活中观察人们如何生活，理解人们，由此为他们做出能够让生命值得庆祝的设计。</p><blockquote>“当生活方式和建筑融为一体的时候，生命才能开始庆祝”——印度建筑设计师多西</blockquote><p>为什么理解人对设计师来说是件必要的事情？其实理解他人背后的动机应该包括愿意关心他人，这也是一件必要的事。因为设计师，不管是哪一个领域的设计，有很大一部分工作都是在创造，而创造的方式里，又有一部分是在改造，改造放在具体 product design 的语境里面，通常说成，优化。但你怎么判断这对用户来说是“优化”？你认为对他们来说的“更好”，他们也会这样接受么？</p><p>我在问自己，也想问问大家：</p><ul><li>使用者有没有可能不按你的设计去使用？</li><li>什么情况下会 ，那时我们该怎么办？</li><li>我有没有觉得用户的反馈不重要的时候？有没有觉得你的个人意志高于使用者反馈的时候？</li><li>有没有过度自信觉得自己完全可以预测用户行为的时候？</li><li>我有没有真的想理解他们？有没有持续性的在这上面付出努力？</li></ul><p>作为设计师，设计领域的很多知识和经验教给我们很多策略和技巧，你将会知道用什么方式可以引导用户视线最有效，也会知道用什么因素去强化用户动机，促使他们按照设计行动，不确定的话，你也能提前测试，尽可能多的消除风险。很多时候这些方法都是被证明有效的。这些方法也渐渐会让你有一些预判能力，这是非常宝贵的。然而这种预判能力，会让你有一种错觉，你觉得你对用户行为有掌控感，而这被我称作是设计者的自大。</p><p>设计过程中一定会有判断，设计方案本身就是你判断的结果。我们在presentation的时候所展示的，全都是判断。所有以“用户会……”开头的句子都值得怀疑，而时刻提醒和反思自己认知的局限性和失败的可能性则值得鼓励。“用户会……”其实等同于“我希望用户会……”，而很多时候你的希望都是会泡汤的。所以这句话或许会给你自己一些信心，但无法真正起作用。</p><p>作为产品设计师，真正能起作用的是，尽可能真正的扎实的理解人的多样性，直面你只能在众多多样性需求中满足极其有限的一小部分共性需求，又只能在众多可能的解决方案中选择一个解决方案而已的这种现实具有多大的风险。</p><p>我觉得设计师是要经历一些挫败，才能真正直面一个现实，你决定不了用户行为，你的预测、判断可能是错的。用户不按你的设计和设想去行动的可能性远远大于按照你的设想去思考和行动的可能性。他们在自己已有的习惯和经验影响下而去思考、去行动可能性远远大于你有限的设计引导技巧给他们的影响。你的过度自信要么反映了对这一真相的回避要么是缺乏经验，缺乏到不知道自己可能会因为什么而失败。</p><p>不认识自己渺小的设计师无法真正变强大。</p><p>理解他人并不是件容易的事，说实话，也并不常见。需要付出额外的时间，也需要学习。我觉得，先从自己走出来开始吧。</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc15df7071d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guide to Conducting Usability Testing]]></title>
            <link>https://medium.com/@cruxlay/guide-to-conducting-usability-testing-f7ebe98b98a1?source=rss-3aca94d69267------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7ebe98b98a1</guid>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Andrea Lei]]></dc:creator>
            <pubDate>Tue, 13 Mar 2018 05:13:58 GMT</pubDate>
            <atom:updated>2018-03-13T05:13:58.473Z</atom:updated>
            <content:encoded><![CDATA[<p>Main Content：</p><ol><li>What’s usability testing</li></ol><p>2. Qualitative and quantitative usability testing</p><p>3. How to conduct an usability testing?</p><p>4. What to test?</p><p>5. How many test users in an usability test?</p><p>6. What to detect in a testing? While participants:</p><p>7. The severity of usability problems</p><p>8. Tips to usability testing</p><p>9. One last word</p><h3>What’s usability testing</h3><p>Usability testing is qualitative research methods to validate and test the design by observing an individual’s experience with an concrete prototype as he walks through the steps of a given task.</p><ol><li>can users accomplish their goals with your product? (black and white definition)</li><li>how easily and successfully can users accomplish their goals with your product?(shades of grey definition)</li></ol><h3>Qualitative and quantitative usability testing</h3><p>All usability-testing studies involve a participant performing some assigned tasks on one or more designs. There are, however, two types of data that can be collected in a user-testing study:</p><ul><li><strong>Qualitative (qual) data</strong>, consisting of <strong>observational findings</strong> that identify design features easy or hard to use. Qualitative data <strong>offer a direct assessment of the usability of a system</strong>: researchers will observe participants struggle with specific UI elements and infer which aspects of the design are problematic and which work well. They can always ask participants followup questions and change the course of the study to get insights into the specific issue that the participant experiences. Then, based on their own UX knowledge and possibly on observing other participants encounter (or not) the same difficulty, researchers will determine whether the respective UI element is indeed poorly designed.</li><li><strong>Quantitative (quant) data</strong>, in form of one or more metrics (such as task completion rates or task times) that reflect whether the tasks were easy to perform. Quantitative data <strong>offer an indirect assessment</strong> of the usability of a design. They can be based on users’ performance on a given task (e.g., <strong>task-completion times, success rates, number of errors</strong>) or can reflect participants’ perception of usability (e.g., <strong>satisfaction ratings</strong>). Quantitative metrics are simply numbers, and as such, they can be hard to interpret in the absence of a reference point. For example, if 60% of the participants in a study were able to complete a task, is that good or bad? It’s hard to say in the absolute. That is why many quant studies usually aim not so much to describe the usability of a site, but rather to compare it with a known standard or with the usability of a competitor or a previous design.</li></ul><h3>How to conduct an usability testing?</h3><p>Planning a usability study. Tests are designed around tasks and scenario that represent typical end-user goals. Tasks should be specific, concrete and reflect actual goals of the target audience. Scenarios contextualize the task, and are written to provide extra information necessary to complete that ask.</p><ol><li>Goal</li><li>Participants</li><li>Tasks and scenarios.</li><li>Recruiting participants</li><li>Designing the prototype</li><li>Moderating test sessions</li><li>Analyzing the data</li><li>Communicating the results</li></ol><h3>What to test?</h3><p>Usability can be defined by 5 quality components.</p><ol><li>Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design? Are instructions clear? Are instructions necessary? Do labels make sense? Do certain words are understandable?</li><li>Discoverability: Are common items easy for new users to find?</li><li>Efficiency: Once users have learned the design, how quickly can they perform tasks?</li><li>Errors: How many <a href="https://www.nngroup.com/articles/slips/">errors</a> do users make, how severe are these errors, and how easily can they recover from the errors?</li><li>Satisfaction: How pleasant is it to use the design?</li><li>Memorability: When users return to the design after a period of not using it, how easily can they reestablish proficiency?</li></ol><h3>How many test users in an usability test?</h3><ul><li>Testing with 5 people lets you find almost as many usability problems as you’d find using many more test participants. With <strong>5 users</strong>, you almost always get close to user testing’s maximum benefit-cost ratio. Aiming at collecting <strong>insights to drive your design</strong>, not numbers to impress people in PPT.</li><li>For really <strong>low-overhead projects</strong>, it’s often optimal to test as few as <strong>2 users per study</strong>. For some other projects, 8 users — or sometimes even more — might be better. For most projects, however, you should stay with the tried-and-true: 5 users per usability test.</li></ul><h3>What to detect in a testing? While participants:</h3><ol><li>understands the task but can’t complete it within a reasonable amount of time.</li><li>understands the goal, but has to try different approaches to complete the task.</li><li>gives up or resigns from the process.</li><li>completes a task, but not the task that was specified.</li><li>express surprise or delight.</li><li>express frustration, confusion, or blame themselves for not being able to complete the task.</li><li>asserts that something is wrong or doesn’t make sense</li><li>make suggestion for the interface or the flow of events.</li></ol><h3>The severity of usability problems</h3><ol><li>Impact: Will it be easy or difficult for the users to overcome?</li><li>Frequency: Is it common or rare</li><li>Persistent: Is it a one-time problem that users can overcome once they know about it or will users repeatedly be bothered by the problem?</li></ol><h3>Tips to usability testing</h3><ol><li>Planning the testing to focus on important questions about the design.</li><li>Recruit your participants in your target audiences.</li><li>Using scenario to develop user task.</li><li>Observing the test sessions. Focus on participant behavior and their rationale.</li><li>Understand the “how” and “why”.</li><li>Before answer participants’ question, think first why he is asking, is this a potential risk?</li><li>Test late enough in the process that there’s a concrete design to test, and early enough to allow adjustment in the design and implementation.</li><li>Ask participants to perform explicitly defined tasks while thinking aloud.</li><li>Share findings with stakeholders. Invite some to observe.</li><li>Open-ended questions.</li></ol><h3>One last word</h3><p><strong>Usability testing is, at its core, a means to evaluate, not create.</strong> It is not an alternative to interaction design, and it will never be the source of that great idea that makes a compelling product. Rather, it is a method to access the effectiveness of ideas you’ve already had and to smooth over the rough edges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7ebe98b98a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>