Paper Prototypes and Wire Frames

Debug your applications before you write code

Prototyping helps to clarify specifications, reduce risk

Paper Prototyping

- is fast, fun, effective

improves on team building and
communication

- needs proper facilitation

Executive Summary

Definitions

Prototype: an individual that exhibits the essential features of a later type
(Merriam Webster)

Usability: The extend to which a product can be used by specific users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use."
(ISO 9241:11)

The Problem

Telling vs. Doing

Best Quality

Shortest Time

Lowest Cost

Pick any 2

Cost of Software Fixes

UAT

Prototyping

40%

Patterns of large software systems: failure and success(Capers Jones)

Prototyping Results

Hidden Requirements

Application Ownership

Common Understanding

Team Building

World Peace!

At least no more opinion wars!

Your Toolbox

HTML

Visio

Visual Basic

Photoshop

Prototyping Software

Denim (Berkeley University)

Balsamic Mockups

Demo Time:
BALSAMIC MOCKUPS

If it looks to good it took too long!

Now it needs to work!

Problem here:

Effort similar to
full application

Change cycles to long

Wrong impressions
about progress

Paper?

Looking good is bad!

If it looks good, users expect it to be completed and available!

So how does it actually work?

Let user interact!

But it is Paper?

You are the CPU!

Demo Time
(Video on Youtube)

What can you test?

This works:

Concepts

Terminology

Navigation

Workflow

Task flow

Content

Functionality

Layout

Brand

Other tests required:

Micro actions

Keyboard/Mouse errors

Size

Timing

Long term use

Compatibility

Looks?

Setting up a prototype

Breath & Depth

Interaction Model

2 Distinct Steps!

Create!

Test!

Create!

Test!

Get your story right!

Breath

LookDepthInteraction

Keep the unfinished look!!!!

Overcome Objections

It doesnt look real

Waste of time

Not scientific

Unprofessional

Session Preparation

Location, Setup

Participants

Facilitator

Computer (max. 0.00001 MHz)

Observers

Tester

Introduction, Ground Rules

Observers

The developers

The system architect

The project manager

NOT the boss of the test person

The Session

Introduce the session

Introduce to observers

Ask for consent if you tape it

Introduce the tasks:

Scheduled duration

Think aloud

No spoon feeding!!!

The Facilitator's Roles

Flight Attendant

Sports Caster

Scientist

Findings

Watch what users do

Listen what users say

Give feedback only AFTER the session and only about the prototype

Use creativity

techniques to sort

out your findings

Debriefing

The debriefing session is as important as the test

Affinity diagrams

Mind maps

Action plan

Common Challenges

Screen estates

More Pitfalls

Selection of testers

Session disruptions

Available scope

Guidance
(too much / too little)

User goals incomplete

Resources

http://www.paperprototyping.com

http://www.useit.com

http://www.upassoc.org/

http://www.formsthatwork.com

http://www.origami.com/

Your local papershop

http://www.balsamiq.com/products/mockups

http://mayo.svidnik.com/images/blog_pics/feed-icon.png

Q&A

Thank you!

Stephan H. Wissel
Lotus Technology & Productivity Advisor
notessensei@sg.ibm.com

Click to edit the title text format

Click to edit the title text format

Click to edit the title text format

Click to edit the outline text format

Second Outline Level

Third Outline Level

Fourth Outline Level

Fifth Outline Level

Sixth Outline Level

Seventh Outline Level

Eighth Outline Level

Ninth Outline Level

emerging technologies

emerging technologies

IBM Workplace, Portal, Lotus & Collaboration Software 2003 IBM Corporation