Start with a proof of concept
You have a goal, big idea, or change.
Do you start with design, a pilot, or going big?
What if it is none of those?
If you have low certainty about the goal, or what you actually need to build, the next step may be to prove the idea first.
When to prove the idea first
Sometimes, when your goal is unclear, it will be difficult to select the best option.
That is when a proof of concept can help. It gives you a small way to test whether an idea can work before you ask people to commit to a bigger route.
I created a short demo to show how to use Confluity’s Setup To Prove It Works play.
Specifically, it shows how you may want to test the idea before you commit to a larger build, design, or pilot.
Watch the short demo
Click to watch the suggested YouTube video on using a proof of concept to test the idea before you commit to a larger route.
Implication for the reader
A project can feel urgent and still need a small test first.
If the goal, route, or solution is unclear, going straight into design can create more work later. A proof of concept helps you learn before the cost of change becomes too high.
One quick action
Before you decide how big to go, ask:
- What assumption would change our decision if it was wrong?
- What small test could prove whether that assumption is true?
- What would we do differently after the test?
If the answer is useful, start with a proof of concept.
Further reading
- Context: Job 2: Prove It Works
- What: Setup To Prove It Works
- How: Plan a Proof of Concept
Get the big things right with Confluity.
Greg
Use the free quick readiness check to identify the one thing to improve next.
Use the quick guided readiness check →
