Title: When is design done?
Context: We should all be familiar with the Agile definition of done, but what is the design definition of done? Probably – no – DEFINITELY, not the same thing.
Synopsis: There are lots of cues that let you know when a project is done, i.e. you run out of money, you run out of time, your manager tells you that you are done and should go home and spend time with your family instead of sitting in front of a computer until 2 AM every night for a month straight. But let’s be honest, that last one never happens. But how do we ourselves, as designers, decide when something that we are working on is done? From Microsoft Word (was done in 1991) to Evernote (may never be done) to Photoshop (keeping pace with technological advancements means never having to say you’re done) software is notoriously hard to “finish”. For myself, I probably can’t define “done”, but I know it when I see it.
Best Bit: “Design is done when its evolution plateaus. A couple of versions are released with little more than rearranging the deck chairs. Rework or changes to the interface reflect passing fashions rather than fundamental shifts in direction or functionality. Innovations in the marketplace or in technological breakthroughs are not incorporated or addressed in the design. Evolution grinds to a halt, the product ceases to advance in meaningful ways.”
via stefanklocek.com
Leave a Reply