This doc I put together to share my views on some of most common myths about Design-Enterprise Software.

1. Design Myths
in Enterprise
Software
Ganesh Burle
UX Consultant

2. Let’s see how some
of most common
opinions have
turned out as
myths...

3. #1
“Enterprise products don’t require
great design; their users are experts
and can figure it out easily”

4. A real world example!
Enterprise Product Consumer Product

5. Risk
A real world example!
Risk
Enterprise Product Consumer Product

6. Risk
A real world example!
Risk
Features
(complexity) Easy to handle
Enterprise Product Consumer Product

7. Risk
A real world example!
Individual Risk
Features
(complexity) Easy to handle Organization
Enterprise Product Consumer Product

8. Risk
A real world example!
Risk
Individual
Self-operating
Features
(complexity) Easy to handle
Group-operating
Organization
Enterprise Product Consumer Product

9. Enterprise
Consumer
Risk
A real world example!
Risk
Individual
Self-operating
Features
(complexity) Easy to handle
Risk Group-operating
Features Complexity
Organization
Enterprise Product Consumer Product

10. Enterprise
Consumer
“Enterprise products require great
design and a nice approach!”
Risk
A real world example!
Risk
Individual
Self-operating
Features
(complexity) Easy to handle
Risk Group-operating
Features Complexity
Organization
Enterprise Product Consumer Product

11. #2
“When all that I’m showing numbers,
then there is not much scope for
design!”

12. 8008883836
This is a number or a total of something. But what it is?

13. 8008883836
This is a number or a total of something. But what it is?
Transaction
Number?
Customer ID? Account Number?
Reference #of Transactions?
Number?
Phone Number?
#of Logins?
Bill number?
#of Downloads?

14. 800 888 3836
Transaction
Number?
Customer ID? Account Number?
Reference #of Transactions?
Number?
Phone
Number #of Logins?
Annual Turnover?
#of Downloads?

15. 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
8 0088 838 36
800 888 3836
8008883836
8008 88 3836
80 0888 3836
8 008 8838 36
8008883836
80 0888 38 36
+ 25...

16. 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
8 0088 838 36
800 888 3836
8008883836
8008 88 3836
80 0888 3836
8 008 8838 36
8008883836
80 0888 38 36
+ 25...

17. A google designer says...
small change - big impact!

18. ‘The Joy of Stats’ by Hans rosling
The world in 200 countries over 200 years
using 120,000 numbers - in just 4 minutes!

20. “Data and information are not
boring; Add life to numbers by
giving them context and meaning”

21. #3
“Design takes a lot of time & money;
we can’t do it in our budget and
timelines.”

22. Planning Implementation
● Requirements gathering
● Prioritization
● Scope Of Work
● Design Phase
● Development Phase
● Testing Phase
● Bug fixing and release

23. 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

24. Planning Implementation
week weeks
● UX/Prototype
2 people
Proposed Model
● Design Phase
○ Interaction Design (1 week)
○ Visual Design (2 weeks)
● Development Phase
● Testing Phase
● Bug fixing

25. Planning Implementation
“A little place in the time of planning
week weeks will ● help UX/Prototype
to meet deadlines”
2 people
Proposed Model
● Design Phase
○ Interaction Design (1 week)
○ Visual Design (2 weeks)
● Development Phase
● Testing Phase
● Bug fixing

26. #4
“Okay. We did a design assessment
with our customers in last year and
there were no complaints. We’re
done with the product design.”

27. 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

28. 2007

29. 2010

30. 2012

31. 2014

32. “Design is NOT static; it evolves
with time.”

33. But, how to make this happen?

34. How to make this happen?
Let’s see what experts says....

35. We must unlearn what we’ve learned!
“Earth is in the middle of
universe”
“Sun is in the middle of
universe”

36. We must unlearn what we’ve learned!
“we’ve one milky way
galaxy/one universe” “We are multiverse”

37. Kepler 186F

38. “...design is not just about buttons,
images, icons and screens. It’s far
beyond that, it’s behaviour of
product!”
Kepler 186F

39. Let’s complete the picture!
Planning time (discover)
Implementation time (design)
Testing time (decide)
Scope
Effort

40. Let’s complete the picture!
Planning time (discover)
Implementation time (design)
Testing time (decide)

41. Design is not just a differentiator!

42. Design is not just a differentiator!

43. Design is not just a differentiator!

44. Design is not just a differentiator!

45. Design is not just a differentiator!

46. Design is not just a differentiator!

47. ...it’s foundation factor!

48. ...it’s foundation factor!
Thank you!
www.ganeshburle.com