what i learned from 200 projects (amsterdam ux)

209
What I learned from oh, I don’t know, around 200 projects Peter Boersma (@pboersma) Interaction Design Director at Blast Radius Amsterdam UX Meetup July 2, 2014

Upload: peter-boersma

Post on 11-Aug-2014

1.418 views

Category:

Career


18 download

DESCRIPTION

Focussing on teamwork, deliverables and processes, I walked the audience through a selection of projects from my 20 years of experience with designing interactive systems, sharing the lessons that I learned the hard way, and showing how some things in design agencies have changed while others have stayed exactly the same. I hope that some of the lessons resonate with the audience, and that the models I include (like the T-model, or overviews of where UX can live in organizations) helps them reflect on their practice and consider improvements to the way they design.

TRANSCRIPT

Page 1: What I learned from 200 projects (Amsterdam UX)

What I learned fromoh, I don’t know, around

200 projects

Peter Boersma (@pboersma)Interaction Design Director at Blast Radius

Amsterdam UX MeetupJuly 2, 2014

Page 2: What I learned from 200 projects (Amsterdam UX)
Page 3: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 4: What I learned from 200 projects (Amsterdam UX)

around 200 projects

1995 - 2000 - General Design 70 102000 - 2002 - Satama Interactive 20 102002 - 2005 - EzGov 15 52005 - 2006 - User Intelligence 10 202006 - 2010 - Info.nl 20 52010 - 2012 - Adaptive Path 5 2.52012 - 2012 - freelance 5 102012 - present - Blast Radius 55 40

Total 200 10

#proj /year

Page 5: What I learned from 200 projects (Amsterdam UX)

scope, teams, skills, org charts, deliverables

Page 6: What I learned from 200 projects (Amsterdam UX)

the scope of our projectshas expanded from one-way

webdesign to service design for networked brands

Page 7: What I learned from 200 projects (Amsterdam UX)
Page 8: What I learned from 200 projects (Amsterdam UX)

http://www.abnamro.nl

Page 9: What I learned from 200 projects (Amsterdam UX)

640px

480px

Page 10: What I learned from 200 projects (Amsterdam UX)
Page 11: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 12: What I learned from 200 projects (Amsterdam UX)
Page 13: What I learned from 200 projects (Amsterdam UX)

!SOCIAL CONTENT

MOBILE CONTENT

STORES CRM

PR

CSR

ALWAYS-ON CONNECTED PLATFORMS

Starbucks.com

Page 14: What I learned from 200 projects (Amsterdam UX)
Page 15: What I learned from 200 projects (Amsterdam UX)
Page 16: What I learned from 200 projects (Amsterdam UX)

our teams have haddifferent types of people

in them

Page 17: What I learned from 200 projects (Amsterdam UX)
Page 18: What I learned from 200 projects (Amsterdam UX)
Page 19: What I learned from 200 projects (Amsterdam UX)
Page 20: What I learned from 200 projects (Amsterdam UX)
Page 21: What I learned from 200 projects (Amsterdam UX)

my roles at interactive agencies

1995 - 2000 - UI Designer2000 - 2002 - Consultant User-Understanding2002 - 2005 - Senior Information Architect2005 - 2006 - UX Consultant & Partner2006 - 2010 - Senior Interaction Designer2010 - 2012 - Experience Designer2012 - 2012 - Freelance (Process) Designer2012 - present - Interaction Design Director

Page 22: What I learned from 200 projects (Amsterdam UX)

we had different skills, starting at Computer Science, HCI and Design

leading to User Experience

Page 23: What I learned from 200 projects (Amsterdam UX)

HCICS Des

Page 24: What I learned from 200 projects (Amsterdam UX)

HCICS DesIxDIAMarCom

InfoDes Copy Usab

Page 25: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 26: What I learned from 200 projects (Amsterdam UX)

shallowknowledge

User Experience

deepknowledge

businessknowledge

