RE: Discuss-interactiondesigners.com Digest, Vol 15, Issue 18

19 Dec 2004 - 3:25pm
9 years ago
1 reply
335 reads
Danny Bluestone
2003

Hey Rick

Sounds like a good process. I have a question for you.

Who manages the project once a strategy and budget have been agreed? Is it a
Producer/Interaction Designer or a different person such as a project
Manager?

Cheers
Danny Bluestone
Interaction Designer
Cyber-Duck

-----Original Message-----
From:
discuss-interactiondesigners.com-request at lists.interactiondesigners.com
[mailto:discuss-interactiondesigners.com-request at lists.interactiondesigners.
com]
Sent: 19 December 2004 20:03
To: discuss-interactiondesigners.com at lists.interactiondesigners.com
Subject: Discuss-interactiondesigners.com Digest, Vol 15, Issue 18

Send Discuss-interactiondesigners.com mailing list submissions to
discuss-interactiondesigners.com at lists.interactiondesigners.com

To subscribe or unsubscribe via the World Wide Web, visit

http://lists.interactiondesigners.com/listinfo.cgi/discuss-interactiondesign
ers.com

or, via email, send a message with subject or body 'help' to

discuss-interactiondesigners.com-request at lists.interactiondesigners.com

You can reach the person managing the list at

discuss-interactiondesigners.com-owner at lists.interactiondesigners.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss-interactiondesigners.com digest..."

[For those using lower bandwidth, or the DIGEST version of this list; the
administrators ask people to voluntarily trim their postings to only include
relevant quoted material.]

Today's Topics:

1. Re: [ID Discuss]: When to bring in technology (Rick Cecil)

----------------------------------------------------------------------

Message: 1
Date: Sun, 19 Dec 2004 10:40:29 -0500
From: Rick Cecil <rickcecil at gmail.com>
Subject: Re: [ID Discuss]: When to bring in technology
To: Interaction Designers <discuss at interactiondesigners.com>
Message-ID: <79f2ef56041219074044aa36 at mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII

> I'm interested at what point in the process we should make a decision on
> what technology should be used. Sure there's a big "it depends", but
> generally there is a hiatus point in the process where design cannot
> continue unless technology constraints are considered.

Our process has worked quite well. We have an interaction designer and
information architect conduct user interviews (we prefer contextual
inquiry, but are sometimes limited to phone conversations due to
budget constraints) and competitive analysis. From there, we develop
and scenarios. From the scenarios, we can extrapolate the features our
users will want/need/use.

With the feature list in hand, we meet with the Tech Lead and Business
Analyst to review the proposed features. We're not looking for
feedback on feasibility or budgetary constraints at this point--we
just want to communicate the purpose and need for each feature.

The Tech Lead takes the feature list back for review as does the
Business Analyst. The BA examines the features that are important to
the business, and the Tech Lead reviews the features that are easiest
to implement. Meanwhile, the IxD and IA are busy prioritizing the
features based on user wants/needs.

During this prioritization phase, the Tech Lead should be consulting
with his team to best determine what technology should be used or how
best to extend an existing technology.

Once everyone is finished, we meet and compare our prioritizations.
There is a lot of negotiation during this review process--and even
some heated arguments, but it works because everyone is involved in
the planning process. You virtually eliminate project sabotage from
the tech side and are able to generate management buy-in.

HTH,
Rick

------------------------------

_______________________________________________
Interaction Design Discussion List
discuss at ixdg.org
--
to change your options (unsubscribe or set digest): http://discuss.ixdg.org/
--
Questions: lists at ixdg.org
--
Announcement Online List (discussion list members get announcements already)
http://subscribe-announce.ixdg.org/
--
http://ixdg.org/

End of Discuss-interactiondesigners.com Digest, Vol 15, Issue 18
****************************************************************

Comments

19 Dec 2004 - 10:44pm
Rick Cecil
2004

