Comments on: Why you shouldn’t rush into a solution too quickly https://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/ User Experience Design, Research & Good Old Fashioned Usability Tue, 13 Oct 2009 06:30:45 +0000 hourly 1 By: Design’s only purpose « transmogrifant https://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-111490 Tue, 13 Oct 2009 06:30:45 +0000 http://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-111490 t rush into a solution too quickly [...]]]> […] » Why you shouldn’t rush into a solution too quickly […]

]]> By: How many alternatives, concepts, or sketches are enough? « Simpler is better https://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87821 Mon, 19 Jan 2009 23:52:00 +0000 http://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87821 […] 20, 2009 · No Comments Harry Brignull’s post, Why you shouldn’t rush into a solution too quickly, about some of the slides from my presentation at OZIA has sparked off an interesting thread on the […]

]]> By: JeromeR https://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87812 Mon, 19 Jan 2009 20:10:25 +0000 http://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87812 How many alternatives are enough? There’s a risk in providing a specific answer, but here’s my rule of thumb. In my experience, when designing software, interaction, or web sites, you need three people to independently come up with five distinct ideas. When they get together to compare, you’ll see some overlap, but 9 times out of 10 the space will be sufficiently saturated to sovle the problem. Of course, divergence (generating ideas) is only part of the process. More is required to ensure success.

]]> By: Parag https://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87790 Mon, 19 Jan 2009 13:33:07 +0000 http://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87790 I was wondering what you meant by “Design is a wicked problem?” Maybe you can elaborate? thanks.

]]> By: Danny Hope https://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87785 Mon, 19 Jan 2009 12:00:15 +0000 http://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87785 An analogy can be drawn between patient design and crystals that have been allowed to form slowly – both are more robust and beautiful. God I sound like a hippy.

]]> By: Harry Brignull https://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87781 Mon, 19 Jan 2009 10:32:33 +0000 http://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87781 I think you can only ever be truly certain is in hindsight. Say 10 years later, after your product has lived its full lifecycle in the market, and then some.

But that’s not a helpful timeframe. ;-)

Initial research can define the problem space: the breadth and variety of the human problems you are trying to address. An understanding of the limitations of your chosen technology and your business objectives will define your design space. By having an understanding of both will let you know how “narrow minded” you are being.

In other words, if you do some good solid requirements gathering research to start off with, you will have a better idea of how many ideas/sketches you need to work with. But there is no absolute answer. Design is a wicked problem.

]]> By: Jakub Linowski https://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87779 Mon, 19 Jan 2009 10:08:14 +0000 http://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87779 This begs the question of how many design alternatives are enough? How can we know whether 3 or 50 alternative sketches or ideas have covered the design space? Any ideas?

]]> By: Context is everything « Simpler is better https://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87228 Wed, 14 Jan 2009 23:59:52 +0000 http://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87228 […] Harry Brignull’s post (Why you shouldn’t rush into a solution too quickly) about my OZIA presentation reminds me that I had every intention of extracting a few of the key […]

]]> By: Kevin Arthur https://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87207 Wed, 14 Jan 2009 18:38:57 +0000 http://www.90percentofeverything.com/2009/01/14/why-you-shouldnt-rush-into-a-solution-too-quickly/#comment-87207 This is an important point. Bill Buxton also makes it at length in his Sketching User Experiences book (and elsewhere).

]]>