I've been covering the link between future trends and innovation strategies for 30+ years. I went back through my blog posts, stretching to 2002, to dig out the nuggets of innovation insight I've discovered along the way. This series revisits those stories, tests what still holds up, and turns them into practical lessons for what comes next.
"In the absence of clarity, taking initiative today is significantly better than finding a perfect plan tomorrow."
I've come back to this idea repeatedly in my work because the mindset behind innovation usually changes before the results do. What people notice, question, challenge, and act on determines how ready they are for what comes next.
Uncertainty tempts people to plan harder. Sometimes that helps. Often it becomes a sophisticated form of delay.
When conditions are changing quickly, a perfect plan can be obsolete before it is approved. Small action produces information that planning alone cannot.
The answer is not to abandon strategy. It is to make strategy more iterative. Act, learn, adjust, repeat.
Clarity often arrives after movement, not before it.
So what does that mean in practice? It means challenging the assumption, habit, or hesitation that is keeping you anchored to the present. Here are three places to start.
Action Items:
- Break one stalled plan into a decision you can make this week.
- Ask what evidence only action can produce.
- Put a time limit on planning before an experiment must begin.
Explore the full How Innovation Happens series.
Real-World Examples
These researched examples show the lesson at work in the real world.
GOV.UK: Launch the unfinished service and learn in public
Britain's central government once spread its online information across Directgov and numerous departmental sites. The eventual goal was a single, simpler home for public services. A conventional response could have meant years of requirements documents, procurement exercises and one enormous launch. The Government Digital Service chose a more exposed route: put real pages in front of users while the design was still evolving.
On 31 January 2012, the GOV.UK team launched a public beta. Its own account describes a small group of designers, developers and managers using open software, cloud hosting and agile working practices. The beta covered hundreds of user needs but was explicitly not yet the official destination for government transactions. Visitors were invited to tell the team what worked and what failed.
The GDS project history records that developers changed the site within a day of its release in response to user feedback, and made further changes the next day. More government material followed in subsequent phases. The existing Directgov site was replaced later in 2012. Progress came through shipping, observing and correcting rather than pretending the first release would be final.
The unusual decision was institutional, not technical: government publicly admitted it had an unfinished product, then treated that as an advantage. It kept the distinction between safe public testing and official services, but refused to let the desire for a perfect master plan block useful evidence from real people.
Why it matters: A responsible pilot turns uncertainty into usable evidence faster than another round of internal presentations.
Sources:
Flint: Residents collected the evidence that official assurances lacked
In Flint, Michigan, residents were reporting serious problems with their water after the city changed supplies in 2014. Waiting for the official argument to resolve itself was not a realistic option for families worried about exposure to lead. A group of residents, led on the ground by LeeAnne Walters, joined with researchers at Virginia Tech to organize independent testing while the controversy continued.
The researchers developed a sampling process and worked with residents to distribute kits and collect water from homes across Flint in August 2015. A subsequent peer-reviewed analysis records that 277 of 300 distributed kits were returned, an unusually high participation rate. The study documents both the citizen-led effort and the methodological limitations of its voluntary sample.
The results helped establish that significant lead contamination demanded urgent attention. Virginia Tech's account describes an initiative that moved from individual complaints to citywide evidence through an alliance of community volunteers and technical expertise. Its findings were part of a larger sequence involving public health researchers, medical professionals and eventual government action; the sampling alone did not resolve the crisis.
This is not a story about bypassing scientific rigor. It is about refusing to confuse bureaucracy's lack of consensus with a lack of actionable evidence. Residents and researchers built a disciplined way to measure the problem instead of waiting indefinitely for someone else to define the next step.
Why it matters: When the stakes are real and the evidence is incomplete, a carefully designed test can be the most responsible immediate action.
Sources: