Many organizations start down the path of building a new website with an abundance of enthusiasm. On website launch day accolades are generously distributed to the marketing company for its design and the development team for its tenacity in stamping out bugs and delivering a usable system.
Six months post launch, the rumblings begin about how we might "do it" differently next time and within a year there is a wholesale movement from front line staff and sometimes the CEO for yet another new website. Sound familiar?
So how can this be avoided? How can we develop websites that are built to last?
If you've been following my blog you know I write mostly on customer experience. So you likely expect me to focus on website design principles to improve the user experience and maybe approaches which ensure your website reflects the brand you are working so hard to build. But that's not the focus of this post.
If you are looking for website experience information there are many good sources. Here are a few (you can download them without providing an email - a bit refreshing for a change):
- Forrester's website user experience scorecard
- Forrester's website top 10 scorecard
- Forrester's website brand review scorecard
- Will the website reflect your primary purpose? Corporations tend to struggle with this one less than non-profits / government. Often websites are viewed as large content repositories which talk about "our organization and our offerings". Users to the website are greeted with volumes of content, with little understanding of how they can be engaged meaningfully to aid the organization in achieving its primary purpose. This disconnect often happens because the website is given a lower priority by leadership, not tapped for its true potential, and assigned lower risk transactional functions or objectives.
- What's the website being built to do? This seems obvious, but when I read the objectives for web development projects they are often very fuzzy and clearly hijacked by the marketing department. An objective should have a measurable outcome (remember SMART?). Will the new website sell more products and services? Recruit more members? Increase customer satisfaction with improved service levels? Reduce operating costs? Increase donations? How much and by when?
- Will it do your business? If your new website is not an extension of your business into the communities you serve (and communities include paying customers) then you should go back to the drawing board. I have talked about online customer service in other posts, but I think we need to go far beyond customer service. Your website must seamlessly integrate with your back-office and make doing business with you easy. If you collect money, customers should be able to pay online and check outstanding balances online. Product manuals and training should be online and available as video or podcasts where applicable. Online forums, newsletters, and company bloggers are now only table stakes for any website. Customers should be able to do business with you on their time and in their preferred method on your website.
- Will you address the needs of key segments and communities? Not many organizations have the luxury of dealing with a homogeneous base of stakeholders. What are the key segments with which your new website needs to interact? What are the communities which already exist with which your website and social media strategies will need to interact? What are the needs of those segments and communities? Have you surveyed them to solicit their input and needs? I am often reminded of a Venn diagram I have seen many times. In it, the circle on the left defines "what we provide on our website" and on the right is "what users want on our website". The overlap of the two circles in the middle is tiny. You need to avoid this mistake by asking your users in advance.
- Will the site be customer centric? This is my favorite topic. Some day the tried and true tabs across the top (Home, Products, Services, Solutions, About Us) will be replaced with something more like (Your problems, Your needs, Your potential solutions, Customers we have like you, What you might want to do next, How else can we help you?, Want to join our community?).
- How will you support mass customization? Mass customization is the future of the web so you might as well get started. In the most advanced form of mass customization the user is able to store a version of your website which they tailored specifically for their own needs through their interaction with it. Automotive companies do this by allowing you to store car configurations on their site. You might have to start with some reasonable goals in this area. What are the dialogues you can offer which are customized to user's needs?
- Is your team engaged? This is not a project for the marketing department. Include the CEO and ensure you have representation from all parts of the business. They all have amazing insights to share. Identify a role for providing input from your customer segments and communities, but don't abdicate responsibility to them. Your core team must decide what is best for your organization.
- Have you identified the processes required to support the website? This goes beyond technical support. Who will have ownership of content development of identified sections of the site? What is the expected time budget required? Be realistic. The content on your website must be kept fresh and current - always. In addition, what other business processes (backend systems, marketing communications, etc.) must provide support and work hand-in-glove with the website? Document these processes and identify process owners who are accountable for quality and results.
- Do you have an integrated social media strategy? And this isn't just a corporate Facebook page. I had lunch with a social media guru a couple of week ago who told me there about 800 social media "channels" out there. How do you navigate them, monitor them, and ensure they work collaboratively with your new website?
- Have you selected the right platform? I have a strong bias here. I am a Drupal bigot. And it appears other mainstream bloggers are coming around to the same way of thinking. You require a CMS platform which can work in the Cloud, be supported by a large base of global experts, is social media aware, and can scale to meet the needs of ecommerce and high throughput, while supporting advanced search and the semantic web. We have used Drupal to deliver hundreds of client projects.
Website projects are perhaps one of the most important pillars of implementing your business strategy. I believe we often don't assign the correct importance to our online presence through lack of focus, stingy resource allocation (in terms of budget and key internal resource participation), and by treating the exercise as a marketing project instead of what it really is - a critical business initiative which requires a strong business focus. And just like any other investment you make in your business, your website investment must produce business results.

