Experiment

Validate your assumptions in the real world.

Experiment is next.

Ideas and concepts are only a hypotheses. Regardless of how well they have been researched, how much time has gone into understanding the problem and iterating the idea, it needs to be put into the world to assess whether the idea as realised will have the expected value.

This, again, should not be a shock: validating assumptions should happen throughout an iterative approach to problem solving. Validation, experimentation, testing – in this case, they’re all the same thing. 

What the idea or concept is will determine how you might validate it. Validation can be as simple as quite literally asking someone a question to verify a fact, all the way through to elaborate testing initiatives with software and lab coats. The most important thing is doing just enough to validate assumptions and confirm the value is real – or real enough to build confidence in moving forward. 

There are only three results of an experiment: (1) Success, (2) Change of hypothesis and (3) No.

Of these, No is the most definitive option and not used nearly enough. In a world where multi-million dollar budgets hang on the success and viability of projects, how often have some initiatives moved forward even under the knowledge they will be stillborn or of little value when they’re done?

(That was a rhetorical question. It happens often – and I’m sure you may have even been a part of one or two yourself… I know I have)

Saying no clears the decks for valuable ideas. It is a natural part of prioritisation. It shows your team you’re serious about delivering value and won’t accept wasting time on ideas that won’t solve the problem.

Put your ideas into the world to show they have value in a small controlled experiment. Test your hypotheses. Don’t be afraid to say no and pull the pin – life is too short.

Photo by Bill Oxford on Unsplash