The problem is that sometimes “simple” ends up treated as “minimal”, resulting on faulty features that don’t add much value to the user until the next iteration comes around, causing flaws on the user experience. In order to deliver fast, simple and easy, the outcome must be simple.
Understanding Simplicity
Provide just enough functionality for the users to get things done without getting in their way
- This can be achieved by reducing the amount of features or hiding things until they are necessary
- Attention must be paid when going down this path to not lose quality on your product
Delegating control to the application
This approach is most valuable on situations where complex tasks must be performed.
- The problem with this approach is that it relies heavily on feedback. If the application fails to communicate its state to the user, the experience will quickly become confusing.”
Giving the user more control
This approach is most valuable when direct manipulation or customization is required
- Sometimes the application must accommodate custom preferences, so some decisions are delegated to the user
- On the technical side, this approach opens possibility for the creation of modes, which can complicate the experience even more if not managed properly
Tesler’s Law- Why things will never be that simple
Also known as the law of conservation of complexity, it presents the following concept: Every application has an inherent amount of complexity that cannot be removed or hidden.
- Instead, it must be dealt with, either in product development or in user interaction.
Conclusion
Take the time to figure out when you’re providing the most value to the user
- Aim for exceeding expectations without overwhelming the experience
- Try to reduce time to perform a task
- Provide clear and organized steps towards achieving the end result
- Reduce the amount of distractions
- Bring data forward in order to facilitate the process
Finding the perfect balance
You want the application to be easy to use and provide value to the user in a simple way.
- On the other hand, it should provide just enough functionality to get stuff done.
- The goal is to reduce functionality without significant penalty.
