Latest / 5 Minute UX / Creating Usability Recommendations
Transcript
- 0:08This lesson is Creating Usability Recommendations. Let's
- 0:11get started.
- 0:18Before we dive into the six-step usability testing sequence,
- 0:21let’s ground this in your current practice. You already
- 0:23know that defining project objectives before starting
- 0:25maintains focus during approach selection. This clarity
- 0:28determines whether you choose quantitative methods, which
- 0:30provide numerical data and high- confidence repeatable results,
- 0:33or qualitative methods. The choice isn’t arbitrary; it’s
- 0:35driven by what answers you are trying to find. Once that
- 0:38approach is set, you need to prepare the necessary test
- 0:40artifacts. This includes discussion guides, consent
- 0:42forms, and checklists, for which Steve Krug provides helpful
- 0:45templates at sensible.com/download-files.
- 0:47These documents structure the interaction, ensuring you
- 0:49capture meaningful data without bias. You also need a
- 0:51functioning version of the site or application, often in beta
- 0:54mode, to ensure the environment supports true-to-life
- 0:56performance testing. Many teams mistakenly believe usability
- 0:59testing only happens near deployment, but it provides
- 1:01insights much earlier. By establishing these objectives
- 1:03and artifacts first, you create a stable foundation for the
- 1:06research. This preparation ensures that when you move to
- 1:08planning the research scope and logistics, you are building on a
- 1:11clear, objective-driven strategy rather than guessing.
- 1:19You move into the six-step usability testing sequence,
- 1:21starting with choosing an approach that aligns directly
- 1:23with your project objectives. Because you’ve already defined
- 1:25those goals, you can now decide whether you need quantitative
- 1:28methods for high-confidence numerical data or qualitative
- 1:30insights for deeper understanding. This decision
- 1:32anchors the entire study, ensuring your methodology
- 1:34supports the specific evidence you need to drive
- 1:36recommendations later in the process. Next, you plan the
- 1:38research by defining the scope and logistics required to
- 1:40execute that chosen approach. This phase sets the boundaries
- 1:43for what you will test and how you will measure success,
- 1:45preventing scope creep from diluting your findings. It’s
- 1:47where you determine the resources needed and the
- 1:49timeline for gathering meaningful performance data
- 1:51before you even touch a prototype. Then comes recruiting
- 1:53and logistics, where you secure participants and set up the
- 1:56testing environment to ensure realistic conditions. You need
- 1:58people who represent your actual users, not just convenient
- 2:00volunteers, so their behavior reflects true-to-life
- 2:02performance. Setting up the space, whether virtual or
- 2:04physical, ensures that environmental factors don’t
- 2:06interfere with the natural flow of the user’s interaction.
- 2:09Finally, you write discussion guides that contain task scripts
- 2:11focused strictly on user goals rather than interface labels. If
- 2:14a button says "Submit," you must not use the word "submit" in the
- 2:16instruction, because that leads the participant instead of
- 2:19testing their natural discovery. You frame tasks around the
- 2:21answers they are trying to find, which prevents leading questions
- 2:23and reveals genuine usability issues. This careful wording
- 2:26ensures the data you collect during facilitation is valid for
- 2:28analysis.
- 2:34You facilitate the tests using those discussion guides to
- 2:37gather performance data, ensuring participants frame
- 2:39tasks around their actual goals rather than interface labels.
- 2:42This prevents leading them, which means if a button says
- 2:44submit, you simply do not use that word in the instruction.
- 2:46Afterward, you analyze and present results to process the
- 2:49gathered data, looking for patterns that reveal where users
- 2:51struggle or succeed. You ground these findings in design
- 2:54principles like Jakob Nielsen’s ten usability heuristics,
- 2:56checking for issues like poor visibility of system status. The
- 2:59final output is creating recommendations for
- 3:01improvements, which serves as the tangible result of your
- 3:03analysis. These suggestions feed directly into the iterate phase
- 3:06of the project lifecycle, following the develop, test, and
- 3:08refine cycle. By generating specific improvement
- 3:10suggestions, you provide the team with insights to refine the
- 3:13solution. This ensures the testing process delivers true-
- 3:15to-life performance information earlier, correcting the
- 3:18misconception that evaluation only happens near deployment.
- 3:20You have now walked through the sequence from planning to
- 3:22recommendation, establishing a clear path for iteration. Next,
- 3:25we will examine common pitfalls to avoid during this process,
- 3:28ensuring your approach remains focused and effective.
- 3:35Let’s test your instinct on timing. Do you schedule
- 3:38usability testing only near deployment, or do you run it
- 3:40earlier to capture true-to-life performance data? [pause:1s] The
- 3:43reason early testing matters is that it prevents the costly
- 3:46misconception that validation belongs solely at the end of
- 3:49development. Now, look at your discussion guides. If a button
- 3:51says "Submit," do you use that word in your task instructions?
- 3:54[pause:1s] You must rewrite those instructions to focus on
- 3:57the user's goal rather than interface labels, because using
- 3:59specific terms leads participants and skews natural
- 4:02behavior. Think about your project objectives. Are they
- 4:04defined before you select your research approach? [pause:1s]
- 4:07You need strict adherence to those objectives during approach
- 4:10selection to prevent losing focus between quantitative and
- 4:12qualitative methods. Finally, verify your recommendations. Are
- 4:15they derived from actual user research rather than
- 4:18assumptions? [pause:1s] Ensuring your suggestions stem from
- 4:20analyzed test results, not guesses, is how you apply the
- 4:23goal-framing technique effectively. With these pitfalls
- 4:25avoided, you are ready to apply recommendations to iterate on
- 4:28the design.
- 4:35You integrate those tangible improvement suggestions into the
- 4:37Iterate phase, which follows the develop, test, and refine cycle.
- 4:40This is where your analysis changes the solution. You treat
- 4:43the six-step usability testing sequence as a reliable checklist
- 4:46for future projects, ensuring consistency. Using this
- 4:48structured approach helps you maintain focus and avoid common
- 4:51pitfalls like leading participants. Early testing
- 4:53provides true-to-life performance information,
- 4:55boosting overall project lifecycle efficiency. You’ll
- 4:57find that applying these recommendations creates a
- 5:00smoother path from insight to implementation.
- 5:05Welcome to The Take. I'm joined by a fellow practitioner and
- 5:08together we're going to dig into Creating Usability
- 5:10Recommendations — what it means in practice and what's worth
- 5:13remembering.
- 5:15[HOST] The bit about framing tasks around user goals instead
- 5:18of interface labels really stuck with me. It’s easy to slip into
- 5:21leading questions when you’re pressed for time. [LEARNER]
- 5:24Exactly. If I tell a user to click the submit button, I’ve
- 5:27already solved the problem for them. That defeats the whole
- 5:30purpose of the test. [HOST] Right. We need to see if they
- 5:33can find the action themselves, not just follow instructions. It
- 5:37forces us to write cleaner discussion guides. [LEARNER] But
- 5:40writing those guides is where I struggle most. I often worry
- 5:43that being too vague will confuse the participant. How do
- 5:46you balance clarity with neutrality? [HOST] You focus on
- 5:49the outcome they want, not the UI element. Ask them to complete
- 5:52a purchase, not to find the checkout button. [LEARNER] That
- 5:56makes sense. I’ve started using AI to draft those task
- 5:58scenarios. It helps me spot accidental leading language
- 6:01before I even record. [HOST] That’s a smart use of the tool.
- 6:04It acts as a first-pass filter for bias. Just make sure you
- 6:08review the logic yourself afterward. [LEARNER] Definitely.
- 6:11The AI doesn’t understand the specific context of our product
- 6:14yet. I still need to tweak the nuance. [HOST] True. It’s a
- 6:17drafting assistant, not a strategy replacement. The real
- 6:20value comes when you analyze the results against those neutral
- 6:23tasks. [LEARNER] Agreed. Once we've that clean data, turning
- 6:26it into recommendations feels much more defensible.
- 6:29Stakeholders respect evidence over opinion. [HOST] And that’s
- 6:32the goal. We’re not guessing anymore. We’re iterating based
- 6:35on what actually happened in the test. [LEARNER] It changes the
- 6:39conversation from debate to diagnosis. I love that shift.
- 6:42[HOST] It does. Keep pushing for that early testing window too.
- 6:45It saves so much rework later.