421 Delivery Model
Why do the majority of large scale IT projects fail (where fail is defined as running over time or budget or delivering less value than predicted)?
Most studies on this subject draws three main conclusions:
- Complexity in the business processes and consequently the change programme set-up are the main reason for failure.
- Organizational and individual mindsets and beliefs are key for creating long term buy-in and achieve lasting behavior change.
- Technical skills are seldom the cause of IT project failure.
Yet still the most of today’s project management disciplines have a strong focus on the IT side the project. The 421 delivery model broadens the focus towards a more complete set of activities needed throughout the change journey. The purpose of this is to avoid the most common pitfalls we’ve seen in the execution of complex change initiatives.
To learn more about 421s view on the most common pitfalls, read our perspective on “10 pitfalls to avoid for a successful change journey”.
The 421 delivery model includes the following main activities:
- As Is Analysis: Ensuring a solid understanding of the point of departure
- Change Management focusing on how commitment to and pull for the change is created and maintained even after the formal journey has ended.
- Change Strategy and Execution focusing on key strategic considerations during the shaping phase as well as core disciplines needed to create transparency and control during the execution.
- Business Transformation focusing on preparing the organization including third parties in terms of new or updated organization structures, processes, roles and responsibilities and governance structures.
- IT transformation focusing on the completeness, execution and quality of the IT deliveries required from the initiative.
- Benefit Realization focusing on how the initiative ensures that identified benefits are realized as part of the change journey.
- To Be Definition: Bringing clarity to the target picture including clearly defined and measureable objectives. A crucial part of the To Be definition is clear linkage to the underlying reasons that trigger the need for change – the “why”.
Change Checker by 421
Change Checker combines 421 delivery model with our experience from delivering complex change initiatives to the banking industry. It’s designed not only to visualize the current state of your initiative but also to produce proactive advice. As input you’ll answer 30 carefully selected questions based on our experience where biggest risk for failure lies.
Change Checker is also a great tool for verifying that all key aspects are covered in your next planning workshop or as self audit to help you widen your perspective.
Hope you find it useful!