Innovation gets described, in most business writing, as though it arrives in sudden, dramatic leaps \u2014 a breakthrough product, a radical new strategy, a moment of inspired genius. In practice, a large share of genuinely valuable innovation looks much less dramatic than that. It starts as a small, easy-to-dismiss idea, survives an early period of scepticism or indifference, gets tested in some modest way, and only becomes recognisable as “innovation” well after the fact, once its cumulative impact has become clear.<\/p>\n
This distinction matters because organisations that wait for the dramatic breakthrough often miss the much larger volume of value sitting in small, incremental ideas \u2014 the kind that rarely get proposed at all in a culture that only recognises and rewards the spectacular.<\/p>\n
A small, incremental idea has a specific disadvantage compared to a dramatic one: it’s easy to dismiss as not worth the effort. “We could save fifteen minutes a week by changing this step” doesn’t generate the same enthusiasm as “we could transform the entire product line” \u2014 even though, multiplied across a team and sustained over a year, the small idea might deliver more actual value.<\/p>\n
This bias toward the dramatic isn’t irrational exactly, but it does mean organisations systematically under-invest in the kind of incremental improvement that, cumulatively, often matters more than the occasional genuine breakthrough.<\/p>\n
Make small ideas explicitly welcome, not just big ones.<\/strong> If the only ideas that get real attention are the ambitious, high-visibility ones, people will rationally stop proposing the smaller, more modest improvements that are actually easier to test and implement.<\/p>\n Lower the bar for testing an idea.<\/strong> A significant amount of incremental innovation dies not because the idea was bad, but because testing it felt like it required more process and approval than the idea’s modest scale actually warranted. Making it genuinely easy to try a small change on a small scale \u2014 without a lengthy approval process \u2014 lets far more ideas actually get tested.<\/p>\n Treat a failed small test as information, not a setback.<\/strong> Because small ideas are, by definition, low-stakes, they’re an ideal way to build a genuine culture of experimentation \u2014 testing something, learning from the result whether it worked or not, and moving on quickly, without the heavy weight that surrounds a failed large-scale initiative.<\/p>\n Look specifically at the edges of the work, not just the centre.<\/strong> People closest to the day-to-day details of a process \u2014 the actual mechanics of how something gets done \u2014 often notice small inefficiencies and improvement opportunities that leadership, working at a higher level of abstraction, simply doesn’t see.<\/p>\n Compound small wins deliberately.<\/strong> A single small improvement rarely transforms anything on its own. The genuine value shows up when small improvements accumulate consistently over time \u2014 which requires actively tracking and building on them, rather than treating each one as an isolated, forgotten event.<\/p>\n Give credit specifically for small contributions, not just large ones.<\/strong> If recognition only ever goes to dramatic, high-visibility achievements, the much larger pool of people quietly contributing smaller, steady improvements gets no signal that their contribution matters, which reduces the likelihood they’ll keep offering it.<\/p>\n In fast-moving, resource-constrained environments, the appetite for a single, high-risk, high-reward breakthrough is often limited \u2014 there simply isn’t the runway to bet everything on one big idea. In those settings, a steady accumulation of smaller, well-tested improvements is often both the more realistic and the more sustainable path to meaningful innovation, even though it’s less exciting to describe.<\/p>\n A team lead notices that her team rarely proposes new ideas, despite being full of experienced, capable people. Reviewing recent history, she realises the only ideas that ever got serious attention were large, ambitious proposals \u2014 and several smaller, genuinely useful suggestions had quietly been dismissed as “not worth a full proposal,” discouraging people from raising anything less than a major initiative.<\/p>\n She introduces a lightweight way to propose and quickly test small changes \u2014 no formal proposal required, just a short conversation and a small-scale trial. Within a couple of months, several modest process changes have been tested, and two have been adopted permanently, delivering meaningful, if unglamorous, time savings across the team. None of them would have qualified as a “big idea” under the old system. Collectively, they add up to more value than the team’s last several ambitious, ultimately unrealised proposals combined.<\/p>\n Only recognising and rewarding dramatic ideas.<\/strong> This teaches people to either withhold smaller, genuinely useful ideas or inflate them into something more ambitious than the situation actually warrants.<\/p>\n Requiring the same level of approval for small tests as for large initiatives.<\/strong> Heavy process for low-stakes experimentation kills far more good small ideas than it protects against bad ones.<\/p>\n Treating a failed small experiment as a setback rather than information.<\/strong> This discourages the very experimentation that produces the eventual successes.<\/p>\n Failing to track and compound small wins over time.<\/strong> Without deliberate tracking, the cumulative value of many small improvements is easy to lose sight of, which undersells the genuine impact of an incremental-innovation culture.<\/p>\n Waiting for the next big breakthrough idea means missing the much larger, steadier stream of value available in small, incremental improvements \u2014 the kind that rarely feel significant individually but compound meaningfully over time. Building a genuine habit of welcoming, testing, and recognising small ideas, rather than reserving attention for the occasional dramatic one, is one of the more reliable, sustainable paths to a genuinely innovative team culture.<\/p>\n Is incremental innovation as valuable as breakthrough innovation?<\/strong> How can I make it easier for my team to propose small ideas?<\/strong> Should failed small experiments be treated the same as failed large initiatives?<\/strong> Why do organisations tend to under-invest in small ideas?<\/strong> How do I keep track of the cumulative impact of many small improvements?<\/strong> Does building an incremental-innovation culture mean giving up on bigger, more ambitious ideas?<\/strong> Most breakthrough ideas didn’t start as breakthroughs. They started small, survived early skepticism, and got the chance to be tested. Here’s how to build that habit.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[7,19],"tags":[50,9,20,15],"class_list":["post-2034","post","type-post","status-publish","format-standard","hentry","category-leadership","category-management-skills","tag-innovation","tag-leadership","tag-management-skills","tag-productivity"],"yoast_head":"\nWhy This Matters More in Some Environments Than Others<\/h2>\n
A Practical Scenario<\/h2>\n
Common Mistakes<\/h2>\n
Action Steps<\/h2>\n
\n
Key Takeaways<\/h2>\n
\n
Conclusion<\/h2>\n
Frequently Asked Questions<\/h2>\n
\nIn cumulative terms, often more so \u2014 a steady stream of small, well-tested improvements frequently delivers more total value over time than the occasional, high-risk breakthrough attempt.<\/p>\n
\nLower the process required to test a small-scale change, and make clear that modest, incremental ideas are genuinely welcome, not just ambitious ones.<\/p>\n
\nNo \u2014 a failed small, low-stakes experiment should be treated as useful information gathered cheaply, which is a very different thing from a failed large-scale initiative with significant resources invested.<\/p>\n
\nSmall ideas are often less exciting to propose and champion than dramatic ones, which means they’re easy to overlook or dismiss even when their cumulative value would be substantial.<\/p>\n
\nDeliberately track and periodically review small changes and their effects, rather than treating each one as an isolated, quickly forgotten event.<\/p>\n
\nNo \u2014 the two aren’t mutually exclusive. A healthy innovation culture makes room for both, rather than treating incremental and breakthrough innovation as competing priorities.<\/p>\n","protected":false},"excerpt":{"rendered":"