Law 1: Reduce
"The simplest way to achieve simplicity is through thoughtful reduction"
Maeda's first law of simplicity is to reduce complexity:
The easiest way to simplify a system is to remove functionality. Today's DVD, for instance, has too many buttons if all you want to do is play a movie. A solution could be to remove the buttons for Rewind, Forward, Eject, and so forth until only one button remains: Play.
But what if you want to replay a favorite scene? Or pause the movie while you take that all-important bathroom break? The fundamental question is, where's the balance between simplicity and complexity?
On the one hand, you want a product or service to be easy to use; on the other hand you want it to do everything that a person might want it to do. The process of reaching an ideal state of simplicity can be truly complex, so allow me to simplify it for you. The simplest way to achieve simplicity is through thoughtful reduction. When in doubt, just remove. But be careful of what you remove (2006, Law 1: Reduce).
When launching new technology initiatives in a classroom, school or district reducing complexity is paramount, because the more complex the new initiative the more likely the end users (teachers, students, parents etc.) will become frustrated and resist the initiative. Find the core goal, or "play button", for your initiative and thoughtfully simplify your plans to focus on creating a convenient user experience.
In the comment field below share the what the "play button" is for your initiative. Then share your initial thoughts on how to reduce the complexity of your initiative to focus on your "play button", finally, illicit advice from your peers on areas you want to reduce complexity but are struggling with how. Make sure to check back to see advice from others and to provide your own keen insights to the questions posed by others.