Limited time offer: get your first week of Confluity Pro for £1, then £7 per month. Cancel anytime. Start for £1
Help us improve Confluity, Give feedback

Better projects start with clarity.

Before you build new, check what already works

Hello fellow clarity builder

This week is about the Simple Rule: Look for Tried and Tested Options.

Greg Krawczyk with text: Reflections on a project that went wrong
Reflections on a project that went wrong.

I don’t talk much about this example openly.

Some years ago, I was delivering an IT project for a public sector organisation.

We had been asked to build a new system.

  • After months of work, I was able to determine that the system was going to cost a lot more than originally thought.
  • It transpired that we could achieve the same aims by reusing what had been created by another team.
  • That saved a lot of public sector money and reduced risk.

It was an important learning moment for me.

I learned that, as humans, we have a tendency to commit to options, particularly when they are new, instead of reusing existing options.

This behaviour is caused by many of the biases that affect human behaviour, with commitment bias strongly at play here.

For projects, my learning was this simple rule for success:

Use what has been done before when looking at your options.

I think it is important that we share real-world stories, as best we can.

Many projects fail by believing they are unique or jumping into solutions too early.

Don’t reinvent the wheel. Explore multiple options before you commit and ask yourself: is there a way to deliver this using something that already works?

Do One Thing

Check what has already worked

Before you commit to a new build, take 20 seconds and ask:

  • What already exists inside our organisation?
  • What has another team already proved?
  • Could we reuse, adapt, or test that before starting from scratch?

Explore Look for Tried and Tested Options →

Further Reading

Start with a proof of concept

This article explores the Setup To Prove It Works play. It helps you decide whether a proof of concept is the next best step when the goal or route is unclear.

Read the full story →

Why perceived uniqueness matters

This article explores the Oxford working paper Uniqueness Bias: Why It Matters, How to Curb It. It helps you understand why perceived uniqueness can make projects harder to compare and easier to overrun.

Read the full story →

Have you found the same on any of your projects?

See you next time

Greg

One quick, practical solution each week.

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

Discover more from Confluity

Subscribe now to keep reading and get access to the full archive.

Continue reading