Comments on: Question the details

By: Paul Boag

Paul Boag — Fri, 08 Apr 2011 11:53:53 +0000

It is indeed :)

By: Jan Brašna

Jan Brašna — Thu, 07 Apr 2011 16:11:50 +0000

BTW is it Keynote you're using for the prototype?

By: Paul Boag

Paul Boag — Mon, 04 Apr 2011 12:41:22 +0000

Its all custom because this site has very specific requirements. That said, I am not convinced that much in my list couldn't be achieved with an off the shelf system and a bit of creativity.

By: Mike Healy

Mike Healy — Mon, 04 Apr 2011 11:54:10 +0000

Good post. I think this illustrates how wireframes can demonstrate to your client how you've thought about their problem. A visual design is nice, but probably makes it hard for the client to see anything other than the "look". The wireframe lets them see the real design underneath.

One question Paul — are you building a custom checkout from scratch to have such control over all these things?

By: Jeffrey B.

Jeffrey B. — Sun, 03 Apr 2011 16:23:10 +0000

I've gotten into web development in the last two years but I've never really thought about all these details that should be considered on a wireframe.

You have pointed out some great things that got me thinking on a totally different level when it comes to saving users time and get right to the good stuff and thanks for making me realize to go with the simple solution for the user. Again, these are things I usually not think about but now will.

Great post Paul, thanks.

By: Billee D.

Billee D. — Fri, 01 Apr 2011 17:16:18 +0000

I've been a staunch advocate of wireframing since my early days as a web professional. I've always felt that wireframes were sexy and really help me to focus on the details of the UI. To me there is no design without them; design work without specification is called "speculation" or simply dressing up the dross.

The thing that always struck me as odd is how little wireframing is used within the development processes on some of the teams and companies I've worked with. I recently worked with a fairly well-known US agency and after asking repeatedly about their wireframing process I received one of the oddest and totally asinine responses of my career:

"I don't care about the wireframe, William. The client wants to see the design NOW. You can wireframe all you want AFTER you've finished the design!!!"

I'll let that sink in for a bit...

Obviously this statement was based on an almost complete lack of understanding of what wireframes are actually for. But I also feel that a large portion of our community feel the same way this woman does. It's nice to see others who value and understand the benefits of wireframing.