Technology projects rarely run late because of one bad estimate. They run late when the business problem, ownership, dependencies and adoption work have not been made visible.
This practical checklist is Recalibrate’s own version of the project controls that matter most to SME leaders. It is informed by wider project-management discussion, including material originally published by Harvard Business Review; it is not a republished extract.
Why technology projects run late
- The outcome is not agreed by the people who will use or fund the change.
- Scope keeps moving because the underlying problem is not clear.
- The team is expected to deliver while carrying competing priorities.
- Dependencies, data, vendors or decisions are left outside the plan.
- The business assumes technology will fix a problem that requires a change in behaviour.
What leaders need to control
Make the desired outcome concrete. Name the business owner. Agree what is in and out of scope. Check that the people doing the work are available. Identify dependencies and decisions before they become blockers. Plan adoption, not just implementation.
A practical project health check
- Can everyone explain the business result in one sentence?
- Who can make the next decision without waiting for a committee?
- What assumption would most damage the plan if it proved wrong?
- Which people, data or systems sit outside the project team?
- How will we know the new way of working has been adopted?
The most important ownership question
IT can deliver a system. The business must own the problem, the trade-offs and the change in work. If no one owns the outcome, the project can be technically complete and still fail.
When to pause or reset
Stopping to clarify the outcome, remove scope or reassign ownership is often cheaper than continuing a project that is quietly losing confidence. A useful reset is a leadership action, not a failure.
Explore digital transformation or start a conversation.
Originally published in 2014; substantially rewritten for SME leaders in July 2026. External source context retained for attribution.
Technology projects rarely run late because of one bad estimate. They run late when the business problem, ownership, dependencies and adoption work have not been made visible.
This practical checklist is Recalibrate’s own version of the project controls that matter most to SME leaders. It is informed by wider project-management discussion, including material originally published by Harvard Business Review; it is not a republished extract.
Why technology projects run late
What leaders need to control
Make the desired outcome concrete. Name the business owner. Agree what is in and out of scope. Check that the people doing the work are available. Identify dependencies and decisions before they become blockers. Plan adoption, not just implementation.
A practical project health check
The most important ownership question
IT can deliver a system. The business must own the problem, the trade-offs and the change in work. If no one owns the outcome, the project can be technically complete and still fail.
When to pause or reset
Stopping to clarify the outcome, remove scope or reassign ownership is often cheaper than continuing a project that is quietly losing confidence. A useful reset is a leadership action, not a failure.
Explore digital transformation or start a conversation.
Originally published in 2014; substantially rewritten for SME leaders in July 2026. External source context retained for attribution.