An recent article on the Entrepreneur website outlined 6 common misconceptions that CEO’s have about web development.
The article was written by Zach Ferres and while I agree with some of the points he makes there are some others that I think merit a little more discussion.
I think the article starts off on the right note:
Remember the last website project you were involved with – the one that went over budget and missed all the project deadlines that were agreed at the outset – was most likely your fault (by using the term ‘your’ I’m assuming that you were part of the marketing department that was in charge of leading the project within your organisation).
There is no doubt that most website projects are a lot more painful than they need to be. It really is very simple – and with some forward planning and a better understanding of what it is that you are trying to deliver you can avoid all of this pain.
One of the best lines I’ve ever read about web development projects came from a guy at a company called Fathom in Belfast – he said ‘It’s entirely possible for a website to be pretty and pretty awful at the same time.’
Why does this happen? Because too many web development projects are built around what we (the organisation) want to talk about rather than what our customers are actually looking for. I’ve written another post on this very subject called ‘Your website – for you or your customers?’
Anyway, back to the 6 misconceptions that CEO’s have about web development:
1 – Website development is easy
I agree with Zach Ferres here – those not directly involved in the project have very little appreciation for how long the ‘under the bonnet’ development work actually takes. Our role as project leaders for the web development project is to try and build this understanding – break down the project plan into the relevant phases that your development company has given you and highlight the time devoted to the development work.
This is difficult because most CEO’s, other board members and other people in your organisation are just dying to see the big reveal of your new home page design. They care very little about the journey planning element of the website architecture which is essential if the website is going to perform to maximum potential.
My advice – involve them in this stage. Get them involved in understanding who it is that is visiting the site and what they are trying to achieve when they get there. This will help to build an evidence based argument about what content should be on the site and where it should live.
2 – Everyone should be involved
In the original post Zach Ferres believes that the project should only be left to the people doing the work – I’m afraid I disagree. I’ve seen too many website projects fail because the project didn’t have the buy in of people across the organisation.
I believe it’s wrong to assume that only marketing will know what people are looking for when they visit your website – this is not a marketing project.
Your website is a project that should involve as broad a cross-section of people and opinions as you can muster. All of this work should be done at the outset and once all of the intelligence has been gathered then the build process will come together a lot more quickly than without these essential steps.
You will also find the because buy-in now exists across the organisation the final website will be much better received internally when your launch date arrives. This is because the decisions about how to categorise information, how to present information, what calls to action to include were all taken by your development group and were based on evidence.
This avoids subjective opinions on colours, button sizes and the location of information being used as the basis on which people judge your website. The only judging criteria worth considering is the user experience on your website and ultimately the results that it delivers for your business.
3 – Websites are a commodity
I am fully behind Zach on this one – if you want to use free website build templates for your website project you’ve got to accept their limitations. The more customisation you want to be able to introduce to your website, the more likely it is that a custom build is the route you are going to have to take.
4 – Once a site is built it’s done
Your website project doesn’t have a completion date – the end of the development project is marked by your ‘go live’ date. This is only the beginning of the journey to turn your website into a pipeline stuffing machine (or whatever your stated objective is from the website).
5 – Anyone can create a great user experience
While Zach Ferres disagrees with this statement in the original post I’m actually inclined to support the view that anyone can create a great user experience on their website.
The problem is that most people don’t.
But the reason why they don’t is (in my humble opinion) a result of the process that is followed during the web development project.
Too many projects jump straight into defining the various menu options and then deciding what information to house in these silos. Then the marketing department starts writing copy (largely with the aim of hitting all the required keywords).
And all of this is done with no consideration for who will be visiting the site.
- Who is it that visits your website?
- What are they looking for when they get there?
- How did they get there in the first place?
- What other sites have they been on before they got to yours?
- Is this the first time they’ve been to your site or are they a repeat visitor?
Doing an internal workshop with the people in your organisation who interact with customers most regularly will give you some great insights into what content you actually need to look at for your new website.
You can then validate this information by asking some of your customers whether your assumptions are right. This is extremely powerful – it takes the guesswork out of the exercise and gives you confidence, even during the build process that you are building something that will deliver better results for your business.
This is a very simple process – anyone who knows about your business can contribute whether they’ve built a website before or not.
6 – It’s your website so you dictate the design
I’m back to agreeing with Zach again on this one – there are web designers with much better knowledge of what works in relation to web design than you. They will make sure your site follows best practice guidelines which will maximise the potential for your website to deliver for your business.
Once again, ask yourself the question – is your website for you or your customers?
No project should be signed off until it has been tested with real users and feedback taken and acted upon to improve the site experience.
Thanks to Zach Ferres for the original post. I hope you find these observations useful.
If you’re working on a website development project and you’d like some help then get in touch.
Your message has been sent




