A friend emailed me this link to a list of Design Laws put together by Dave Akin of the University of Maryland. Having been involved in spacecraft and space systems design and development for his entire career, including teaching the senior-level capstone spacecraft design course, for ten years at MIT, Dave Akin compiled a list of 40 wise maxims, some of which I’ve included below as being particularly relevant to rowing coaching!
- To design a spacecraft right takes an infinite amount of effort. This is why it's a good idea to design them to operate when some things are wrong
- (de Saint-Exupery's Law of Design) A designer knows that he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away
- Engineering is done with numbers. Analysis without numbers is only an opinion
- Design is an iterative process. The necessary number of iterations is one more than the number you have currently done. This is true at any point in time
- In nature, the optimum is almost always in the middle somewhere. Distrust assertions that the optimum is at an extreme point
- Not having all the information you need is never a satisfactory excuse for not starting the analysis
- When in doubt, estimate; in an emergency, guess. But be sure to go back and clean up the mess when the real numbers come along
- Sometimes, the fastest way to get to the end is to throw everything out and start over
- There is never a single right solution. There are always multiple wrong ones, though
- Design is based on requirements. There's no justification for designing something one bit "better" than the requirements dictate
- (Edison's Law) "Perfect" is the enemy of "good"
- (Shea's Law) The ability to improve a design occurs primarily at the interfaces. This is also the prime location for screwing it up
- The previous people who did a similar analysis did not have a direct pipeline to the wisdom of the ages. There is therefore no reason to believe their analysis over yours. There is especially no reason to present their analysis as yours
- The fact that an analysis appears in print has no relationship to the likelihood of its being correct
- Past experience is excellent for providing a reality check. Too much reality can doom an otherwise worthwhile design, though
- The odds are greatly against you being immensely smarter than everyone else in the field. If your analysis says your terminal velocity is twice the speed of light, you may have invented warp drive, but the chances are a lot better that you've screwed up
- A bad design with a good presentation is doomed eventually. A good design with a bad presentation is doomed immediately
- (Larrabee's Law) Half of everything you hear in a classroom is crap. Education is figuring out which half is which
- When in doubt, document. (Documentation requirements will reach a maximum shortly after the termination of a program.)
- It's called a "Work Breakdown Structure" because the Work remaining will grow until you have a Breakdown, unless you enforce some Structure on it
- (Varsi's Law) Schedules only move in one direction
- (von Tiesenhausen's Law of Program Management) To get an accurate estimate of final program requirements, multiply the initial time estimates by pi, and slide the decimal point on the cost estimates one place to the right
- (Mo's Law of Evolutionary Development) You can't get to the moon by climbing successively taller trees
- (Patton's Law of Program Planning) A good plan violently executed now is better than a perfect plan next week
- (Roosevelt's Law of Task Planning) Do what you can, where you are, with what you have
- Any run-of-the-mill engineer can design something which is elegant. A good engineer designs systems to be efficient. A great engineer designs them to be effective
- (Henshaw's Law) One key to success in a mission is establishing clear lines of blame
- Space is a completely unforgiving environment. If you screw up the engineering, somebody dies (and there's no partial credit because mostof the analysis was right...)