Writing a Brief for a Developer
22 Feb 17
Writing a brief for your new website, or any kind project, can be confusing. How much information is too much information? What details should you include and what if they change? Don’t worry, we’re here to help you write the perfect brief for your developer!
The easiest (and best) way to start your brief is with a quick description of your company. It sets the scene for your developer or agency and gives them an insight into the business. With all successful relationships there needs to be mutual understanding, so it’s useful at this point to read up on them too, so you’re comfortable they’re the right fit.
Once you’re happy with the overview of you/your company, start to consider what’s driving your need for a new website. It may be encroaching competitors, feedback from users or perhaps you don’t have a website at all yet. This will help shape the designs and features of your website and form the basis of your specification.
Next up is your Minimum Viable Product (MVP), you’ll want to have a clear idea of the minimum your developer needs to deliver to satisfy your requirements. This doesn’t mean you’ll get a basic site, it means when you receive your project you will definitely get something that solves your core problems.
Specifications can seem tricky, especially if you’re not a techie! At Cold Banana Studio all our developers are pros at translating geek speak (they have loads of practice when talking to our marketing team), just give as much description as you can! Things to bare in mind is the platform you’re using or want to use if you need marketing, payment or other integrations.
Set a good example! The design is one of the first things someone will notice when they view your website so this is another high priority item. You may have templates you wish to use, a rough idea, or brand/style guidelines you want following, either way, we want to know.
And lastly, don’t be afraid to be upfront. If you’re working within a certain budget, or to a tight deadline, let your developer know. It’s much better to have hard conversations at the beginning so everyone knows the lay of the land than risk crossed wires at the end. Your developer won’t think you’re a client-zilla, they’ll appreciate your candour!
One last thing, there’s a reason it’s called a brief, keep it clear, concise and compact 😉.
Author: Kira Bull