Technology Projects Fail When the Planning Is Too Vague

A technology project can have a good product and still fail because the project itself was not defined clearly.

Define the outcome

What should be different when the project is complete? “Upgrade the network” is less useful than “provide reliable wireless coverage for these areas and support these users.”

Identify dependencies

Projects can depend on cabling, providers, accounts, hardware, software, training and other projects. Missing one dependency can delay everything.

Assign responsibility

Someone needs to know who is responsible for each part of the project, including vendor coordination.

Plan for change

Real projects encounter surprises. A useful plan can adapt without losing sight of the outcome.

Measure completion by the business result

A project is not complete because the equipment arrived. It is complete when the intended business capability works and the people using it understand the change.