Projects

No projects found. Use a tool to create one.
Not logged in
Storage: calculating…

Navigate

Model / Deliver a Project / Set the Direction / Recognise your project is not unique
Rule 06 of 13

Recognise your project is not unique.

Before you plan, look at similar projects and learn what worked, what did not, and what it took to deliver them.

Rows of repeated yellow-handled objects showing a familiar pattern.

Questions to reflect on

Where has something like this been done before?

If you want more support from senior management, and to avoid common pitfalls, look to how other organisations delivered similar projects, and what resources they used. Identify and learn lessons from those who have achieved similar outcomes or from projects with similar components.

  • Who has achieved similar outcomes before?
  • Which projects have similar components?
  • What was the actual cost, how long did it take, and what surprised them?

What can we learn before we commit?

A 2024 study by the universities of Oxford and Copenhagen into 219 IT projects found that 1 in 5 teams rated their project as highly unique. They ran 45% higher cost overruns on average. The more unique you think your project is, the worse it performs.

  • Where are we treating this as more unique than it really is?
  • What examples would help others back the work?
  • What lessons can we borrow before we move forward?

Review readiness

Loading project readiness…

Plays are tools and guides to help you apply this rule.

Find similar projects

Learn from comparable projects so you can avoid repeating predictable mistakes.

Run learning meetings

Use structured meetings to capture what others learned and what it means for your project.

Further reading

  1. Article

    Why perceived uniqueness matters

    Oxford research on uniqueness bias shows why project teams should compare options before assuming their project is too different to learn from what already...

    Read

Ready to move on?

Once you have looked outside and learned from comparable work, you are in a better position to compare real options instead of jumping at the first one.

Next: Look for tried and tested options Return to Set the Direction

Confluity Project Model sitemap

Model overview

What are Jobs?

The model is organised into three Jobs:

Job 1: Set the Direction - shape the purpose into options and a preferred way forward.

Job 2: Prove It Works - test assumptions and reduce risk before going big.

Job 3: Make It Happen - deliver at scale and make sure people actually use what you build.

What are Simple Rules?

The model contains simple rules. These are short principles drawn from experience that help you make better decisions. Jobs, tasks, and plays help you put those rules into practice.

What is a Play?

A Play is a method or tool that helps you apply a rule or complete a task. Use the recommended Plays first for simpler projects before exploring others.

Downloads