[Sigia-l] Axure

[Matthew Hodgson]

Andrew is right. Conceptual is the best way to go -- rapid, iterative, dirty, rough, with all its wrinkles so we can get to best articulate how the UX will operate.

M

________________________________________
From: sigia-l-bounces at asis.org [sigia-l-bounces at asis.org] On Behalf Of Andrew Boyd [facibus at gmail.com]
Sent: Thursday, 1 November 2007 2:22 PM
To: W Evans
Cc: SIGIA-L
Subject: Re: [Sigia-l] Axure

On 11/1/07, W Evans <wkevans4 at gmail.com> wrote:

> I am moving far away from the old "define, document, wireframe, prototype,
> test, build, deploy" process - and thinking that prototyping, fast, nasty,
> ugly prototyping - should move far upstream in the process - way before a
> prototype for the purposes of functional and design specification is even
> thought of being done.

Hi Will,

I'm coming to the same conclusion. That conceptual design should be
done before the project proposal, before the funding proposal - use it
to define the business case/statement of need (or local equivalent)
prior to going anywhere near the high level design spec.

And yes, I take your point that design is not linear, nor is it a
stage in a wider process, but an ongoing activity (albeit one that may
have strategic-within-project and tactical-within-project tasks).

Best regards, Andrew

--
---
Andrew Boyd
http://onblogging.com.au
------------
IA Summit 2008: "Experiencing Information"
April 10-14, 2008, Miami, Florida

-----
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable Archive at http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l at asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you received this message in error or are not the intended recipient, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained herein. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Company. The recipient should check this email and any attachments for the presence of viruses. The Company accepts no liability for any damage caused by any virus transmitted by this email. Thank you for your cooperation.