Spec Wreck
Why is it so difficult to build to spec? (Just to be clear, I’m referring to all design fields, not just the software industry.)
Is compromise just an inherent part of the process? How detailed do our specs really need to be? Lately, my specs have become pretty lean. This seems to work well on a small scale because additional verbal communication adequately bridges any gaps, but what about on a larger scale when verbal communication might not be an option (due to different time zones, etc.)? Is creating detailed specs, only to have to compromise during development, really the best way to go?


Tweets that mention Spec Wreck | User Interface Trends -- Topsy.com
Jul 20, 2010
10:44 pm
[...] This post was mentioned on Twitter by Michael Davis, Russell Wilson. Russell Wilson said: New post: Spec Wreck (http://bit.ly/bpaI4T) http://bit.ly/bpaI4T #design #design_pattern [...]
Lindsay Holmwood
Aug 1, 2010
6:40 am
Not at all. Creating a spec overburdened with detail that’s will be thrown out half way through implementation because you made wrong assumptions is just wasting your time and your client’s money.
Vision is the key. Have an idea about where you want to go, and focus on the next step required to get you there, nothing more. As long as you’re always shipping something usable by the customer that’s deliverable in a short timeframe, you’ll be right as rain.