Sorry Dad! |
So what's the best way to tackle the revamp? Rip down everything and start afresh or work on patching up what we have? Like any big project the temptation is to opt for the latter. The danger is that once it's all done the money is spent, other more pressing concerns get in the way and things start to fall into disrepair. Everything starts looking out of date and before long it's embarrassing to invite any visitors round!
The above is also true when undertaking any big design project like launching a new website. An old rotting website can cause visitors ending up with a bad impression and rarely returning causing damage to the brand. The cycle then repeats itself again at considerable effort and cost. The chief danger here is that for most of the website's life it is operating below peak efficiency.
Goodbye and good riddance |
The single worst thing that can be done is to migrate any content across. The equivalent of this is me using old bits of skirting board to make new ones. See it as the perfect opportunity to reduce the size of the site and write only what is needed. By listing the questions the user may have and prioritising them it ensures that no page is wasted.
During the build it's easy to try and glory in what has been learnt from the previous site. But by making so many changes all at once, and completely replacing it, how is it possible to be sure?
It's not quite this bad! |
By taking this approach to website management the site is always being optimised. It also helps spread the cost rather than having to find a massive lump sum for a complete revamp every five (or ten!) years. There's also no throwing out of good working elements just to recreate them. And of course at risk of sounding like a broken record it allows for "evidence based decisions" (I'm quoting my past self there!) and not wasting time and money building unnecessary features. This approach also helps get new features up and running before the competition and keeps users coming back to what's new on offer.
To get this model working there needs to be a decent set of in-house skills. A scaleable CMS means not relying on an agency to access the more advanced features. If the design isn't too wedded to the technology it's even better to allow adaption to any new developments. This team needs to have skills which involve stakeholder management and content creation alongside the usual technical expertise.
Let's do this! |
I guess I'm literally the 'in-house' team when it comes to our home improvements. At least one of the many perks of working at Kier is I get a Trade Point card. How long does Google Maps say it is to the nearest B&Q?
0 comments:
Post a Comment