week8_303

When creating a persona to represent a product user, what is the primary purpose of including personal details like a name, age, and photograph?

• A. To ensure the development team can perform a background check on the user type.
• B. To create a realistic character that helps the team empathize with the user ("step into their shoes").
• C. To meet the legal requirements for user documentation.
• D. To define the specific salary bracket for pricing the software.

Answer explanation

Personal details transform an abstract user type into a character that the team can relate to, fostering empathy and a shared understanding of who they are building for.

Which of the following is the most effective element to include in a persona description to help developers judge UI complexity?

• A. The user's long-term life goals (e.g., "wants to retire early").
• B. The user's educational background and technical skill level.
• C. The user's favorite color scheme.
• D. The user's manager's name.

Answer explanation

Knowing a user's education and technical skills helps the team assess whether features and interfaces will be understandable or too complex for that specific user type.

Why is it generally advised to avoid focusing on "user goals" (e.g., "career progression") when writing personas?

• A. Users never have goals when using software.
• B. Goals are too broad and often do not directly relate to why a user needs a specific piece of software to get through their day.
• C. Goals are always financial and irrelevant to functionality.
• D. It is impossible to write a goal in less than three paragraphs.

Answer explanation

Goals are often broad concepts (like self-improvement) that don't help define specific software needs; it is better to focus on why the software is useful and what the user wants to do with it.

You are developing a new product and have very little data. You create "proto-personas" based on the team's best guesses. What is the limitation of this approach?

• A. They are too detailed to be useful.
• B. They cannot be used to write scenarios.
• C. They are not as accurate as those based on user research, though they still provide a shared team vision.
• D. They require legal approval before use.

Answer explanation

Proto-personas are created from limited information; while better than nothing for building a common understanding, they lack the accuracy of personas derived from detailed user studies.

How many personas should you typically create to identify the key features of a system effectively?

• A. One for every potential user of the system.
• B. At least 20 to cover every possible demographic.
• C. A small number (e.g., up to 5) to avoid overlapping requirements and confusion.
• D. Only one "average" persona.

Answer explanation

Using too many personas can make design difficult due to overlap; usually, no more than five are needed to identify key system features.

Which of the following best describes the correct "level of detail" for a starting scenario?

• A. A strict, step-by-step list of every mouse click and keystroke.
• B. A high-level narrative describing a user's problem and an imagined solution without technical specification.
• C. A complete code-level specification of the feature.
• D. A vague statement saying "the user solves the problem" with no description of how.

Answer explanation

A scenario is a narrative that briefly explains the problem and presents an imagined way it might be solved, without becoming a detailed system specification.

When writing a scenario, why might you include specific technical details (like "Log in with Google") rather than a generic phrase (like "User performs authentication")?

• A. Because generic phrases can be confusing, while specific examples are often easier for users and developers to understand.
• B. Because you are required to use Google products.
• C. Because the code has already been written.
• D. Because scenarios must always dictate the final implementation database.

Answer explanation

Writing generally can be confusing; referencing widely understood mechanisms (like specific login types) makes the scenario easier to read and understand.

What is the primary advantage of using a "narrative" style (natural language) for scenarios over a "structured" style (fields and flowcharts)?

• A. Narrative scenarios are machine-readable.
• B. Narrative scenarios are accessible and understandable to non-technical users and stakeholders.
• C. Structured scenarios are too short.
• D. Narrative scenarios are legally binding contracts.

Answer explanation

Narrative scenarios facilitate communication because they are natural and accessible to users and funders, whereas structured scenarios can be intimidating.

Which action should you take to identify software features from a written scenario?

• A. Count the number of adjectives used.
• B. Highlight the "active verbs" (actions) in the text to see what the user is doing (e.g., "upload," "share").
• C. Rewrite the scenario in a different language.
• D. Remove all references to the persona.

Answer explanation

A recommended technique is to look for user actions, usually denoted by active verbs, and highlight them to identify features that support those actions.

A scenario describes a teacher using a tool to organize a class trip. What represents the "Problem" element of this scenario?

• A. The teacher logs in.
• B. The teacher wants to share photos but needs to ensure student privacy and copyright compliance.
• C. The teacher has a degree in History.
• D. The system sends an email.

Answer explanation

A key element of a scenario is explaining problems that can't be readily addressed by existing systems, such as privacy/copyright issues that require specific functionality.