design myths in enterprise software
TRANSCRIPT
Design Myths in Enterprise Software
Ganesh BurleUX Consultant
Let’s see how some of most common opinions have turned out as myths...
“Enterprise products don’t require great design; their users are experts and can figure it out easily”
#1
A real world example!
Enterprise Product Consumer Product
Risk
Risk
A real world example!
Enterprise Product Consumer Product
Risk
Features(complexity) Easy to handle
Risk
A real world example!
Enterprise Product Consumer Product
Risk
Features(complexity) Easy to handle
Organization
IndividualRisk
A real world example!
Enterprise Product Consumer Product
Risk
Risk
Features(complexity) Easy to handle
Individual
Self-operating
Group-operating
A real world example!
Enterprise Product Consumer Product
Organization
Risk
Risk
Features(complexity) Easy to handle
Individual
Self-operating
Group-operating
A real world example!
Enterprise Product Consumer Product
OrganizationRisk Features Complexity
EnterpriseConsumer
Risk
Risk
Features(complexity) Easy to handle
Individual
Self-operating
Group-operating
A real world example!
Enterprise Product Consumer Product
OrganizationRisk Features Complexity
EnterpriseConsumer
“Enterprise products require great design and a nice approach!”
“When all that I’m showing numbers, then there is not much scope for design!”
#2
8008883836This is a number or a total of something. But what it is?
8008883836This is a number or a total of something. But what it is?
Transaction Number?
Customer ID? Account Number?
#of Transactions?Reference Number?
Phone Number?#of Logins?
#of Downloads?
Bill number?
800 888 3836
Transaction Number?
Customer ID? Account Number?
#of Transactions?Reference Number?
Phone Number #of Logins?
#of Downloads?
Annual Turnover?
This can be designed in other ways..
8 008 883 836 80 088 838 36 8008 883 836
8 00 888 3836
800 8883 836
8 00 88 838 36
8008 88 3836
800 888 3836
8008883836
8008 88 3836
8 0088 838 36
8 008 8838 36
8008883836
80 0888 38 36
80 0888 3836
+ 25...
A meaningful framing is what Design!
8 008 883 836 80 088 838 36 8008 883 836
8 00 888 3836
800 8883 836
8 00 88 838 36
8008 88 3836
800 888 3836
8008883836
8008 88 3836
8 0088 838 36
8 008 8838 36
8008883836
80 0888 38 36
80 0888 3836
+ 25...
‘The Joy of Stats’ by Hans rosling
The world in 200 countries over 200 years using 120,000 numbers - in just 4 minutes!
“Data and information are not boring; Add life to numbers by giving them context and meaning”
“Design takes a lot of time & money; we can’t do it in our budget and timelines.”
#3
● Requirements gathering
● Prioritization
● Scope Of Work
● Design Phase
● Development Phase
● Testing Phase
● Bug fixing and release
Planning Implementation
Planning Implementation
● Requirements gathering
● Prioritization
● Scope Of Work
2 people
Current Model
weeks
● Design Phase
○ Interaction Design (2 weeks)
○ Visual Design (2 weeks)
● Development Phase
● Testing Phase
● Bug fixing and release
Planning Implementation
● UX/Prototype
2 people
Proposed Model
● Design Phase
○ Interaction Design (1 week)
○ Visual Design (2 weeks)
● Development Phase
● Testing Phase
● Bug fixing
week weeks
Planning Implementation
● UX/Prototype
2 people
Proposed Model
● Design Phase
○ Interaction Design (1 week)
○ Visual Design (2 weeks)
● Development Phase
● Testing Phase
● Bug fixing
week weeks“A little place in the time of planning will help to meet deadlines”
“Okay. We did a design assessment with our customers in last year and there were no complaints. We’re done with the product design.”
#4
Must-be Quality: These attributes are taken for granted when fulfilled but result in dissatisfaction when not fulfilled. An example of this would be package of milk that leaks.One-dimensional Quality: These attributes result in satisfaction when fulfilled and dissatisfaction when not fulfilled. An example of this would be a milk package that is said to have ten percent more milk for the same price will result in customer satisfaction, but if it only contains six percent then the customer will feel misled and it will lead to dissatisfaction.Attractive Quality: These attributes provide satisfaction when achieved fully, but do not cause dissatisfaction when not fulfilled. For example, a thermometer on a package of milk showing the temperature of the milk.Indifferent Quality: These attributes refer to aspects that are neither good nor bad, and they do not result in either customer satisfaction or customer dissatisfaction.
Kano model
2007
2010
2012
2014
“Design is NOT static; it evolves with time.”
But, how to make this happen?
How to make this happen?
Let’s see what experts says....
We must unlearn what we’ve learned!
“Earth is in the middle of universe”
“Sun is in the middle of universe”
We must unlearn what we’ve learned!
“we’ve one milky way galaxy/one universe” “We are multiverse”
Kepler 186F
Kepler 186F
“...design is not just about buttons, images, icons and screens. It’s far beyond that, it’s behaviour of product!”
Let’s complete the picture!
Planning time (discover)
Implementation time (design)
Testing time (decide)
Scope
Effort
Let’s complete the picture!
Planning time (discover)
Implementation time (design)
Testing time (decide)
Design is not just a differentiator!
Design is not just a differentiator!
Design is not just a differentiator!
Design is not just a differentiator!
Design is not just a differentiator!
Design is not just a differentiator!
...it’s foundation factor!
...it’s foundation factor!
Thank you!www.ganeshburle.com