I think that's a sure sign that you need to move from the wireframe to a prototype. You will be amazed at their quick attention to detail on the prototype. I had a client last week that said, no joke, "wow, this devnotes tool is REALLY powerful!". A silly little textbox gets a comment like that. Amazing.
Seriously, let them see the application. Build the front end and their eyes will light up. Steve Kevin Roche wrote: > Hi, > > I have a client that steadfastly refuses to look at the wireframes. I still > build them because it forces me to to ask questions that in the past might > have been forgotton or caused assumptions to be made. > > Where does that link go ? > > After you ask that question for every link on every page you have solved > your problems and thw ireframne is as good a wayt as any to document the > collection of the answers and make sure you don't havbe any missing pages. > > Kevin > > -----Original Message----- > From: John Farrar [mailto:[EMAIL PROTECTED]] > Sent: 05 April 2002 14:30 > To: [EMAIL PROTECTED] > Subject: Re: Wireframes and clients > > Yes, > > Wireframes are the way to go. Yet, it takes a bit of sales ability to get > the client to wait for the interface. In the end you will have a better > product if you can outline the project without the client being sidetracked > by the container. The variables are the person selling the project and the > person who it is being sold to. It would not be reasonable to loose a job, > just so you could avoid the container until the project functions were > completely outlined. Yet, it would be better for you... and the client to do > full needs discovery and outlining. It is sometimes better to not have a > project that is not defined... because there is no end of attempts to > satisfy the client. If you can get by without contracts that are not > wireframed it is best... but, you in the end have to make the call. After > all, we all need to eat! > > John Farrar > > >>> [EMAIL PROTECTED] 04/04/02 11:37PM >>> > Anyone else have an opinion? ;) > ----- Original Message ----- > From: Steve Nelson > To: [EMAIL PROTECTED] > 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 ==^================================================================
