Fire the “web designer”

Reading time: About 0 minutes

You’ve hired the wrong guy. After reading David Airey’s forget about design and Andrew Maier’s User Experience Designer vs. Creative Director I’ve come to the conclusion that the role “web designer” is a cheap ass effort to fudge a graphic designer into a role requiring two entirely separate fields of knowledge.

Web teams still need graphic designers to communicate visually appealing messages. And graphic designers moving from a print team to a web team should stay graphic designers. What’s needed to compliment a web team’s graphic designer is someone to account for the complexities of human-computer interaction (HCI). Surely a manager in any field can’t expect staff to adopt a completely opposite, complex knowledge base overnight.

Welcome the missing link: User experience designer.

User experience design is a blend of usability, information architecture (IA), and user interface (UI) design.

A web-based user experience designer is charged with learning about users and creating interfaces that match website goals and user needs. They deliver interaction specs and simple mockups to the graphic designer as a framework for user-centered visual communication. Then, of course, the web developer makes the interaction work.

Don’t mix up the two roles, user experience designer and graphic designer. Neither should do the others’ job. They should never be blurred into “web designer.”

If you’re going to make the leap into a more complex communication channel, account for its complexities or it’ll bite you in the ass when your competitors “get it.”

54 comments skip to comment form

  1. Seth Etter said— 9 minutes later

    Great post, and I couldn’t agree more! While calling myself a web designer for so long I still always felt on the fence between being a graphic designer, or a developer, and felt I should specialize in one or the other. Web designer is a combination of two entirely different fields.

    #1

  2. Rob L said— 1 hour later

    I agree to a point. I think a web designer is a person who is capable of designing and building HTML & CSS UI components. They do not make the website or the back-end code. They simply skin a website.

    In my situation I am the web developer, totally seperate from web designer, and I rely on a graphics designer to design a site in Photoshop with an concept presented by a system architect to develop. The graphics designer then creates a concept mock-up and tears the mock-up into pieces that they then send to me.

    I then take these pieces, create the CSS, and create the markup. I then plumb in the events/interactions to a middle layer that I also build that then interacts with our web service or database back-end system. By being able to incorporate both UI/middle/back-end layers I lump myself into web developer. Being that I develop web based systems.

    So using that setup I can clearly see why you’d have troubles with web designer as they don’t typically do any markup/coding as they just simply create a mock-up design that is really the role of graphics designer given a fancy title of web designer because their concept was meant for the web. Dumb considering they also create our mock-ups for desktop applications so you get into a role confusion when trying to transition from web to desktop concepts. I just think it’s organizational confusion that leads to these misleading titles.

    I say fire organizational HR people and consolidate titles company wide to get rid of this ambiguous nonsensical title system.

    -Developer

    #2

  3. Brian Cray said— 1 hour later

    Hehe…. well said Rob. Sounds like your organization follows this setup

    #3

  4. Rob L said— 2 hours later

    Alas, I wish they did. They’re just as confused as other organizations, but my statement was more of a personal observation. Organizations almost need an intervention to help refine title structures with people who know these differences. Anyway, I enjoyed your post, and know now there are ‘other’ people out here who get it too.

    #4

  5. Brandon Cox said— 2 hours later

    Well crud, Brian! Now I gotta totally rebrand myself again!! :)

    #5

  6. Brian Cray said— 2 hours later

    Brandon: This is definitely food for thought, but I don’t think I’ll single handedly take down the title “web designer.” I think you’re part of the rare bread that understands graphic design and users anyway =)

    #6

  7. Sheni said— 2 hours later

    I couldn’t find any reason to disagree….

    #7

  8. Daniel H. said— 2 hours later

    I would suggest the term User Experience Architect as it is probably more accurate than designer. When you use the word designer people immediately think and expect graphics, regardless of what words come before it. When you use Architect people think and expect “blueprints” (wire-frames and interaction docs). I have held both titles and can honestly say there is a difference in how developers and other team members interact with me and what deliverables the expect to see.

    #8

  9. Brian Cray said— 2 hours later

    Daniel: Great point. It’s funny how subtle changes in language can change our perceptions. I completely agree.

    #9

  10. Jason said— 2 hours later

    I agree to an extent, but at the same time any graphic designer worth a damn is also schooled in visual hierarchy and visual problem solving, not just making things look pretty. Web design – not development, but design – is just that: an exercise in understanding and applying rules of visual hierarchy and various aspects of user interaction.

    So I don’t necessarily think there’s as much a need for a completely separate area of focus deemed “user experience design”, but I do feel there’s a need for graphic designers to rely less on Photoshop and more on problem solving. The computer is a just another tool, after all. It can’t design for you. Sadly, few “designers” nowadays realize this.

    There’s also a need for developers to stop thinking they’re designers.

    #10

  11. Veronica Domeier said— 2 hours later

    Great article Brian! This is s topic I’ve been going back & forth on with a few colleagues. I agree “web-designer” is so vague. It means different things to different people.
    So now what do I call myself? Crap – lol!!

    #11

  12. Brian Cray said— 2 hours later

    Jason: I agree that visual problem solving is an important function of a competent graphic designer. But visual problem solving does not take into account the full complexities of human-computer interaction. There are man y opportunities to solve behavioral problems, which many times aren’t visual problems.

    #12

  13. Ryan said— 2 hours later

    Interesting, but ultimately pointless. You must fit into the job that needs doing! This is nitpicking over a term when what matters is hiring the right person. I have more development experience than design experience, someone else will shift the other way — which does your company need? Pick one!

    #13

  14. Brian Cray said— 3 hours later

    Veronica: thanks for the comments =) I think that there is a strong need for graphic designers that have an understanding of the many facets of web design. So I’d say it’s a personal branding oppportunity.

    #14

  15. Brian Cray said— 3 hours later

    Ryan: How we name things has a big impact on how we perceive things. Commentor “Daniel H.” has had personal experience with role definition and its impact on role expectations. My wife is a HR consultant and she can confirm the importance of role definition accuracy.

    #15

  16. Colby Russell said— 3 hours later

    Fantastic, so long as this person has competence in actual UI design and accessibility. Otherwise, you’ve just got a graphics artist formerly known as “web designer” producing the same stuff, like webpages that can’t even fit on a 800 pixel wide viewport without invoking horizontal scroll bars, requiring around 975 pixels to get rid of them.

    The good thing about things like CSS is that almost anyone can pick it up. The bad thing about web design is that it’s too easy to do exactly that and then deem yourself a professional web designer, which is the kind of person the industry is filled with.

    #16

  17. Brian Cray said— 3 hours later

    Colby Russell: To make a blanket statement about what the horizontal width of a website should be is ignoring the very basics of user-centered design, which is to know your users. Less than 1% of my visitors have less than a 1024 wide resolution. Why would anyone ignore the opportunity to use the extra horizontal space to design for a 1% segment? Never make blanket statements about what users need.

    #17

  18. Lindsey Tyner said— 3 hours later

    “Don’t mix up the two roles, user experience designer and graphic designer. Neither should do the others’ job. They should never be blurred into “web designer.””

    I don’t necessarily agree with that statement. Yes, there are benefits of having a team where the graphic design and user experience design are not within the same job role. However, I think there are many people out there successfully doing both for small to average sized projects where the budget doesn’t allow for multiple job roles. I consider myself to be one of those “web designers”. In the past, I have held jobs where I was a programmer, UI developer, interface designer, and graphic designer.

    Web designers have to be good at creating both aesthetically pleasing design as well as functional, useful, friendly design. That’s our job. The problem in my opinion is that there are a LOT of bad “web designers” out there who don’t understand their job role. Graphic designers who decide to give web design a try often stop at “making things pretty”. Also, web developers often forget the user experience and the graphic design when they try to be web designers.

    It takes hard work and natural talent to be able to understand and apply both principles, but don’t take the title away from those of us who actually know what we are doing when it comes to web design.

    #18

  19. Brian Cray said— 3 hours later

    Lindsey: Good points. Even if you’re part of the rare bread with a “web designer” title you are still perceived to be a part of the same group as the other jack of all trades that actually don’t know half what you do. =)

    #19

  20. Erwin Heiser said— 3 hours later

    How is this different from calling a garbage man a “waste disposal manager” or a cleaning lady a “domestic hygiene consultant” (nothing but respect to people working these jobs by the way).

    #20

  21. Dave said— 3 hours later

    I couldn’t agree more with this. I am currently pursuing a masters degree in HCI. My undergrad background is in Computer Science. I’ve picked up enough graphic design know-how to get by. (So I’ve got credentials on all sides here)

    I’ve seen way to many designers create websites that look great but aren’t practical to implement or easy for the user to understand and I’ve seen developers create sites that function, but only if you’re willing to wade through an ugly, convoluted interface.

    What serious web development needs is people with enough technical AND design understanding to facilitate a happy medium between form and function. It’s not just about a different title for the job, it’s expecting the person in charge of a website to be more than just a graphic designer working in a web medium (or a software developer forced to cobble together some html).

    #21

  22. Brian McDaniel said— 4 hours later

    I’m with Brandon, now struggling with a professional “identity crisis” thanks to you! Actually, I guess it’s a “title crisis”. Maybe since I am a one-man freelance operation I should change my list of titles to include “User Experience Designer” and “Creative Director” along with accountant and janitor. Sounds impressive, anyway.

    Great post (again). I love looking at things we take for granted from another angle.

    #22

  23. Tim Read said— 5 hours later

    Haha. My thoughts entirely. I couldn’t help chuckle Brian, when I read that. Add to your list marketing director – and hardware engineer (just been fixing the pipes in the kitchen).

    #23

  24. LSR said— 6 hours later

    Thank you so much for this article.
    I feel much better, after my shoals of unsuccessfull applications.

    #24

  25. --- said— 8 hours later

    I work at a place where the Instructional Designer structures content and maps out the website based on user needs, the Graphic Designer follows this and mocks up and slices a design in Photoshop, and the Developer codes it for the web. As a graphic designer, I’ve found there are not many Developers who can actually take a design and code it for the web without destroying it. Doesn’t matter how specific instructions and slices are given, there are loads of differences between the example and final product. I think there is definitely a place for the Web Designer role – someone who can do both. But I do agree that in most cases the low paying ‘web designer’ job adverts are just a “cheap ass effort to fudge a graphic designer into a role requiring two entirely separate fields of knowledge”. The skills should be recognized, the rates should be higher.

    #25

  26. Tim S said— 9 hours later

    As an independent “developer” I am often torn between several roles, graphic design being my worst. I tend to pride myself on the coding and lose focus on the visual appeal. Over the past several year I have shifted a bit in my thinking and started with the design as it tends to take me the longest to develop. I can hash out many languages faster than Waffle House can mangle up hash browns but when it comes to pixelating a user interface I may as well be cleaning toilets.

    My point here is both roles are equally as important and anyone who gets hosed into doing both is getting screwed. As a hobby it is fine, as a company you need the segregation between the two. Finally if you were me, I am sorry :)

    #26

  27. jp said— 10 hours later

    I would probably fire -you-.

    Because this “problem” is ten years old. Large consulting companies defined these roles as “user interface developer” (code), “interaction designer” (Flash/layout), “info architect” (Visio/MindMap/language/hirarchy) and “designer” (Photoshop) in early 98/99.

    The smugness of todays “web workers” is a very sad thing to behold. Although “a web designer” was sometimes “some dudes ex-girlfriend” that forgot to leave the office. They even hired a guy for a week that came with a skateboard to his job interview. But he left because his mom had more money.

    “User experience designer” is just a fabricated title made up of UX from desktop/industrial design and “designer” from “omg.. we are so creative.. like really..”.

    #27

  28. wizely said— 14 hours later

    Love it… someone willing to poke into the omnipotence of web designers! Could I be cheeky enough to throw my profession into the mix (I promise it’s relevant!). I’m a copywriter and we tend to get left out of the web design party in the rush to get to the pretty stuff!

    You see we deal with the message – the ‘communication’ part of communication design. In other words what you’re designing for. I work with designers (‘pure’ graphic or web) and developers. To paraphrase… my job is learning about potential customers and creating messages that match website goals and customer/business needs.

    And modern copywriting for the web doesn’t just mean writing real pretty. It also means creating the right structures, funnels, focus-points, linking… to get a response. A good copywriter goes a long way to being your ‘user experience designer’ or at the very least should be working closely with him/ her?

    Reckon it takes us all pitching in to create beautifully effective sites! I did write an article on such heresy – http://bit.ly/WnN6W which also links to excellent articles on Web Depot looking at the interaction between developers/ designers. All of which could support a case for a ‘User experience designer’!

    #28

  29. Brian Cray said— 18 hours later

    Wizely: I agree that a copywriter is definitely an important part of an effective web design team–especially one who understands the reading (or I should say lack thereof) behaviors of website visitors.

    However, I would not say that a copywriter is a user experience designer or vice-versa.

    #29

  30. nuzzaci said— 18 hours later

    If someone asked me what I do for a living and I answered ‘web-based user experience designer’ I would either burst out laughing or blush of embarrassment before I have even managed to finished the sentence.

    I make website.

    I agree, on different notes, with Lindsey Tyner and Erwin Heiser above.

    nuzzaci,
    part time web-based comment copywriter

    #30

  31. Steph said— 20 hours later

    Two very big thumbs up. As a Web Developer/Designer I now find it important to re-brand myself as a Web Developer/UI Designer. Very important distinction!

    #31

  32. Colby Russell said— 1 day later

    Colby Russell: To make a blanket statement about what the horizontal width of a website should be is ignoring the very basics of user-centered design, which is to know your users. Less than 1% of my visitors have less than a 1024 wide resolution.

    Screen resolution does not equal window size, although you might have misspoken and are instead using some other heuristics to determine the actual size of users’ viewports.

    Why would anyone ignore the opportunity to use the extra horizontal space to design for a 1% segment?

    See, I think that this website is designed unobtrusively, for the most part. But what have you done to utilize or necessitate the extra width? A string of graphical ads? A set of fixed-width divs simulating columns for which there is deficient browser support and repeating the follies of tabular layouts?

    Never make blanket statements about what users need.

    There was no such message in my original comment. (There was, however, a rather pointed generalization about web designers.) The fact of the matter is that reading proficiency decreases with long lines of text, regardless of personal preferences, and your stats are likely to stay frozen so long as the content users are pulling discourages the very class of people who comprise that 1%.

    #32

  33. count_schemula said— 3 days later

    Sounds like a luxury to have all these specialized people focusing on specific tasks. Does this actually exist anywhere in the world? In the off chance that the real world is not like that, and one or two people have to do everything, I think it’s important to realize that there are various and distinct phases of the development process, even if people have to cross over to do them. Design, UI and coding all need to be viewed within their own context. Is the design good? Does the UI function well? Is the code tight? And then, can we make all three sing? It would be ideal to have designers, copywriters, UI experts, code specialists, but there are some many places that are just not like that, esp in-house.

    #33

  34. 2stGeorge said— 5 days later

    I agree… to some point. I think its all about defining what the particular expressions (web designer, graphic designer, UX designer, IA) means.

    I understand design as giving a form to the information, a hierarchy and architecture to the interface, of a way of telling a story. Design is how it looks, but mainly how it works.

    #34

  35. Jen said— 5 days later

    I don’t think having all these different roles is realistic in most organizations…its if you can find someone that can wear multiple hats. I was trained in digital art (which covers design, usability, and coding). I do design, usability testing, wireframes, multimedia, and development. There is no way we could afford to have 3-4 people doing my job. Quite honestly…would they even have enough to do all day??

    Also, I think designers who specialized in print don’t understand a lot of the issues with designing for the web.

    I have had a variety of job titles, media specialist, web designer, user interface designer, multimedia designer, but the jobs where similar…bottom line, ask the right questions in the interview and have the right job description and you will get what you want. To me the title doesn’t make much of a difference.

    #35

  36. Brice said— 5 days later

    I’m going to have to put myself in the same boat as Brian McDaniel at this point. As a freelancer, and generally curious problem-solver, I want to have all of the tools of the trade at my disposal. However, I am schooled and more experienced in the visual design aspect (what I consider to be “front-end”) of web solutions. When it comes to UI / UX, I am completely confident in assisting with this aspect as well, however many clients are completely unfamiliar with this aspect and are therefore more reluctant to pay for this service.
    My concern recently comes from companies and prospective clients that are seeking a “web designer” and expecting him or her to know everything from page layout and grids to PHP and CMS systems. Is this a reasonable request, or do more finite lines need to be drawn with regards to position titles?

    #36

  37. Brian Cray said— 5 days later

    Brice:

    “My concern recently comes from companies and prospective clients that are seeking a “web designer” and expecting him or her to know everything from page layout and grids to PHP and CMS systems. Is this a reasonable request, or do more finite lines need to be drawn with regards to position titles?”

    Therein lies the problem. The whole industry is perceived as tactical and simple. Yet, the web is the strategic communication and marketing channel of the future. Until we have professionals to represent in depth all of web’s complexities the web’s potential will be that of a jack of all trades. In short, why are marketing arms spending little on the web? Because we keep on approaching the web tactically. Tactical channels and work will never be perceived with the value the web should be.

    #37

  38. Randall A. Gordon said— 5 days later

    Indeed, but there’s a larger problem at hand. Labels are constraints. They belong in systems to aid users. But, they don’t belong on people. So many people are highly capable of wearing many hats that communicating the who, what and why of a person and his or her skill set is a baffling problem. One for which we’re in desperate need of a True Zen Master to solve.

    Optimally, a system doesn’t need labels for it to be easy to use, everything should be obvious. Now, more than ever, we’re able to reach out to our social networks to find people with precisely the experience required to solve a problem we have. (At least, this works for many tasks, others not so much.) Perhaps we’re headed towards a day where utilizing specific labels to define our careers becomes obsolete?

    There’s gonna be a lot of infrastructure to lay down before that day arrives, however…

    #38

  39. Brian Cray said— 5 days later

    Wow. STELLAR perspective Randall. Damn you’re a smart dude.

    #39

  40. Paul Sutton said— 5 days later

    It’s becoming obvious that the industry needs to redefine or re-establish our own identities as often as we change our personal preferences in design styles.

    I am personally tired of the titles, they do nothing but attempt to explain to each web designer/developer/information architect/UX designers etc… what part of the spectrum you fit in. Have you ever asked any of your clients the difference in the titles? And I’ll bet they would get a headache is you tried to explain it to them.

    Not many design agencies/marketing firms/creatives/etc… staff someone who separately handles information architecture/design mock-ups/front end development/backend development/ and UX design.

    Seems to me it really is as simple as “graphic design” and you either design for the web or for print (both in some cases), and all the other jargon is just that… jargon! All that really matters is the outcome of the service, and if that fails, then eventually so will you.

    #40

  41. Freelance Graphic Design | Tony said— 2 weeks later

    Great post and comments. It all boils down to what you can offer and up to what limits you’re capable of. It pays to know every designing-related field to have that edge when looking for jobs and projects.

    #41

  42. Chris said— 2 months later

    It’s definitely a gray world–no black and white–and when you have a team you focus on your main responsibility–where your title usually comes from–and then collaborate to make the best end result. Provide the best case and evidence, and then test, and then end up doing what the client wants because they’re paying.
    Great post.

    #42

  43. Jason said— 3 months later

    OMG this is the best post. I could not agree anymore. Working @ my current job where I am an one man department, I do need some programmers for some programmer which is beyond my knowledge of the web. I went to school as a graphic designer and no being pulled into web design. I still believe a designer should be well rounded in print and web ( just the understanding to make a site) It would help a lot to creative a wonderful user friendly site. Now a days I just outsource my site to programmers. Also, its great to quote clients this way, clients are so cheap and want to have a bundle (programmer/designer).

    #43

  44. Nic Rosental said— 4 months later

    I couldn’t agree more. Web designer means so many things to so many people that it’s very hard to explain exactly what each one of us really does. I’m fortunate enough to work with a team of excellent designers and professionals in other disciplines that allows me to concentrate strictly on development.
    Hopefully as our industry – and our customers – mature we won’t have to work so hard to explain why you can’t have just one person do it all.

    #44

  45. Jason Leimgruber said— 4 months later

    How about the term “stylist”? There are web “stylists” who make sites look good. And then there are web “designers” who make a good looking site that accomplishes a goal.

    The way I see it, there may be a spectrum (with 5 “colors”):
    1. Web Stylist – visual only
    2. Web Designer – visual w/ some strategic
    3. User Interface Designer – strategic, some architectural and visual
    4. User Interface Architect – strategic w/ some architectural
    5. Information Architect – architectural w/ some strategy

    #45

  46. Mark Koberlein said— 6 months later

    I do agree that many times companies try to force their “print” designers into the role of web designers because it’s usually cheaper than hiring another designer for the web. Most of the time this causes the project to fail. Either because the designer’s work isn’t usable online or they don’t understand HTML and CSS so they can’t implement it themselves and will then hand their work off to a programmer who doesn’t know Photoshop.

    It all depends on how motivated the “print” designer is in becoming a “web” designer. If it’s their choice, they can be successful. “Usability, information architecture (IA), and user interface (UI) design” can be learned as long as the web designer knows that this is a whole different ballgame than the print world.

    #46

  47. Barry Harrison said— 6 months later

    It’s more than linguistics, it’s about skill sets. I’ve seen a lot of “graphic designers” who are clueless about IA and UI, and some who understand it. This creates a lot of confusion in the mind of the buyer of services who may not know how to evaluate them.

    #47

  48. Vernon said— 6 months later

    Thought-provoking post, though I really can’t apply to my current situation where by necessity each person wears many hats – i.e. my web design guy is my database guy is my legal compliance guy – you get the idea.

    Oh, by the way, a small nitpick – the word you want in the second paragraph is “complement”, not compliment.

    #48

  49. Justin Davis said— 6 months later

    It’s amazing to me the denial we live in inside the web industry. Be it pride, self-absorption, or ignorance, we’re unable to look at this industry, and the process of creating our products (web sites and applications) through an objective lens.

    The web industry is one of the only industries going through this design process identity crisis. Take the physical product industry (whichever specific product you want to use as an example) – to say that a “product designer” is the one who designs the architecture of the product, researches the use and develops strategy, applies the visual styling *and* actually builds the object itself would sound ludicrous.

    The same goes for architecture – perhaps one of the closer siblings to what we do on the web. The process of creating a building contains very defined, and separate, roles – architects who take requirements and use cases and craft a strategy for designing the experience, contractors who manage the interpretation of this design and oversee the process of translating a building strategy into bricks and mortar, and the actual workers themselves, who literally build the object.

    See, in almost every other industry, it’s a foregone conclusion that the activity of design as it relates to strategy and use (what we in the web world refer to as ‘user experience design’), the activity of visual styling, and the activity of production are separate actions, performed by distinct and separate professionals.

    To those who think that it’s wasteful and confusing to work at drawing these distinctions, consider the damage you’re doing to your own brand or specialty. A programmer who calls himself a “web designer” gives visual designers that call themselves a “web designer” a bad name.

    While it may not be realistic to have these separate roles in-house, to blindly argue that no distinction should be made is to keep this industry in a perpetual state of immature development. We owe this industry more than defensive positions – we owe it to each other to work through what the roles are and to educate our clients as to the importance of it.

    #49

  50. O said— 6 months later

    The ultimate are user experience designers with a nice aesthetic and high technical skills in Photoshop. These are the ones creating today’s best UIs.

    #50

  51. Web Development said— 6 months later

    Just because they require different skills doesnt mean you need different people. Specially if you are bootstrapping – the same person can fill both roles; or the UI can be defined by someone else, such as the project manager.

    #51

  52. Tori said— 6 months later

    A graphic designer should have knowledge (schooling) in user experience, that’s the whole point of a design, otherwise they’d be an artist.

    Graphic designer: a person who PLANS, ANALYZES, AND CREATES visual solutions.

    Some people are even smart enough to do both print and web design. Obviously, there are differences, I’m not saying the same rules should apply to both, just that a person can be knowledgeable in more than one area.

    Maybe instead of saying “graphic designers moving from a print team to a web team should stay graphic designers” the smarter thing to say is “if your graphic designer has the knowledge to move from print to web (or doing both which is more likely the case) they should be paid more for the additional skills they will be contributing”.

    #52

  53. Oskar Smith said— 8 months later

    Because the web industry is still in it’s relative infancy, defining roles for the people that work within it is definitely something that’s still in a period of transition. Good points in the article though.

    I guess the only thing I would add to this is that it’s worth remembering that to most small to medium sized clients, no matter what you try and brand yourself as, whether it be a UI Designer, Front End Designer, Creative Director etc., to them you are always just “a web designer”.

    #53

  54. Luke said— 8 months later

    we all like to put things into boxes and categories. It makes us feel in control with our surroundings.

    Doing so in such a new industry is expected as everyone tries to make sense of how it all works, but people, listen to me, RESIST! It’s a new industry, take control of what you do within you job, don’t get boxed in!

    I also think we all need to be aware the web industry could change as drastically as it started. All dev work has the potential to get mopped up by ‘off the shelf’ technology. Current example – who needs custom cms when you got wordpress. I not saying that though – clients do. Whay pay a dev when all I need is a designer and wordpress.

    So I say lets not get comfortable with these job titles just yet.

    #54

  55. Respond to this post—

Return to navigation
1255