Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am primarily a Web Developer (back end programming) - but intend to offer a complete service to my clients, from concept, to brand design, photoshop mock-ups and everything else in between. I'm aware that it's a good idea to outsource this design aspect of the project to someone that I trust. My question is more about the process:

I imagine that in order for the designer to really grasp what the client wants to create, they would need some sort of interaction. Therefore, does anyone know if it is common to bring both parties into a 3 way discussion? Or is it more common to get all of the info from the client, and then pass it onto the designer, and act as a back and forth middleman? Afterall, I am the designer's client.

Any insight into this would be great

share|improve this question
Thanks for making your first post to Stack Exchange Programmers. Your posts can be even more effective and you can earn a badge by reading the FAQ at . – DeveloperDon Oct 5 '12 at 1:07
up vote 4 down vote accepted

Don't be a middle-man between your graphic designer and your client. Be there for the first meetings between them. Make the designer write up a summary of each meeting and send it to all three of you. Once you know that the meetings are going well and that the summary is suitable to keep you informed, you can drop out and just read the summary emails.

You can join any meeting at any time if your designer and client need more management, either for scope, technical guidance, or other reasons. Projects move slowly enough as it is. The cost to everyone of "he said, she said" can be huge.

Maybe you double as an interior decorator, but even if you do, it's really hard to convey to your designer that your client wants more of a peach-blush background than a warm pink, then get back to the client that the designer thinks peach-blush will wash out the key-lime highlight in the logo, and that it will have to be changed to more of a spring-grass-green, etc. Don't be the middle man any more than you have to be.

share|improve this answer
Great advice here. You make it clear that in essence, any work between the client and designer, is really between them. Whilst I have outsourced the work for the designer, and will be responsible for their payment - they should treat my client as their own, and they should operate business as usual, with optional input from me. Would you agree with my summary? – Alex Sep 30 '12 at 11:51
Exactly. If you hire a professional adult, you should be able to set the scope (e.g., "Call me if it looks like this will take more than 20 hours") and mostly just let them do their work. Obviously, you want to stay informed, even when your intervention is not needed. – GlenPeterson Oct 2 '12 at 22:23

I would think that you would act as a middle man or more like a project manager. you would get the information from the clients on what they want and then pass that information on to the designer. this way you know what is going on so that either you can tell him what you need for coding or you know what he is doing with it for when you code. this is very necessary for functionality of the application. if you have worked together a lot, then you would have a better understanding of what the other needs to create a good product and could determine, per client, whether it would be beneficial to have both of you there with the client.

you should have several iterations as well, so if need be you can bring the designer to one of the iteration meetings, which is probably what I would do in the given scenario.

share|improve this answer

You should act as the project manager on behalf of the client, gathering their requirements and managing their expectations, while passing as much information onto the designer as they need (it's especially important that the designer be someone you know/trust).

I may be inclined to take the designer to the kick-off meeting though this should be decided on a per-project basis.
Once work has started, I'd bring the designer along to a couple of meetings (dependant on the size of the project) so they can get a better feel for your client, this will probably more important as the design progresses and becomes more finalized.

There's always a certain amount of fluidity in these projects and some clients like to "tinker" with the design right up to the last minute, having the designer in the room can be a great help here.

share|improve this answer

I vote that you embrace design to at least some degree. Some introductory material that I like is included in a Mix 09 talk Design for Developers by Robby Ingebretsen. If I remember right, there is material in this talk about making a team that includes several specializations.

Many of the development tools are pushing toward templating a huge portion of the designers job, particularly the interaction designers job, on to the programmer, or at least into his tool set.

Whether your designer is your partner or a subcontractor, as a trained software developer and key stakeholder, your involvement throughout the process can insure that requirements are elicited effectively and scope is defined to produce a cost effective and rapid solution for the client.

share|improve this answer
Thanks for the link, and thanks for your input on this – Alex Oct 5 '12 at 7:59

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.