Systems Thinking. Four Universal Patterns of Thinking

And then we called it a day. Some days it didnБЂ™t work so we said, БЂњOK, weБЂ™ll do it again tomorrow.БЂ«There wasnБЂ™t enough time to do a second pass in a day. But about one pass in a day worked fine. Because it gives us about two hours to discuss it in the morning, about two hours to write the documentation or code it up. And if you spent four hours really thinking hard, thatБЂ™s a good dayБЂ™s work. So that worked very, very well. I donБЂ™t know how long we worked like that for. Ten weeks, twelve weeks, something like that. And then we got the basic framework and then we had more people. WeБЂ™d specified the architectureБЂ”now we could start growing it. WeБЂ™d get three or four more programmers in. Seibel: And then how did you divvy up the work for those new folks? Armstrong: Well, we knew what were prototypes and what were final versions. IБЂ™ve always taken the view of system design, you solve the hard problems first. Identify the hard problems and then solve them. And then the easy problems, you know theyБЂ™ll just come out in the wash ...»