|
Anyone else have an opinion? ;)
----- Original Message -----
Sent: Thursday, April 04, 2002 2:58
PM
Subject: Re: Wireframes and clients
In my opinion that's the only way to do wireframes, but others
might disagree. I tend to use wireframing almost as a sales pitch. I try to
spend no more than a couple hours on a wireframe, usually within the first few
minutes of meeting with the client. Once we're past the hand shaking and
schmoozing and they start explaining what they want their application to do,
I'll usually interrupt them and say: "let me take some structured notes".
(this is when I whip out the laptop with the wireframe tool) After they've
explained something, I'll walk through the wireframe and explain it back to
them. They'll either say "yeah that's it" or "wait, change blah blah blah".
I NEVER finish a wireframe. I use it for a couple hours to take initial
notes and then I move onto prototypes. My clients prefer seeing the
application's front end than seeing a description of the application's front
end.
Steve Nelson
Craig wrote:
Hey all. I am thinking about using wireframes. I have
2 big clients, one of which is a CGI/Unix programmer who is used to doing
"fly by the seat of your pants" programming. He wants to limit the
Analysis and Design phase and just see some work up and running. The
other client is totally open to design phase but she is very
demanding. Has anyone had luck with using wireframes to quickly and
efficiently gather requirements? Please let me know what you
think. Funny thing is,
both sites are likely going to be done using ASP.NET, NOT fusebox or
coldfusion. Craig
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
|
