client approval of wire frames
Out of context: Reply #6
- Started
- Last post
- 11 Responses
- PonyBoy0
it's hit or miss...
... there are always clients who 'get it' as they're not <em>morons</em>... but then you have plenty of them too...
... they're the same people (those morons i mentioned above) who look at an actual 'design comp' that's been clearly labeled and vocally verified that this comp is indeed for LOOK AND FEEL ONLY. Alas... that 'lorum ipsum' scares the shit out of them... I can only imagine how that client reacts to lorum ipsum... IN A WIREFRAME!!
:) bottom line... Account Managers & sales folks should pre-judge the client and see if they're capable of handling such 'updates' w/out losing their shit.
I got a few agency projects that have just been draaaaaggggging mad butt because the client needs to be educated at what they're looking at every step of the way. If it's a long-term client who's paying a monthly fee (server maintenance... hosting... site updates)... then yeah, you grab your ankles and smile knowing the sun comes up in the morning...
... else... no... don't share the freakin' wireframes... that's more of an internal blueprint (in my mind) that makes sure the AI, AM, AD (WHAT'S THE NEW GhAY-BUTT 2.0-FUCKING ACRONYM FOR A DEVELOPER?!!)... blah blah blah... TO MAKE SURE ALL PEOPLE WORKING ON THE PROJECT ARE 'ON THE SAME PAGE'.
