Dhananjay Parashivmurthy

Background

About Dhananjay Parashivmurthy

Design is really an act of communication, which means having a deep understanding of the person with whom the designer is communicating. Good design is actually a lot harder to notice than poor design, in part because good designs fit our needs so well that the design is invisible, Principles of design: 1. Use both knowledge in the world and knowledge in the head. Simplify the structure of tasks. Make things visible: bridge gulfs between Execution and Evaluation. Get the mappings right. Exploit the power of constraints. Design for error. When all else fails, standardize. Rule of thumb: if you think something is clever and sophisticated beware-it is probably self-indulgence. Learning should take place when it is needed, when the learner is interested, not according to some arbitrary, fixed schedule. A brilliant solution to the wrong problem can be worse than no solution at all: solve the correct problem. The idea that a person is at fault when something goes wrong is deeply entrenched in society. That’s why we blame others and even ourselves. Unfortunately, the idea that a person is at fault is imbedded in the legal system. When major accidents occur, official courts of inquiry are set up to assess the blame. More and more often the blame is attributed to “human error.” The person involved can be fined, punished, or fired. Maybe training procedures are revised. The law rests comfortably. But in my experience, human error usually is a result of poor design: it should be called system error. Humans err continually; it is an intrinsic part of our nature. System design should take this into account. Pinning the blame on the person may be a comfortable way to proceed, but why was the system ever designed so that a single act by a single person could cause calamity? Worse, blaming the person without fixing the root, underlying cause does not fix the problem: the same error is likely to be repeated by someone else- Father of Ux says