President Volodymyr Zelensky dismissed Defense Minister Mykhailo Fedorov on July 16, 2026, as part of a broader government reshuffle that saw the Verkhovna Rada send Prime Minister Yulia Svyrydenko's cabinet into resignation. Fedorov, previously Ukraine's digital transformation minister and creator of the Diia e-government platform, had held the defense portfolio for just over six months — the sixth person to run the ministry since Russia's 2022 invasion (The Record). Protesters carrying signs reading "We Want to Fight With Drones, Not People" gathered in Kyiv, Lviv and Odesa the same week, an unusual public reaction to a cabinet reshuffle in a country at war (The Record).
What Fedorov actually built
The substance behind the protests is traceable and specific. In March 2026, Fedorov signed an order restructuring how the ministry buys drones: instead of officials picking suppliers, demand would be "generated automatically based on high-quality battlefield data" pulled from five systems — ePoints (combat-effectiveness scoring), DOT-Chain and Brave1 Market (unit-level procurement), and DELTA and Mission Control (targeting synchronization). Eighty percent of the budget now flows to solutions with proven frontline performance; twenty percent is reserved for testing new technology (Ministry of Defence of Ukraine). The ministry credits the broader push with lifting drone-interception rates from 83% to 91% and cruise-missile interception from 47% to 87% during Fedorov's tenure, alongside a first-ever competitive tender for 5,000 tactical pickup trucks (Ministry of Defence of Ukraine). Ukraine's Defense Procurement Agency contracted roughly $8 billion in drones in the first half of 2026 alone — double the same period a year earlier — with in-stock systems reaching front-line units in as little as nine days through the DOT-Chain marketplace (Euromaidan Press).
The stated reason, and the real one
Officially, Zelensky attributed the reshuffle to two things: a diverging strategic vision between Fedorov and Commander-in-Chief Oleksandr Syrskyi, and the ministry making procurement decisions "at their own discretion" rather than through requests routed via the General Staff. Fedorov's own account, delivered at a combative farewell press conference, inverted the framing — he accused Syrskyi of blocking modernization initiatives outright and said the general chose to "split the country" rather than negotiate reform (Euronews). Analysts have also floated a less flattering explanation for Zelensky: internal polling reportedly showed Fedorov with a wider net-trust margin than the president himself, a fact that, if accurate, would make a popular reformer a political liability independent of any procurement dispute (Euromaidan Press).
Steelmanning the chain-of-command objection
There is a real institutional argument behind Zelensky's stated rationale, and it deserves to be taken seriously rather than dismissed as bureaucratic jealousy. A ministry that generates procurement demand from its own battlefield-data platforms, bypassing formal requisitions from the General Staff, risks duplicating systems, fielding equipment incompatible with existing command-and-control doctrine, or creating accountability gaps in a $16-billion-a-year weapons budget. Militaries fight better with unified logistics chains than with two centers of procurement authority pulling in different directions, and a wartime government has legitimate reasons to prize predictability in command structure over the disruptive pace of a reform-minded outsider. That case is not manufactured.
Why the personnel churn is still the bigger risk
But the objection proves too much if it treats every fast, data-driven procurement decision as a discipline problem to be centralized away. The interception-rate gains and the nine-day delivery cycle exist precisely because Fedorov's team built infrastructure — DOT-Chain, ePoints, DELTA integration — that routes around exactly the kind of slow, requisition-based bureaucracy Ukraine's pre-2022 defense ministry was infamous for. That infrastructure is software and process, not a person; it should have outlasted any one minister's tenure. Instead, Fedorov becomes at least the sixth defense minister since the full-scale invasion began, and each transition carries real risk that platforms tied to a departing minister's political capital lose institutional priority, budget, or staff. Ukraine's wider digital-battlefield resilience already has a well-documented single point of failure in Starlink connectivity, which Russian jamming systems like Volna Kupol Garant have begun to target at meaningful scale (Meduza, citing Reuters). Adding a second point of fragility — procurement and battlefield-data systems whose survival depends on which minister currently holds favor — compounds a risk Ukraine can least afford three and a half years into a full-scale war. The proportionate fix is not to re-litigate reform versus hierarchy with every cabinet reshuffle, but to write Fedorov's procurement architecture into statute or standing ministry procedure so it survives him — the same logic that led Estonia to protect its e-government backbone as critical infrastructure independent of any single agency head. Ukraine's allies supplying money and matériel have a direct stake in that continuity, since the systems being protected are the ones stretching every dollar of Western aid further at the front.