At this stage, the discussion reaches its natural conclusion. After analysing the operational environment, reviewing field experiences, and proposing structural and procedural adaptations, a final question remains: how do we transform what we have observed into doctrine?

This is not a trivial step. It is, in many ways, the most difficult one. The transition from battlefield innovation to doctrinal development is not automatic. It requires a structured process capable of translating experience into standardized knowledge, and ultimately into training and operational practice. The framework presented highlights that this process is already defined, but not always fully exploited.

At its core, the process follows a continuous cycle: experimentation, standardization, training, and lessons learned, all feeding back into each other. This cycle is not theoretical. It represents the mechanism through which NATO adapts to changes in the operational environment.

However, the effectiveness of this process, in a Mountainous environment, depends on one critical condition: it must remain connected to the field.

One of the key insights emerging from the discussion is that innovation cannot be developed in isolation. Testing, validation, and refinement must involve operational units at every stage. Individual testing may confirm that a system works. Battalion-level experimentation demonstrates whether it adds tactical value. Only at the integration level does it become clear whether it can function within a broader system, interacting with other capabilities and contributing to operational outcomes.

This highlights a recurring issue. Too often, innovation is treated as a technical problem, focused on the performance of individual systems. In reality, the challenge lies in integration within a system of systems, where interfaces, coordination, and information flow become decisive.

The example of logistics experimentation further illustrates this point. Comparing traditional solutions, such as cableways, with emerging drone-based approaches shows that no single solution is universally superior. Each brings advantages and limitations, depending on terrain, weather, and operational constraints. What matters is not the platform itself, but the ability to combine different solutions into a coherent system, adapted to the environment.

This reinforces a broader principle: innovation is not about replacing existing capabilities, but about reconfiguring how they are combined and employed.

At the same time, the discussion highlights the importance of operating across all levels of warfare. Tactical innovation, such as the use of drones at company level, must be connected to operational and strategic frameworks. Without this connection, local adaptations remain isolated and cannot be scaled or standardized. This creates a natural tension between decentralization and coherence.

On one hand, adaptation must occur at the lowest levels, where the problem is experienced directly. On the other hand, doctrine requires consistency, interoperability, and a shared understanding across the Alliance. Bridging this gap requires a process that allows innovation to emerge from below, while ensuring that it is captured, analysed, and translated into doctrine.

This is precisely the role of organizations such as MWCOE.

The workshop itself can be seen as part of this process. It represents a point within the broader cycle, where observations, experiences, and ideas are collected and refined. However, its value depends on what follows. Without a deliberate effort to transform these insights into structured outputs—doctrinal proposals, training adaptations, and standardized procedures—the knowledge generated risks remaining fragmented.