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.
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.
For projects, my learning was this simple rule for success:
Use what has been done before when looking at your options.
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?
Read online →
|
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
|
Tools
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 →
|
|
Decision Clarity
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