Building a Future of Scalable Innovation: Inside Skapa’s Flywheel Approach

Saab’s Skapa initiative has taken on this challenge, developing what we call the Skapa Innovation Flywheel. But what does this really mean, and how does it actually work to deliver better solutions?

The Flywheel is more than just a clever diagram of circles and arrows. At its core, it's a dynamic process that transforms problems into scalable solutions, involving multiple actors from research and development teams to university startups. With an emphasis on collaboration, the Flywheel enables us to respond quickly to operational needs and continually improve on what we deliver.

Imagine, Create, Iterate, Intersect

The first key to understanding the Flywheel is recognizing its cyclic nature. It doesn’t follow a linear path of development like traditional R&D models. Instead, it begins by identifying problems directly from end-users, i.e. operators in the field. These problems are the friction points that the Flywheel is designed to resolve. From there it kicks into motion, fuelled by the phases of Imagine, Create, Iterate and Intersect.

1. Imagine: This stage taps into the creative potential of our engineers, external partners and stakeholders. We always begin with the problem. With a dedicated and diverse team of innovators, engineers and doers we look at the problem from every angle.   We involve the problem holders, the end users in this process.​ Then we imagine novel ways to solve that problem, informed by the past, but not constrained by it. During the imagine phase, diversity of experience and perspective is our superpower and our most valuable piece of tech, is the whiteboard. ​
2. Create: We then translate those ideas and sketches from our whiteboard to a minimum viable product (MVP) designed to solve that problem​. We leverage a ‘team of teams’ approach across the triple-helix to do this – where multiple teams from different disciplines work on the problem together, bringing diverse perspectives to the larger team. This is the personification of Skapa, which in Swedish means “to create”. ​
   
   
3. Iterate: We take that MVP and get it in the hands of the end user in the operational environment, and against real problems we test, iterate and improve - fast. ​ We want to take our product to the point of failure then push past, because truly new capability is on the other side of failure.
4. Intersect: Informed and improved by iterating with the end user, we transition the MVP to a product that can solve their problems at scale. 

A More Efficient Path to Scalable Solutions

What makes this Flywheel different from traditional methods of product development is the constant loop of feedback between the different actors. We aren’t just aiming to solve problems; we are iterating continuously until those problems are met with effective, scalable solutions. Whether through collaboration with university startups, internal R&D, or direct feedback from the operators themselves, the Flywheel keeps innovation in motion—constantly evolving and responding to new information.

For example, imagine a scenario where operators in a naval environment express concerns about radar limitations in adverse weather. With the Flywheel, this issue is fed directly into the system. University partners might explore new ways of integrating AI into radar technology, while our internal R&D team works on optimizing the hardware for harsh environments. As we test and iterate, we receive ongoing feedback from operators, ensuring that the end solution is practical and fit for purpose.

Why It Matters: Speed and Relevance

The ultimate aim of the Innovation Flywheel is clear: to get the best technology into the hands of operators as quickly as possible. In defense and security, the consequences of lagging behind are severe. Delays in technology adoption could mean missed opportunities, security vulnerabilities or operational inefficiencies. The Flywheel approach mitigates this risk by accelerating the development process and keeping the focus squarely on the end-user.

What’s more, this continuous feedback loop ensures that the solutions we develop are not only innovative but also relevant to the needs of those using them. It prevents us from falling into the trap of developing technology for technology’s sake. Instead, every step in the Flywheel is designed to address specific problems, ensuring that we’re always aligned with real-world demands.

Building a Bridge Between Innovators and Operators

A key strength of this model is its ability to bridge the gap between innovators and operators. In the past, these two groups often worked in silos. Innovators would create, while operators would use, with little interaction between the two. The Flywheel changes this by making operators an integral part of the innovation process. Their problems, feedback and insights guide every phase, ensuring that the technology being developed is exactly what they need to stay ahead in rapidly evolving environments.

Looking Ahead: Scalability and Future Impact

While the Flywheel is already showing results, the potential for future scalability is where it truly shines. The iterative nature of the process means that as technologies evolve and new problems emerge, the Flywheel can accommodate and accelerate solutions for a wider range of industries and sectors. It’s not just limited to defense or naval operations. The same principles can be applied to energy infrastructure, civil security or any area where technology and problem-solving intersect.

In the end, the Flywheel is about creating a culture of constant innovation—a perpetual motion machine that responds to problems in real-time, incorporates diverse perspectives and iterates until the best solution is found. It’s about making sure that our end-users, the operators, always have the best tools at their disposal, keeping them ready and resilient in an unpredictable world.

By leveraging this innovation model, Skapa isn’t just building better products—we’re building better futures.