Discovery - finding out what the client needs
Design - turning wireframes into comps
Development - turns out the templates
Deployment - translates templates on the back end
It's important to admit our mistakes because it allows our process to improve.
Discuss the key points of the design before the coding starts to get a sense of the priorities. Make sure the developer is invested in the work.
Who is the client, really? Treating your co-workers as clients can be a helpful exercise when you're handing off your work to them. You want to have a complete understanding of the work.
If there is anything important about your design, make sure your developer knows where to find it. You spend time making it good for the client but making it work for the developer isn't at the front of your mind.
As a developer, make sure the designers get to see your work to make sure you've met their needs.
The new W3C site is pretty....we got a preview :-)
Don't fear prototyping - if it will help the client visualize it, jump on it.
Make sure your process isn't interfering.
(This presentation was a lot of examples, so not many notes to be had)
No comments:
Post a Comment