1. Making Deliverables
Making Deliverables
Consumable
By
The Designers

4. Why can’t developers and designers
Wh ’d l dd i
understand each other?

5. What is the use of
We need to do
designers when we
di h
User study…
are the one who
build applications

6. Why do you need Why do you take 3
the screens, we days to come up
first need to make the
fi t dt k th with a wireframe,
ith if
work flow and which looks like a
architecture scribble

7. If its just a sketch
why can’t you
accommodate the
d t th
changes in
requirement?

8. Because they don’t speak
the same language!
the same language!

9. Do you think users are
important ?
important ?

10. Users, not technology, drive the
product’s success

11. So, What is User Centered Design?

12. • Example of bottle design
Example of bottle design
• Manufacturing design and UCD design

13. An approach With
that supports User‐centered
the entire activities
development
process
So, What is User Centered Design?

14. An approach In order to
With
that supports create
User‐centered
the entire applications
activities
development
process
So, What is User Centered Design?

15. An approach In order to
With
Which are easy
that supports create and are
User‐centered
to use
the entire applications
activities
of added value
development to the intended
process users.
So, What is User Centered Design?

16. What do we do?

17. The client gave us “sample”
screens , requirements
screens requirements
and information finalized

21. Application redesign Requirements fixed

22. Concept fixed

23. Concept fixed

24. Product Strategy

25. Product innovation

26. Product innovation

27. Product innovation

28. Which means, we are saying …

29. Good design is good business
Good design is good business
– TJ Watson, founder IBM

30. Good design is For good business
Good design is ‘For’ good business

31. To sum up, design helps business
To sum up, design helps business
The biggest cost benefit that UCD can provide is by more accurately
•
defining requirements.
– A change made late in the design process will typically cost ten times
more than if the change were identified during requirements.
– Making changes to working systems will cost about one hundred times
more.
Design helps in making a better product
•
– by innovation and better interaction, aesthetics
– by acting as a business differentiator
by acting as a business differentiator.

32. How do we do it ?

33. How do we do it ?

34. How do we do it ?

35. How do we do it ?
H d d i?

36. Process diagram – actors, roles, relationships, questions
Gram e’Arth

38. Let us condense this a nut shell…
Business
Product
User
Technology
User Requirement
We are here to help you build things….

39. Hand in Hand with Agile

40. Product
Pd Planning
Pl i Building
B ildi
Stakeholder
Concept
Product Owner
Product Owner Designer +
Designer +
Stakeholder Team Developer
Hand in Hand with Agile

41. Planning
Product
Pd Building
B ildi
Product Owner
Stakeholder
Concept Team
Designer +
Designer +
Designer + Product
Stakeholder Developer
manager +
User Representative
Hand in Hand with Agile

42. Product Building
B ildi
Planning
Pl i
Concept
Stakeholder
Market research
+
Business Goals
Business Goals
Agile and UCD Process

43. Planning
Product Building
B ildi
Concept Phase 0:
User requirement
User requirement
gathering
Phase 1:
Ph 1
Feature list,
according to priority
1. 2, 3,4, 5 ….
Break it into
independent
independent
modules (stories)
A (1, 2, 3) , B (4, 5)
Agile and UCD Process

44. Building
Developer
Designer
Release A
Research 1+2 D l
R h 1 2 Development
Design 1 groundwork
Design 2
Design 2 Develop 1
Develop 1
Release B
Rl B
Research 3
Design 3 Develop 2
Research 4
Test 1
Product
Agile and UCD Process

45. How this helps….
How this helps….
• Better understanding of the problem
Better understanding of the problem.
• Allows rapid testing and validation of story
concepts before time consuming coding.
concepts before time consuming coding
• Provides a clear, sociable visual representation
of the project vision.
fh j ii
• Engaging the end user as a customer.
• Improves basis for estimation.
• Mitigates project risk
Mitigates project risk.

46. UCD in an agile environment
UCD in an agile environment
• Ideal Role Sharing
Ideal Role Sharing
• Team Based
• Team (designer + developer) takes ownership
(d i dl )k hi
of the design
• Provides the vision of the design for multiple
development cycles

47. Thank you !