Lanes in the Road: Untangling STRATCOM's Org Chart After the Merger

by Lexa V., 27 September 2026

In October 2002, U.S. Strategic Command absorbed U.S. Space Command, folding two commands built around very different missions into one. STRATCOM inherited more than Space Command's satellites and its space-surveillance mission. On top of its own nuclear-deterrence core, it took on a slate of newly assigned responsibilities: global strike, integrated missile defense, command, control, communications, computers, intelligence, surveillance, and reconnaissance systems (C4ISR), and information operations. Nearly a year later, the merged command was still working out how all of that actually mapped onto its own organization chart, and a hard deadline was bearing down: Full Operational Capability, targeted for 1 January 2004.

What it was. On 14 August 2003, STRATCOM stood up a project team to answer exactly that question: which division owned which function, in every mission area, down to the individual task. With a staff officer's dry humor, it was named the "Lanes in the Road" Project Team, or LRPT. Its charter gave it forty-five days.

It took nearly five months.

The overrun was not a planning failure. It was a discovery. Two weeks into the review, the team found that most division chiefs did not actually understand how the command's newly assigned missions were supposed to fit their own organization chart. Nearly every division's first-pass input covered only the traditional nuclear mission and, somewhat less thoroughly, the old Space Command mission. Global strike, missile defense, the C4ISR mission, and information operations were largely invisible to the people who, on paper, already owned them. A command built from two organizations was still, functionally, running as though the merger had never happened.

To fix that, the team built a framework it called MAPPER+S. The framework sorted the command's work into six mission areas, five operational missions plus a "Command Support" category, and it assigned ownership by a simple rule keyed to time horizon. Anything resolvable inside an hour belonged to whoever was on watch. Anything spanning an hour to ninety days went to the command's Global Integration Center. Anything longer went to whichever division owned the underlying long-range mission. The team also had to impose order on the raw material itself. Some divisions had submitted mission statements running six to eight hundred words, and function statements running past a thousand. The team capped mission statements at three sentences: short enough, as the team put it, to fit on a performance report or to be memorized by the people doing the work.

Midway through, the ground shifted again. On 1 October 2003, STRATCOM's operations directorate reorganized its own "super-divisions" and stood up an entirely new one for space enhancement. That change pushed the team's delivery back another two weeks, on top of the delay the discovery had already caused.

What Mike did. Mike sat on the team as the Command Secretariat — not a delegate sent from that office, but the officer who ran it. The Secretariat was STRATCOM's administrative backbone. The command's generals and admirals owned the mission and the people; Mike, as CSS, owned the paperwork that got the staff's mission done. So when the charter named the Secretariat to lead the effort, it named his office, and the team roster lists him first. Ahead of the 1 January 2004 FOC stand-up, the team delivered an Organizations and Functions document and a supporting database cataloguing more than eight hundred specified and implied functions across the headquarters, each one assigned an office of primary and collateral responsibility. The closing assessment in the team's final report was characteristically unsentimental: "The work of the team will never be done, but we believe this reflects the 80% solution of HQ USSTRATCOM for 1 Jan 04 COMMAND FOC."

The impact. That 80 percent was the difference between a command with a mission on paper and a command with a mission its own divisions could recognize. Nearly five months of tracing lanes across a newly merged org chart turned a structure nobody fully understood into one that finally matched, division by division, how the command actually worked.