The most dangerous thing about innovation conversations is this: everyone is waiting for the big idea. Managers search for a ‘transformative move’ in meetings, consultants fill their slides with ‘radical redesign’ proposals, and meanwhile the small, measurable improvement opportunities inside the company get buried under the weight of big ambition. In the final quarter of last year, I worked with a mid-sized food manufacturer in Konya — 312 employees, established regional brand, solid export relationships. The factory manager told me early on that they needed ‘a real innovation’ before committing to a large ERP investment. Yet during the plant tour that same week, I noticed that three consecutive shift groups were independently encountering the same equipment fault, with no one reading the previous shift’s observations. A simple information-sharing habit could have prevented three working days of accumulated loss. That is where innovation actually begins — not in the big project.This tension is a defining feature of Turkey’s business landscape. On one side stands the ‘big idea’ school: innovation only counts when it involves a new product, a fundamentally new business model, or a major technology investment. On the other stands the ‘small steps’ school: competitive advantage accumulates through doing things slightly better every single day. Both views are partially correct — but in the Turkish SME context, I find the second is almost never practiced, while the first rarely returns the investment it consumes. The core problem is this: the pursuit of the big idea actively suppresses the discipline of small improvement. These two approaches do not have to be mutually exclusive — but sequence is everything.The kaizen philosophy, which spread from Toyota’s production system to global management thinking, treats ‘continuous, incremental improvement’ as a cultural matter rather than a project. In Turkey, this concept is most commonly encountered while preparing a quality management certification. Once the certificate is filed, kaizen tends to get filed with it. Yet kaizen’s essence is not documentation — it is behavior. It is the psychological safety that allows an employee to ask ‘why does this step happen here?’ It is the decision speed that allows a manager to say ‘good catch, let’s try it.’ It is the feedback loop through which outcomes are measured and shared. None of this requires a large budget. But all of it requires management maturity — and this remains the scarcest resource in Turkish SMEs.Back to the food manufacturer in Konya. Together with the factory manager, we asked one simple question: what is the most expensive, preventable, recurring problem in the last six months? The answer came from shift supervisors within two hours: the shift handover process. Every incoming shift began work without any written record of equipment status, pending work orders, or quality observations from the previous shift. Verbal handovers happened under time pressure, and more than half of critical information was lost in translation. The solution? A paper-based, standardised shift handover form. It was implemented in three weeks. By the end of the eleventh week, equipment-related downtime had declined noticeably compared to the previous quarter — by roughly one third, according to the factory manager’s own tracking. No software investment. No consulting contract. No ‘digital transformation’ roadmap. Who could argue this is not innovation?Now let us not dismiss the legitimate counter-argument: small improvements may not be enough. If a technology-driven competitor is entering your sector, no matter how well your shift handovers are documented, you will not defend your competitive position through process notes alone. This is real. In food manufacturing, supplier traceability, cold chain management, and shelf-life tracking increasingly require digital infrastructure. By 2018, major retail chains are beginning to impose data-sharing obligations on their suppliers — and that pressure cannot be answered with small steps alone. So the right question is not ‘big or small?’ but rather: ‘Can a large investment succeed without a small-improvement discipline already in place?’ My answer is clear: no. Installing software in a company without process discipline is like adding floors to a building with an unstable foundation. The improvement culture must come first.So where does a manager start on Monday morning? Three concrete steps. First: spend one month logging recurring problems — who, when, which process, what kind of breakdown. An unwritten problem is an unsolvable problem; this has not changed in 2018. Second: from that list, select the single most frequent and most time-consuming issue, assign a responsible team leader, and set a measurable improvement target for six weeks. Third: share the outcome — successful or not — with the entire team. This sharing culture builds something far more durable than any major innovation project: a learning organisation. And a learning organisation compounds its advantage every quarter, regardless of what technology it is running.At the end of our engagement, the factory manager in Konya said something that stayed with me: ‘We bought the ERP, but what I really learned is that people being able to ask each other the right question is worth just as much as any system.’ That sentence carries the core of the innovation debate. The big idea may come one day — or it may not. But every big idea that arrives before small-improvement discipline is in place will dissolve at the implementation layer. Count how many small improvement suggestions your team has made, how many you actually tested, and how many you measured. That number will give you a more honest read of your organisation’s true innovation capacity than any consulting report on your shelf.
This article was originally published in Turkish by Gökhan MERCANOĞLU on January 20, 2018. The English edition has been reviewed and edited by the author.