Delivery Logistics

by Laura Kalbag

7 Reader Comments

Back to the Column
  1. Great way of thinking, I love to combine the design and development processes. This gives an interesting twist in the whole process as you can test your designs immediately. I think it is a good way to have developers give advices during the design phase.

    Copy & paste the code below to embed this comment.
  2. Good read Laura and fine points to make. I would also say that design process expectations change with region and tech-savvy. Building a website for a small mom and pop business in the sticks where they’re still running windows XP on a machine they bought in 2003 is a much different design presentation process than building one for a large company in the city where every employee is attached to a smart phone. It is GOOD to guide the client toward YOUR process in design and development but I would never be afraid to tailor that experience just a bit to better fit the client’s capacity to understand it. If you hit a the mom and pop client with the same fervor and pitch as the big city client, that is also a recipe for disaster. The methods you use to get to the design can be similar but just remember who you’re talking to when presenting it.

    Copy & paste the code below to embed this comment.
  3. Yes, It’s about educating the client. The best motivator I’ve found for breaking clients of predetermined expectations is money. If you explain why they don’t need X, Y, and Z and it would save them money by not implementing it. The clients are usually open to the idea.

    Copy & paste the code below to embed this comment.
  4. I understand the need for flexibility but I’m curious – if you aren’t outlining your process or deliverables as part of your estimate and proposal, what exactly are you proposing to the client? How do you estimate and schedule work when you don’t know what tasks you might perform?

    Copy & paste the code below to embed this comment.
  5. Terrific article. Clients hire us for our expertise—because we have a skill they need but do not have internally. So basing everything off what the ‘client expects’ is putting our job on their shoulders.

    Assuming that: a) we know what we’re doing and b) the client needs to be helped through the process (i.e. we take the lead) has always led to better, less stressful projects in my experience.

    You can still respect the client without expecting them to know best.

    Copy & paste the code below to embed this comment.
  6. Hi Jessie. I would definitely outline my process, and through that I tend to explain that there are these different types of documents that I’ll use to communicate my ideas, and that I’ll try to use them when I think is most appropriate.

    Here I also try to emphasise to the client that if they feel uncomfortable with the fidelity of a document, or that it needs more work for them to understand where I’m coming from, then I’ll be happy to find a more effective way to communicate with them.

    Copy & paste the code below to embed this comment.
  7. I made a set of worksheets that goes over possible deliverables, activities, and risks for each stage of a UI Design project.  Sometimes I’ll go through them with a client to work out their project’s specific needs, and that’s also a good time to nudge them towards or away from deliverables for their own sake.  It also includes the idea of formality – a set of requirements can be a bullet list in an email if that hit’s the right level of communication.  A wireframe can be delivered as a hand-drawn sketch if the designer and developer really are on the same page (so to speak).

    Copy & paste the code below to embed this comment.