Introduction

Army's rank system was built on a simple, durable assumption: that seniority is earned by commanding soldiers. For most of the Army's history, that assumption held, because the skills that decided battles – leading under fire, manoeuvring formations, sustaining troops in the field – were skills a career of command produced. That assumption is now under a pressure it was never designed to withstand. Technical mastery – in software, data, autonomous systems and whatever technical domain follows them – has become as decisive to capability as command ever was, and it is not produced by a career of command at all.

It is produced by a career spent innovating, building, breaking, and scaling technology in industry, on a timeline unrelated to years in uniform, and that timeline is only getting shorter. Army has not resolved the tension between these two sources of seniority. It has mostly avoided noticing it.

The argument in this article is not that the Army is behind on technology. The Army constantly adapts to new equipment and tools within its existing corps and does so well. Drone operators, signals technicians, and intelligence analysts absorb new systems into established trades every year, and no one is proposing a new corps every time a new sensor or platform enters service.

The argument is narrower, and harder to dismiss. No internal training pipeline can produce deep, civilian-grown technical mastery in time, at scale, or with genuinely cutting-edge currency, and the Army has no other way to import it. A soldier who spends 20 years mastering a system is still, at the end of it, the end user of that system. They learn to employ it, adapt it, even develop a clever tactic or feature around it, but that is not the same path that leads to designing it in the first place.

That mastery is built somewhere else entirely, in the industry that develops the technology rather than the force that fields it, and no number of years in uniform turns an end user into its architect.

The Army's current answer to this gap is contracting, and the real cost of contracting never appears on the invoice. A contractor delivers what the contract specifies, then leaves with the understanding of why it was built that way, taking the judgement that should have stayed inside the institution along with them.

There is no channel for someone with that level of frontier expertise to shape how a capability develops, is implemented, is used, or evolves, because that person is never inside the institution long enough to be asked. Institutional knowledge does not accumulate, capability development stalls when the contract ends, and doctrine is written by people who only ever received the technology as a finished product. Expertise that stays inside the institution compounds on itself over years, while expertise that is rented for a task is gone before it has the chance to.

Two different problems Army is treating as one

The introduction names a tension between command and mastery. The first problem is operational competency: teaching soldiers to use new technology. Army solves this through existing corps, existing training pipelines, and existing career structures. A soldier learns to fly a drone, employ an AI-enabled targeting tool, or operate a new-networked system, and does so inside the trade they already belong to.

The second problem is frontier technical mastery, the kind built over 10 to 20 years at the leading edge of a technical domain, by people designing the systems rather than operating them, and understanding their failure modes at a level no short course can teach. A fitter armourer can strip, repair, and return a rifle to specification. That is not the same expertise as the engineer who designed its rifling for accuracy at range. This is not something an internal training pipeline produces, however well that pipeline adapts operationally. It is grown in industry over a career, and it cannot be compressed into a posting.

Someone reading this could reasonably object that Army already uses drones and artificial intelligence across multiple corps, so there is no gap to speak of. However, this argument misses the point. A unit that fields a new loitering munition learns to employ it in a strike. That is not the same as understanding the targeting algorithm well enough to know when and why it will fail, or how to continuously adapt it to remain effective in contact with the enemy.

The distinction matters most when Army has to judge something it has not seen before. When Evelyn Owen brought his prototype submachine gun to ordnance officers in 1939, they were competent users of every weapon then in service, and that competence gave them no way to assess a class of weapon Army did not yet employ.

Owen was told Army was not interested. His design reached production only because a manager at Lysaght's recognised what he was looking at and had the standing to push it past Army objections to the Minister. Trials in 1941 found the Owen more reliable than both the Sten and the Thompson, and it stayed in Australian service until 1971. Those officers were not poorly trained. They were trained to employ weapons, which is what Army's pipeline is built to produce, and nothing in it equipped them to recognise what Owen's design might become. He enlisted the following year of his own accord and served as a private while the design went nowhere, until a civilian manufacturer saw the potential and had the standing to act on it.

What cases from the United States military actually prove

Two recent developments in the United States military illustrate this distinction precisely, and both were built within about 12 months of each other.

The Army Software Factory case began as a retention failure, named as exactly that by the officer who fixed it. Howard Brewington, deputy director of the Mission Command Center of Excellence and a 21-year infantry veteran, described a concerted, high-priority effort to stop the Army, in his words, “haemorrhaging talent”.

Soldiers with software skills had no way to remain in the field and progress, so the Army was losing them to industry. In response, Brewington's team stood up a new specialty, Functional Area 28, Software Operations, in the fourth quarter of fiscal year 2025, and compressed the traditional transition from non-commissioned officer to warrant officer from up to 2 years down to 4 months.

This was not a response to drone or AI use inside operational units. It was a recognition that the Army's own training pipeline could not produce software systems mastery fast enough to keep the people who already had it.

