Public Voice Network
- Shit QBNers think 7070
- Pic of the Day 5937759377
- Ageless Male
- Ageless Male
- Shit QBNers Say 131131
- Ageless Male
- FMT 020312 4747
- Show Yo Dog 2012
- Ageless Male
- Light in the box coupons
- Multicolored logos? 1414
- Politics 1759817598
- blog 5558055580
- Light in the Box Coupons
- Vid of the Day 1096110961
- TYPO San Francisco 55
- Suggest a good movie... 936936
- Logo from Locked PDF? 33
- American Musical Supply C… 11
- intern -> job 2121
- Your Last Concert 375375
- the gif animation thread 1132211322
- Steve Jobs FBI file 66
- What are you listening to… 41734173
Client Approval Process 2626 Responses
Last post: 1 year, 11 months ago | Thread started: Mar 12, 10, 8:21 a.m.
- persona_non_grata
What approval process do you use in your respective industry. Print/web/design
just something briefI'm looking to get some ideas for a proposal i've been tasked with...(for a website) - but this could help everyone
I'm thinking :
concept approval with set # of revisions
functional [technical] demo for IT team
final approval of design concept
...[build time]...
final review and revision- Mar 12, 10, 8:21 a.m. – Permalink
- persona_non_grata
Peter Principle
http://en.wikipedia.org/wiki/Pet…
- Dog-earMar 12, 10, 8:27 a.m. – Permalink
- bulletfactory
I just tell the client to back the fuck off and let me do what they hired me to do.
* haven't worked in years.
- Dog-earMar 12, 10, 8:32 a.m. – Permalink
- persona_non_grata
great advice zray - looked up content delivery plan , great stuff
- Dog-earMar 12, 10, 9:32 a.m. – Permalink
- persona_non_grata
yes I was thinking of what level to incorporate the client. They aren't that technical at all. But they may be more comforted by seeing the wire frame stage....something I am wrestling with.
- Dog-earMar 12, 10, 9:37 a.m. – Permalink
- ItalianStallion
I made a web service. Clients can download and approve documents. It also handles file versions.
It was a revolution for me, no more mail attachments and confusion...- Dog-earMar 12, 10, 9:40 a.m. – Permalink
- d_rek
Oops, however, it is completely option to show them that work. I have found that most clients find wireframes useful. Actually I cant think of one who has said "Wtf is this shit where's my beautifully designed website at. Why are you showing me lines and squares?"
- Dog-earMar 12, 10, 9:58 a.m. – Permalink
- d_rek
I understand the mindset where idiots is coming from, i just don't agree with it. I believe a designer's job, on occasion, is to also educate the client about the creative process. The deeper the understanding they have of it the more they can appreciate what goes into it. If all they see is a pretty website then they will simply commoditize and devalue the work you have done.
- Dog-earMar 12, 10, 10:31 a.m. – Permalink
- idiots
i stopped holding my clients hands a long time ago. they come to me for a service. i assume they have the respect to believe my choices/reasoning. i don't tell the mechanic how to work on my car, i only tell them what's wrong, i don't tell the hairstylist how to cut my hair, only how i want it to look, their methodologies are why i pay them. same goes for my service/client relationships
- Dog-earMar 12, 10, 10:35 a.m. – Permalink
- Dancer
That is a very dogmatic approach idiots. I always ask my mechanic more info of what is involved... I like to learn.
My clients really appreciate that I have time to explain the process and what is involved they really feel like they are getting service for the money they pay. I tend to get a "I never knew all of this was involved" statement.
- Dog-earMar 12, 10, 10:47 a.m. – Permalink
- dMullins
Here is what my schedule for services looks like typically for a freelance project:
1. Kick Off and Client Brief
2. Strategy / Position Meeting to Review R&D First Steps
3. Create Final Project Creative Brief
4. Design Concepting
• Brainstorms • Mood Boards • Style Screens • Writen Rationale • Brand Structuring / Positioning • Wireframes • Etc.5. Internal Review (with my team)
6. Feedback / Amends Meeting with Client
7. Revisions
8. Internal Sign Off For Amends (check vs. strategies, revision requests, etc.)
9. Client Review for Amends
10. Prototyping (for web, per your example, this would be slicing/staging)
11. Prepares Technical Brief for Launch, Submit Prototypes to Client for UI/UX Review, Etc.
12. Prototype Amends Meeting
13. Implementation
14. Project-wide sign-off by client
- Dog-earMar 12, 10, 10:54 a.m. – Permalink
- idiots
don't get me wrong, they are informed, but not overly so as i hold their hand explaining why i am going from one step or thought to the next. i'd rather display a working comp with page styles for a real experience instead of asking them to imagine (what am i getting paid for again)
and if you refer to my car analogy as getting fleeced, wake up, my point is yeah, ok the drive shaft broke, that banged some other stuff and fucked up the yoke on the rear end... just fix it. i don't need to know how you'll take it apart and put it back together, i trust you can, you're a mechanic....
ok so you're going to wash my hair, then trim up the sides, then adjust the top length, fade the sides and back into the top and then buzz trim the edges?
who fucking cares!? just cut my hair
i hope you get it.
quite simply, if you could have designed a simple mock comp of size, dimension, and color but instead gave your clients black border boxes you're wasting both their time and money
- Dog-earMar 12, 10, 10:54 a.m. – Permalink
- dMullins
In my opinion, the argument here isn't whether or not to do wireframing (if you don't that's up to you, but I think it's silly that some people do not). The argument sounds like it's really whether to show them to the client, or use them for your personal processes only. The answer to that will be one of personal preference, I believe.
- Dog-earMar 12, 10, 11:02 a.m. – Permalink
