Web Design Disciplines Explained Through the Medium of Dungeons & Dragons | January 27, 2012

First off let me apologise for the laboured metaphor I’m about to inflict on you, but I thought it could be entertaining to try and describe the web design industry using a medium I’m sure you’re all familiar with; Dungeons & Dragons. However I should point out that I’m no D&D expert, having played it last when I was 13. So please don’t leave comments to the line of “you got that all wrong as those character classes were changed in AD&D 2nd Edition, Unearthed Arcana.” or I’ll pull out my +2 broadsword and go Berserker on your ass.

In the world of Dungeons & Dragons, characters could have a variety of professions such as Fighter, Thief or Magic-User. These professions were loosely related to a character’s natural abilities. So if you were intelligent you’d be well suited to becoming a magic-user, whereas if you were dexterous, becoming a thief was a good option.

In the real world, your natural interests and abilities will also dictate the career path you follow to some extent. It’s doubtful that you’ll have a natural ability in a particular discipline, but your innate attributes will make it easier for you to pursue certain careers than others. So if you’re a logical thinker, development is a natural avenue, while if you’re empathetic, people management is a good career. If you have both, you get to choose one or the other or maybe even combine those skills and become a scrum master.

In the world of Dungeons & Dragons, Fighters were the bedrock of any quest. For a new party, you wouldn’t get very far without a fighter or two to guard your back, while a group of fighters could easily operate on their own, without the assistance of other classes. The same is true on the web. Programmers are the fighters of the web. It’s entirely possible to start an online business with a couple of programmers and you’d be successful for a while at least.

Thieves are sharp, agile and good with technology. The hackers of the fantasy world. In a modern campaign you’d want at least one thief along to pick locks, disable traps and run interference. With their penchant to form guilds (The Guild of Accessible Web Designers anyone), Thieves were front end developers of the D&D multiverse.

Thieves and Fighters could make pretty good headway on their own, but throw an illusionist into the mix and you’ve got a powerful combination. Illusionists are learned in the arcane sigils (typography to you and me) and had the power to dazzle people with their magical incantations. Relatively useless straight out of college, they only came into their own at higher experience levels, where they become formidable allies. Illusionists benefit from being around higher-level magic users as they can swap spells and learn faster. Similarly design is typically a learned profession but novice designers struggle on their own. So they need lots of support from senior practitioners. However when designers start to become seniors themselves, they are amazingly powerful, and a good creative director is worth their weight in sharpies (5,500 if you assume the average weight of a man is 62kg).

Clerics are the wise healers of the pack. Their job is to look after the spiritual and physical well being of the team. A little like a good project manager when you think about it.

Lastly you have the Rangers. Rangers require higher than average attribute scores across a range of different areas, so tend to be less common. Like Wizards and Thieves they are also a learned class, having to study things like tracking and animal lore. In fact, higher level Rangers even have the ability to cast certain spells or defuse traps. As such they are a bit of a hybrid. Rangers are great in open country and typically work alone. However they’re not much use in towns. So Rangers aren’t needed on every quest and are a bit of a specialism. To me, Rangers are the UX Designers of the D&D world. Highly trained specialists, of use in a subset of specific projects.

Characters in Dungeons & Dragons progress by gaining experience points which relate to the complexity of the quests they undertake and the level of the foes they defeat. If they do something themselves all that learning goes to them. However if they are part of a team the experience is typically distributed amongst everybody. So the more quests you undertake, and the bigger those quests are, the more you’ll progress in your careers. If you play infrequently and only accept easy challenges it can take you ages to move forward, while if you work with a small but experienced team on tricky adventures you’ll grow much faster.

The same is true with the web. Learning comes through experience and the more projects you undertake the better you’ll get. If you accept simple projects with little risk you’ll have an easy life but you won’t push yourself. It’s only by taking risks and working on projects that are slightly outside your comfort zone will you learn new skills and push your career forward apace.

With some character classes, new skills become available at higher levels. You could argue the same is true on the web. There are certain skills you would typically only pick up at higher experience levels and are unlikely to be present in junior practitioners. As such, your level of experience really does impact what you can and can’t contribute to a project.

Now here’s where things start to get interesting. In D&D it’s possible for characters to follow multiple classes. However if you do this you have to split your experience across the different classes making progress much slower. In new of mid level teams, this isn’t so much of a problem. So a 2nd level Thief-Illusionist can hold their own with a 4th level fighter. But a 6th level Thief-Illusionist would probably be outclassed by a 12th level Ranger.

This is also true in the real world. It’s totally possible to do both design and development, and in the early stages one will actually aid the other. But as you undertake one project after another you’ll find that it’ll take you longer to become an expert in either. So it’s great if you’re an all rounder in a team of all rounders, but becomes difficult to carve out a meaningful niche amongst a group of experts.

There is one caveat here and that’s that Bard character. Bards were a really weird class and therefore not something many people played. They had to have really high ability scores across a range of attributes. They also had to start out as a Fighter, then duel class as a Fighter-Thief and then finally duel class as a druid. It’s only after going through this long and laborious process that they could become a 1st level Druid and start all over again.

I think this is the position a lot of UX practitioners have found themselves in. Rather than going through the higher education track, they have worked their way through the design and development professions, never settling on either. Instead they will get to a medium level of mastery before getting bored or distracted by something else. As such, there is a subtle but important difference between a designer and developer who does a bit of UX (think multi-class character) and a self trained UX practitioner (think a multiclass character who took a specific set of steps in order to change class to a Druid).

And that’s it. My slightly laboured, incredibly nerdy description of the web design industry, as explained through the medium of D&D.

You have the initiative. What’s your next move going to be?

Comments (2)

UX Developer is a misleading and potentially damaging job title | January 27, 2012

I was really disappointed to see a recent post from somebody I admire and respect defend the validity of the new UX Developer job title that has been cropping up of late. As well as being misleading, the title, UX Developer has implications that are damaging to the field of User Experience and will hasten the current devaluation of the term.

Despite what many newcomers to the industry may think, User Experience Design is a well-defined specialism as distinct from visual or interface design. The practice of user experience design is a specific field of study with its own books, conferences, membership organisations and college courses. User experience designers therefore have a distinct set of skills and practices that form the core of their profession.

That being said, user experience designers don’t own these practices any more than developers own the ability to code up wireframes. So it’s right that designers and developers look to understand more about user experience as it is for UX designers to want to understand more about the technology that drives their products or the designs that bring them to life. This is one of the aspects of being a professional; the desire to develop your core skills while understanding where your domain overlaps with others.

When I look at new job titles my first question is to ask what new or specific activities form the core of that discipline and make it distinct from other fields. Is this indeed a brand new field of practice or simply a catchy name for a set of composite skills? So when I first heard the term UX Developer I was intrigued. What new skills or techniques are these practitioners using that are specific to the technological side of the equation, and is there anything here I can use?

With eager anticipation I grilled every self styled UX Developer I met to find out what new skills or techniques they had developed. However the more people I asked the more disillusioned I became. Rather than being a new discipline, it became clear that UX Developers were simply developers interested in UX. So developers who wanted to get involved with the initial research, attend (or even set up) usability tests, build HTML/CSS prototypes, consider user needs when coding up pages and put pressure on designers and managers when these needs fail to be address.

I’ve been working with people like this for years. They’re called “good developers.”
There seems as little need for the title UX Developer as there is for the term UX Product Manager, UX Programmer or UX Database Engineer. Similarly, if you’re happy for Developers that do some UX activities to invent a new title, what should a UX person who does a bit of front end or back end development call himself or herself? How about front end UX designer, or creative UX technologist? That has a nice ring about it and isn’t confusing at all.

The sad truth is that UX has stopped referring to the quality attribute of a product or a set of specific skills and activities, and has become a value judgement. For some reason people think that the term UX means “better”, “more valuable” or “more important”. So by adding UX to your business or job title it somehow sets you apart as a better designer, a better developer or a better agency. That, or at least one that can charge more money. This is obviously nonsense and disrespectful to all the talented designers and developers out there. So when I see people adding the term UX to an otherwise perfectly descriptive job title, it makes me view them with a healthy dose of scepticism.

[Andy Budd spent 5 years as a designer and front end developer before transitioning to a dedicated UX designer; a role that he has had for over 8 years. During this transition period he would never have dreamed of calling himself a UX Developer. He hopes other developers feel the same way.]

Comments (14)