Detachment 201 went further still. The Army stood up the unit, formally the Executive Innovation Corps, in June 2025, directly commissioning four technology executives as lieutenant colonels: Shyam Sankar of Palantir, Andrew Bosworth of Meta, and Kevin Weil and Bob McGrew, both formerly of OpenAI.

In June 2026, Army Secretary Daniel Driscoll commissioned a second cohort of three more consisting of Dane Knecht of Cloudflare, Sam Pullara of Sutter Hill Ventures, and Serkan Piantino, co-founder of Facebook AI Research. All entered at lieutenant colonel, a rank that typically takes a career officer more than a decade to reach, on the strength of at least 10 years of civilian technology experience and a demonstrated record of scaling organisations.

Over the same period, the Army cut its direct commissioning timeline from more than 18 months to about six. The US Navy followed within days, announcing its own Navy Innovation Unit on 12 June 2026, building on a Navy Innovation Center it had already run since 2022 and modelled explicitly on Detachment 201 and the Marine Corps' own Marine Innovation Unit, active since 2023.

Navy officers under the new pathway will be commissioned anywhere from ensign to commander, a rank that normally takes 15 to 20 years to reach, while keeping their civilian jobs. Within days of applications opening, the Navy had received more than 200, many from senior executives at major technology firms.

A sceptic might argue this is simply a US response to a specific skills shortage, not evidence of a structural problem elsewhere. But three services, independently, building three separate entry mechanisms in the same year is not a coincidence; it is a pattern, and the pattern is consistent. Deep mastery cannot be grown in time, so it has to be imported permanently rather than contracted temporarily.

Army's existing precedent, and its limit

Army does not need to invent this idea from nothing. It already runs the Specialist Service Corps model for legal, medical, nursing, and chaplaincy – professions where a surgeon or a barrister enters uniform at a rank that reflects their civilian standing, not at the bottom of the ladder. A senior surgeon or an experienced barrister with a decade or more in practice can be commissioned directly as a major or a lieutenant colonel, on the strength of their civilian record alone, without ever having worn a uniform before. But every one of these is static, a fixed corps for a fixed, long stable profession, built once and never designed to be extended further.

Autonomous systems, machine learning, and networked warfare are already reshaping how the Army will fight, and the doctrine covering them is being written now, by people who likely have only ever used the technology rather than built it. If the Army waits for these domains of expertise to settle into something recognisable as a profession, the doctrine will be set, and the capability decisions made long before the corps exists to inform them. The principal Army already accepts that civilian mastery can outrank years in uniform, regardless of the technical domain, is still true. A shifting technical landscape calls for a mechanism flexible enough to survive the shifts, not for no mechanism at all.

Why Army resists what Navy and Air Force already accept

Navy and Air Force are platform-centric services. A ship or an aircraft is itself a complex technical system, and both services have always had to separate command authority from technical mastery as separate qualifications rather than a single ladder. Both maintain engineering and technical officer streams in which progression to senior rank rests on technical and support responsibility rather than on command appointments. Navy applies the same logic at the institutional level, upgrading its Systems Commander appointment, which carries responsibility for the fleet's training, engineering and logistics, from commodore to rear admiral in 2008. Rank built on mastery rather than command is not a new idea to either service, it is how their engineering and technical branches have always worked.

Army carries no equivalent structural habit. Its rank system is built around, and remains culturally centred on, command of soldiers in the field. Seniority is earned by leading people, not by mastering a system. An obvious objection here is that Army already has plenty of technical corps, in engineering, signals and intelligence, alongside the Capability and Project Management pathway, and clearly values technical expertise.

It does, but valuing a technical trade is not the same as recognising frontier level civilian mastery at commensurate rank, and capability and project management is a discipline of schedule, cost, risk, and requirements that can be performed well by someone who has never built the technology being acquired. Army's technical corps still require entry and progression through the standard command linked rank structure, unlike the technical streams in Navy and Air Force, where seniority can be built on technical and engineering responsibility without command appointments entering the equation.

The proposal, tested against the practical objection

The proposal is a generalised, standing Specialist Service Officer and Senior Non-Commissioned Officer pathway, built on the same reservist model US Detachment 201 and the US Navy Innovation Unit already use. These officers do not leave their civilian careers to take up the commission, they hold it alongside them, drilling and contributing part time while remaining inside the institution year after year rather than for the length of a single engagement. The mechanism recognises and commissions deep expertise at the rank that expertise warrants, in whatever domain currently demands it, rather than a corps built around any single named technology, and rather than a full-time uniformed workforce Army would need to recruit, train, and fund from scratch.

The hardest objection should be addressed first rather than saved for last. If deep expertise is this rare and valuable, would the civilian sector not simply outbid Army for it regardless of rank offered? The question assumes a trade-off that a reservist commission does not require. Detachment 201 and the Navy Innovation Unit do not compete against industry salaries, because their officers never leave those salaries behind, they keep their civilian jobs and are commissioned to serve alongside them. What Army is offering is not pay, it is influence and self-actualisation. A lieutenant, however expert, has no real standing to shape a decision, and will be heard politely and then overlooked. A lieutenant colonel sits inside the room where the decision is made and is heard as a matter of course rather than by exception. A rolling contract cannot offer that either, a contractor can be highly skilled and still have no seat at the table where the judgement gets formed.

