Igal Koshevoy
unread,Dec 3, 2009, 3:24:13 PM12/3/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to pdxcr...@googlegroups.com
Does anyone have some suggestions on how to best explain the concept and
intent of wireframes/mockups? Either a response or a link or such would
be helpful.
I keep running into situations where I just can't get a client to
understand that I'm showing them a picture in hopes of establishing
bi-directional communications with them. That I want us to have a shared
vision and understanding of what their future product should be and how
it should behave. That I want to collaboratively create an artifact
representing what I'm going to build for them.
Conversely, I'm struggling to get them to understand that I'm not going
to implement features that aren't in these pictures, am not trying to
waste their time by randomly showing them unrelated abstract artworks,
and am not seeking feedback on the purely artistic merits of these
typically low-fi images or whether they "pop" or are "shiny" enough.
I realize that there's a limit to what can be done, but I can't help but
think that there's got to be a better way. I'm frequently reminded of
trying to teach Boy Scouts to use maps, where most would quickly catch
on and grow in their knowledge, but a few just couldn't seem to
understand that there was a relationship between the squiggly lines on
the paper and the territory in front of them.
-igal