Here are the components:
1. Change Simplicity - This refers to thinking about a transformation / project as a TV series as opposed to a movie. We should break change into phases, or “micro projects,” that can be implemented iteratively. “Rinse and Repeat,” as the wisdom of the shampoo bottle tells us. This way, we can easily adjust to changing marketplace relevance.
2. Market Simplicity - This is about stating the “Why” of the project as succinctly and clearly as we can, so everyone understands what results we want. It is also about prioritizing, clarifying, and triaging business requirements, so that we focus on only implementing change that is strategic to the business. Transformations and projects are successful when the outcomes are relevant, stated simply, and clearly worded. Many problems occur not because of technical issues, but because of communication issues.
3. Decision Simplicity - Having to make decisions based on ambiguity and/or having too many options results in paralysis by analysis. We need to narrow choices and filter information in a way that allows apple-to-apple comparisons. All through the project—from strategy through implementation– we need to be able to synthesize information to make timely, informative decisions.
4. User Simplicity - Most companies are aware of the need for positive user experiences for their customers, but they neglect their “internal customers” (employees). Many technology companies have employees straining to be productive on internal systems with clunky interfaces that they would never sell to their customers. Timely implementation success depends on teams being able to work effectively, without having to deal with unessential road blocks.
2. Market Simplicity - This is about stating the “Why” of the project as succinctly and clearly as we can, so everyone understands what results we want. It is also about prioritizing, clarifying, and triaging business requirements, so that we focus on only implementing change that is strategic to the business. Transformations and projects are successful when the outcomes are relevant, stated simply, and clearly worded. Many problems occur not because of technical issues, but because of communication issues.
3. Decision Simplicity - Having to make decisions based on ambiguity and/or having too many options results in paralysis by analysis. We need to narrow choices and filter information in a way that allows apple-to-apple comparisons. All through the project—from strategy through implementation– we need to be able to synthesize information to make timely, informative decisions.
4. User Simplicity - Most companies are aware of the need for positive user experiences for their customers, but they neglect their “internal customers” (employees). Many technology companies have employees straining to be productive on internal systems with clunky interfaces that they would never sell to their customers. Timely implementation success depends on teams being able to work effectively, without having to deal with unessential road blocks.
