Temperatures were unusually high over the past few days. Today we had a true to God thunderstorm in the middle of the day along with unusually large hail (my wife says this is the largest she has seen). Here are some pics courtesy my wife :-)

my commentary on using progress to benefit me instead of being swept away by it.

I would amend the title to say "Do not stop with gathering requirements". Gathering requirements is just the first step, the science part. The subsequent steps are where the art and the intuition factor in. The job of the product manager is to collaborate with the other teams (engineering, services, support, docs, etc.) and try to flush out the true customer market need that is buried within those requirements. Sometimes it means extrapolating (customer is not seeing their own problem), and other times it means pruning (customer is treating multiple symptoms instead of one cause).
It's hard to see how any of this would have happened had Jobs hewed to the standard touchy-feely philosophies of Silicon Valley. Apple creates must-have products the old-fashioned way: by locking the doors and sweating and bleeding until something emerges perfectly formed. It's hard to see the Mac OS and the iPhone coming out of the same design-by-committee process that produced Microsoft Vista or Dell's Pocket DJ music player. Likewise, had Apple opened its iTunes-iPod juggernaut to outside developers, the company would have risked turning its uniquely integrated service into a hodgepodge of independent applications — kind of like the rest of the Internet, come to think of it.
Question Boxes leap over illiteracy, computer illiteracy, lack of networks, and language barriers.check it out.
