HOW TO AVOID A FIGHT WITH YOUR WEB-DEVELOPER
Getting what’s in your head into the head of another person is hard work. Especially if you’re not sure what you want yourself.
The old adage that “the faintest ink is more powerful than the strongest memory” applies here so make sure you commit your thoughts in a document rather than a conversation with your developer.
tip 1: style
Gather examples of sites you like from a style perspective. This will act as a visual guide and reference point when discussing the “look” of your site with your developer. This is key as it’s the first thing people notice when they land on your site – and the difference between them staying to learn more - or leaving - within seconds.
tip 2: information architecture
Create your information architecture: how are the pages of your site going to be organised and how do they link to each other? Consider the UX (User Experience) i.e. can you make the user journey seem natural and logical? Carry out SEO research i.e. identify relevant Google searches that match to your product and target one or two keyword phrases per page.
tip 3: page architecture
Create your page architecture and break down the look of your key pages. Decide on the sections of each page, what content will be placed in each section and the rationale behind these choices. UX is key here. Ensure that you are taking the visitor on a journey that flows and leads to a conclusion i.e. a call to action.
tip 4: content
Gather content that you’ll need for your pages. You’re looking to hit the head and the heart so you’ll need content that supports your product e.g. video demos, client testimonials and content that will evoke an emotional response (in our case an exciting show-reel).
tip 5: be prepared for...
I lied earlier. Be prepared for a fight. It’s inevitable. However, if you’ve created a detailed document you’ll have a better chance of winning the argument and getting what you want and at the quote you agreed.