Visualising design

Darren Menachemson

the problem

This is not your audience.

Humans’ ability to make a rational decision is inversely proportionalto the complexity of the information upon which the decision is based.

the problem

So why do we do this?

“You can’t eat an elephant in one bite”

- Some Guy

“We need a smaller elephant.”- Me

“That’s like 200 pages of high-level design. Um, do you know what high-level actually means?”

- Anon

AestheticInformation architectureInteraction designBusiness architectureStrategic design

Defining the “design” bit

the solution

What is a visualisation?Shows the future solution in operation

Scope is as big as it needs to be

Narrative is led by an experience set

Uses visual language

What is a visualisationShows the future solution in operation

Scope is as big as it needs to be

Narrative is led by an experience set

Uses visual language

TimeJan Jul Jan Jul

Construction complete

Deployment complete

System in use

the solution

What is a visualisationShows the future solution in operation

Scope is as big as it needs to be

Narrative is led by an experience set

Uses visual language

people things channels process location Time &sequence

messaging Systems &tech

the solution

What is a visualisationShows the future solution in operation

Scope is as big as it needs to be

Narrative is led by an experience set

Uses visual language

the solution

What is a visualisationShows the future solution in operation

Scope is as big as it needs to be

Narrative is led by an experience set

Uses visual language

From http://www.kwikpoint.com

the solution

Who are they for?Execs – decision making

Stakeholders – consultations

Users – design walkthroughs

Other project teams – shared vision

Comms, training, etc, etc

Reuse factor

Bridesmaid dress

Jeans

Some examples…Simple one-pager…tells a story in a single page, describing key people, systems, processes, UI features, business outcomes.

Don’t just tell the design decision makers – show them, warts and all. Get beyond the hype and the confusion!

Some examples…Simple one-pager…tells a story in a single page, describing key people, systems, processes, UI features, business outcomes.

Don’t just tell the design decision makers – show them, warts and all. Get beyond the hype and the confusion!

Some examples…Full scenario spelling out the design, including:• High-level overview• Persona• Stepped process• User impact lenses

Some examples…Comic book, focussingon a user experience.

From http://www.boxesandarrows.com

Some examples…Hand drawn systems, post-it messages and play-actor actors…

Lo-fi works too!CRM

InboxRegister

Client manager Service user

How much detail is enough?

Somewhat complex, detailed, informative. Some understanding and analysis required

Simple, unambiguous.

A. As much as isneeded (sorry)

Very complex, highly detailed. Specialist analysis required.

Very complexVery simple

Discuss business outcome

Show a message flow

Highlight a bit of UI

Abstract an interaction set

Examine the user’s outcome

Demonstrate a strategic risk eventuating

Show a service desk interaction

Principles for getting the right pitch…• Show what you need ‘em to know• Generate the right discussion• Let them walk away with clarity

The process of visualisingUnderstand the contextLearn about the context, systems, users, and the desired business outcomes

Find the senior sponsorUnderstand the issues and solve them, review regularly, escalate, add value

Pick the right brainsFacilitated workshops, interviews, project meetings, documentation, user discovery

Partner with the teamBuild strong relationships, share the work, build a sense of contribution and ownership

Get something out EARLY,review, iterate, repeat

Have a deadline and an eventSenior stakeholder commitment v. important

Visual ideas

Know your “style”Branding, recognition, consistency

Gather your resources(photos, icons, abstract people etc)

Have techniques for dealing with issues(breakouts, post-its, zooms, relationships/groupings)

Source imageswww.istockphoto.com

Edit imagesPhotoshop/Illustrator

Layout visualisationPowerPoint

A visualisation workbench

Others:• Adobe Flash• Plasq Comic Life• Etc

A visualiser! ! The offspring of a talented BA, a passionate user experience architect and a mad information designer (process mapping + design)

! ! Very strong communicator (including storytelling, facilitation)

! ! Able to facilitate and build relationships with senior people

! An understanding of IT concepts and business architecture

! Preferably people and project management experience

! Ability to help lead and shape solutions, championing the user and the business outcome

Hard to find, sometimes hard to hold onto.

The “Oh, hai, nice to meet you” phase

The “I’ve got to do a WHAT?”phase

The “I’ve got real work to do and we’re drawing piccies?” phase

The “All these hard questions and nasty issues. I wish it were all still ambiguous!” phase

The “At last! The right conversation”phase

The “maybe we should visualiseit” phase

Drawbacks

Time-intensiveSpecialist skills

Sounds “funky” until you see itThe fun doesn’t end after the event

What it avoids/provides

• Cultural/semantic misunderstanding• “I didn’t think that’s what I agreed to”• Early review at concept stage• Contextualising issues• Shaping the right solution

Try it…Choose one of these• Last meal you cooked…• How you booked your last flight…• Your last big shop at a supermarket…

Sketch up a rich visualisation showing the user experience, process, channels, technology, data etc – either in-line or layered (60 seconds)

Walk the person next to you through it (60 seconds)

Stories can bind complexity, because stories are fundamental to our humanity.