15 principles for web development

Tom Loosemore of BBC New Media put up a list of the 15 web principles the BBC 2.0 project has been applying:

  1. Build web products that meet audience needs: anticipate needs not yet fully articulated by audiences, then meet them with products that set new standards. (nicked from Google)
  2. The very best websites do one thing really, really well: do less, but execute perfectly. (again, nicked from Google, with a tip of the hat to Jason Fried)
  3. Do not attempt to do everything yourselves: link to other high-quality sites instead. Your users will thank you. Use other people’s content and tools to enhance your site, and vice versa.
  4. Fall forward, fast: make many small bets, iterate wildly, back successes, kill failures, fast.
  5. Treat the entire web as a creative canvas: don’t restrict your creativity to your own site.
  6. The web is a conversation. Join in: Adopt a relaxed, conversational tone. Admit your mistakes.
  7. Any website is only as good as its worst page: Ensure best practice editorial processes are adopted and adhered to.
  8. Make sure all your content can be linked to, forever.
  9. Remember your granny won’t ever use “Second Life”: She may come online soon, with very different needs from early-adopters.
  10. Maximise routes to content: Develop as many aggregations of content about people, places, topics, channels, networks & time as possible. Optimise your site to rank high in Google.
  11. Consistent design and navigation needn’t mean one-size-fits-all: Users should always know they’re on one of your websites, even if they all look very different. Most importantly of all, they know they won’t ever get lost.
  12. Accessibility is not an optional extra: Sites designed that way from the ground up work better for all users
  13. Let people paste your content on the walls of their virtual homes: Encourage users to take nuggets of content away with them, with links back to your site
  14. Link to discussions on the web, don’t host them: Only host web-based discussions where there is a clear rationale
  15. Personalisation should be unobtrusive, elegant and transparent: After all, it’s your users’ data. Best respect it.

Now there’s a neat collection of good principles to follow when you’re working on a web app or web service – of any kind, really. Even if you’re familiar with all of these guidelines, it’s probably best to print them out and pin them right to your wall, next to your desk, just to never, evar forget. Well, maybe that’s a tad too nerdy. However, in every future web project I shall at least follow the general rule of thumb: keep it user-friendly, open and transparent – the more, the better.

Link

Leave a Reply