A project manager manages the project. She has no experience in
actually designing or building digital products, so she has no bias.
We do, though, make sure the IxD and IA have support time during
development. Likewise, the Tech Lead has support time for the IxD and
IA during user requirements definition.

We've found, too, that our up-front research provides a general
road-map and that a good portion of the design is done during
development using this support time.

-Rick

On Sun, 19 Dec 2004 20:25:00 -0000, Danny Bluestone
<danny at cyber-duck.co.uk> wrote:
> [Please voluntarily trim replies to include only relevant quoted material.]
>
> Hey Rick
>
> Sounds like a good process. I have a question for you.
>
> Who manages the project once a strategy and budget have been agreed? Is it a
> Producer/Interaction Designer or a different person such as a project
> Manager?
>
> Cheers
> Danny Bluestone
> Interaction Designer
> Cyber-Duck
>
> -----Original Message-----
> From:
> discuss-interactiondesigners.com-request at lists.interactiondesigners.com
> [mailto:discuss-interactiondesigners.com-request at lists.interactiondesigners.
> com]
> Sent: 19 December 2004 20:03
> To: discuss-interactiondesigners.com at lists.interactiondesigners.com
> Subject: Discuss-interactiondesigners.com Digest, Vol 15, Issue 18
>
> Send Discuss-interactiondesigners.com mailing list submissions to
> discuss-interactiondesigners.com at lists.interactiondesigners.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> http://lists.interactiondesigners.com/listinfo.cgi/discuss-interactiondesign
> ers.com
>
> or, via email, send a message with subject or body 'help' to
>
> discuss-interactiondesigners.com-request at lists.interactiondesigners.com
>
> You can reach the person managing the list at
>
> discuss-interactiondesigners.com-owner at lists.interactiondesigners.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Discuss-interactiondesigners.com digest..."
>
> [For those using lower bandwidth, or the DIGEST version of this list; the
> administrators ask people to voluntarily trim their postings to only include
> relevant quoted material.]
>
> Today's Topics:
>
> 1. Re: [ID Discuss]: When to bring in technology (Rick Cecil)
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 19 Dec 2004 10:40:29 -0500
> From: Rick Cecil <rickcecil at gmail.com>
> Subject: Re: [ID Discuss]: When to bring in technology
> To: Interaction Designers <discuss at interactiondesigners.com>
> Message-ID: <79f2ef56041219074044aa36 at mail.gmail.com>
> Content-Type: text/plain; charset=US-ASCII
>
> > I'm interested at what point in the process we should make a decision on
> > what technology should be used. Sure there's a big "it depends", but
> > generally there is a hiatus point in the process where design cannot
> > continue unless technology constraints are considered.
>
> Our process has worked quite well. We have an interaction designer and
> information architect conduct user interviews (we prefer contextual
> inquiry, but are sometimes limited to phone conversations due to
> budget constraints) and competitive analysis. From there, we develop
> and scenarios. From the scenarios, we can extrapolate the features our
> users will want/need/use.
>
> With the feature list in hand, we meet with the Tech Lead and Business
> Analyst to review the proposed features. We're not looking for
> feedback on feasibility or budgetary constraints at this point--we
> just want to communicate the purpose and need for each feature.
>
> The Tech Lead takes the feature list back for review as does the
> Business Analyst. The BA examines the features that are important to
> the business, and the Tech Lead reviews the features that are easiest
> to implement. Meanwhile, the IxD and IA are busy prioritizing the
> features based on user wants/needs.
>
> During this prioritization phase, the Tech Lead should be consulting
> with his team to best determine what technology should be used or how
> best to extend an existing technology.
>
> Once everyone is finished, we meet and compare our prioritizations.
> There is a lot of negotiation during this review process--and even
> some heated arguments, but it works because everyone is involved in
> the planning process. You virtually eliminate project sabotage from
> the tech side and are able to generate management buy-in.
>
> HTH,
> Rick

Syndicate content Get the feed