Secrets of Effective Design and Execution Software
The discovery, design and execution cycle is the same for all companies whether effective or not. It begins with the discovery that something needs to be done, moves into a planning process and then to execution, at least in theory. There are four things that distinguish a fast and agile competitor from a slow and cumbersome organization.
- the time from discovery to execution is short - they can turn on a dime
- design is paramount - 'how can we ensure that this can be executed?'
- collaboration is prevalent at all stages of the process
- learning is harvested at the start of each cycle for continuous improvement
- lack of clarity: policies and procedures are difficult to access or understand
- complexity: systems and procedures are complicated and slow
- clutter: what's important is buried under what's not important
- lessons unlearned: new knowledge does not replace the old thinking
- a leadership gap: where are all the leaders?
- fear: a potentially paralysing barrier if not managed
There are two key principles to be followed when designing for effective execution.
Paradoxically, being simple and clear is not easy. It takes discipline and practice. David Graycreated a wonderful diagram to describe the process which we modified slightly.
- Step 1: connect people to the best processes, knowledge and tools available, making operational knowledge visible and accessible.
- Step 2: collaborate to createsimple clear and executable plans and publish them to your Global Performance System for deployment.
- Step 3: harvest innovation and lessons learned and feed them back into the planning process.