Make

Create a testable solution.

Prototyping

What

A rudimentary version, either static or functional, of something that exhibits realistic form and function.

Why

To enable direct examination of a design concept’s viability with a number of other methods such as usability testing or a cognitive walkthrough. Static prototypes (often paper) are helpful for gaining feedback on users’ intentions and various design elements. Functional prototypes (often coded) are helpful for observing how users interact with the product.

Time required

4 hours

How to do it

  1. Create a rudimentary version of your product. It can be static or functional. Think in the same way you would about a wireframe: demonstrate structure and relationships among different elements, but don’t worry about stylized elements.
  2. Give the prototype to the user and observe their interactions without instruction.
  3. After this observation, ask them to perform a specific task.
  4. Ask clarifying questions about why they do what they do. Let the user’s behavior guide the questions you ask. It can be helpful to have them narrate their thought process as they go along.
  5. Iterate! Prototypes should be quick and painless to create, and even more quick and painless to discard.

Applied in government research

No PRA implications. The PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. See the methods for Recruiting and Privacy for more tips on taking input from the public.

18F

Sketching

What

A team activity wherein each member sketches 6-8 ideas regarding the project at hand within a 5 minute time limit.

Why

To quickly brainstorm and get ideas for a project.

Time required

5 minutes per session, 15 minutes for discussion.

How to do it

  1. Before the meeting, prepare several sheets of paper with a 2×2 or 2×3 grid. Make sure boxes are large enough to sketch an idea, but not so large that multiple ideas can be put into a single box. Try to have space for at least 10 ideas per round.
  2. When the meeting begins, give each player a sheet and explain how the activity works.
  3. Next, set a timer for 5 minutes.
  4. Tell the players to sit silently and sketch out as many ideas as they can until the timer ends — with the goal of reaching 6-8 ideas. The sketches can and should be very rough — nothing polished in this stage.
  5. When the time runs out, the players should share their sketches with the rest of the group. The group can ask questions of each player, but this is not a time for a larger brainstorming session. Make sure every player presents his/her sketches.
  6. With time permitting, repeat another few rounds of 6-8-5. Players can further develop any ideas that were presented by the group as a whole or can sketch new ideas that emerged since the last round. They can continue to work on separate ideas, or begin working on the same idea. But the 5-minute sketching sprint should always be done silently and independently.

Adapted from Gamestorming

18F

Wireframing

What

A simple visual representation of a product or service interface.

Why

To prioritize substance and relationships over decoration as you begin defining the solution. Wireframing also gives designers a great opportunity to start asking developers early questions about feasibility and structure.

Time required

1-3 hours

How to do it

  1. Build preliminary blueprints that show structure, placement, and hierarchy for your product. Steer clear of font choices, color, or other elements that would distract both the researcher and the reviewer. Lightweight designs are conceptually easier to reconfigure. A few helpful tools for building wireframes are OmniGraffle and Balsamiq, which purposefully keep the wireframe looking like rough sketches.
  2. Use this opportunity to start listing what UX/UI patterns you will need.
  3. Review your wireframes with specific user scenarios and personas in mind. Can users accomplish their task with the wireframe you are sketching out?
  4. Use the wireframes to get the team’s feedback on feasibility and structure.

Applied in government research

No PRA implications. No information is collected from members of the public.

18F