The Manhattan Project and Apollo as Project Management

By Victor Hoang · Updated Oct 24, 2026

Picture September 1942. The bomb effort has a name. It has rival ways of separating uranium. It has no production plant. On September 17 the Army appointed Colonel Leslie Groves to run it. He was an engineer who had built the Pentagon. Within two days he had secured a Tennessee site and a higher priority rating for project materials.

Big-program management took shape between 1942 and 1972, in two American efforts that NASA's own historians call comparable. The Manhattan Engineer District was set up by general order on August 13, 1942. President Kennedy announced the Moon goal on May 25, 1961.

The throughline is a trade. The first program showed that one empowered manager could run research, construction and production at the same time. The second turned that gamble into written methods: a program office, configuration control, phase reviews and all-up testing. The Manhattan program had no network schedule, work breakdown structure or baseline to lean on, because none of them existed yet. This article follows what Groves improvised, what the Air Force and NASA turned into method, and what a team can still use. For the wider field, see the history of project management.

Timeline at a Glance

The Precursor Years (Antiquity-1941)

Builders coordinated crews, but nobody ran a program

Around 2550 BCE an inspector named Merer kept a log of crews moving limestone from the Tura quarries. His papyrus logbook, found at the Red Sea harbor of Wadi el-Jarf by a team led by Pierre Tallet in 2013, is part of the oldest papyrus archive found in Egypt. Its entries record stone moved to the Great Pyramid and goods delivered to the workers who moved it. That's coordination at scale, and the ancient megaprojects story tells the rest of it, from Roman water gangs to Chinese labor levies. Later centuries added the railroads, which drew the first organization diagrams.

Those are precursors, not the thing itself. The pyramid crews coordinated labor on a known design. The 1940s programs had to do something else: pay for the research, the factories and the delivery of a product that did not yet exist, all in the same years. NASA's own historians say the "program management" concept was borrowed in the late 1950s from the military/industrial complex, so the name came well after the practice.

The federal side began modestly. Roosevelt named Lyman Briggs to head an Advisory Committee on Uranium, which first met on October 21, 1939 and was told to look into where uranium research stood. By January 19, 1942, Roosevelt had approved a report that put a science organization at the top of the government and a Top Policy Group with direct access to the President. What the effort still lacked was a manager with authority over steel, land and schedules.

What this means for teams today: a coordination method that works on a known design breaks when the product itself is unknown. Name which kind of project you're running before you pick tools.

Groves's Gamble (1942-1946)

An Army engineer builds an unproven bomb on a deadline

The Manhattan story starts with a slow summer. Colonel James Marshall received the assignment and set up the Manhattan Engineer District in New York, but Marshall and his Army superiors were inclined to move cautiously. In one case he delayed buying an excellent production site in Tennessee while the scientists pressed for an immediate purchase, and the account notes that no mechanism existed to settle disagreements between the scientists and the military. The fix was a person. After the September 17 appointment, Groves moved the district headquarters from New York to Washington and made Colonel Kenneth Nichols, Marshall's deputy, his chief aide and troubleshooter for the rest of the war. A Military Policy Committee with one member each from the Army, the Navy and the Office of Scientific Research and Development sat above him.

Groves ran the program on a few visible habits. He forced decisions on a date. At the Metallurgical Laboratory in Chicago on October 5, 1942, he gave the scientists a week to settle the pile design, arguing that a wrong decision beat no decision and that time was worth more than money. He hedged with parallel bets, since four isotope separation processes stayed under consideration that fall. And he hired competence instead of building it. DuPont agreed on October 3 to design and build the chemical separation plant, and Groves got the company for one dollar over actual costs, and the account credits DuPont's proven administrative structure with assuring good coordination. DuPont's own appraisal had warned that plutonium could be mass-produced by 1945 only under the best circumstances and that the odds were low, as the account of that appraisal records. Groves went ahead anyway.

On December 28, 1942, Roosevelt approved the full program, what the account calls a government investment that ultimately exceeded $2 billion. The pieces then went up fast across the country. A survey party led by Colonel Franklin Matthias started looking at sites on December 16, 1942, and picked Hanford, Washington for the plutonium plants. The Tennessee site, the Clinton Engineer Works, covered about 59,000 acres, and by the end of the war its town of Oak Ridge was the fifth largest in the state while the works consumed one-seventh of the nation's electric power. At Los Alamos, set up in spring 1943, Oppenheimer was chosen to lead the weapons laboratory despite concerns about his administrative inexperience. The same account calls the partnership between Groves and Oppenheimer, two very different temperaments, a major factor in the project's success.