Page 27: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 28: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 29: What I learned from 200 projects (Amsterdam UX)

since 1995, we have been lookingfor the right place of UX

in the organization

Page 30: What I learned from 200 projects (Amsterdam UX)
Page 31: What I learned from 200 projects (Amsterdam UX)
Page 32: What I learned from 200 projects (Amsterdam UX)
Page 33: What I learned from 200 projects (Amsterdam UX)
Page 34: What I learned from 200 projects (Amsterdam UX)
Page 35: What I learned from 200 projects (Amsterdam UX)
Page 36: What I learned from 200 projects (Amsterdam UX)
Page 37: What I learned from 200 projects (Amsterdam UX)
Page 38: What I learned from 200 projects (Amsterdam UX)
Page 39: What I learned from 200 projects (Amsterdam UX)
Page 40: What I learned from 200 projects (Amsterdam UX)
Page 41: What I learned from 200 projects (Amsterdam UX)
Page 42: What I learned from 200 projects (Amsterdam UX)

what we call our work,our deliverables,changed too...

Page 43: What I learned from 200 projects (Amsterdam UX)

“Here is how we work:Step 1: we send you a contractStep 2: we design your site and you approve the designStep 3: we build your site, and you approve the designStep 4: we send you an invoice”

Page 44: What I learned from 200 projects (Amsterdam UX)

Design

ResearchEvaluation

Prototype

Test

SketchDetailed Design

Concept

Personas

Interviews

Page 45: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManage

Pitch

Scenarios

Position

Roadmap

Service Design

Prototype

RequirementsReviewTest

Scope

Optimize

Estimate

Beta

SketchDetailed Design

Concept

Personas

Competition

Process

Roles

Steps

Interviews

Page 46: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 47: What I learned from 200 projects (Amsterdam UX)

GOODBAD

per company

Page 48: What I learned from 200 projects (Amsterdam UX)
Page 49: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 50: What I learned from 200 projects (Amsterdam UX)
Page 51: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManage

Pitch

Scenarios

Position

Roadmap

Service Design

Prototype

RequirementsReviewTest

Scope

Optimize

Estimate

Beta

SketchDetailed Design

Concept

Personas

Competition

Process

Roles

Steps

Interviews

Page 52: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 53: What I learned from 200 projects (Amsterdam UX)
Page 54: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 55: What I learned from 200 projects (Amsterdam UX)

1995-2000 - General DesignCompany profile:- Dutch startup that grew from 3-30 people- made interactive sites for small & large brands

My responsibilities:- in the beginning: everything- from interface design- via software programming- to sales and project management

Page 56: What I learned from 200 projects (Amsterdam UX)
Page 57: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 58: What I learned from 200 projects (Amsterdam UX)
Page 59: What I learned from 200 projects (Amsterdam UX)
Page 60: What I learned from 200 projects (Amsterdam UX)
Page 61: What I learned from 200 projects (Amsterdam UX)

• A conference is more than the proceedings

• Also: it’s not that hard to get on stage!

Page 62: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManage

Prototype

RequirementsReview

Estimate

SketchDetailed Design

Competition

ProcessScope

Page 63: What I learned from 200 projects (Amsterdam UX)

BrBreakingead

share late-night pizza with developershave lunch with clients

go for drinks with colleagues

35

35

Page 64: What I learned from 200 projects (Amsterdam UX)

General Design

GOODBAD

* gave me broad experience

* mix of academic research and practical focus

* time to discover what I like (not project management)

* being project manager & UI designer on 10 projects

* leading to a short, 4-week burnout

Page 65: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 66: What I learned from 200 projects (Amsterdam UX)

2000-2002 - SatamaCompany profile:- Finnish web-and-mobile agency going global- General Design turned into Amsterdam office

My responsibilities:- Consultant User-Understanding- concept design, IA, IxD, usability tests- for the first time: process designer

