Skip Navigation

Executive Expectations vs. Website Reality

Diffily.com

An extract from an email sent by a senior executive to a website manager.

An image of three pie charts illustrating the combinations of High Quality, High Speed and Low Cost referred to in the text

From: George
To: Tony
Subject: Website redevelopment

Reference our conversation, I agree that we should redevelop the site along the lines you suggested, i.e. Web Standards, best usability practice, accessibility, etc. I have discussed this with the CEO and she said we should push ahead without delay.

We can discuss details later but in summary, I want you to create a high quality (award winning?) website that surpasses those of our competitors. Of course, given this year's tight budget, I expect you to get creative about how this will be resourced (my niece is quite good at design-perhaps she can help?). Finally, as the summer season is approaching fast, the new site MUST be in place before July 1st.

Any problems, let me know...


There is an old saying in the consulting business.

"We can give you three things:

  1. A high quality deliverable
  2. High speed turnaround
  3. Low cost

Now, choose any two."

"I want to have my cake...

The simplicity of this equation is lost on many executives when it comes to website production. They seem to believe the web development process can somehow be 'improvised'.

"You aren't called a web-'master' for nothing. Make it happen!"

The truth, of course, is more complicated. If a high quality deliverable is required, adequate resourcing and time must be provided. In their absence, the value of a development will inevitably suffer. The challenge for a webmaster is to make this clear to senior management.

...and eat it too!"

Happily, there is a way through this conundrum. It comes down to what a business is prepared to accept in return for a given sum of money.

For example, does the business want to create a highly complex eCommerce site like Amazon.com, or a more simple site like Diffily.com. Both are possible—but for the same sum of money, the quality will differ significantly. This difference can be explained by way of the 'scale' of the two sites.

Website Scale is a means for categorising a site in terms of 3 factors:
  1. Size: The time needed to produce and maintain content.
  2. Complexity: The intricacy of the technology used for hosting and content delivery.
  3. Levels of Activity: The levels of traffic received.

Read more about Website Scale on www.alistapart.com

For example, Amazon.com is large in scale. That is, it is very large, has a highly complex infrastructure and receives millions of visitors per week. In contrast, this website (www.diffily.com) is small in scale—it has little content, uses basic technology and is relatively quiet.

Bang for your buck

The decision faced by stakeholders is this: Based on a given sum of money and the scale of the website desired, what level of quality are they prepared to tolerate?

For example, imagine that a business has €50,000 to spend. Should it:

  1. Commission a small-scale website knowing it will be of high quality and can be delivered in a relatively short period of time? (This is because €50,000 is a quite a lot of money for such a site and developments of this type can be expedited reasonably fast.)
  2. Create a large-scale site knowing it will inevitably be of lesser quality and may take much longer to develop? (This is because €50,000 is a small base from which to build a complex, eCommerce site. This small sum also provides less incentive to developers to prioritise development.)

For my part, I believe that a business should focus on quality first, by building a small scale site and then growing organically from there. Any organisation that is driven by the idea that it can have it all (high quality, low cost, high speed) is delusional and will have to learn the hard way how to create a successful web presence.


Website Scale is explained in extra detail in 'The Website Manager's Handbook', now on sale.