
I have designed quite a few websites in my time and some of them I have even built and coded. The biggest trouble with being a designer working on web projects is undoubtedly working with developers. Good ones are hard to come by, and often you are working to completely different schedules – in my experience, they work nights and mornings to have their weekends off, while I need a little more sleep than that. Couple that with a designers need for perfection and a developers need for function and you have the potential for some sleepless nights and heavy frustration. In my experience, as with all things, it really comes down to good, open and honest communication. Similarly to briefing in a client, I’ve got some simple tips for briefing in a project to your dev team: 1. Always start with a face to face meeting. As a small and local business owner myself, I believe it’s incredibly important to support those Aussies who are working on their dream, so I strictly work with Australian developers. I have worked with a number of them over the past few years and the most successful projects have worked out when there was a face to face meeting, earlier in the design phase – once you’ve gotten an overall concept signed off by the client. Sit down, have a coffee and talk about what you expect from them; what you will do, where you go from here. Then take the time to explain how you think it will function, then get their expert input. If you don’t know about CMS’s or development languages because you’re newer to the game, that’s fine – but lean on your developer to make these recommendations so you don’t over promise to the client. 2. Project manage. At the end of the day, this is your client and it’s absolutely your ass if you can’t deliver. So work out a schedule (Gantt Chart for those in marketing), allow a buffer of time and start riding your developer a little. Anyone working on a far off freelance project is going to need a nudge, so drive the beast. 3. Content. Ultimately in website development nothing can be done by your developer without content. Text, images, graphic assets, the whole works. Get it together in web optimised .jpegs, sort it into page folders in your Dropbox, name everything using a…
Read More