What are some tips for writing concise and unambiguous task instructions?

In my experience, knowing and researching the audience that will consume this information is the first step in framing your content. Once you realize the market you are writing for, then you can utilize ‘inclusive’ language that accommodates your audience. The second step will be to design and test the content with samples of the audience to ensure that what you have designed achieves the purpose of communicating with the audience.

Menos es más Habla en simple Lo que no sea de conocimiento general (jerga técnica), tradúcelo a una figura que sea comprensible por todos

- Use bullets (always works for me) - Think the reader has no clue about the process or task - What is obvious for you might not be so obvious for the reader, so dont miss adding the simplest of details - Call out the time by when you expect the task to be closed clearly (I need this ASAP is really vague!) - If there are any specific tools/platform need to conduct the task call out separately

- Bullet points: have the overarching goal, and supporting tasks to achieve it - Assume that this is being read by people who aren't familiar with your process or the product (e.g. customer support, sales) - Make it visual with infographics (especially with processes) - Use tables to split your information and organize clearly

Along with the other great advice people have offered here, start with the end in mind then work backwards. Then follow your instructions based on what you've written, not what you already know. After a rewrite, have someone who's never done the thing follow your instructions. Rewrite based on how you clarified their questions.

Definition of done What does good look like? Points? Analytics? Research? Expected fidelity or output Provide a target "sizing", such as "you can present this subject in 10 minutes" sizing Timeframe Exactly when you need it and why Delivery method Spreadsheet? Deck? In the.repo? Word doc? We get what we ask for and if we ask for generalism, well, we shouldn't expect more

Enhance task instructions by offering context and purpose for each action. Clearly explain why participants are tasked with specific actions, outlining the goals and desired outcomes. This provides a meaningful understanding, maintaining participant motivation and engagement. For example, replace "Search for a product on the website" with "Imagine you want to buy a new laptop. Search for a laptop on the website that meets your needs and budget."

Il faut également annoncer le contexte du test et spécifier s’il le faut à quel moment du parcours le test prend place. Il est également important de poser un cadre bienveillant pour le test en indiquant à l’utilisateur que le but n’est pas de l’évaluer quand à son utilisation mais plut?t d’évaluer l’interface, il n’y a donc pas de bonnes ou mauvaises réponses.

Most usability tests push users to perform tasks they would not normally do ("Imagine..."). Results from those tasks are untrustworthy. Instead, ask open-ended questions about what they do, then use that in tasks. "What are some things you buy online?" Followed by - "Show me how you might find <name user provided>". This also avoids terminology problems (use their terms) and stops users from simply looking for UI features you've named (search, budget, compare, filter, sort...).

Remember to explain why each task matters and what you're hoping to achieve with it. This not only gives clarity but also keeps people interested and motivated. For example, instead of just saying "Update your profile information," try "Please update your profile so we can better tailor our services to your preferences." This way, people understand the task's value and are more likely to engage with it.

In interviews, I'm fond of asking, "Talk to me about what you're seeing." You can only gather a first impression once. I'll follow up with more focused questions if they are unanswered things we want to know about. I also like to preface my conversations with a general disclaimer of, "I'm a researcher, I didn't make the thing, you can't offend me" and such. A favorite metaphor is, "In this experience, you're the professor and we're the student - we just want to know how we did."

Instead of focusing on specific aspects like price, also ask broader questions like "Tell me about your experience finding what you were looking for." This gives users more leeway to share their unfiltered thoughts.

It is important to use open-ended questions instead of leading questions. Open-ended questions are questions that cannot be answered with a “yes” or “no” response, or with a static response. They are phrased as a statement which requires a longer answer. Open-ended questions encourage conversation and allow the respondent to provide more detailed answers. They can help you gain a deeper understanding of your user base and their needs. To avoid leading questions, you should ask for information in a neutral, straightforward way. Use objective wording and avoid using words that reflect your own opinions and preferences.

Ao se preparar para um teste de usabilidade, é muito importante escolher um público diverso como idades diferentes, habilidades, origens, etc., a representatividade vem a minimizar o enviesamento dos resultados. Depois disso, crie cenas realistas para obter resultados reais. Mantenha a neutralidade para n?o influenciar os participantes e garantir um resultado mais confiável.

Ser objetivo e direto em que realmente deseja obter de resposta, auxilia para n?o abrir margem em resposta "ambígua" ou até mesmo, fugir da dúvida em quest?o.

