Solve for X

“Solve For X is a place to hear about and discuss radical technology ideas for solving global problems. Radical in the sense that the solutions could help millions or billions of people. Radical in the sense that the audacity of the proposals makes them sound like science fiction. And radical in the sense that there is some real technology breakthrough on the horizon indicating that these ideas could really be brought to life.

This combination of things – a Huge Problem to solve, a Radical Solution for solving it, and Breakthrough Technology to make it happen – is the essence of a technology moonshot.

Solve For X is intended to be a forum to encourage and amplify technology-based moonshot thinking and teamwork. The forum began in 2012 with a small face-to-face event co-created and co-hosted by Astro Teller, Megan Smith, and Eric Schmidt.”

https://www.solveforx.com/about/

The story behind Skunkworks

Lockheed_Martin_s_Skunk_Wor

 

 

“A skunkworks project is a project developed by a small and loosely structured group of people who research and develop a project primarily for the sake of radical innovation. The terms originated with Lockheed’s World War II Skunk Works project.”

“Everett Rogers defines skunkworks as follows: “It is an especially enriched environment that is intended to help a small group of individuals design a new idea by escaping routine organizational procedures. The research and development (R&D) workers in a skunkworks are usually specially selected, given special resources, and work on a crash basis to create an innovation.”

The term originated during World War II when the P-80 Shooting Star was designed by Lockheed’s Advanced Development Projects Division in Burbank, California, under similar circumstances. A closely guarded incubator was set up in a circus tent next to a plastics factory in Burbank. The strong smells that wafted into the tent made the Lockheed R&D workers think of the foul-smelling “Skunk Works” factory in Al Capp’s Li’l Abner; the job no one wanted: to be the inside man at the ‘Skonk Works’ (as called in the comic).

Since its origination with Skunk Works, the term was generalized to apply to similar high-priority R & D projects at other large organizations, featuring “small team taken out of their normal working environment and given exceptional freedom from their organisation’s standard management constraints.”

The term typically refers to technology projects developed in semi-secrecy, such as Google X Lab.Another famous skunkworks was the lab of about 50 people established by Steve Jobs to develop the Macintosh computer, located behind the Good Earth Restaurant in Cupertino.” wikipedia

Here is the amazing story as presented in Popular Mechanics (as pdf)

Kelly Johnson’s 14 rules of Skunkworks projects

1. The Skunk Works manager must be delegated practically complete control of his program in all aspects. He should report to a division president or higher.

2. Strong but small project offices must be provided both by the military and industry.

3. The number of people having any connection with the project must be restricted in an almost vicious manner. Use a small number of good people (10% to 25% compared to the so-called normal systems).

4. A very simple drawing and drawing release system with great flexibility for making changes must be provided.

5. There must be a minimum number of reports required, but important work must be recorded thoroughly.

6. There must be a monthly cost review covering not only what has been spent and committed but also projected costs to the conclusion of the program.

7. The contractor must be delegated and must assume more than normal responsibility to get good vendor bids for subcontract on the project. Commercial bid procedures are very often better than military ones.

8. The inspection system as currently used by the Skunk Works, which has been approved by both the Air Force and Navy, meets the intent of existing military requirements and should be used on new projects. Push more basic inspection responsibility back to subcontractors and vendors. Don’t duplicate so much inspection.

9. The contractor must be delegated the authority to test his final product in flight. He can and must test it in the initial stages. If he doesn’t, he rapidly loses his competency to design other vehicles.

10. The specifications applying to the hardware must be agreed to well in advance of contracting. The Skunk Works practice of having a specification section stating clearly which important military specification items will not knowingly be complied with and reasons therefore is highly recommended.

11. Funding a program must be timely so that the contractor doesn’t have to keep running to the bank to support government projects.

12. There must be mutual trust between the military project organization and the contractor, the very close cooperation and liaison on a day-to-day basis. This cuts down misunderstanding and correspondence to an absolute minimum.

13. Access by outsiders to the project and its personnel must be strictly controlled by appropriate security measures.

14. Because only a few people will be used in engineering and most other areas, ways must be provided to reward good performance by pay not based on the number of personnel supervised.

Source: http://www.lockheedmartin.com/us/aeronautics/skunkworks.html

 

 

Moonshot thinking

“Moonshots live in the gray area between audacious projects and pure science fiction; instead of mere 10% gains, they aim for 10x improvements. The combination of a huge problem, a radical solution, and the breakthrough technology that might just make that solution possible is the essence of a Moonshot.”

https://www.solveforx.com/about/whatisamoonshot/

(feature picture Apollo mission http://history.msfc.nasa.gov/saturn_apollo/photos/images/apollo17_GPN-2000-000636.jpg)