At the beginning of my business career I learned about the “Skunk Works“, also known as the Lockheed Martin Advanced Development Projects. The way I was told it was a heroic little band of engineers that stuck it to the man and snuck off to a secret location to do what the big company with its bureaucracy and hide-bound leadership of the larger company could not. Projects (like developing a U.S. jet-fighter during WWII) were started on a handshake.
A careful reading of the history tells a more mundane story. The Advanced Development Projects was deliberately established as a prototyping facility, where the KISS principle was the principle. Speed was essential, cost was not. The secrecy was because of what they were working on, not because they were pulling a fast one. It makes for an inspiring story, but it’s just not true.
Unfortunately in the last fifty years the term “skunkworks” has come to be an excuse for siphoning people and resources from sanctioned projects to get around controls, avoid oversight, or to reduce the risk of the official project by having a backup to go to when it fails.
Here’s the problem. By stealing resources from a project because we think it might fail, we are increasing the liklihood that it will fail. The talent, time, and materials taken from one project and given to another secret, unofficial skunkworks may contribute to the failure of the first. By allowing a skunkworks to exist we are failing in our duty as a leader in two ways:
If the first instance, where the main project succeeds, we incurred the additional cost of supporting a skunkworks without benefit. In fact we’ve probably increased the time and cost, and decreased its quality because we didn’t have all the resources available to us working on it, and we’ve wasted all the time & effort used in the skunkworks because it didn’t get used. Where the skunkworks succeeds and the main project fails, we’ve incurred the cost of supporting the chosen alternative for no benefit.
As managers and leaders we’re supposed to provide the greatest benefit to the company the employs us for the least cost. Running two projects that do the same thing betrays that responsibility.
Again, allowing an alternative, secret project to exists increases project risk, cost, schedule, and the likelihood that the main project will fail. When we make a decision we should strangle all other ideas in their cribs. Before they grow and interfere with our decision and plans.
Even if we don’t agree with the choice we must still put our heart and effort behind the choice that’s been made. Bosses need to know, and we need to show, that we support the choice they made. We need to do everything in our power, in both word and deed, to give it the best chance of being successful. No whining, no complaining, and no “If I was in charge things would be different” sabotage and gossip.
Here’s a side-effect of supporting our bosses decisions, even if in our heart of hearts we don’t agree with them or they turn out to be wrong. The next time a tough or controversial choice needs to be made, and your boss has seen that you’re a team player, you’ll have more influence. She’s more likely to listen to you if she knows that when the decision is made you’ll work like hell to make it successful. No matter if you agreed with the decision in the first place or not. This means you have a better chance of getting things done your way the next time.
Who knows. Maybe even your boss might be right once in a while and we’ll learn something. Which is better than the alternative of getting the blame for sabotaging the project.
Next time: when a decision turns out wrong -why you shouldn’t have a “Plan B”.