The disciplines required on a successful web team
Some time ago, Jesse James Garrett (a much revered hero of new media) produced his second most famous diagram, illustrating the nine pillars of successful web teams. In other words the skills you need to get the job done.
One of the things that I love about this diagram is that it highlights an important gap that causes so many web projects to stall horribly or just end up with a third rate results. That gap is content - both the strategy (deciding what should go on the site) and production (writing the copy; sourcing the photos etc.) These two disciplines take up a big old chunk of the diagram but all too often they fall down the gap between the client and the web agency, because often clients think they can do this bit themselves ("how hard can it by to write the text for some web pages?") And then, inveitably, the agency waits and waits and waits for third rate content to actually arrive.
So the lesson here is to treat the content side of your web project as seriously as the bits you already know are important like understanding your users; graphic design; programming and all the rest of it. And if you're not an expert then get some help with it (exception: if you're writing a blog then just go for it!)
As an aside, this is why I think it was great to see our friends Spannerworks hire Anthony Mayfield - someone who just 'gets it' (and will proudly show you his mention in The Guardian to prove it :-)
There has been a recent revival of the 'content is king' mantra that had become so very old fashioned. This time it's more interesting though, with user-generated content; syndication and aggregation all being added into the content mix. This is why it's so important to get some help from the experts when you're planning the content aspects of your website.
But anyway, getting back to the original subject, here's my own take on the disciplines required on a successful web team, building on Jesse's work:
- Business / marketing strategy to define the business problems that the site hopes to address.
- User research to understand the people who will use the site and what they want.
- Site strategy to define the specific things that the website will do.
- Content strategy to decide what to say.
- Content production to write the words and source the images.
- Abstract design to architect a blueprint for the site.
- Graphic design to make everything look great.
- Technical design to plan how the software elements of the site will work.
- Coding to actually build the site.
- Search engine marketing to ensure the site will be found.
- Quality assurance to test the site and ensure everything works as it's supposed to.
- Project management to get the job done on time and budget.
- The users who can no longer be thought of as just an 'audience' of the website, but people who will contribute to it.
As Jesse pointed out in his original essay on this, it's perfectly acceptable to have people on the team who cover more than one discpline.
Recent Comments