Skunkworks

Transfers

Lockheed Martin’s Advanced Development Programs — the original Skunk Works — designed the U-2, SR-71 Blackbird, and F-117 stealth fighter. Kelly Johnson ran the division with 14 rules that boiled down to one principle: a small team, isolated from the parent organization, can move faster than any bureaucracy. The metaphor maps this military R&D structure onto software teams that operate outside normal organizational process.

Key structural parallels:

• Organizational isolation — the Skunk Works was physically separated from the rest of Lockheed, with restricted access and independent reporting. In software, a skunkworks team operates outside the normal sprint cadence, ticket system, and approval chain. The isolation is the point: it removes the friction that slows conventional teams.
• Small team, broad mandate — Johnson kept his teams to 10-25% of what conventional programs would staff. Each engineer covered multiple disciplines. Software skunkworks teams are similarly lean, staffed with generalists who can own a feature from prototype to deployment without handoffs.
• Speed through autonomy — the Skunk Works delivered the XP-80 jet fighter in 143 days. The structural reason was elimination of approval layers: Johnson reported directly to one executive, not a committee. Software skunkworks replicate this by bypassing architecture review boards, design committees, and cross-team alignment meetings.
• Reintegration problem — the Skunk Works produced prototypes that eventually had to be manufactured at scale by conventional Lockheed divisions. Software skunkworks face the same challenge: the prototype works, but it was built without the team’s coding standards, CI pipeline, or security review. Reintegrating is where the metaphor earns its keep — and where most skunkworks projects die.

Limits

• Military skunkworks have institutional backing; corporate ones often don’t — Kelly Johnson had a direct relationship with the Pentagon and a formal charter from Lockheed’s CEO. Most software skunkworks are unauthorized: a few engineers sneaking time to build something they believe in. The metaphor borrows the prestige of sanctioned independence while describing unsanctioned rebellion. When leadership discovers the project, it gets killed or adopted — but rarely with the graceful handoff the military metaphor implies.
• The metaphor romanticizes isolation — in military R&D, secrecy was operationally necessary (Soviet intelligence). In software, isolation from the rest of the engineering organization means building without feedback, without shared context, and without the constraints that exist for good reasons. Skunkworks code often ignores accessibility, internationalization, and security — not because the team is elite, but because they’re unsupervised.
• Survivorship bias — we remember the SR-71. We don’t remember Lockheed’s failed skunkworks projects, or the dozens of corporate skunkworks that produced nothing usable. The metaphor carries an implicit promise of breakthrough innovation, but most skunkworks projects produce prototypes that never ship.
• Scale mismatch — military skunkworks operated for years with hundreds of millions in dedicated funding. A software skunkworks is usually three engineers for three weeks. Calling it a “skunkworks” maps the ambition of the F-117 onto a React prototype, which flatters the project beyond its actual scope.

Expressions

• “We’re running a skunkworks project” — building something outside the official roadmap, usually with implicit management ignorance
• “Skunkworks team” — a small autonomous group, often self-selected, working on something the organization hasn’t sanctioned
• “It started as a skunkworks and now it’s in production” — the success narrative, where unofficial work becomes official product
• “Kelly Johnson rules” — invoking the original 14 management principles, usually to justify cutting process

Origin Story

Clarence “Kelly” Johnson founded Lockheed’s Advanced Development Programs in 1943 to build America’s first jet fighter, the XP-80. The team worked in a rented circus tent next to a plastics factory whose smell was so bad that engineers answered the phone “Skonk Works” — a reference to the foul-smelling “Skonk Oil” factory in Al Capp’s comic strip Li’l Abner. The name stuck, eventually formalized as “Skunk Works” (one word, no second ‘o’) and trademarked by Lockheed Martin.

The term entered software culture in the 1990s, particularly at companies like Apple (the original Macintosh team) and Google (early Gmail and Google Maps teams). It now refers to any small team given — or taking — freedom to build outside normal organizational constraints.

References

• Johnson, C.L. & Smith, M. Kelly: More Than My Share of It All (1985) — Johnson’s autobiography detailing Skunk Works principles
• Rich, B. & Janos, L. Skunk Works: A Personal Memoir of My Years at Lockheed (1994) — Johnson’s successor on the culture and methods