BAB 3 DESIGN PROCESS PART 2

Question 1

What is the purpose of a UI design workshop?

Answer 1

to have participants quickly sketch rough ideas for the user interface.

Question 2

outputs of a UI design workshop(3)

Answer 2

storyboards, design concepts, and guidelines

Question 3

What is the definition of storyboards in a UI design workshop?

Answer 3

A storyboard communicaates a story through images displayed in a sequence of panel that chronologically maps the story’s main events

Question 4

What is the role of design concepts in a UI design workshop?

Answer 4

Design concepts frame UI ideas to ensure an aesthetically-consistent app, software, or website.

Question 5

What is the role of guidelines in a UI design workshop?

Answer 5

Guidelines set design rules based on the agreed design concepts, ensuring consistency across the project.

Question 6

What is a design pattern in the context of user interface design?

Answer 6

A design pattern is similar to a recipe for handling common user interface design issues.

Question 7

How can design patterns be useful when facing a design problem?

Answer 7

When facing a design problem, it can be useful to look at several patterns to see if they help solve the problem.

Question 8

What are the advantages of using design patterns?

Answer 8

The advantages include not having to reinvent the wheel and learning from others’ mistakes.

Question 9

What are the limitations of design patterns?

Answer 9

The limitations are that only common things have patterns, and patterns are not one-size-fits-all; what works in one situation may not work in another

Question 10

What are the different formats for getting input from users? (4)

Answer 10

Flexible format, forgiving format, fill in the blank, and structured format.

Question 11

What is a Flexible/Forgiving Format?

Answer 11

It is a user input method where users can quickly enter data in a way that the system can interpret, even if the input isn’t perfectly formatted.

Question 12

When should you use a Flexible/Forgiving Format?

Answer 12

When select boxes, radio buttons, and checkboxes make the input process too complicated.

When the time it takes to complete a task exceeds the importance of the user’s goal.

When the input is related to a single topic, such as a physical location or an event with a start time.

When the expected input can be easily interpreted by a computer program.

Question 13

When should you not use a Flexible/Forgiving Format?

Answer 13

When users might input anything or ask questions unrelated to the task.

When there isn’t a clearly defined purpose for the input.

Question 14

What is a Fill-in-the-Blank Format?

Answer 14

It is an input method where users enter data directly into blank spaces within a sentence, making the context of the input clear.

Question 15

When should you use a Fill-in-the-Blank Format?

Answer 15

When creating labels for input fields that do not adequately explain the input’s purpose.

When labels for input fields are long and complicated, making it hard for users to understand.

When the context of the input field can be better expressed by placing it within a sentence.

When filling out input fields within a sentence structure forces users to read the entire sentence and understand the context of each input field.

Question 16

When should you not use a Fill-in-the-Blank Format?

Answer 16

When there are many input fields that are not required to be filled out.

Question 17

How should input fields be represented in a Fill-in-the-Blank Format?

Answer 17

Input fields should be placed within a sentence, so the context is clear

The sentence should be structured in a way that guides the user to understand what is being asked for in each input field.

Question 18

What is the rationale behind using a Fill-in-the-Blank Format?

Answer 18

It simplifies the user interface by reducing the need for long and complicated labels.

It ensures that users read and understand the context of each input field, reducing errors and misunderstandings.

By integrating input fields into sentences, it makes the form more intuitive and user-friendly.

Question 19

What is a Structured Format?

Answer 19

It is an input method where users need to enter data in a predefined structure, ensuring the input adheres to a specific format.

Question 20

When should you use a Structured Format?

Answer 20

When select boxes, radio buttons, and checkboxes make data entry too complicated.

When the task completion time is disproportionate to the importance of the user’s goal.

When the input data type is specific, such as a zip code, date, time, or phone number.

When the expected user input follows a specific format that can be easily interpreted by a computer program.

Question 21

When should you not use a Structured Format?

Answer 21

When the user input is open-ended and does not follow a predictable pattern.

Question 22

How should input fields be represented in a Structured Format?

Answer 22

Input fields should be presented with accompanying labels that clearly describe the expected input format.

Labels should specify the structure users must follow to input valid data.

Use mechanisms like date selection calendars to help users enter data in the correct format.

