To really value simple software and make avoiding complexity visible, one should aim to shorten the feedback loop and reward the simplicity often.
This could be done by celebrating and drawing attention to this.
Examples of celebrating and showing simplicity
- Document weighted options, including more complex ones
- Shine light on quickly shipped features
- Celebrate the ease of on boarding colleagues
- Argue for the last responsible moment
How to check if complexity is warranted
- Why is this all necessary?
- What signals are that these will be requirements down the line?
- What is the current scale, and resource usage?
- What is a bottleneck or a single point of failure?