The method had a price, and the record is frank about it. The district operated, in the account's words, like a large construction company, but it invested hundreds of millions of dollars in unproven processes and dropped the pilot-plant stage entirely, which the account says violated manufacturing practice and led to shutdowns and endless troubleshooting. Y-12, the electromagnetic plant, is the case in point. Its first track leaked, shimmied out of line and shorted its magnet coils, and Groves arrived on December 15, 1943 and shut it down. The first four tracks did not run together until April 1944, a full four months late. When Los Alamos warned in July 1943 that three times more fissionable material would be needed than estimated, Groves agreed to roughly double the electromagnetic complex. And when the gaseous diffusion and electromagnetic plants both struggled in 1944, the Navy's thermal diffusion work became a stopgap. Groves gave a contractor ninety days from September 27 to bring a 2,142-column plant online, where the Navy's prototype had held 100 columns.

The payoff came on July 16, 1945, at 5:30 a.m., when the Trinity device released about 18.6 kilotons. Little Boy fell on Hiroshima on August 6 and Fat Man on Nagasaki on August 9. The Department of Energy says the effort peaked at 130,000 workers and spent $2.2 billion by the war's end. The Atomic Energy Commission succeeded the district on January 1, 1947.

Notice what the project lacked. It had no network scheduling and no earned value, which arrived with PERT and the critical path method more than a decade later. Its management was authority, deadlines and personal attention. That worked once, in a war, with a blank check and secrecy that made decisions possible with little regard for peacetime politics. Peacetime programs would need the authority written down.

What this means for teams today: a single accountable owner and a firm decision date can unstick a stalled effort. But skipping the pilot stage turns every surprise into a production problem, so decide on purpose which stages you'll compress.

The Air Force Blueprint (1954-1961)

Missile programs write the playbook NASA inherits

Between the bomb and the Moon sits a program most readers have never heard of. NASA's administrative historian Arnold Levine writes that the only programs since the Manhattan Project comparable to NASA's mission were the weapon systems programs the Air Force managed from 1954. In 1954 the Air Force set up a Western Development Division under General Bernard Schriever to run its ballistic missile effort, and the problems it hit were the same ones NASA would meet: cost estimates that couldn't be trusted, general uncertainty and long lead times.

Schriever's answer had two parts. The first was concurrency, which meant simultaneous work on research, vehicle design, component design, test facilities, production facilities and launch sites, so the missile wouldn't wait on any one of them. The second was an industrial structure. The Air Force delegated the research and development cycle to private contractors, used several associate contractors for components and subsystems, and hired a separate firm, Ramo-Wooldridge, as technical director. That firm was excluded from producing hardware. Levine calls the Western Development Division a blank-check outfit running a crash program, so the similarity to NASA shouldn't be pushed too far. Even so, the habits traveled. NASA's histories describe Samuel Phillips as the architect of the Minuteman ICBM program, and he went on to serve as Apollo Program Manager from 1964 to 1969, one of several Air Force officers detailed to the agency.

The Navy was running its own program in parallel. Its Polaris office produced PERT, and Levine notes that some of NASA's most important projects were later managed by military detailees trained in PERT. That strand has its own story in the history of PERT.

The new problem was oversight. A contractor-heavy system moves quickly, but the government still owns the outcome. How does a small staff steer a thousand firms? NASA would have to answer that in public, with Congress watching.

What this means for teams today: if you outsource the building, keep the integrating role and the technical judgment in-house. Whoever integrates the pieces has to be someone with no stake in selling you one of them.

Webb and Mueller (1961-1967)

A deadline from the White House forces a management system

On February 7, 1961, James Webb was appointed to run NASA, and Levine's history says the President wanted someone with experience in the political rough-and-tumble of Washington, someone who could handle Congress, the Bureau of the Budget and a Defense Department that wanted NASA to be a supporting agency. Webb, a former Budget Bureau director, demanded on being offered the job the authority to run the agency as he saw fit. A headquarters study committee chaired by George Low had reported in February 1961 that a manned lunar landing could be accomplished during the decade for just under $7 billion through fiscal 1969. On May 25 Kennedy asked Congress for a $549 million supplemental appropriation and set the goal.

The scale that followed is the first fact worth holding. NASA's civil service rolls grew from 10,000 in 1960 to 36,000 by 1966, and contractor employees rose from 36,500 in 1960 to 376,700 in 1965. Procurement actions went from roughly 44,000 in 1960 to almost 300,000 by 1965, and the same monograph says Phillips's program management orchestrated more than 500 contractors. Between 1959 and 1973, NASA spent more than $25 billion on human spaceflight, with nearly $20 billion for Apollo. The monograph's author, Roger Launius, adds that Project Apollo was comparable in size only to the Panama Canal as a non-military American effort and to the Manhattan Project in wartime.

