1. Intentionally reduce the number of features/changes in a deliverable
1.1. the trick is to still deliver a meaningful & valuable increment
2. Less features, more often
2.1. Directives
2.1.1. AND incrementally roll out the changes
2.1.1.1. the number of people impacted/affected by deliverable
2.2. Benefits
2.2.1. Deliver valuable outcomes earlier
2.2.2. Lowers exposure to typical risks because:
2.2.2.1. earlier
2.2.2.1.1. (actual!) demonstration of technical feasibility
2.2.2.1.2. (actual!) demonstration of meaningful progress
2.2.2.1.3. feedback on (actual!) benefits realization
2.2.2.1.4. opportunity to course correct (micro or macro adaption) or move planned investment (budget) to a different initiative
2.2.2.2. minimize blast radius
2.2.2.2.1. less people and less functionality impacted, if things go wrong or feature "wrinkles" need ironing out
2.2.3. Reduces impact related to change and transition management
3. Provide focus
3.1. Directives
3.1.1. Remove distractions
3.1.1.1. Distractions are anything that is stopping people from actively making progress on the most important piece of work
3.1.2. Reduce need for firefighting
3.1.2.1. fires are also distractions but can become important
3.1.3. Nevertheless derisk and prepare the upcoming work (runway)
3.1.3.1. tomorrow's risks soon become today's issues
4. Adapt the plan
4.1. Directives
4.1.1. Change the plan as new insights are gained
4.1.2. Make the change transparent to all stakeholders
5. Identify and address bottlenecks and impediments
5.1. What do we wait on or slows us down that impacts most our progress?
5.1.1. decisions
5.1.2. expert knowledge
5.1.3. skills
5.1.4. dependencies
5.1.4.1. people
5.1.4.2. teams
5.1.4.3. systems