Oh man , do I have a story for you. How many times have we been in charge of a product when “higher powers” have come along with suggestions on how to make the product better? Or perhaps they suggest features that the product just must have before it goes out the door?
These types of suggestions can kill a product no matter how carefully you have nurtured it up to this point. The impacts can range from timelines, expenses, all the way to final product price. So much for your best laid plans.
George Neville-Neil over at the Communications of the ACM is well aware of events like this. He tells the story of the the good ship Vasa and this tale has a lot of warnings for us Product Managers.
This is a story that starts back in 1626 when the king of Sweden, King Gustavus Adolphus, ordered the building of the Vasa. It took two years to create this ship. King Adolphus was keen to have it because at the time he was trying very hard to rule the Baltic Sea.
Just to prove to you that things really don’t change, you need to understand that King Adolphus was deeply involved in the design of all of the ships in his naval fleet. Can you say “too much senior management involvement”?
Back in the 1600’s, warships had one deck of cannons on both the left and the right side of the ship. The commission orders for the Vasa ordered that she be created with this design.
Now at just about this time, good King Adolphus discovered that the Poles had somehow created ships with two decks of guns on them (for a total of four decks of guns). Needless to say the King developed a serious case of cannon envy.
Since he was king and could basically do anything that he wanted, King Adolphus modified the design of the Vasa to now include two decks of guns. To the king’s credit, on paper the Vasa was now the most powerful ship of its day and had a great deal of firepower.
As with all great senior management plans, this one had just one little flaw. The designers of the ship realized that there was now a problem and attempted to explain that to the king. What they had discovered was that the ship’s design called for it to have too little ballast in order to support two heavy gun decks. They believed that building the ship that the king had designed would result in a ship that would be unsafe to sail.
You know how this story goes – it’s good to be king. The king wanted his ship and he wanted it the way that he had designed it. The building of the ship continued.
(This is my favorite part of the story that George tells) In 1628 the ship was done and ready for initial testing. One of the tests that they did was a stability test. In this test, 30 sailors were selected and asked to run back and forth from side-to-side on the ship’s deck. If the ship didn’t tip over and sink then it was basically good to go. During this testing of the Vasa, the ship started to tilt widely and they ended up cancelling the test.
You would think that this was the end of the story. But it isn’t.
On August 10th, 1628, the king’s mighty ship the Vasa set sail for the first time. The ship got about a mile away from the dock when a good stiff breeze came along and knocked the ship sideways, she took on too much water, and then she promptly sunk.
Of course there was an investigation in order to find out what had gone wrong. Since the king, of course, could not have been the problem, the question was who was to blame. In the end, the sinking was chalked up to an “Act of God” and forgotten.
However, in the 1960’s the Vasa was raised from the sea and was placed in a museum in Stockholm. If you ever get there, make sure that you drop in and see it – a shrine to all product mangers who’ve had to deal with meddling senior management.
Have you ever been given “suggestions” from senior management for your product? Where they any good? What did you do with them? Was the product made better by them? Leave me a comment and let me know what you are thinking.