Early structure came fast. The Office of Manned Space Flight set up a Management Council chaired by Brainerd Holmes, which at its first meeting on December 21, 1961 settled the standard Saturn configuration and gave Marshall Space Flight Center responsibility for integrating the three stages. General Electric took on testing and checkout, and AT&T formed a separate corporation, Bellcomm, for systems analysis. In July 1962 NASA chose lunar orbit rendezvous as the way to the Moon. Webb also held the portfolio together. When Holmes asked in late 1962 for another $400 million for the landing, Webb refused, because the money could come only from a supplemental appropriation or from decimating NASA's other programs. That's an early example of what project portfolio management calls balancing, though NASA's own phrase was a "balanced program".

Then Holmes left. George Mueller, who came from Space Technology Laboratories, replaced him in September 1963, and Levine argues that the most important administrative changes at the office occurred in a little more than one year, from September 1963 to the end of 1964. Mueller organized the office along program lines instead of having one office for launch vehicles and another for spacecraft. He divided each program into discrete "work packages", developed vehicles and ground support equipment at the same time, added redundancy and introduced the all-up approach. He also required that each major system have one person responsible full-time for performance, cost and schedule. That is the same idea as a work breakdown structure with a named owner, and the story of how those structures became standard is in the history of the WBS. Mueller delegated schedules, budgets and systems engineering to Phillips, the Apollo program manager, and cut his Management Council down to himself and the three center directors.

All-up testing was Mueller's biggest bet. It meant flying a vehicle as complete as practical on every flight, so the Saturn V's three stages would fly together with the Apollo spacecraft instead of being tested one stage at a time. Levine notes that Mueller and the Management Council made the decision, not the Administrator's office, and that Mueller knew of the Air Force's all-up testing of Minuteman. His center directors resisted at first, but the logic of the end-of-decade deadline, schedules that were already slipping and the slow Saturn I testing history won them over. The decision also forced other disciplines: stricter control of quality, close monitoring of contractors, weight budgets and built-in redundancy.

The harder discipline was control of change. Mueller revived a dormant Panel Review Board in late 1964 to get a tighter rein on configuration control for the spacecraft and launch vehicles, and the spacecraft manager Joseph Shea set up a stronger Configuration Control Board, with a written Configuration Management Plan, as Chariots for Apollo records. On January 15, 1965, Phillips issued an Apollo Program Development Plan in 17 subdivisions that laid out who did what and how changes would be approved. By mid-August 1965 Mueller and Phillips had set six checkpoints for Apollo hardware: a Preliminary Design Review, a Critical Design Review, a Flight Article Configuration Inspection, a Certification of Flight Worthiness, a Design Certification Review and a Flight Readiness Review. The same year NASA issued its phased project planning guidelines in October, so that projects would run in sequential phases with agency top management taking part at every major decision point. Levine adds that the concept was older than the name. Seamans called the Goldstone 64-meter antenna a textbook case before the policy existed.

Trouble was what forced the paperwork. In September 1964, Associate Administrator Robert Seamans warned Mueller that the landing would miss the decade and the cost would exceed twenty billion dollars if trends continued. Mueller asked Phillips to review North American Aviation, the prime contractor for the command and service modules and the Saturn V's second stage. The review ran from November 22 to December 6, 1965, and its findings went to the company on December 19. The Phillips Report found that milestones kept slipping, that NAA's estimate for the ten-stage S-II program had more than tripled, that workmanship was poor, and that the configuration management procedures the company and NASA had agreed on were not being followed by the engineering organizations.

What this means for teams today: write down who may change the design, and make every change pass through one board. Plans don't stop drift, but a named gate does. Compare the vocabulary here with the waterfall methodology, which describes the sequential-phase pattern in its general form.

Fire and Flight (1967-1972)

A launch pad fire tests the system, then the deadline is met

At 6:31 p.m. on January 27, 1967, during a simulated launch sequence on the pad, a fire broke out in the Apollo 204 capsule. Gus Grissom, Edward White and Roger Chaffee died, the first deaths directly attributable to the U.S. space program. The day after, NASA appointed an eight-member board chaired by Floyd Thompson. It concluded the fire had been caused by a short circuit that ignited combustible materials in a pure-oxygen atmosphere, and that it could have been prevented.

The fire also exposed a management failure. The Phillips Report from 1965 had gone to North American, but the NASA history page says that after the fire it was discovered that Webb apparently did not know the report existed. Congressional committees demanded its release, while Webb and Seamans argued that doing so would break faith with a NASA contractor. Launius records that Webb deflected much of the backlash from the agency, though he never recovered personally, and left NASA in October 1968. A program built on paper controls had still let a hard truth stay at the wrong level.

