Refinement vs Exploration

Cool illustration that explains where refinement and iteration should take place. While there are different theories for approaching a problem, I still think research and exploration always comes first, followed by prototypes and iteration.

Explore1.jpeg

  • http://twitter.com/miqcie Chris McConnell

    I find that drawing out the problem often reveals the solution. 

    • Anonymous

      Got any sketches? I’d love to see your process. :)

  • Jon Fukuda

    Fantastic – this is often a hard message to convey – Design is a process.. thanks for highlighting this!

    • Anonymous

      Yah, there are several theories for approaching a problem now-a-days. Engineers and developers typically like to start building a prototype immediately and iterate—This is kind of like the 37signals approach. On the other hand, designers typically like to cast a wider net to explore a problem space first, and then hone in on the problem they’re solving. There are pros and cons for both theories. I think the way for designers to make more impact is to think like an engineer… try to spend less time on casting a huge net, and get to a prototype faster. By having a prototype, you can get user feedback earlier—this can give a designer concrete direction.

      I think the key is not to release anything that could be a bad experience—this could taint the brand you’re designing. It’d be terrible if your brand was associated with words like, “confusing”, “takes too long”, or “miserable”. It’s hard to change that reputation afterwards.