Page 67: What I learned from 200 projects (Amsterdam UX)
Page 68: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 69: What I learned from 200 projects (Amsterdam UX)
Page 70: What I learned from 200 projects (Amsterdam UX)
Page 71: What I learned from 200 projects (Amsterdam UX)
Page 72: What I learned from 200 projects (Amsterdam UX)
Page 73: What I learned from 200 projects (Amsterdam UX)
Page 74: What I learned from 200 projects (Amsterdam UX)
Page 75: What I learned from 200 projects (Amsterdam UX)
Page 76: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManagePosition

Requirements

Scope

Estimate

Detailed Design

Concept

Competition

Process

Roles

Steps

Interviews

Page 77: What I learned from 200 projects (Amsterdam UX)

Satama Interactive

GOODBAD

* mobile experience: designed WAP sites, and created a mobile portal evaluation tool.

* process focus: I managed a 2-year program to document the Satama Unified Process.

* I wasn’t considered a good fit for consultant team

* leading to a long, 8-month burnout

Page 78: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 79: What I learned from 200 projects (Amsterdam UX)

2002-2005 - EzGovCompany profile:- software & consultancy for online transactions- between governments and citizens/businesses

My responsibilities:- Information Architect- Also: Usability Engineer- And: Process Designer

Page 80: What I learned from 200 projects (Amsterdam UX)
Page 81: What I learned from 200 projects (Amsterdam UX)
Page 82: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 83: What I learned from 200 projects (Amsterdam UX)
Page 84: What I learned from 200 projects (Amsterdam UX)
Page 85: What I learned from 200 projects (Amsterdam UX)
Page 86: What I learned from 200 projects (Amsterdam UX)
Page 87: What I learned from 200 projects (Amsterdam UX)
Page 88: What I learned from 200 projects (Amsterdam UX)
Page 89: What I learned from 200 projects (Amsterdam UX)
Page 90: What I learned from 200 projects (Amsterdam UX)
Page 91: What I learned from 200 projects (Amsterdam UX)
Page 92: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 93: What I learned from 200 projects (Amsterdam UX)

3 Phases

5 Disciplines System AnalysisInformation Architecture & Interaction DesignUsability & Accessibility TestingContent DesignVisual Design & Information Design

Elaboration ConstructionInception

EzGov Standards for UXEzGov Standards for UX

Page 94: What I learned from 200 projects (Amsterdam UX)
Page 95: What I learned from 200 projects (Amsterdam UX)
Page 96: What I learned from 200 projects (Amsterdam UX)
Page 97: What I learned from 200 projects (Amsterdam UX)
Page 98: What I learned from 200 projects (Amsterdam UX)
Page 99: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManage

Service Design

Prototype

RequirementsReviewTest

Scope

Estimate

Detailed Design

Personas

Process

Roles

Steps

Interviews

Page 100: What I learned from 200 projects (Amsterdam UX)

EzGov

GOODBAD

* good cooperation with Development and PM

* spent time defining design process (StUX)

* developed in-house screenflow tool (J-flow)

* styleguides made visual design work boring

* org. overhead made our work expensive

Page 101: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 102: What I learned from 200 projects (Amsterdam UX)

2005-2006 - User IntelligenceCompany profile:- small usability company that expanded into design- founder was looking for a business partner

My responsibilities:- User Experience Consultant and Manager Design

Page 103: What I learned from 200 projects (Amsterdam UX)
Page 104: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 105: What I learned from 200 projects (Amsterdam UX)
Page 106: What I learned from 200 projects (Amsterdam UX)
Page 107: What I learned from 200 projects (Amsterdam UX)
Page 108: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManage

RequirementsReviewTest

Scope

Optimize

Estimate

Detailed Design

Concept

Personas

Competition

ProcessInterviews

Pitch

Page 109: What I learned from 200 projects (Amsterdam UX)

User Intelligence

* we defined the basis for good team & good company

* got to think about corporate strategies

* unprepared for partner talks with founder

* our communication styles made cooperation hard

* had to leave, shortly after bringing in friends

Page 110: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 111: What I learned from 200 projects (Amsterdam UX)

2006-2010 - Info.nlCompany profile:- very Dutch agency ("normal is crazy enough")- founded in1994 and still going strong

My responsibilities:- senior interaction designer- Also: restructured department & renamed job titles- Also: attempted to document design process

info.nl !FULL!SERVICE!INTERNET!AGENCY!!

Page 112: What I learned from 200 projects (Amsterdam UX)
Page 113: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 114: What I learned from 200 projects (Amsterdam UX)
Page 115: What I learned from 200 projects (Amsterdam UX)

Life

Play

Learn

Buy

Page 116: What I learned from 200 projects (Amsterdam UX)
Page 117: What I learned from 200 projects (Amsterdam UX)
Page 118: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManage

Pitch

Scenarios

Position

Roadmap

RequirementsTest

Scope

Estimate

Detailed Design

Concept

Personas

Competition

Process

Page 119: What I learned from 200 projects (Amsterdam UX)

Info.nl

GOODBAD

* cooperation with developers

* sales reached out to sell UX

* management lacked vision about process

* sales defined projects: teams designed to budget

Page 120: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 121: What I learned from 200 projects (Amsterdam UX)

2010-2012 - Adaptive PathCompany profile:- famous San Francisco agency came to Amsterdam- defined User Experience as we know it- Adaptive Path is run by designers

My responsibilities:- Experience Designer- design, lead projects, sell projects- teach workshops, host UX Week

Page 122: What I learned from 200 projects (Amsterdam UX)
Page 123: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 124: What I learned from 200 projects (Amsterdam UX)
Page 125: What I learned from 200 projects (Amsterdam UX)
Page 126: What I learned from 200 projects (Amsterdam UX)
Page 127: What I learned from 200 projects (Amsterdam UX)
Page 128: What I learned from 200 projects (Amsterdam UX)

the elements ofuser experienceHenning FischerDirector, Adaptive Path [email protected]@henningfischer

Peter BoersmaDesigner, Adaptive Path [email protected]@pboersma

RGB

108, 190, 7773, 155, 69

Page 129: What I learned from 200 projects (Amsterdam UX)
Page 130: What I learned from 200 projects (Amsterdam UX)
Page 131: What I learned from 200 projects (Amsterdam UX)
Page 132: What I learned from 200 projects (Amsterdam UX)

First deliverable: NarrativeAs a result of initial conversations with the client, our designer-led sales team would create a Narrative.

A Narrative consists of:

- key business needs

- project summary and team overview

- phase-by-phase description of activities and outcomes

- examples of expected deliverables

- timeline and budget

Page 133: What I learned from 200 projects (Amsterdam UX)

But what happened to it?Designers’ narratives were translated by Salesinto a Statement of Work with a lot of legalese.

We had to go back to the original narrativeto kick off projects with the team.

Page 134: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManage

Scenarios

Position

Roadmap

Service Design

RequirementsReviewTest

Scope

Estimate

Sketch

Concept

Personas

Competition

ProcessInterviews

Page 135: What I learned from 200 projects (Amsterdam UX)

Adaptive Path

GOODBAD

* designers lead projects from sales to delivery

* many internal discussions about the field

* time to teach back to community

* 14 hour workdays due to time zones

* European sales handed over to America

Page 136: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 137: What I learned from 200 projects (Amsterdam UX)

2012-2012 - FreelanceCompany profile:- me :-)- interaction designer & design process consultant

My responsibilities:- set up the business, pay tax, do sales & PM- define processes and design concepts for clients

Page 138: What I learned from 200 projects (Amsterdam UX)
Page 139: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 140: What I learned from 200 projects (Amsterdam UX)
Page 141: What I learned from 200 projects (Amsterdam UX)
Page 142: What I learned from 200 projects (Amsterdam UX)
Page 143: What I learned from 200 projects (Amsterdam UX)
Page 144: What I learned from 200 projects (Amsterdam UX)

MOBILEAPP

MUSIC PLAYER IN BAR

out of scope

MUSICMATCH

Page 145: What I learned from 200 projects (Amsterdam UX)
Page 146: What I learned from 200 projects (Amsterdam UX)
Page 147: What I learned from 200 projects (Amsterdam UX)
Page 148: What I learned from 200 projects (Amsterdam UX)
Page 149: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManageRoadmap

Prototype

Requirements

Scope

Estimate

Sketch

Concept

Process

Page 150: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManage

Review

Process

Roles

Steps

Page 151: What I learned from 200 projects (Amsterdam UX)

Freelance

GOODBAD

* freedom in deciding when to work

* freedom in deciding how much to work

* freedom in deciding for whom to work

* office/tax/legal stuff is hard!

* no team = no feedback

* no idea if I was at good at freelancing

Page 152: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 153: What I learned from 200 projects (Amsterdam UX)

2012-present - Blast RadiusCompany profile:- “agency for the connected world” (= Marketing)- owned by global digital agency network Wunderman

My responsibilities:- Interaction Design Director in Amsterdam office- design concepts and prototypes (with freelancers)- manage a Business Analyst- support offices in Hamburg, London and Paris

Page 154: What I learned from 200 projects (Amsterdam UX)
Page 155: What I learned from 200 projects (Amsterdam UX)
Page 156: What I learned from 200 projects (Amsterdam UX)

User Experience

HCICS DesIxDIAInfoDes

MarCom Copy Usab

Page 157: What I learned from 200 projects (Amsterdam UX)
Page 158: What I learned from 200 projects (Amsterdam UX)
Page 159: What I learned from 200 projects (Amsterdam UX)
Page 160: What I learned from 200 projects (Amsterdam UX)
Page 161: What I learned from 200 projects (Amsterdam UX)
Page 162: What I learned from 200 projects (Amsterdam UX)
Page 163: What I learned from 200 projects (Amsterdam UX)
Page 164: What I learned from 200 projects (Amsterdam UX)

Small ± 9 x 6 cm!Galaxy S2/S3/S4, iPhone, HTC One !

!

Medium ± 11 x 16 cm!Nexus 7, iPad mini, Kindle 7!

!

Large ± 21 x 14 cm!

Nexus 10, iPad (1, 2, Air), Tab 10.1, Kindle 8.9!

Small

Medium

Large

Page 165: What I learned from 200 projects (Amsterdam UX)

small portrait

small landscape

medium landscape & large portrait

small medium large

medium portrait

large landscape

desktop (large & non–touch)

640 px? 1024 px? %#@&*iPad Mini!

Page 166: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManage

Pitch

Scenarios

Position

Roadmap

Service Design

Prototype

RequirementsReviewTest

Scope

Optimize

Estimate

SketchDetailed Design

Concept

Personas

Competition

ProcessInterviews

Page 167: What I learned from 200 projects (Amsterdam UX)

Blast Radius

* international work environment

* working for small number of big accounts

* allows for tracking of success of designs

* project were never ran by UX (often by Developers or Art Directors)

* limited input in early stages of projects

Page 168: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 169: What I learned from 200 projects (Amsterdam UX)
Page 170: What I learned from 200 projects (Amsterdam UX)

Best team?

Page 171: What I learned from 200 projects (Amsterdam UX)
Page 172: What I learned from 200 projects (Amsterdam UX)

Jesse James GarrePeter MerholzJeff VeenJanice FraserDan SafferLane BeckerIndi Young

Page 173: What I learned from 200 projects (Amsterdam UX)

Best place for UX?

Page 174: What I learned from 200 projects (Amsterdam UX)
Page 175: What I learned from 200 projects (Amsterdam UX)

Best deliverable?

Page 176: What I learned from 200 projects (Amsterdam UX)

Business

Design

ResearchEvaluation

StrategyManage

Pitch

Scenarios

Position

Roadmap

Service Design

Prototype

RequirementsReviewTest

Scope

Optimize

Estimate

Beta

SketchDetailed Design

Concept

Personas

Competition

Process

Roles

Steps

Interviews

Page 177: What I learned from 200 projects (Amsterdam UX)

NarrativeAs a result of initial conversations with the client, our designer-led sales team would create a Narrative.

A Narrative consists of:

- key business needs

- project summary and team overview

- phase-by-phase description of activities and outcomes

- examples of expected deliverables

- timeline and budget

Page 178: What I learned from 200 projects (Amsterdam UX)
Page 179: What I learned from 200 projects (Amsterdam UX)
Page 180: What I learned from 200 projects (Amsterdam UX)

MOBILEAPP

MUSIC PLAYER IN BAR

out of scope

MUSICMATCH

Page 181: What I learned from 200 projects (Amsterdam UX)
Page 182: What I learned from 200 projects (Amsterdam UX)

Best process?

Page 183: What I learned from 200 projects (Amsterdam UX)
Page 184: What I learned from 200 projects (Amsterdam UX)

SUP wasn’t used, and SUP-Light was created to fix that

Page 185: What I learned from 200 projects (Amsterdam UX)
Page 186: What I learned from 200 projects (Amsterdam UX)
Page 187: What I learned from 200 projects (Amsterdam UX)
Page 188: What I learned from 200 projects (Amsterdam UX)
Page 189: What I learned from 200 projects (Amsterdam UX)
Page 190: What I learned from 200 projects (Amsterdam UX)
Page 191: What I learned from 200 projects (Amsterdam UX)
Page 192: What I learned from 200 projects (Amsterdam UX)
Page 193: What I learned from 200 projects (Amsterdam UX)
Page 194: What I learned from 200 projects (Amsterdam UX)
Page 195: What I learned from 200 projects (Amsterdam UX)
Page 196: What I learned from 200 projects (Amsterdam UX)
Page 197: What I learned from 200 projects (Amsterdam UX)
Page 198: What I learned from 200 projects (Amsterdam UX)

Best process?

your process

Page 199: What I learned from 200 projects (Amsterdam UX)

userreseach

concept design

detaileddesign

prototype & evaluate

Persona

SITEMAP

wireframesrequire-

ments

usability testScreen

FLOW

proto-type

designprinciples

Page 200: What I learned from 200 projects (Amsterdam UX)

Best client

Page 201: What I learned from 200 projects (Amsterdam UX)

the elements ofuser experienceHenning FischerDirector, Adaptive Path [email protected]@henningfischer

Peter BoersmaDesigner, Adaptive Path [email protected]@pboersma

RGB

108, 190, 7773, 155, 69

Page 202: What I learned from 200 projects (Amsterdam UX)

Government of Jamaica

Page 203: What I learned from 200 projects (Amsterdam UX)

Best business lesson?

Page 204: What I learned from 200 projects (Amsterdam UX)

Office Managers manage the company

office managers run the agency

Page 205: What I learned from 200 projects (Amsterdam UX)

don’t postpone talking about money

don’t be afraid to talk about money

Page 206: What I learned from 200 projects (Amsterdam UX)

it takes A LOT of work to get work done

Page 207: What I learned from 200 projects (Amsterdam UX)

20 years at interactive agencies

1995 - 2000 - General Design2000 - 2002 - Satama Interactive2002 - 2005 - EzGov2005 - 2006 - User Intelligence2006 - 2010 - Info.nl2010 - 2012 - Adaptive Path2012 - 2012 - freelance2012 - present - Blast Radius

Page 208: What I learned from 200 projects (Amsterdam UX)

Thank you!

Page 209: What I learned from 200 projects (Amsterdam UX)

What I learned fromoh, I don’t know, around

200 projects

Peter Boersma (@pboersma)Interaction Design Director at Blast Radius

Amsterdam UX MeetupJuly 2, 2014