Question 23

What is the rationale behind using a Structured Format?

Answer 23

It sets clear expectations by ordering input fields in a structured format, guiding users on the required input.

Chunking large input fields into smaller bits reduces data entry errors and makes it easier to transcribe or memorize long numbers.

Structured formats are well-suited for predictable input, while forgiving formats are better for open-ended input.

It saves time for users who repeatedly fill out the same input fields as part of frequent tasks, streamlining and controlling inputs.

It aids in speeding up data capture tasks and reducing errors, thus addressing the “garbage in, garbage out” problem.

Question 24

How does the UI Pattern Card Deck help designers?

Answer 24

It helps designers consider all available options and how they match the needs of the project.

It provides inspiration and guidance for designing user interfaces by presenting common patterns and solutions.

Question 25

What is the UI Pattern Card Deck?

Answer 25

It is a set of ideation cards available at ui-patterns.com, used to help designers think through and identify necessary UI elements.

Question 26

What are sketches good for?

Answer 26

Sketches are great for brainstorming and quickly refining ideas, experimenting with basic elements, and collaborating with your design team.

Question 27

What are some things to consider when sketching for UI design?

Answer 27

Have specific user goals and tasks in mind.

It doesn’t need to be beautiful; focus on functionality.

Expect to discard many ideas as part of the process.

Question 28

What are wireframes good for?

Answer 28

Creating the first draft of an app across multiple screens.

Exploring, testing, and iterating on ideas with more refinement.

Sharing with design teams, clients, and users for early feedback.

Gathering feedback on structure and overall concepts, rather than aesthetic details.

Planning the placement of buttons, tabs, icons, and other key UI elements.

Question 29

What should you consider with wireframes?

Answer 29

Wireframes can be paper-based or digital; templates or graph/layout paper can help maintain neatness if paper-based.

Keep wireframes greyscale to focus on layout, structure, and arrangement of key elements, not aesthetic details.

Use wireframes when you understand the goals and needs of users, and have a broad idea of the type of content on your site or app.

Use wireframes to establish what is of primary and secondary importance to the user who will interact with the design.

Question 30

What are mockups good for?

Answer 30

Performing usability evaluations such as heuristic evaluations, cognitive walkthroughs, and think-aloud tests.

Making decisions about font choice, color schemes, and other visual aspects.

Integrating knowledge about users, including affordances, metaphors, gestalt principles, and layout design into the visual representation.

Question 31

Here are considerations for mockups:

Answer 31

Create multiple mockups to explore different font types, sizes of text and buttons, and color schemes.

Maintain consistency with the “design system” by using symbols and components consistently across the mockup.

Ensure a common visual theme throughout all mockups.

Use tools that facilitate mockup creation and allow for easy sharing with team members, clients, and users.

Question 32

What are prototypes good for?

Answer 32

They enable exploration of user journeys and flows.

They show results based on user actions.

They provide opportunities for detailed usability feedback, useful for Think Aloud sessions.

Question 33

What should you consider with prototypes?

Answer 33

Settle on the final overall visual design before starting.

Initially, avoid simulating all functionality; focus on specific user flows.

Plan the sequence of page flows off-screen first.

Question 34

What is the value of prototyping?

Answer 34

Prototyping allows for creating lots of variations quickly and with different degrees of fidelity.

Question 35

What are the different stages of prototyping?

Answer 35

The stages of prototyping include sketches, wireframes, mockups, and prototypes.

Question 36

How do you test a prototype?

Answer 36

Form a group of sample participants.

Ask participants to try the prototype.

Obtain feedback via interviews, surveys, observation, or remote data gathering.

Use the feedback to improve the prototype.

Question 37

What is a Minimum Viable Product (MVP)?

Answer 37

A version of a product with just enough features to be usable by early customers who provide feedback for future development.

Question 38

Why focus on releasing an MVP?

Answer 38

To avoid lengthy and potentially unnecessary work by iterating on working versions and responding to feedback.

Question 39

Why do software companies issue updates?

Answer 39

To fix bugs and add functionalities, as there is no such thing as “complete” software.

Question 40

What is the purpose of obtaining feedback from early customers?

Answer 40

To challenge and validate assumptions about a product’s requirements and improve future versions.