Why projects go wrong (2/2)

I talked in my earlier posting here about health-check services when things go wrong and I covered specific reasons (causes) of what goes wrong, how and why.

In this posting, I would like to continue the reasoning behind failures and reveal some more factors in this regard.

• Wrong Assumptions that go invalidated/unverified all the way to the execution/implementation phase and become effective in net outcomes of the system/process
• Harmful compromises that are usually taken under pressure from constraints in time, money and/or resources otherwise needed to do the job right from first time.
• Fragmented responsibility/accountability/liability between different entities/persons allowing failures to pop up to the surface while no one is held responsible for what goes wrong in this regard

If you take these three factors as global factors that may intervene throughout all project/program/initiative lifeycles from A to Z, you may pinpoint problems during these phases

1. Turning "true needs" into "official requirements"
2. Mapping "official requirements" to "proposed solution capabilities"
3. Specifying/allocating proposed solution elements
4. Drafting an implementation for the proposed solution
5. Execution of the proposed solution implementation plan
6. Testing and verifying interim and final results of the implementation match the original requirements
7. Securing concurrence/approval of the key stakeholders all the way through
8. Documenting the above from A to Z for future audits / health-check services

Hopefully this sheds more light into the challenge of failure and why/how it happens 

Have A Great Day !