Alan Cooper's Goal-Oriented Design process - step-by-step

30 Apr 2008 - 2:53pm
6 years ago
5 replies
2235 reads
Brandon E.B. Ward
2008

Anybody have a super-distilled version of the Cooper design process? I'm thinking something like:

1. Research user goals.
2. Refine research results.
3. Develop personas.
4. Write high-level scenarios.

Etc. etc.

I guess one could make one based on the chapter/section titles from About Face 3, but ... If anyone has something like this that'd be grrrrEAT!

B

Comments

30 Apr 2008 - 7:30pm
Chad Vavra
2008

I haven't, but I did recently come up with a distilled philosophy.

"To create a human connection in technological products with usable
form and content by understanding business and user desires, needs,
and motivations. "

My company uses a version called,

"Discover, Design, Develop, Deploy"

but I I worry sometimes as Design is so early and so not what is
traditionally "design".

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=28587

1 May 2008 - 10:42am
Stew Dean
2007

Looks like a fairly standard approach.

I split design in to Concept and Detail and use an overlapped
iterative approach to phases - no water fall or throwing things over
the wall.

I also use a task based process rather than a goal based, this is an
evolution from goal based and attempts to define the users by what
they do, not what car they drive (as can happen with badly created
personas). In all cases tasks, users etc I try to keep as real as
possible.

Stewart Dean

2008/5/1 chadvavra <chad.vavra at imedstudios.com>:
> I haven't, but I did recently come up with a distilled philosophy.
>
> "To create a human connection in technological products with usable
> form and content by understanding business and user desires, needs,
> and motivations. "
>
> My company uses a version called,
>
> "Discover, Design, Develop, Deploy"
>
> but I I worry sometimes as Design is so early and so not what is
> traditionally "design".
>
>
> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
> Posted from the new ixda.org
> http://www.ixda.org/discuss?post=28587
>
>
>
>
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> Unsubscribe ................ http://www.ixda.org/unsubscribe
> List Guidelines ............ http://www.ixda.org/guidelines
> List Help .................. http://www.ixda.org/help
>

--
Stewart Dean

1 May 2008 - 11:14am
Chad Vavra
2008

Do you find that a Task Based approach silos your product?

I feel like it is too easy to focus on a task and end up forgetting
that it may only be part of a larger goal.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=28587

2 May 2008 - 6:09am
Jarod Tang
2007

Hi Brandon,

>From my humble experience, there's no so much needs for the detail or
distilled version of the process. but instead, better have insight on
the metaphor of the process ( in his book, cooper compare it with
movie making). and the key points runs along the process:
1. concept model
2. behaviour pattern
3. persona for user modeling
4. etc
this makes use less bounded to specifice steps (or even create
localized version that fit your own problem)

Cheers
-- Jarod

On Thu, May 1, 2008 at 3:53 AM, Brandon E.B. Ward <brandon at pluggd.com> wrote:
> Anybody have a super-distilled version of the Cooper design process? I'm thinking something like:
>
>
> 1. Research user goals.
> 2. Refine research results.
> 3. Develop personas.
> 4. Write high-level scenarios.
>
> Etc. etc.
>
> I guess one could make one based on the chapter/section titles from About Face 3, but ... If anyone has something like this that'd be grrrrEAT!
>
> B
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> Unsubscribe ................ http://www.ixda.org/unsubscribe
> List Guidelines ............ http://www.ixda.org/guidelines
> List Help .................. http://www.ixda.org/help
>

--
Designing for better life style.

http://jarodtang.spaces.live.com/
http://jarodtang.blogspot.com

2 May 2008 - 9:25am
Charles Hannon
2008

One thing I would add to this thread is the use of "story" in the
Cooper method as a way of doing requirements definition. This is more
fully developed in About Face 3 than in previous editions. When I
teach this book, I find "story" (through context scenarios, key
path scenarios, and validation scenarios) an effective way to define
data elements and functional requirements, especially in relation to
the personas that students have previously developed.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=28587

Syndicate content Get the feed