A related objection follows naturally, that contracting already solves the cost problem, so why add the complexity of a new rank pathway. Contracting solves access for the length of a single work order, then that access ends. New and innovative ideas are not necessarily shared freely by contractor but reserved for sale as future business. A reservist commission solves something contracting structurally cannot, a standing place inside the institution that persists across postings, projects and years, the same access Detachment 201 was explicitly built to provide, sometimes described as getting expertise inside the tent rather than calling it in from outside. That channel is what lets a capability's development, implementation, and evolution stay shaped by the same judgement over time, rather than being handed back to a contractor with no standing reason to return.

Addressing the remaining objections

A handful of further objections deserve a direct answer rather than being left implicit.

• Does this dilute command authority? No. Specialist Service Officers already do not hold troop command under the existing legal and medical model, and generally only exercise Technical Control (TECHCON), so this proposal extends an existing, accepted boundary rather than creating a new one.
• Does this risk conflicts of interest, particularly around procurement? Yes, and the risk is not hypothetical. Detachment 201 officers are governed by a Joint Ethics Regulation framework requiring mandatory confidential financial disclosure, annual ethics training, legal review of each work assignment, and mandatory recusal from any matter touching their own financial interests. A governance framework does not remove the risk, it manages it, and it needs to be built before the first Australian appointment, not assembled afterwards under public pressure. Defence already has robust policies, processes, and procedures for managing conflicts of interest, as outlined in the Defence Instruction Administration and Governance Provision 5: Conflicts of interest.
• Does this grow the officer corps unnecessarily? No, and the reservist structure established in the previous section is precisely why. These are not full-time uniformed positions the Army would need to recruit, house and pay for year-round. They serve part-time, on the same basis as Detachment 201's minimum of 112 hours a year, while remaining in their civilian roles and drawing their civilian salary. The proposal adds standing commissions, not headcount, and draws on the same Reserve structure Army already funds and administers.

A way forward

1. Formally extend the Specialist Service Officer and Specialist Senior Non-Commissioned Officer concepts beyond their current fixed list of professions, framed as a standing, reservist-based mechanism rather than a case-by-case exception, so it does not require the Army to invent a new corps every time a new technical domain becomes critical.
2. Build the governance and recusal framework early, before the first controversial appointment forces it into existence reactively, on the model Detachment 201 already runs, mandatory financial disclosure, annual ethics training, legal review of each work assignment, and recusal from anything touching an individual’s own financial interests, particularly where procurement intersects with a civilian role.
3. Set a clear boundary between operational technology roles, which remain inside existing corps and training pipelines, and frontier mastery roles, which sit inside the new pathway, so the proposal cannot be mistaken for duplicating what existing corps already do well.
4. Measure the pathway's success by how much of Army's frontier capability development shifts, over time, from work delivered purely through contracting to work shaped by standing Specialist Service Officers and Specialist Senior Non-Commissioned Officers, using Army's current contracting spend on frontier technical expertise as the baseline, so the proposal is judged against a measurable outcome rather than an assertion.

Conclusion

Army is not behind on technology. It invests in operator innovation, and programmes like MakerSpace do that job well, giving soldiers the tools to solve the problems their own experience of the equipment reveals to them. That is worth having, and it is not the same thing as understanding why a system was built the way it was. Army is behind on a harder recognition: that the soldier who has spent 20 years mastering a system is still its end user, and that no length of service turns an end user into the person who designed it. That expertise is built in industry or not at all, which means the Army's only options are to bring it inside or to keep hiring it by the task.

Contracting delivers the task. It does not deliver a standing channel through which that expertise shapes how a capability develops, how it is fielded, and how the doctrine covering it is written. Doctrine is being written now, for systems that will define the next fight, largely by people who have only ever received those systems once delivered.

Letting rank follow mastery rather than years in uniform or direct command experience is not a foreign idea to the Army. It already accepts the principle, narrowly, in legal, medical, nursing, and chaplaincy. What it has avoided is confronting how much further that principle now needs to reach, because its rank system remains built around command of soldiers in a way its sister services no longer require.

The answer is not to grow the officer corps, and it is not to keep renewing contracts. It is to extend the Specialist Service Officer and Specialist Senior Non-Commissioned Officer models Army already runs into a standing, reservist pathway, the same mechanism the United States has now built three times, across three services, inside a single year. Expertise that sits inside the institution compounds. Expertise that is heard politely, or that leaves the building when the contract ends, never gets the chance.

Still Interested?

Why not also read Becoming the Effective Signaller

Cove+ offers short learning courses on related topics, including Introduction to Organisational Design.