“We’ve got to get through all the first of class — I’m going to call them hiccups — because there’s going to be things we learn because we’ve never operated it before,” Vice Adm. Robert Gaucher said. That sentence, plain and unadorned, frames a program-level dilemma: push to deliver a complex new platform by a specified year, or accept the time and resources needed to work through the inevitable surprises of first-of-class systems.
A blunt assessment from the Navy’s submarine czar
Vice Adm. Robert Gaucher — described in coverage as the Navy’s “sub czar” — told reporters that delivering the first Columbia-class submarine in 2028 “will prove ‘wicked heavy lift.’” He followed that characterization with the observation quoted above about first-of-class “hiccups” and the learning that will come because the service has “never operated it before.” Those are the explicit facts at hand: a delivery date referenced, a candid label of difficulty, and an acknowledgement that untested operational realities lie ahead.
What the comments reveal about program risks
Gaucher’s choice of words matters. Calling the delivery “wicked heavy lift” signals more than timetable risk; it is shorthand for a cluster of challenges that typically accompany introducing a new class of warship. By naming “hiccups” and learning from operations not previously conducted, the vice admiral put operational integration and the unknowns of fielding a new design at the center of the discussion.
Even without additional granular detail, that framing implies two linked realities: the technical or industrial tasks of completing and delivering a previously unbuilt platform, and the operational tasks of figuring out how to operate, maintain and support it once it joins the fleet. Gaucher’s comment ties both to the program’s near-term horizon.
First-of-class problems: what “hiccups” usually mean
When a senior official refers to first-of-class “hiccups,” he is flagging iterative, often unanticipated issues that appear only when a system is assembled, activated and used in real conditions. Gaucher’s own words make clear the root cause: “there’s going to be things we learn because we’ve never operated it before.” That sequence — build, test, learn, adjust — is the one he expects to repeat.
From a program management angle, this implies a need for robust testing regimes, an ability to accept and manage schedule slips, and the institutional flexibility to incorporate fixes after initial delivery. From an operational angle, it means crews and sustainment organizations will have to adapt procedures and logistics to support new behaviors and equipment that have not yet been exercised in real-world operations.
How different stakeholders might read the warning
- Technologists and engineers will hear an implicit call for intensive systems integration and rigorous trials. Gaucher’s forecast of learning through operation suggests that early platforms will illuminate design gaps and integration issues that are difficult to detect in laboratory conditions.
- Policymakers and program managers will hear a caution about schedule risk and the need to resource follow-on fixes. Describing the 2028 delivery as a “wicked heavy lift” signals that meeting that date without contingency could strain resources or require trade-offs.
- Operators — the crews who will “operate it” — receive a blunt reminder that they will be pioneers. Gaucher’s statement acknowledges the human side of fielding a new class: procedures, training and institutional learning must evolve alongside hardware.
- Potential adversaries, while not mentioned by Gaucher, would likely take note when a senior official publicly highlights the challenges inherent in new systems; the acknowledgment of learning in operation is, in itself, a candid admission of vulnerability during the initial period.
Implications for program execution and oversight
Gaucher’s remarks suggest several implications for those overseeing or executing the program. One is the importance of allowing time and budgetary flexibility to resolve first-of-class issues discovered after delivery. Another is the need to sequence testing, training and logistics support so that learning can be fed back into the program without cascading schedule or capability shortfalls.
By noting that the Navy has “never operated it before,” Gaucher implicitly places a premium on realistic operational testing and on capturing lessons from the very first units delivered. That requires not just technical fixes but organizational structures to institutionalize lessons learned — a point that follows directly from his observation.
Managing expectations while preparing for unknowns
The vice admiral’s language is striking in its plainness. “Hiccups” is an almost colloquial term, while “wicked heavy lift” combines urgency with understatement. Together they perform a communicative task: they temper expectations about flawless, on-time success and prepare audiences for an iterative process of discovery and correction.
Preparing for those unknowns means several practical steps implied by the remarks: prioritizing test results, planning for additional training and sustainment, and building program structures that accept the iterative nature of first-of-class maturation. Those steps flow naturally from Gaucher’s forecast that things will be learned only through operation — an admission that the program will have to adapt in the wake of real-world experience.
Where this leaves the program and the public
Vice Adm. Gaucher’s candid framing forces a choice between two paths: accelerate delivery to meet a horizon and accept the operational learning curve happening under time pressure, or build in explicit breathing room to reduce the risk of fielding an immature capability. His comment does not prescribe which choice to make, but it does put the trade-off plainly before decision-makers and the public.
As the Navy and its partners move forward, the essential questions remain: how will the program balance schedule and capability; how will the service capture and act on lessons from first-of-class use; and how will stakeholders ensure the initial “hiccups” do not cascade into systemic shortfalls? Vice Adm. Gaucher’s words provide a candid starting point for that conversation: delivering the first Columbia-class submarine in 2028, he said, will be a “wicked heavy lift,” and “there’s going to be things we learn because we’ve never operated it before.”
