Fedorov at the Ministry of Defense: an attempt to turn war into a system of speed

The appointment of Mykhailo Fedorov as Minister of Defense was not merely a personnel rotation, but a signal of a change in the very logic of managing the war. This is not about yet another classical administrator for a large ministry. It is about an attempt to bring the logic of the digital state into the Ministry of Defense, where the main currency is not only resources, but also the speed of data processing, decision-making, and delivery of results to the front.

That is why Fedorov today looks not so much like a political minister as an operational architect of a new model of war. At the center of his approach is an attempt to turn the Ministry of Defense into a system driven by data. This means moving away from manual distribution, multi-stage paper bureaucracy, and slow approval of decisions. Instead, a model is being built in which logistics, procurement, drone distribution, assessment of combat effect, and subsequent contracts are tied into a single cycle, where decisive importance belongs to the speed with which information moves from the battlefield to the manufacturer and back to the unit.

In practical terms, this means automating logistics through SAP, abandoning the manual distribution of part of the resources, using combat data to determine real demand for equipment, and trying to shorten the path from battlefield use to state contract. If the previous model of defense management was largely measured by diplomatic packages, intergovernmental agreements, and major institutional decisions, Fedorov is sharply shifting the emphasis to the speed of the cycle: data, decision, contract, delivery, feedback from the front. This is where his main difference from his predecessors lies.

A key element of this model has become Brave1. For Fedorov, this is not just a platform for startups and not a symbolic showcase of defense innovation, but an attempt to decentralize technological development and move it out of the slow state machine into a fast circuit of testing, codification, and procurement. That is why Brave1 serves as a one-stop window for military tech developers who previously often got lost among ministries, procedures, and incompatible requirements. The task now is to ensure that innovation ceases to be the accidental success of a single team and becomes part of a state infrastructure for scaling.

This directly affects the change in Ukraine’s military strategy as well. Ukraine looks less and less like an army preparing a major summer offensive in the logic of 2023, and more and more like a system of active defense and mathematically calculated attrition of the enemy. The emphasis is not on a spectacular mechanized breakthrough, but on creating a guaranteed kill zone through drones, on shifting part of the risk from infantry to machines, on systematic strikes against Russian logistics and oil refining infrastructure, and on isolating the enemy’s critically important hubs. That is why long-range strike drones, ground robotic systems for logistics, mining, and evacuation, as well as the broader concept of a technological blockade of the Russian war economy, are coming to the forefront.

In this sense, Fedorov is no longer operating in the logic of a classical “offensive for territory,” but in the logic of attrition for the sake of changing the balance. This is less spectacular for external audiences, but much more effective in a long war where decisive importance belongs to the pace of degradation of enemy infrastructure, the enemy’s costs, and Ukraine’s ability to preserve its own human resources.

However, the romantic phase of the war of startups has already ended. In 2022 and 2023, Ukraine truly had an almost monopolistic advantage in the flexible and innovative use of commercial drones. That advantage rested on the volunteer environment, engineering improvisation, and a very short adaptation cycle. Today the situation has changed. Russia, despite all its inertia, has moved to industrial scale, standardized serial production, and mass implementation of solutions in the field of electronic warfare and reconnaissance-strike systems. Therefore, Ukraine’s advantage no longer lies in the mere fact that it has FPV drones. It lies in whether the state can turn an engineering idea into a standardized system faster than the enemy.

This is where Fedorov’s real task begins. He must carry out the transition from a war of startups to a war of factories. In other words, he must transform thousands of small teams and flexible manufacturers into several dozen powerful, scalable, and standardized defense corporations capable of producing large quantities of equipment in series. This is no longer a story about individual creative solutions, but about the industrial organization of innovation. That is why the priority becomes machine vision systems, autonomous engagement loops, AI guidance at the final stage of attack, and other tools that are supposed to neutralize Russian mass production and the effectiveness of enemy electronic warfare.

Fedorov’s logic becomes even more visible in the issue of protecting cities. Ukraine cannot indefinitely close the sky using only expensive Western interceptors. The economics of such a model simply cannot withstand a confrontation with cheap mass drones such as the Shahed. That is why the answer is being sought in a different plane. Not in the accumulation of ever more expensive batteries, but in building a new network architecture of air defense, where the main role is played by algorithms, sensors, mobile groups, mass cheaper interceptors, and local electronic warfare contours.

This is why predictive analysis systems are becoming increasingly important, systems that unite optical and acoustic sensors into a single neural network for calculating the routes of enemy UAVs. The scaling of the so-called national electronic warfare dome also fits into this architecture, meaning an echeloned system for suppressing satellite navigation around major cities and critical infrastructure. If this is translated from technical language into political language, Fedorov is trying to build the cheapest possible system of mass protection, where software, sensor networks, and the rapid integration of the private sector compensate for the lack of expensive classical air defense means.

But this is exactly where the limits of this approach begin. The biggest conflict now visible in the Ministry of Defense is the clash of two systems. On one side is the state in a smartphone, driven by data, fast, automated, and open to experimentation. On the other side is Soviet military inertia, paper culture, multi-stage approvals, and a middle layer that often sees digitalization not as a tool of efficiency but as a threat to the established order. That is why the speed that Fedorov’s team is trying to impose regularly runs into internal friction and partial sabotage.

There is an even harsher limitation. Digitalization does not replace people. Automating the register of those liable for military service, simplifying deferments, digital recruitment, and more transparent procedures reduce part of the corruption risks and speed up processes, but an app will not hold a trench. Technology can save a soldier’s life, reduce losses, and shift risk onto a machine, but the presence of trained infantry on the battlefield remains irreplaceable. And this is where Fedorov runs into the mobilization crisis that no code can eliminate.

A third limitation, no less important, is financing. Ukraine’s defense industrial potential already significantly exceeds the state’s budgetary capacity to purchase everything that local factories can produce. In other words, the problem is no longer only inventing something or even testing it quickly. The problem is having the resources to buy it, scale it, and supply it steadily to the troops. In this sense, Fedorov is facing three different tempos at once: the speed of innovation, the slowness of military bureaucracy, and the chronic limitation of money.

That is why Fedorov is not a magician who will solve the war with code. His role is far more complex. He is trying to move Ukrainian defense from the logic of political administration to the logic of networked operational management of war. He is trying to make data work faster than bureaucracy, to make algorithms strengthen artillery, to make the drone not an exception but a standard, and to make innovation cease to be an accidental success and become a system. But the success of this model will depend on whether the state can synchronize everything at once: the engineer, the factory, the commander, the budget, and the soldier on the front line. That is where Fedorov’s main test lies.