July 16th, 2009
For today’s designers and developers, the biggest challenges involve how we transition, or hand off, a project at each phase. We know that a conveyor belt system of project management creates issues that can prevent your project from being a successful design. Why get everyone on the same page? Designers will have more control in getting the vision implemented the way they imagine it, and Developers can begin thinking about the problems they will need to solve.
Take that two-way communication out of your process, and the design that emerges from the development process doesn’t work the way we thought it would. You increase your development costs, and deliver a product that’s lost all of it’s interactive goodness.
Unless you’re doing your own implementation, practically impossible for a serious production application, you need to find a way to succinctly communicate what’s important and how it should all work. In this week’s issue of UIEtips, I bring back an article, Getting the Most from Design Deliverables, that discusses how the best design teams go about successfully communicating their ideas to the development team. I think you’ll really enjoy it.
Also, we think this article ties in nicely with our upcoming UIE Virtual Seminar: Comps vs. Code: Case Studies on Collaboration Between Site Designers & Developers with Ethan Marcotte. On July 30, Ethan will use four case studies to teach some insightful lessons about the collaboration between designer and developer. See a preview.
How do you hand off projects at the transition phases in your organization? What types of reviews do you build into the transitions? Join the discussion below.Tweet