The provided example is leading: The step by step instructions are not suitable, if the researcher is interested in whether a user will be able to identify the steps necessary to create an account without any help. Bullet points are a great help to organize information, however researchers should strive to only provide information that will be accessible in a realistic use environment.

Formatting information into lists can be very helpful for condensing information. However, if breaking down the content into list form is not applicable or logical to the flow of thought, another way of condensing it is by chunking information. This is done by separating long-form content, for example, into smaller “bite-sized” paragraphs that are easier for the audience to visually locate and access the information they need if they do not need all of the information presented. It also makes it easier for the audience to read if they do need all of the information presented.

A huge mistake I see new interviewers make is asking their participants compounded questions, or questions that are so long that users cannot track the entire question. Using bullet points underneath a concise question is a good way for you as the researcher to prompt the user if needed, while reminding yourself to keep your questions short and to the point.

In case of long instructions it is possible to place some kind of picture or text description of General steps at the beginning of the task. So that user can imagine full process and then proceed to details. It is done when one set of bullets is not enough.

In usability testing, avoid overly direct task instructions like in the given text. Such guidance leads users towards solutions, preventing us from observing how they naturally interact with the interface and what challenges they might encounter. For complex tasks, break them down into clear, manageable steps using bullet points or numbered lists. E.g., when testing a personal settings function, instead of specifying "click on the settings icon, then open personal account, and change your email by clicking on the pencil icon," frame it as: - Locate the personal settings. - Change your email address. - Confirm if the change was successful.

Testing your instructions with an audience similar to your participants is the most important step. It nearly always brings up ways to improve the instructions. Even so, you will also want to run 1 or 2 pilot sessions with your participants (especially important if you are doing unmoderated testing), as that may uncover confusion or misunderstanding that can be remedied with further revision of the task instructions.

In preparation for the usability test, it's essential to thoroughly assess and enhance your instructions. Enlist colleagues, friends, or potential participants to review and attempt task completion. Request feedback regarding clarity, completeness, and difficulty. Leverage tools such as readability checkers or grammar checkers to enhance the writing. Refine instructions based on both feedback and tools, aiming for increased conciseness and clarity.

A similar variant of that: Before conducting the usability test, it's crucial to test and refine your instructions. Ask colleagues, friends, or potential participants to read and try to complete the tasks. Seek feedback on clarity, completeness, and difficulty. Use tools like readability checkers or grammar checkers to improve writing. Based on feedback and tools, revise instructions to make them more concise and unambiguous.

Umas das praticas de Design mais valiosas, na minha opini?o, é o Design Critique. Apesar do nome assustar um pouco, ele é um passo muito importante para ser concluído. O objetivo é identificar áreas de melhoria e promover discuss?es produtivas: Um grupo de pessoas, que entendem ou n?o sobre padr?es da experiência do design, expressam suas opini?es de maneira positiva e oferecem sugest?es para melhorias antes da hipótese ser testada.

écrire des hypothèses c’est bien mais conduire des tests et voir comment les utilisateurs réagissent et comment ils comprennent votre wording est la clé ?? 1. Vous pouvez utiliser les tests qualitatifs pour recueillir le sentiment des utilisateurs ou des idées. 2. Réalisez un AB test pour voir quelle version vous apporte le maximum de conversion. N’attendez pas d’avoir un produit finalisé pour réaliser ces tests, allez-y franchement.

One thing that might help to improve the analysis of the recorded materials - is including "Task completed" and "Annoyed" tags/indicators. For example, in one study we noticed that our participants kept trying to complete the task despite being 'visible irritated' by the process, during that session we improvised and provided them with a red sticky note, to indicate if a task was 'annoying'. We found it helpful to avoid misintepreting later, and setting a threshold as a "comfortable task completion time".

Consider Task Independence In usability testing, if one task doesn't depend on completing another, it's crucial not to indicate to participants whether they've successfully completed a task. This approach maintains the integrity of the test. If a participant believes they've finished a task, avoid correcting them or leading them with questions like "Are you sure you completed the task correctly?" Instead, after the session, ask why they thought the task was complete to gain insights into any misunderstandings or difficulties. Leading questions during testing can skew results, compromising the reliability of your findings.

In some cases, adding details around "what success looks like" or clarifying output metrics can create useful guardrails without forcing an explicit approach.

é bom imaginar alguém (que n?o seja você ou seu time) lendo as instru??es. Isso ajuda a manter a objetividade e claridade do documento, sem contar que é frequente você precisar dividir o time para ajudar a aplicar o teste simultaneamente. Para isso, também é importante dar o contexto da tarefa, objetivo da tarefa e o que define que a tarefa está completa.