Innovation is hard.
You assemble a smart, motivated team brimming with ideas and ambition, and you set them loose on a bold new project. Energy is high, expectations are great, and the first steps move quickly.
Then reality hits: a part is delayed, an approval drags on, a quote takes weeks to return. Progress stalls. The team shifts focus, juggling multiple half-finished initiatives, none crossing the finish line. Enthusiasm gives way to frustration, morale erodes, and your burn rate climbs—without a tangible outcome to show.
The culprit is not poor ideas or lack of effort. It’s latency. Every delay, no matter how small, siphons momentum. What starts as a sprint becomes a crawl. Multiply these delays across a team, and you get the familiar picture of engineers on a hamster wheel: always busy, but never moving forward.
Innovation doesn’t progress in straight lines; it moves in threads. You can’t Gantt Chart your way to the end when unknowns are constantly emerging. Each thread must advance steadily, or it tangles and stalls. When organizations spread effort across too many stalled threads, apparent progress is just diffusion of energy. The solution is clear: maintain velocity.
Velocity is not recklessness. It’s deliberate structuring so projects move continuously, without waiting for bottlenecks. That means scoping projects into the smallest executable pieces and exposing problems early. A stripped-down system that runs end-to-end—even roughly—is far more valuable than polished components never tested together. Early integration surfaces “unknown unknowns” fast, enabling pivoting before months of work are wasted.
Equally crucial is mindset. Innovation thrives on iteration—and iteration means failure, repeatedly. The trap is seeing each failure as proof the team isn’t capable or the idea isn’t strong enough. In reality, each misstep is fuel: data points guiding you toward clarity. Teams that treat failure with curiosity instead of shame maintain energy, keeping progress rhythmic rather than stalled.
Human factors go beyond resilience. Projects are not tasks—they’re people. Ask first: Who needs to be involved? Map beneficiaries, knowledge holders, and decision-makers up front.
Projects embraced by stakeholders build momentum; projects lacking buy-in generate resistance. Motivation itself is a form of velocity. Big, distant goals inspire on paper but demoralize in practice. Near-term wins, celebrated daily, create a rhythm of progress: success generates energy, energy fuels persistence, persistence keeps threads alive through setbacks.
Grit alone doesn’t win. Tenacity without adaptability is stubbornness. Innovation demands adjusting course without losing sight of the destination. Teams succeed not by brute force but by flexing intelligently around obstacles.
The urgency of velocity has never been greater. Startups race against shrinking runways, corporations reinvent under relentless pressure, governments are expected to operate at speeds once reserved for private ventures. In all these contexts, latency is lethal: every day delayed is payroll spent, opportunities lost, competitive ground ceded.
Designing projects around velocity transforms outcomes. Engineers feel engaged instead of drained. Threads close instead of multiplying. Burn rates stabilize. Creativity flourishes because the cycle of test, fail, learn, and adapt keeps ideas alive. The organization moves with purpose rather than treading water.
Innovation is not perfect planning. It’s building the conditions for momentum. The DNA of breakthrough projects is simple but disciplined: eliminate latency, structure work for continuous forward motion, and embrace iteration as a human process of discovery. Do this, and projects won’t just survive—they’ll thrive at the velocity today’s world demands.
As Clayton Christensen famously noted in The Innovator’s Dilemma, “disruption is most easily executed by those who move fast and learn fast”—but only if they avoid the drag of organizational latency.
