Kolko says:
“A concept map is overwhelming when it is first presented. It was an extremely effective tool for the person who made it. It becomes a point of confusion for the person who has to read it, and this is where a concept map crashes and burns: it’s a manifestation of the expert blindspot. In creating a concept map, you’ve learned new things and you see the world in a new way. It’s tempting to present the finished artifact as proof of this new vision. But the audience wasn’t along for the ride. They didn’t learn what you learned, they don’t see the world the way you do, and because the map is visually complex (as was your learning), they’ll be intimidated.
And so I recommend that you use a concept map for organizational change over a period of months, strategically, socially, and with a goal of manipulating the trajectory of your company by helping colleagues view the world as you do.”
User Interface Design patterns are recurring solutions that solve common design problems. Design patterns are standard reference points for the experienced user interface designer.
This site will help you in two ways: You can read insightful design pattern articles and browse screenshot examples.
How to avoid (or mitigate) change aversion
1. Warn users about major changes.
2. Clearly communicate the nature and value of the changes.
3. Let users toggle between old and new versions.
4. Provide transition instructions and support.
5. Offer users a dedicated feedback channel.
6. Tell users how you’re addressing key issues they’ve raised.
Design by Simon Fletcher. Powered by Tumblr.
© Copyright 2010
