Client-first is the way forward
I guess I’ve always kind of known that client work wouldn’t be all it was made out to be. I always knew that as a designer, I’d be told that my designs weren’t what the client expected and that I’d have to change things, and that it wouldn’t be perfect the first time around. I’ve known that from both my education – where our work would go through iteration after iteration before coming out at the final product – and from personal illustration/design work. But I suppose the difference is that in those cases, I was working towards a better end product.
It seems right now I’m just moving backwards.
Before I go any further, a couple of notes:
- I’m just on placement. I work in a small development agency and we don’t get huge clients coming to us. A lot of our client base is made up of charities.
- I don’t do the design work. We hire someone else to do the designs, we just code them and add functionality. Most of the time, I’m the one coding the design and making it look nice (effectively online prototyping).
Right, so bearing that in mind: one of our clients at the moment wants certain things in their navigation. That deviates from the pretty good design that we had given them originally. In itself, that’s fine. But the way they wanted to change it was not so fine. It meant that they’d have five areas of navigation on a single page – and on some pages, six (depending on the user context menu). In order to make space for it, they chose to remove the search box. Great.
I made it very clear that I wasn’t comfortable with doing that, and my colleague made it very clear to them that I wasn’t comfortable with doing that, but the client made it very clear to us that that was how she wanted it done. So that’s how it’s been done. Because that’s how she uses the web, so that’s how other people will, too.
Over the last few months there’s been a lot of discussion about responsive web design and whether or not that’s the “right” way to do things. I saw quite a good tweet the other day that summed up my feelings on the matter. Unfortunately it seems I was stupid and didn’t favourite it, but it ran something along the lines of “what sort of industry is this if people who are new to it immediately get told that they’re doing things ‘wrong’?”
And that’s fair. There shouldn’t be a right and wrong way of doing things on the web. You shouldn’t need to have arguments about vendor prefixes or responsive web design or whether PCs or Macs are better. (PCs, obviously.) As much as I hate to admit it, I think that article in the Guardian a couple of days ago was a pretty good one. Not that I agree with him by any means (I think graphic designers make the web a beautiful place to be), but the reason I use to the web is to find out about things – to find information. There are few sites out there that are designed for the sake of being designed.
So information, if it’s what you’re looking for, should be prevalent on a website. Make it look pretty, by all means – after all, the example cited in the above article was just awful – and make it functional. Code it well, and you won’t have to worry about cross-browser compatibility. But then add your quirks to the top. Then add your vendor prefixes and your responsive stuff and your JavaScript fallbacks for browsers that don’t support them. Get your information across first, get the basic design right, then play around with it.
That’s why I’m not enjoying working for this particular client. They seem to be forgetting that users are going to come to their site looking for information, and their five areas of navigation and lack of a search bar is going to make it extraordinarily difficult for them. And that’s not even going into their convoluted submenu system.
So where should you use those pretty things you’ve picked up? Well, where you can show them off. If it’s not client work, or if it’s not essential to the work at hand… then go ahead and play. Portfolios, app pages (of your own creation, not for a client), CMS pages and so on… in my opinion, that’s where you ought to be playing. Of course, I’ll still whimper if you tell me it’s webkit-only (because I use Firefox), but there’s your playground, there’s where you can move the web forward. It won’t affect your clients’ websites. If you’re one of those lucky people (those so-called “elitists” … you know, those people who have worked hard to get where they are), then go ahead and charge clients for the privelege of having those things on their sites, too. Bigger clients should get those choices.
But a simple charity website doesn’t need those things.
So if the client doesn’t need them, should you spend the time faffing over them? No, I don’t think so. Lower-end clients aren’t going to ask for a mobile-first design that has glowing borders on the search box that has an AJAX dropdown because lower-end clients quite often don’t know what any of that stuff means. They just want to log onto a website and use it and leave again. Remember, these people don’t even know which version of Internet Explorer they’re using.
Finally, a note to myself: draft your posts before you start writing them, Sophie, because this was all over the place and didn’t make much sense. Also, get more sleep if you’re going to try blogging. That really doesn’t help.
