Mr. Ankur Sharma was one of the trainers who talked about what the design should be, how to start with one and how to get there.

1. Designing UI
Principles and Process

2. Design

3. which one?
how to figure them out when you are in shower, half blind?

4. connector
loop{flip, can’t insert, flip again, can’t insert}

5. freeze or boil
how to set perfect temperature?

6. divider
are they even safe? during night??

7. but how?
What was the installer/interior/engineer thinking?

9. Criteria

10. affordances
When you see it you will know it.

11. affordances
What to do with this controls

12. constraints
restrict user interaction to reduce error

13. constraints
Which of the controls are usable

14. conceptual model
mental image of how system works, more closer to functionality the better.

15. mapping
relationship between control parameters and it’s effect

16. visibility
make sure the available controls are obvious and visible

17. feedback
let user know what is happening

18. feedback
The states description

19. consistency
similarity in similar function and identical way to perform them

20. consistency
The button arrangement across different OSes

21. Principle

23. Dieter Rams 10 principles of good design
•Is innovative
•Makes a product useful
•Is aesthetic
•Makes a product
understandable
•Is unobtrusive
•Is honest
•Is long-lasting
•Is thorough down to the
last detail
•Is environmentally
friendly
•Is as little design as
possible

24. Design process

25. develop concept
objective, user and resources

26. research
do need analysis, business research and constrains

27. prototype
you never know until you do it

28. refinement
iterate, review, tests and prototype again

29. Implement
practices, documentation and polishing

30. support
evaluation, maintenance and training

31. Ethnography

32. https://www.youtube.com/watch?v=N4t3-__3MA0
How the design is perceived by real world

33. Project Synopsis

34. Content for synopsis
• Summary (One sentence
description)
• Application (One paragraph brief
explanation)
• Activity (Bullet list of activities)
• Audience (One paragraph about
intended audience)

35. Requirement

36. Fashion store app
• Functional: Allow consumers to browse and purchase clothing merchandise
• Data: The system must have access to prices, pictures of merchandise, and up-to-
date inventory.
• Environmental: Widely distributed, usually home. On phone and tablets.
• User: Anyone with interest in clothing purchases
• Usability: Simple to operate. Give feedback on stage is sales process.
Distinguish buying from “window shopping” payment application.Optimised for
tablet viewing.

37. User story

38. persona
• Body
• Psyche
• Background Information
• Emotion and Attitude
• Personal Traits

39. persona

40. conceptual design

41. metaphor
physical link with interface

42. interface style
physical link with interface

43. interaction style
physical link with interface

44. Prototype

45. Best description?

47. visual and haptic
You can feel, use and improve the product

48. pretendotype
Palm pilot prototype by Jeff Hawkins

49. types

50. lo-fi
pen and paper, goes well with scenario

51. hi-fi
Talks about look and feel, as good as final product

52. functional
Shows interactions, let user use it

53. compromises

54. horizontal vs vertical
The scope helps set target right

55. Evaluation

56. WHY EVALUATE
to test the usability of the system and to avoid pitfalls

57. COGNITIVE WALKTHROUGH
define a task and walk through necessary steps to perform the
given task

58. LIKERT SCALE
asking questions the right way.

59. NIELSEN AND MOLICH'S NINE
HEURISTICS
• Simple and natural dialog
Simple means no irrelevant or rarely used information. Natural means an order that matches the task.
• Speak the user's language
Use words and concepts from the user's world. Don't use system-specific engineering terms.
• Minimize user memory load
Don't make the user remember things from one action to the next. Leave information on the screen
until it's not needed.

60. NIELSEN AND MOLICH'S NINE
HEURISTICS
• Be consistent
Users should be able to learn an action sequence in one part of the system and apply it again to get
similar results in other places.
• Provide feedback
Let users know what effect their actions have on the system.
• Provide clearly marked exits
If users get into part of the system that doesn't interest them, they should always be able to get out
quickly without damaging anything.

61. NIELSEN AND MOLICH'S NINE
HEURISTICS
• Provide shortcuts
Shortcuts can help experienced users avoid lengthy dialogs and informational messages that they don't
need.
• Good error messages
Good error messages let the user know what the problem is and how to correct it.
• Prevent errors
Whenever you write an error message you should also ask, can this error be avoided?

62. Tools

63. PENCIL N PAPER
Use what you are comfortable with, don’t build sandcastle with
bulldozer

64. COMMUNICATE
Biggest mistake that can be made is “assumption”

65. COLLABORATIVE EDIT
Helps in iterative documentation and feedback

66. Tips

67. RESEARCH
read, validate, gather information, learn new tricks
Template

68. Setup Confrontation Resolution
BUILD STORY
Every good design tells stories, what is yours?

69. PRESENT
Let them know how awesome your project is. Talk, show and sell

70. FUN

71. https://www.youtube.com/watch?v=kifMGc5cYuw

72. Ankur Sharma
Director/UX
ankur@expresivstudios.com
Thanks!