\"Fast, simple and easy to use\". This is the motto that drives the majority of tech companies nowadays. Fueled by Agile methodologies, these companies strive for fast deliveries and quick iteration cycles.<\/p>\n
But, in order to deliver fast, the outcome must be simple. But how simple? One of LEAN's methodology principles says the following:<\/p>\n
(\u2026) Keep things simple. Keep the requirements simple. Keep the technical solution simple. Find the easiest way to meet the users\u2019 goals. Don\u2019t over-engineer. Don\u2019t spend too long considering future requirements that may never materialize. Get something simple to market and build on it based on real customer feedback\u2014 (source<\/a>)<\/span><\/p>\n 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.<\/p>\n Is the simplest path the best one? Not always. Most of the time unexpected things will get in the way mid process, increasing its complexity.<\/p>\n In order to get a better understanding on this concept, let's take a deeper look at the meaning of simplicity.<\/p>\n I believe the easier way to describe simplicity is being devoid of unnecessary complexity. Professionals are more often used to measuring how complex a process can be by focusing on its technical aspects.<\/p>\nUnderstanding simplicity<\/h2>\n