B C E F G H I L M O P R S T

Objectives

Monish Subherwal

What is it:

Objectives were a method articulated in the book “Discussing Design” by Adam Connor and Arron Irizzary.  Their take on evaluating a design is that it requires us to do objective, critical thinking.

Thus objectives are a type of evaluation criteria that is typically shared with team members allowing design to be evaluated without opinion, bias, or personal preference.

When to use:

When evaluating a design (usually, prior to giving feedback), refer to objectives to determine if the design is “good”.

How it works:

Refer to a project brief or other documentation to have a really good understanding around the context of the design.

Look at:

  • The persona the designer is designing for
  • The project’s problem statement
  • Scenarios or use cases that are in the requirements
  • Design principles that may have been established
  • Any define business goals/metrics or user goals.

For each of these criteria, you can ask yourself the following questions to evaluate the design:

  • Persona – does the design address the wants, needs, and desires of the persona it is supposed to address?
  • Problem Statement – does the design address the project’s problem statement?
  • Scenarios/Use Cases – does the design solve for scenarios and use cases that are required?
  • Design Principles – does the design adhere to established design principles or heuristics?
  • Goals (can be business or user oriented) – does the design meet the business or user’s goals?

References: