Deloitte Cem Ams 25 May2011
-
Upload
theo-slaats -
Category
Technology
-
view
1.003 -
download
0
description
Transcript of Deloitte Cem Ams 25 May2011
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Experience Delivers Roadtour Amsterdam May 25th 2011 Thinking Users Down, Not System Up
“Customer Experience matters”
Premium Sponsor
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Some great tools have long history of design
2
Once a desperate need arose
Once a desperate need arose...
...around the concept of driving a nail into a piece of wood
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
And then.... the Hammer was invented
3
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Hammer evolution
4
Prehistory Now
The hammer has known many shapes
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Hammer engineering
5
Over the years, hammer specialists have optimized the design of the hammer
towards its purpose...
...creating an optimal device for
the user
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Hammer engineering: User Down
6
Hammers are developed with both the user and purpose in mind
user down
The tool is shaped towards the user
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Software engineering
7
From a business process perspective Software is a tool
But in contrast to a hammer...
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Software engineering: System up
8
... software is usually developed with the system in mind
system up
The user needs to adapt to the system
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Software engineering: System up
9
Over the years, software engineers have typically focussed on
• Reliability
• Scalability
• Security
• Maintainability
And with respect to users on... well, actually..... nothing
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Thinking system up focuses on the system, not the users
10
Employees need to use 6 systems on
average to access core business data for
their daily job
Solutions live frequently in siloes caused
by legacy architecture, acquisitions,
mergers etc.
All system functions accessible on
first page, for all users if possible
Lots of manuals, training hours and a
steep learning curve
Next version is planned next year (or
the following)
Have high expectations due to
sophisticated experience of
usability (Facebook, Google,
LinkedIn, Bol.com, iPhones)
No tolerance for cumbersome
interfaces anymore
Used to frequently changing
interfaces of popular sites
Very familiar combining external
sources like newsfeeds, maps,
search, etc.
System functionality User’s Point of View
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
User Down: engage the user
11
When designing systems the business requirements are one key factor,
the other one is usability
Usability factors
Intuitiveness iPad doesn’t come with a manual
Interoperability Systems working seamless together, no window
switching or alt tab needed
Aggregation data from various sources generate useful information
Portability nowadays information lives on many screens
Outside –in external sources adds value to your information
Get to know and understand the user!
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
System up versus User down
12
System up User down
Designed Evolution
vs
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Imagine – these 6 systems to work with
13
The user
Inventory Search
Customer Account
Client Search
Payments
Order Entry
Delivery
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Where do you start – Use a Persona Driven Approach
14
Conduct User research
Look at the
Jobs users do
Define the Roles
Identify use cases Build Wireframes
Build Visual Design
and Prototype
Define relevant usability
metrics
Identify
Personas
Deloitte’s Usability Clock™
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Personas
15
Fictitious characters created to represent the different user types that might use your “product”.
Developed from real-world (client)information.
Reveal the people behind the numbers
Example: Simon Stockbroker, Marc Manager and Billy Banker.
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
The Value of Personas
16
Personas provide target group representation in clear segments.
Personas provide a description per segment in terms of goals wishes and limitations
The use of Personas results into clear and verifiable functional and design-targets
The Persona based approach ensures a constant maintain of focus on the end user.
Personas help build User-Centric Systems
And on a higher level, Personas help build a People-Centric Organization.
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Conduct User Research
17
Who are those people that will be using your product
What is their background
Are they young, old, college educated, etc.
What are their needs, goals, wishes and limitations
What do they like
What do they dislike
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Look at the Jobs Users do
18
What is it that your users do in their daily jobs
What are the tasks they need to accomplish
What are the challenges they face in doing so
How are the current tools supporting them
Identify the support / improvement areas you are targeting.
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Define the Roles
19
Split up the process you are supporting in terms of expertise
Do the same for responsibility
Define who is to be involved at which state in the process
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Identify use cases or user stories
20
Given the Business case
The processes you need to support
The people involved in these processes
The roles you identified
Write down what you expect your system to do.
Do so for each task you can think of (for all of the roles)
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Build wireframes
21
Translate your user stories/ use cases into schematic screen designs.
Visualized concepts offer clarity to all stake holders
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Wireframe – Sketch example
22
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Welcome, User
Sales Control Center
Search Logo
Dashboard
Your Sales Target Sales Funnel Prospects Status
Workflow Items
Activities Opportunities
Subject Request By Due Date
Activity Status Due Date
Wireframe – Elaborated version
23
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Build visual design and prototype
24
Finalize the perceptual input for users and other stakeholders
o Present the design
o Build interactive prototype (high fidelity with finalized design or low fidelity using wireframes)
Test your ideas
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands 25
High-fidelity prototype sample
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Define relevant usability metrics
26
Many aspects of usability are measurable
Be sure to define metrics for your expectations
With these metrics, define usability in your requirements
Be sure to define the budget you want to spend on usability.
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Before After
Transaction
simplification
20 Clicks, 3 Screens 5 Clicks, 1 Screen
Time to create
notification
4 Minutes 2 Minutes
Notifications/hour Up to15 25 to 30
Training participation 27% (Attended) 98% (Attended)
Training efforts Instructor-Led Training (ILT) Computer-Based Training (CBT)
Usability metrics, before and after
27
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Conclusion: a User Down approach adds real value
28
Great systems that are used to the max
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Be prepared for great results
29
Inventory Search
Customer Account
Client Search Payments Order Entry Delivery
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Lessons learned
30
• Usability of Call Centre Software led to
66% agent productivity gain
• Redesign front end ERP services
jumped business process
performance by 30%
• UX enhanced in eCommerce site lead
to 300% increase in revenue
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Dos and don’ts
31
... evangelize usability
... determine metrics to measure success
... get a user experience professional
... stay in perpetual beta
... think through usability change management
DO
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Dos and don’ts
32
... forget the user
... give in to temptation for trends
... forget about integration
... rely on waterfall methodology
... set unrealistic expectations
DON’T
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Questions?
33
Partner | Technology | User Engagement, Pricing, CRM, Social Media & Cloud Computing Theo Slaats
Tel. +31 6 5267 2525
Theme Lead User Engagement Pieter Hering
Tel. +31 6 1100 3899
© 2010 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
© 2011 Deloitte The Netherlands
Disclaimer:
Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited, a UK private company limited by guarantee, and its network of member firms, each of which is a
legally separate and independent entity. Please see www.deloitte.com/about for a detailed description of the legal structure of Deloitte Touche Tohmatsu Limited and
its member firms.
Deloitte provides audit, tax, consulting, and financial advisory services to public and private clients spanning multiple industries. With a globally connected network of
member firms in more than 140 countries, Deloitte brings world-class capabilities and deep local expertise to help clients succeed wherever they operate. Deloitte's
approximately 170,000 professionals are committed to becoming the standard of excellence.
This publication contains general information only, and none of Deloitte Touche Tohmatsu Limited, Deloitte Global Services Limited, Deloitte Global Services
Holdings Limited, the Deloitte Touche Tohmatsu Verein, any of their member firms, or any of the foregoing’s affiliates (collectively the “Deloitte Network”) are, by
means of this publication, rendering accounting, business, financial, investment, legal, tax, or other professional advice or services. This publication is not a substitute
for such professional advice or services, nor should it be used as a basis for any decision or action that may affect your finances or your business. Before making any
decision or taking any action that may affect your finances or your business, you should consult a qualified professional adviser. No entity in the Deloitte Network
shall be responsible for any loss whatsoever sustained by any person who relies on this publication.