# How Innovation Happens — Lesson #6: Think Big, Start Small, Scale Fast
By 

## Article Content
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. "Think big, start small, scale fast." 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. This has been one of my core innovation mantras for years because it solves three problems at once. Thinking big forces you to look beyond today's operating issues and understand the five- or ten-year transformations that could reshape your market. Starting small lets you build experience without betting the company. Scaling fast prevents successful experiments from getting stranded in pilot mode. I once used banking as a simple example. Mobile, text-based and location-sensitive banking were clearly going to matter. The right response was not to build the final system in one giant leap. It was to identify the long-term customer shift, run small experiments that built capability, learn what worked, and then scale the successful pieces quickly. Innovation is not choosing between boldness and caution. It is sequencing them properly. 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: Write down one five-year transformation that could fundamentally alter your business. Launch one small experiment specifically designed to teach you something about it. Define the evidence that will trigger scale before the experiment begins. Explore the full How Innovation Happens series. Real-World Examples These researched examples show the lesson at work in the real world. Kessel Run: A $1 million software bet on a military whiteboard At the US Air Force's combined air operations centre in Qatar, planners once coordinated aircraft refuelling with magnets, markers, spreadsheets and a large whiteboard. Improving the entire military command-and-control system was a daunting, slow-moving acquisition challenge. A small team chose a narrower starting point: digitize the tanker-planning problem that airmen confronted every day. With early funding reported at around $1 million, the project developed Jigsaw by working alongside the actual planners and putting usable software in their hands within months. Air & Space Forces Magazine reported that a process requiring six people for about eight hours could be reduced to around three hours. The tool saved fuel and planning effort and helped demonstrate the viability of the Air Force's Kessel Run software approach. An official Air Force acquisition report later described fuel savings far beyond the initial software cost, and NATO subsequently adopted the application. The ambition was substantial: change the way critical military software is produced. The starting point was remarkably specific: one whiteboard, one painful workflow, one tool. The scaling happened because the limited experiment produced real evidence that a different delivery model could work. Why it matters: A large transformation becomes believable when a small, well-chosen experiment removes a concrete problem people face every day. Sources: India UPI: A small payment interface that became national infrastructure India did not need another isolated payment application. It needed a way for existing banks, new consumer apps and merchants to move money across institutional boundaries. In April 2016, the National Payments Corporation of India piloted the Unified Payments Interface with 21 participating banks. The interface allowed payment requests and transfers to work through a common infrastructure, rather than relying on every company to build its own incompatible network. A public launch followed later in 2016, with more consumer-facing applications arriving as the system developed. The national ambition was large, but implementation came through a bounded platform, bank integrations and successive additions. By the 2025–26 financial year, Indian government figures reported more than 240 billion UPI transactions, although official historical summaries differ slightly about initial transaction counts. The numbers are extraordinary, but the transferable lesson is architectural. India made it possible for thousands of businesses and services to scale on top of a common standard without waiting for every future use case to be specified in 2016. The infrastructure started as a practical, technically constrained arrangement and grew through participation, standards and trust. Why it matters: The most scalable ideas often begin with a narrow capability that makes many other people's experiments possible. Sources:

---
Source: https://jimcarroll.com/2026/10/how-innovation-happens-lesson-006/