The recovery took almost twenty months, until October 1968, before astronauts flew an Apollo spacecraft in orbit. Meanwhile, the Saturn V's all-up gamble came due. The first Saturn V flew on November 9, 1967 with the whole Apollo-Saturn combination. A second flight on April 4, 1968 was only partly successful, because the second stage shut off early and the third stage failed, but Mueller declared the test program complete and said the next launch would carry astronauts. Launius records that across 17 test and 15 piloted launches, the Saturn booster family scored a perfect launch reliability rate.

The same discipline allowed a bold change of plan. In November 1968 Phillips recommended that the next flight be recast as a circumlunar mission, and the Administrator accepted the memo on November 18, which made possible Apollo 8 on December 21-27, 1968. Apollo 11 landed on July 20, 1969, and five more landing missions followed at roughly six-month intervals through December 1972. Separately, in January 1968 NASA set up a Management Council chaired by Associate Administrator Homer Newell, intended to evolve into a top management team sharing responsibility.

Outsiders noticed the method. In November 1968, Launius says, Science magazine suggested that the program's most valuable spin-off might be better knowledge of how to plan, coordinate and monitor large activities. For the distinction between running a program and running a project, see program versus project management. For how risk became a field of its own, see the history of project risk management.

What this means for teams today: a review that nobody senior reads is a paper trail, not a control. Check that bad news can travel up to the person who decides.

The Lasting Template (1972-present)

Apollo's phases and design reviews still shape NASA programs

By the early 1970s the form was set, and the surviving record is the vocabulary. NASA's current life cycle, as the agency's systems engineering reference lays it out, splits a space flight project into Formulation and Implementation, with phases from Pre-Phase A concept studies through Phase F closeout. Key Decision Points between phases let a decision authority judge whether the project may advance. A project that doesn't pass may try again after fixing its problems or may be terminated. Phase B ends with Preliminary Design Reviews and Phase C contains Critical Design Reviews, the same two names that sat on Mueller and Phillips's 1965 list of checkpoints. Phased project planning and today's decision points look like the same idea at different ages.

The wider profession took pieces of this and renamed them. The 1962 DoD and NASA PERT/COST guide, covered in the history of the WBS, is one bridge, and cost control through earned value is another. The profession later organized itself and wrote its own standard body of knowledge, a story told in the history of PMI and the PMBOK Guide, and the longer story of how methods branched is in the evolution of project management methodologies. For the broader sequence of dates, see the project management timeline and who invented project management.

Both programs also left a warning. Their methods rested on huge budgets, hard deadlines and public mandates, and Levine's history of NASA shows how much effort went into keeping control as the agency grew. A team without those conditions can't copy the scale, but it can copy the habits.

What this means for teams today: most of what you do with phases, gates and change boards was tried on a program with a blank check. Keep the gates and scale the paperwork to your risk.

Key People

Key Facts

• The Manhattan Engineer District was established by general order on August 13, 1942, and Groves took command on September 17.
• The Manhattan Project peaked at 130,000 workers and spent $2.2 billion.
• Contractor employees on NASA's programs rose from 36,500 in 1960 to 376,700 in 1965.
• Apollo's six checkpoints included a Preliminary Design Review and a Critical Design Review, and both still appear in NASA's life cycle.
• NASA spent more than $25 billion on human spaceflight between 1959 and 1973, with nearly $20 billion for Apollo.
• The Saturn booster family scored 100 percent launch reliability across 17 test and 15 piloted launches.

The Pattern Behind the History

This is our synthesis, not published research. Five points repeat from Los Alamos to the Cape:

• The deadline comes first. Groves had a war and Webb had a presidential date, and each built the method after the date existed.
• Overlap the stages and pay for it. Manhattan skipped the pilot plant, the Air Force ran everything concurrently, and Apollo flew the whole stack. Each saved time and each created troubleshooting.
• Put one name on every piece. Groves answered for the bomb, Phillips for Apollo, and Mueller wanted a full-time owner for every major system.
• Write change control down. Configuration boards, a development plan and six checkpoints replaced personal oversight once the program outgrew one person.
• Failure writes the next rule. Y-12's shutdown, the Phillips Report and the Apollo 204 fire each led to a harder control.

What It Teaches Teams Today

• Give one person the whole outcome. Both programs had a single name above the integration, and Mueller pushed that down to every major system.
• Hedge the big unknowns in parallel. Groves kept four separation processes alive until the facts arrived. Spend that way only when the unknown decides the project.
• Decide when to skip the pilot. Compressing stages saved months on Manhattan and cost troubleshooting time. Do it deliberately and budget for the fix.
• Control change at a board, not in a hallway. Apollo's drift only slowed once changes went through a Configuration Control Board and a plan.
• Make bad news travel. The Phillips Report existed and the Administrator apparently didn't know. Build a path for audit findings to reach the decision-maker.