Roles & Responsibilities on Web Teams

People are the most important part of any system of web governance. Hire good people and they will generally find clever and innovative ways to get maximum bang for your buck. However, roles and responsibilities have not kept pace with changes in online activity. This has led to dangerous gaps in operations, as well as tension among staff due to competing claims over “who does what”.

In this article we’ll explore some of the ways you can restore peace by delivering the clear job descriptions your team needs.

Download The Info Sheet: Centralized vs. Decentralized Web Teams and learn how Siteimprove can help your website team succeed.

On a web team where everyone knows what they should (and should not) be doing, all tasks have a go-to-guy and nobody has to worry about stepping on a colleague’s toes.

On a website with low volumes of activity, this is straightforward because everything can be done by a single web-guy. Indeed, it is still common to find sites where a ‘Jack-of-all-trades’ webmaster looks after all design, content, code, analytics, marketing, and more.

The only problem is that this ‘all-in-one’ model can’t last forever.

Growing pains

As a site grows in scale, a single webmaster won’t have the time (or the skills) to do everything. As a result, new staff must be hired and new roles and responsibilities created.

When scale increases, the webmaster begins to step back from day-to-day activity and devolve responsibility to newly created roles. Among the first tasks to be handed-over are those in core skill areas such as hosting, code, design and content, followed by marketing, analytics, and more.

To keep things running smoothly, it is important you have a clear system for defining boundaries between new positions as change occurs. While the terms “roles” and “responsibilities” are often used interchangeably, they do in fact have quite distinct meanings.

A “role” represents the key competence or activity for which a staff member is hired, while “responsibilities” are a description of the outcomes expected of that person.

For instance, the role of Developer may be filled by someone hired for her coding skills, while her responsibilities are to produce code that adheres to best practice and organizational standards.

If the shoe fits

Of course, this is not to suggest that responsibilities must always be limited to a staff member’s basic skills. The real world doesn’t work like this.

Budget restrictions mean that people usually end up doing things that aren’t really within their remit, but nevertheless still need to be done.

Most web teams incorporate some woolliness in this regard and it is common for the responsibilities of team members to be much wider than suggested by their titular roles.

For example, responsibility for analytics on a mid-scale site may be allocated to a Content Producer or Designer even though traffic and data analysis are core to neither.

(Happily, many staff have broad enough skills to cope, perhaps with the support of training.)

‘Peak geek’ has been passed

The good news is that as a site grows, much of this fuzziness fades away and staff can begin to focus almost exclusively on their own expertise.

Indeed, a notable trend in web governance is the ongoing specialization of digital roles.

While a decade or more ago you could run a site based on a team with broad code, design and content skills – this is no longer true.

The arms race to develop ever more sophisticated websites has led almost every skill set to fragment into a series of incredibly niche disciplines.

In fact, we have long surpassed the point of ‘peak geek’, where any one person could have a practical working knowledge of every web specialism.

From Content Marketing to User Experience Design to Universal Analytics and Technology, things are just too complex.

This makes it even more essential for roles and responsibilities to be sharply defined, so that existing staff know what is expected of them – and prospective joiners know what they’re getting into.

It’s always personal

How you go about defining things is really a matter of choice, with no hard and fast rules.

A suggested approach can be seen in the document ‘Web Team Job Descriptions’ available for download on my site at diffily.com

You should note how each description includes a clear summary of the role to be filled, as well as a list of important strategic and tactical responsibilities. A catalogue of expected skills is also included.

An important thing to remember is that however technocratic such job descriptions may become, they are among the most delicate professional documents you will ever author.

This is because each one will ultimately be assigned to named individuals, who will take them very personally indeed.

Experience shows that whenever a dispute arises on a web team, the first things to be produced are job descriptions. As such, it is in your interest that each one be as clear and up to date as possible.

Web people are humans too!

The problem on many sites is that this never happens. Scale increases, new activities emerge, new people are hired – but roles and responsibilities remain untouched. It is somehow assumed by senior management that the ‘web guys’ will be able to work it out and fill in any gaps.

But nature abhors a vacuum and web people are as human as anyone else. Before long, staff end up jostling for position along unclear reporting lines as kingdoms are forged and jealousies accumulate.

Then one day – perhaps as the result of some minor incident – things fall apart and someone is given the inglorious task of patching things up.

While uncontentious anachronisms may easily be fixed (for example, a Developer who has traditionally managed analytics but wants rid of it), it is common to find instances where change is vigorously resisted. Say a longstanding Content Producer who wants to retain control of design rather than surrender it to a newly hired UX Specialist.

While retraining or incentivization can go a long way to easing governance transformation, in the worst cases it may be necessary to throw everything in the air and start from scratch; perhaps by defining new roles and requiring existing staff to apply for a position.

A better future?

Inevitably, this is all quite painful.

Sudden, enforced changes to a web team are as disruptive as any other part of a business, as good people who have worked hard over many years are edged-out.

It is my belief that many organizations are working through a period of heightened stress at the moment as this legacy of inattention to online roles and responsibilities is finally put right.

On the bright side this also means that disruptive change is likely to be less common in future, as web management becomes more professional.





Download the Centralized vs. Decentralized Web Teams Info Sheet




Your email address will not be published. Required fields are marked *

*

by Shane Diffily
September 18th
2014

Subscribe to Blog Updates