3 ms·
I think the root cause of both this and the healthcare.gov failure is Gall's Law: http://en.wikipedia.org/wiki/Gall's_law http://en.wikipedia.org/wiki/Gall's_l
by nostrademons 13y ago
I think the root cause of both this and the healthcare.gov failure is Gall's Law:
http://en.wikipedia.org/wiki/Gall's_law http://en.wikipedia.org/wiki/Gall's_law
The problem with dealing with the government is that they have a long list of requirements that they absolutely must have. As a result, the programmers will work to satisfy all of those requirements, and will let the unwritten requirements (like, oh, "must not fall over when more than a dozen simultaneous users connect") lapse. Frequently with software you have to trade off requirements against each other; when you go to implement it you realize that what the customer actually wanted is self-contradictory. The essence of good product management is being able to make these trade-offs smartly.
One thing that all the big companies realize is that to build a large working system, you have to start with a small working system, and then evolve it so it keeps working at all points. Google doesn't dictate exactly how the product is going to turn out at the end - it sets a general direction and product statement, and lots of individual product managers or tech leads then work on figuring out the details.
- danenania 13y agoThis makes a lot of sense. As a consultant, I consider the most valuable and important service I offer to be analyzing, simplifying, and focusing a project's goals and requirements. If this part of the process goes well, it's usually smooth sailing on the design and implementation. If it gets impeded by obstinance, scope creep, or indecision, the project is probably doomed from the start. Being handed a pile of requirements that are sloppy and contradictory and then being told they are non-negotiable is kind of like being asked to build a submarine out of swiss cheese. No amount of money or expertise can make that work.