Work less, produce more

As web professionals we have a culture of long hours. This has to change.

This morning I tweeted the following…

Amazed at how many people on twitter this morning are boasting about the long hours they are working. Don't they know that is a bad thing.

I was amazed by the response I received.

To many it would appear that long hours are a badge of honour. They either represent how ‘overworked and hard done by’ they are or that they enjoy work so much that they don’t mind working 24/7.

But do those arguments really stack up? I don’t believe so. Let me explain why…

I have to work long hours. I have so much work.

Most people claim that the reason they work long hours is because they have too much work to do. However in my experience work expands to fill the amount of time you give it. The more hours you allow yourself to work the more work there will be to fill them.

In my opinion it’s not about how many hours you work, its how smart you work.

Despite what some of my colleagues at Headscape like to think, I output a lot of content. I…

  • Write blog posts like this
  • Do online seminars
  • Record podcasts
  • Speak at conferences
  • Consult on client work
  • Act as Headscape’s R&D department
  • Am heavily involved in the sales process

…and so on.

People often ask me how I get so much done. Well, I can tell you one thing – it’s not because I work long hours. In fact I try and keep very strictly to an 8 hour working day.

I believe that you can achieve more by being organised, rested and motivated, than you ever can by working late into the night.

There maybe some satisfaction in pulling multiple all nighters but I don’t think it means you get more done.

Of course some claim it is not because they have to work long hours, its because they want to.

But its not work

One guy on twitter justified his long hours by quoting confucius…

Choose a job you love, and you will never have to work a day in your life

I can sympathise with this view. However, I believe that ultimately it is short sighted.

When I was young I took this attitude. I worked ridiculous hours because I loved what I did. I couldn’t get enough of the web and was never happier than when I was creating stuff online.

Today things are different. I am still as passionate about the web as ever but I have learnt that having time away from the web is incredibly important.

Participating in life beyond the web provides a valuable perspective that can be missed when you are constantly on the job.

Spending time with my family, friends and doing non web activities actually makes me a better web designer. It enables me to realise that not everybody cares about the web like I do and the web is not the whole world to most people. It also shows me how real people interact with it. Finally, it opens me up to sources of inspiration that otherwise I would miss.

However, although these arguments are valid they pale into insignificance when compared to the plain truth that it is not healthy to obsess over a single thing.

To be a broad, rounded human being we need to engage in non web related activities. Do you have any hobbies outside of the web? Do you socialise with non web people? These are all important not just for our mental health but also to provide perspective in our work.

Don’t get me wrong. I am not saying that pulling the occasional all nighter is wrong. I also recognise that occasionally you need to hustle (as Gary Vaynerchuk would say) in order to make a life transition such as going freelance.

I am just saying that we should not be proud of our long hours. We should recognise them for what they are… an evil necessity.

At the end of the day nobody reaches their death bed wishing they had worked longer hours.

Reviews: Noded and Support Details

This week we have two reviews for the price of one. First we review the freelancing book ‘Noded’ and then take a look at a useful web application called ‘Support Details’.

Noded – The Untouchable

Hello, my name is James Callaghan. I’m an in-house web designer and developer / generalist working for Marshall Aerospace at the Airport in Cambridge and also work freelance.

Before I start, do you know what a Noded Team is?

The entire book, all eighty six pages of the book, attempt to explain what Noded is. During the first few chapters it attempts to cover definitions and examples, which I found a little hard to take in. It took me a few attempts to learn what Noded is, reading a few pages again and again.

With what Noded was vaguely drilled into my head, continuing on, the book focuses on freelancing with tips and advice on many maters such as setting up a business, planning things to managing time. This was of huge interest to me and the book became slightly easier to read.

Though out the book Andreas and Jaan describe their methods and tips on various subjects relating to Noded Working and Freelancing.

Noded Website

One section I did enjoy to read was “A space to work” that explains how important it is to find the right place to work. “As a web worker you can work from any place you fancy – a library, coffee shop, or park bench”.

Most of the time however, it’s nice to have a more personal place to work from.” I’m under the same opinion as Andreas and Jaan – “crappy office, crappy output”, “inspiring office, nice quality output”.

A subject that makes me very sore with my recent data loss that I can say I already adhere to is the tools for the game and why you should use the cloud over your hard drive. With explanations how applications force you to use their logic and structure and therefore are really tiresome and in the end the application is abandoned; instead suggests using cloud based web-apps that are far more flexible and forgiving, examples include: Email, Calendars, Get Things Done (GTD), Project Management, Synced Files, RSS Feeds.

On a more back office subject the book explains why working an 8 hour day is dead to tips on how to break away from the traditional meeting.

I take the same approach as the book, my ideas and creativity cannot materialise on command. They come at the most in-convenient times when I’m not working such as in the show, out on a ride on my bike or whilst out walking my dog. The book suggests using a tool and allowing people to contribute in advance of the meeting, following up with a simple 15 minute meeting to make a decision on the project or simply brief everyone involved.

An idea I am looking forward trialling in the real life! “The 8 hour workday is dead. We don’t believe that being

“being at work” for 8 hours accomplishes more than working for 4 hours, 2 days or 5 minutes. Work is about accomplishments, not measuring time. It is about being effective versus being efficient – doing your job faster and better versus simply doing more work”.

Not sure how to approach my manager on this one though, it is all about the hours here but way to think of it is:

“when you buy a music track that you really like, does it matter whether the artist spent two hours or two months writing the song? Probably not. Does a bowl of pasta taste better if the chef spent more time on it than if he spent the right amount of time on it? Probably not.”

In short, the book has really given me some great tips and methods as to how I should approach my freelance work but also provided me with some great ideas how to handle projects and work within the organisation I work in.

As I read through the book I found myself wanting to know more about something that had be written so instead of getting distracted whilst reading the book, I created a “list” of the pages with references and URLs I wanted to know more about.

The question I asked before reviewing the book was:

“do you know what a Noded Team is?”

If you answered at all, I suggest grabbing a copy of this book and truly discovering what Noded is all about. If you didn’t here is a dictionary definition included in the book.

“Noded Network, a Node Team. A group of individuals, often but not necessarily geographically far apart, that come together to form temporary or recurring project teams. Unlike ‘distributed teams’ Noded teams work for a wide range of clients and any member of a Noded team can take the lead to bring in work, manage work and choose their team members.”

Lastly I would like to say that I have really enjoyed reviewing this book and would like to take a moment to thank Paul and the team for producing such a great podcast but also to Ryan for his time and patience with me as it has taken me quite some time to produce this review. I’ve had to teach my brain how to read again, but also how to write a review that makes sense.

Support Details

My name is Nora Brown; I wanted to let you and Boagworld listeners know about a really handy site I’ve come across. I’m a freelance web designer who does a lot of sites for writers, artists, and small business owners – not necessarily the most tech-savvy folks. Sometimes they don’t even know that they’re using a browser, much less what specific version of IE they might be using.

So to help diagnose problems, I direct them to www.supportdetails.com. From this website, they can simply email you, and it sends you all the details of their browsing environment. You can even give them a link with your email address pre-filled in. An added bonus is that it includes their IP address, so you can create a filter in Google Analytics to exclude their own site visits from their stats.

Support Details website

Again, that’s supportdetails.com. I hope you find it useful.

Super charge your browsing

As web designers and website owners we spend a lot of time working within the web. Discover how you can streamline your browsing experience with launchbar and quix.

Apologises for the rather unprofessional video (with the wife wandering around in the background). However, as this is not strictly about web design and so therefore not strictly a boagworld official post, I thought I could get away with it!

Install the Quix bookmarklet now

Download a demo of Launchbar

10 secrets to staying informed about web design

Keeping up in the world of web design is tough. Things move fast and its hard to stay informed. In this post I share 10 ways that RSS can come to the rescue.

Whether you are a designer, developer or website owner there is an immense pressure to keep up with the latest web innovations. With the web moving so fast what is best practice one day is out of date the next.

Worse still, we are so busy building and running websites, that we rarely have the time to keep informed. However, it is not impossible and the answer lies in the clever use of RSS.

Below are 10 secrets I have discovered that allow me to get a broad overview of the industry without wasting hours of my time everyday.

1. Get a great RSS reader

It goes without saying, but the first thing you need is a great RSS reader.

The key thing you are looking for, is a reader that allows you to identify which content is most likely to be of interest to you. There are two ways this can be achieved.

One approach is to use folders. This is the approach I take. I use Google reader and organise the different feeds into folders that help me prioritise. I talk more about how I organise things below.

The second approach is to use an RSS reader that does this prioritisation for you. One example of this kind of reader is Fever. Fever reads your feeds and picks out the most frequently talked about links. What is great about this approach is the more feeds you add, the better fever gets at identifying important content.

Screenshot of the Fever Website

Whatever approach you use, you must be able to quickly identify important stories and avoid feeling swamped by posts.

2. Organise your feeds

If you choose a more traditional feed reader such as Google Reader it is important to organise your feeds well. If you don’t then great content can get lost among high frequency feeds such as Techcrunch.

Everybody will organise their feeds in a slightly different way and I myself have tried several approaches. However, the one that seems to be working best for me is to have the following folders:

  • Must Read – This is where I place feeds that consistently produce great content and I cannot afford to miss a post.
  • Quantity Feeds – These are feeds from sites that post regularly. Sites like the BBC may produce great content, but there is so much of it that it can overwhelm other feeds. By isolating them I can ensure I don’t miss anything important.
  • Links – I subscribe to several feeds that are just collections of links from people I respect (I will talk about this more later). Because these contain no actual content in themselves, I keep them separate for a time when I can hunt through the list for any gems.
  • The rest – These are less valuable, low volume feeds that I read when additional time is available.

Of course just because this approach works for me does not mean it will for you. You need to find the best folder structure that suits the content you subscribe to.

3. Be mobile

I do most of my RSS reading away from my computer. It is amazing how much content I can get through by utilising the spare moments I have waiting for the wife or sitting on a train.

Screengrab of News Stand

Therefore I need a great mobile RSS reader. The mobile reader I have is called News Stand and it syncs seamlessly with Google Reader. This is the primary reason I use Google Reader rather than Fever.

What is more News Stand has some useful features worth noting. From News Stand I can…

I regularly email myself posts if they contain some new tool that I might want to look at in more depth later. I can even add these posts directly to my task list using Omnifocus.

4. Scan, file and read

How you read your feeds is as important as the tools you use.

With so much great content out there you will inevitably end up with a lot of feeds. There is just not enough time in the day to read them all. The emphasis has to be on finding the really good content fast and then reading it later when you have time.

Normally when I launch my feed reader I am pushed for time. I don’t have the opportunity to trawl through each post and read it in detail. The main objective is to scan headlines and see if anything jumps out.

Instapaper for the iPhone

If I spot something I like the look of I add it to instapaper. This will reformat it in a more readable way and save it offline on my phone for later consumption.

An alternative approach would be to simply star it in Google Reader. However, personally I prefer the accessibility and formatting of instapaper.

Then once I have my list of preferred reading, I use longer blocks of time to read through this list. Train journeys and sitting in bed are ideal opportunities.

However, I have also discovered that even driving in the car or working out at the gym (not that I have personal experience of the latter) are ideal times to work through my reading list. The way I achieve this is using a service on the mac that converts text into an MP3 file. The voice isn’t great but it is a very useful way of getting through a big reading list.

So you have a process in place. The next question is what feeds to follow.

5. Follow the big players

As a web designer you need a broad overview of not just the web design world but also the tech world. It is therefore important to follow a number of big players who post regularly and will provide the majority of posts in your feed reader.

Mashable Homepage

My personal suggestions are:

  • Smashing Magazine provides easily digestible content that either inspires or provides practical advice.
  • The Web Designers Depot is similar to Smashing Magazine but seems to focus more heavily on inspiration.
  • Sitepoint provides both blog posts and detailed articles on every aspect of web design. A great all round publication.
  • Techcrunch will provide a broader perspective on the tech world. However, it can be a little focused on ‘the Valley’ for my tastes.
  • Mashable provides some great articles social media and is definitely worth subscribing to.

The problem with the sites above is that they post frequently. Be sure to isolate them so they do not dominate your feed reader.

6. Track the specialist sites

In addition to the big players there are also a large number of specialist web design sites that are worth your attention. These include, but are not limited to:

  • A List Apart was originally the homepage of web standards but is now broadening its articles to tackle a variety of user experience related issues.
  • Adaptive Path is a company who produce some excellent posts on the latest thinking in the world of UX design.
  • Boxes and Arrows is a blog dedicated to information architecture.
  • Ideas on Ideas is a collection of essays regarding design, brand and experience.
  • Customer experience matters tackles as you might expect from the title, customer experience issues both online and off.
  • Konigi is a research community for user experience designers.

Obviously this is a list of my favourites, and so is biased towards my personal areas of interest. However, if you are starting from scratch these are as good a place to begin as any.

7. Remember the individuals

So far we have focused exclusively on web design / tech publications and ignored the blogs of individuals. There are literally thousands of these, but it is important that a good selection can be found in your RSS reader.

The individual bloggers tend to post less regularly but this is where a lot of cutting edge thinking happens. An idea bounced around in somebodies personal blog can quickly turn into best practice promoted by sites like A List Apart.

My personal favourites are…

  • Jeremy Keith, who writes a lot about HTML5, Javascript and Microformats.
  • Roger Johansson, who covers a variety of topics from accessibility to web standards.
  • Bruce Lawson, who focuses mainly on HTML5 and accessibility.
  • Richard Rutter, who will tell you all you need to know about web typography.
  • Sam Barnes, who shares his personal perspective on web project management.

Over time you will build up your own list of personal bloggers. However, always try and keep an open mind to new people. You should always be adding and removing feeds to keep your list current and relevant.

8. Use bookmarking feeds

The same people who have good web design blogs are often extremely well read themselves. Many of them share the content they find on social bookmarking websites such as delicious. It is well worth subscribing to their feeds on these sites.

Delicious

A few of the many such feeds I subscribe to include:

Subscribing to other people’s feed is an easy way of exposing yourself to content that you might not otherwise have found.

9. Leverage twitter

Of course, increasingly people are not saving links to services like delicious. Instead they are posting them to Twitter.

There are a couple of ways of leveraging twitter for great web design content. One way is to use Twitter search. By searching for web design keywords such as “usability,” “web design” or “accessibility” combined with “http://” you will return all links that match those keywords. You can then subscribe to an RSS feed of that result.

Although this is a good way of discovering new content there is no guarantee as to the quality of those links. They could have been posted by anybody including spambots.

A better approach would be to search for links submitted only by the people you follow. Unfortunately Twitter search does not provide that ability. Fortunately a service called Microplaza does.

Microplaza homepage

The service allows you to see all of the links tweeted by those you follow either organised by date or popularity. You can also see exactly who tweeted the link. However, best of all you call subscribe to an RSS feed so it appears in your feed reader of choice.

10. Signup to aggregators

With a good system, reading your RSS feeds does not need to take long. However you may conclude that this is not something you have time to setup.

If that is the case you could get somebody else to do the hard work for you. There are a number of news aggregators out there, which collect the best of web design news and feed it to your news reader. For example Boagworld runs its own news aggregation service that you can either follow on Twitter or subscribe to via RSS.

Conclusions

As I said at the start, we work in an extremely fast moving industry. There are new innovations on a daily basis and what is best practice today might be replaced tomorrow. It is important to stay up-to-date. However, finding the time can be difficult.

This post demonstrates how I have solved the problem. However, that is just my personal experience.

What about you? How do you stay on top of web design news? How do you remain current and do you think RSS is the answer or has it be surpassed by Twitter? Post your thoughts in the comments.

If you recognise that the mobile web is important and you need help deciding on a strategy, then book a mobile consultancy clinic.

Book a consultancy clinic or contact Rob about a more in-depth review.

187. Jedi Mind Tricks

On this week’s show: Paul looks at how to better communicate and we ask whether you should mask your email address to avoid spam.

Play

Download this show.

Launch our podcast player

Housekeeping

Although we promised you ClearLeft on this week’s show we have had to postpone it until next week. However, that gives you a whole extra week to submit questions via the comments on our blog.

Back to top

News

A web designers time is precious

We are all too busy, period. However, life can be particularly intense if you work as a web designer or developer. The pace of change is so fast it can be hard to find the time to keep up.

Fortunately there are some great articles around that provide time savings tips. Take for example Sitepont’s post this week “How to take control of your time.” It provides some excellent advice including the importance of prioritising, the need to leave adequate time and learning to say no.

Smashing Magazine has a post of their own entitled “20 time saving tips to improve designers workflow.” This includes ways to customise your work environment and better work with tools like Photoshop.

Speaking of Photoshop there is a great cheatsheet that contains all of the keyboard shortcuts you need to speed up your workflow in Photoshop. When combined with the IE6 cheatsheet for solving common IE6 bugs you will find yourself saving considerable time.

The answer to overload is not to work longer hours. It is to work smarter and that is what these posts enable you to do.

15 common ecommerce mistakes

I love working on ecommerce sites. They are by far my favourite. The reason – you get to see an obvious return on your work, because they have an obvious call to action. Conversion either increases or decreases. Profits either rise or fall. You are in no doubt as to whether you have made a difference or not.

However, the other reason I love working on ecommerce sites is because so many of them are terrible. Often when you start working on an ecommerce site there are loads of quick wins that make an instant difference to revenue.

People make the same mistakes again and again. In fact these mistakes are often so predictable that you could write a top 10 list of them… and guess what… that is exactly what Smashing Magazine has done: “15 common mistakes in ecommerce design and how to avoid them“.

Some of my personal favourite mistakes include:

  • Hiding contact information
  • Long winded checkout
  • Poor customer service
  • Not highlighting related products or otherwise upselling
  • Hiding the cost of delivery

If you are designing or running an ecommerce site then you really should check this post out. You will be surprised just how many of these mistakes you make.

The benefits of inline form validation

I have said it before and I will say it again: “forms are the most important feature on most websites.” Most often a sites call to action requires the completion of a form. Get the form wrong and you frustrate users potentially driving them away.

Nobody likes filling in forms. Whether it is a contact form, site registration or just a simple login form. It is therefore vital that we make the process as painless as possible.

There is a post on a List Apart which I have only just gotten around to reading. “Inline Validation in Web Forms” does not sound like the most exciting read but it does provide some invaluable best practice for dealing with forms. However, it doesn’t just provide somebodies opinion on best practice, instead it backs those views up with valuable testing.

The post takes a typical signup form and trials different forms of inline validation with real users. They didn’t just monitor success/failure rates. They also looked at errors made, satisfaction rates and completion time. They even did some eye tracking.

Although the results are not surprising, it is nice to have some numbers to put against what we have known to be true. For example, it was obvious that inline validation makes an enormous difference to both actual success and perceived success. Just validating a form on the client side increased success rates by 22% and satisfaction by 31%. Those numbers went even higher when the user is given feedback as they completed each field.

A valuable post, worth reading.

Innocent smoothies: A case study into corporate communication

When you speak at as many conferences as I do, you often find yourself referring to the same examples of good or bad practice. Whether it is comparing Google and Yahoo or fawning over Apple’s great UX design, the same names keep coming up.

One of the names I often reference is Innocent Smoothies. I love them. They just ‘get the web’. Actually, that is a lie. They get people. They know how to communicate and they know themselves. They have a distinctive voice that makes people warm to them and that is carried through to their website.

This week Anna Debenham has written an excellent case study on Innocent Smoothies looking in detail at what makes them successful online. In particular she looks at their blog and mailing list.

As Anna says at the start of her post:

A lot of the clients I work with who have just set up a web presence for their company think it’s a good idea to start a mailing list and a blog. Everyone else is doing it, so why shouldn’t they? The problem is, so few companies get it right and very few people will bother to read them.

So what makes Innocent different? Anna gives 6 reasons:

  • They show you the real people behind the business
  • They make their copy fun
  • They don’t just talk about their products
  • They are generous
  • They provide useful information
  • They make good use of imagery

Anna’s post is packed full of examples, so be sure to check it out. There is a lot most corporate bloggers could learn from Innocent.

Back to top

Feature: How to persuade your users, boss or client

Whether you are trying to get signoff for a site’s design or persuade a user to complete a call to action. We all need to know how to be convincing. This week, we look at how to present our message

Read Jedi Mind Tricks: How To Persuade Your Users, Boss, Or Clients

Back to top

Listeners feedback:

Email masking

One of the more popular suggestions for topics was how to mask your email address so it doesn’t get harvested by spammers.

This is something that everybody worries about from designers to website owners. However, unfortunately there is no good solution. In my opinion you need to just put your email out there and deal with the spam.

Sure there are a number of possible solutions but none of them are acceptable. They either require the user to be running Javascript (which creates accessibility problems) or they place extra burden on the user. Giving users the ability to contact you is a fundamental part of almost all websites and, so you do not want to make it hard.

There are however two ways of minimising the impact.

First, you could choose not to publish your email address, but instead offer a contact form. Although spammers can spam these too, it is harder and there are ways of minimising spam without putting an added burden on users. However if you do use a contact form, send a copy to the user so they have a record.

Second, you can fall back on good spam filters. Use a site specific email address and make sure it is guarded by a good quality filter. I personally find Google Mails spam filter particularly good, so you might want to consider routing enquiries via that.

However, at the end of the day if a spammer is determined to spam you there is very little you can do to stop them. Unfortunately, this the price of being online.

Back to top

10 tips for efficient design

Being a good designer is not always enough to survive hard economic times. You need to be efficient too.

I don’t want this to be another ‘recession’ post. Sure, being more efficient in the way we work as web designers, makes us more competitive and keeps us employed. However, that is not the only reason we should endeavour to ‘work smarter’.

Working as efficiently as possible brings other benefits too…

  • More time – The faster you can turn around work, the more time you have for personal projects, family and friends. I don’t know about you but this is a major motivator for me.
  • Better promotion prospects – It takes more than good design skills to be promoted. You need to demonstrate that you are proactive and efficient in the way you work. Management will value you more if you generate a higher return.
  • Increased profit – If you are a freelancer it is all about maximising profit. The smarter you work, the more money you earn. It’s that simple.

So how can you be more efficient and begin to work smarter? Here are 10 tips that will get you started.

1. Use snippets

Coda Clips Palette

Let’s start with the obvious technical stuff. First make sure you have a library of code snippets that can be easily reused. These could include Eric Meyers CSS Reset or your own code for dealing with common HTML content such as news listings or pagination.

These libraries of snippets provide two benefits. First, they save a lot of typing. However more importantly, they ensure consistency across projects. Because you are using the same code for each project, all of the IDs, classes and structure remain consistent. This will save a lot of time when trying to remember why you built something in a certain way or how it works.

2. Use a Javascript library

In a similar vein to snippets I would highly recommend you adopt a Javascript library. Personally, I am a huge fan of jQuery because it is designed for those familiar with CSS. It is also amazingly easy to learn and very lightweight.

Using a library like jQuery has proved a massive time saver for me. It has allowed me to avoid endlessly battling with browser inconsistencies (at least in Javascript!) and avoid reinventing the wheel.

jQuery Homepage

jQuery (like most Javascript libraries) also supports a large number of plug-ins produced by third parties. These too can be a massive time saver. However, a word of warning – be careful using a plug-in you do not fully understand. The quality of plug-ins varies massively and if you discover a problem with one, you can waste many hours trying to fix it, if you do not understand how it works.

3. Configure your tools properly

Often in our haste to ‘get on with a project’ we fail to take the time to prepare properly. One example is in how our software is configured. We settle for working with tools ‘out of the box’ when some minor modifications could improve our efficiency.

Photoshop is a good example of this. It has all kinds of configuration options from keyboard shortcuts to palette layout. Take a few moments to set these up for your workflow, and you could save hours of unnecessary clicking over the long run.

Photoshop Palettes

Look at whatever tools you use to build websites and consider how their interface can be tweaked to your needs.

4. Have one system for tasks

For fear of reinforcing a stereotype, designers tend not to be the most organised people. Not only do we need to organise the structure of our software tools, we also need to do the same for our projects.

Fortunately, not all of us have to manage entire projects. However, we do all have tasks that need completing. How we organise those tasks can dramatically affect our efficiency.

A common mistake with task management is to have tasks spread across multiple places. Some tasks exist as emails, some in a todo list, still more in a notebook or on your mobile phone. The result is that things get overlooked.

In order to efficiently manage your tasks they need to be gathered into a single central location. For me that is a task organiser called Omnifocus, which syncs between my desktop and iPhone.

Omnifocus Screenshot

Tasks are still collected using multiple methods. However, once a day I transfer them to Omnifocus. If I attend a meeting and take physical notes that include tasks, I put the notebook into my in-tray until I can add the tasks to Omnifocus. If I receive an email with a task, I drag that email into Omnifocus. Ultimately everything ends up in Omnifocus.

By being this regimented about the way I organise tasks, I ensure nothing ever gets missed. I also avoid wasting time trying to track down the details of a task I have lost.

5. Embrace and manage admin

Inbox Zero - The original 43 folders series

Part of the problem we face is that answering email and organising tasks feels like a waste of time. Its not ‘proper work’. This is especially true when the pressure is on and deadlines are tight. We arrive at work in the morning and launch into our projects without checking our task list. The result is that we prioritise the wrong work and miss deadlines.

I begin each day by doing two things. I answer and file all my emails (I always achieve inbox zero). I then review all of my tasks and identify the ones that I wish to complete that day.

However, I don’t stop there. I have designated admin time. Once I am done my morning review I close my tasks and email until lunchtime. I focus solely on work and avoid admin entirely. This prevents email and other admin from interrupting the flow of my production work. It keeps me focused.

6. Distractions must die

TweetDeck

Of course it is not just email that distract us from work. There is instant messaging, Twitter, Facebook, RSS and… lets face it… the entire internet!

Don’t misunderstand me, some distraction is good. I have a very short attention span and so if I work on a single thing for more than about 30-40 minutes I start to ‘zone out’. However, there is a difference between ‘having a break from work’ and ‘getting distracted’.

Every 40 minutes or so I will take a 5 minute break and fire up Tweetdeck or Google reader. What I try to avoid is keeping these applications permanently open (although with twitter I have to confess I often fail).

By leaving an application open that can distract you with notifications (‘You have a new tweet’, ‘You have mail’, etc.), you risk it interrupting your flow of work. These constant micro-interruptions make it hard to ‘get into the zone’.

7. Keep a tidy environment

Distractions extend beyond your PC as well. Your work environment can also have an impact on efficiently.

If you work from home, endeavour to keep your personal and work life separate. Ensure you can close the door on the rest of the house and that the rest of the family know not to interrupt. Also if possible, try to keep your working area separate from the rest of the house. A garage or loft are ideal. I used to work in a small room directly between our lounge and kitchen. It was impossible to focus on anything with the constant noise from the two rooms.

My Desk

Pay attention to your desk as well. Keep it clean and uncluttered. This reduces distractions but also creates a better mental state conducive to work. Ensure your physical files and disks are easy to find. Knowing you took some notes that are in a notebook somewhere does not make them easy to find. This is especially true when your desk is three feet deep under paper work!

Personally I scan what notes and physical paper I can. What I have to keep in physical form, I file in a single filing cabinet organised alphabetically.

8. Avoid multi tasking

There is a myth that multi tasking makes you more efficient – it doesn’t! As designers we like to ‘flit’ from one thing to another. However, ultimately this is damaging to productivity. We need to learn to focus on a single task and follow it through to completion.

As I have already said, I find it hard to focus for any length of time. In order to help me focus I break my tasks down into smaller ones. That way I rarely have to do one thing for too long. Take this post for example. To write the whole thing from beginning to end would take a couple of hours. That is longer than I could focus for. So, in order to stop me getting distracted and jumping onto another task, I break it down. This post was made up of three tasks…

Task List: Create an outline, write initial draft, add imagery and edit

Once I complete one task, I switch to another project for a while. Once I have completed a task on that project I may switch back to this post.

Although this is a kind of multi-tasking, it is more structured and ensures I spend as long as my attention allows on each project. I do not simply drift between projects.

Depending on your character this might be too extremely. You may find it easy to concentrate for extended periods. However, if you struggle to concentrate, do not use multi-tasks as an excuse to be distracted.

9. Don’t do excessive hours

Another widely held myth of productivity is that the longer you work, the more you get done. After all, on face value this makes sense. However, I sincerely believe this is not true, especially if your job relies on you generating ideas and being creative.

Obviously we have to put the hours in, if we want to pay the bills. However, do not allow your boss or clients to force you into excessive hours. The occasional all-nighter is one thing, regular 12 hour days is another.

It is incredibly easy to get burnt out as a web designer. You are expected to continually be creative, as well as keeping up with one of the fasting moving sectors on the planet. Things are continually changing and evolving and it is a struggle to stay current.

Twitter post of somebody saying they are burnt out by work

Working long hours damages your capability to take on board new information and cripples creative thinking. Ensure you limit your hours and book regular holidays. Do not push yourself too hard or you will fail to deliver.

Finally, accept your natural cycle. When you are ‘in the zone’ work every hour God gives you. However, you must also accept that sometimes you need to just stop and rest. Don’t feel guilty about the days when you hardly do anything.

10. Communicate better

I would like to end this post with possibly the best efficiency tip of all – If you want to avoid wasting time, learn to communicate better.

So much of our time is wasted because of miscommunication and misunderstanding. How many times have you had to redo a design because you misunderstood the client or showed them work too late in the process.

Take the time to really engage with the client and understand their requirements. Make sure that you include them in the design process and show them work often and early.

Example Mood board

Finally, use tools such as gallery sites, mood boards and sketches to ensure everybody has the same understanding and is working towards the same goal.

By effectively communicating with clients, you can potentially save days on each project that would have been wasted on reworks and amendments.

If you recognise that the mobile web is important and you need help deciding on a strategy, then book a mobile consultancy clinic.

Book a consultancy clinic or contact Rob about a more in-depth review.

135. Libraries

In this week’s show we talk with John Resig on javaScript libraries and address the question what is more important when we release an app: speed or quality?

Play

Download this show.

Launch our podcast player

News and events

The complexity tax

Don’t you hate it when somebody beats you to the punch? I recently finished writing a report for our biggest client (Wiltshire Farm Foods). It talks a lot about the need to simplify and remove complexity. It is a lesson we should all learn and so I am in the process of turning extracts from the report into a blog post which we will cover in next weeks show.

However, it would appear I have been too slow and that Gerry McGovern has beaten me to it with an excellent post on the cost of complexity. However, where I focus on why simplicity is important, he addresses the underlying causes of complexity.

For me his post is summed up in the following quote…

Most organizations are producing far too much content. Too many emails, too many PowerPoints, too many reports, too many webpages. All this content creation activity keeps a lot of people busy.

If you are part of a large organisation or work on a substantial website you need to read this post.

10 Rules for Driving Traffic Using Forums

What do you do if you have no marketing budget but have some free time to promote your site? Well, there are a number of guerilla marketing techniques you could use but contributing to forums is one of the most effective.

Sitepoint has posted an article explaining why forums are a great way of driving traffic to your site. It goes on to suggest 10 rules for doing so effectively. These include…

  • Build your profile
  • Follow the rules
  • Start by responding
  • Contribute your expertise
  • Don’t be a ‘me too’ poster
  • Don’t self promote
  • Explain yourself, but be brief
  • If you’re wrong, say so
  • Write intelligently and correctly
  • Negativity is a no-no

This is an excellent article and one that you should definitely read before using forums as a marketing tool. If you do not, you are in danger of damaging your brand, rather than driving traffic.

Accessibility in suit and tie

The life of the corporate web worker who cares about standards and accessibility can be a frustrating one; hampered by office politics and archaic content management systems. In an article on the Think Vitamin site, Bruce Lawson looks at what you can do to make sure your projects are as accessible for your users as possible.

Its a very pragmatic article, which I love. Bruce works from the premise that this is going to be tough and makes suggestions like "some accessibility is better than none". He also talks about the need for ‘buy-in from the top’ but goes on to provide practical tips about how to get that buy in. What is more, his arguments for accessibility were backed up with facts. For example…

Finally, he looks at how to get content providers onboard through education and getting them writing HTML rather than relying on the WYSIWYG editor.

UK Government Browser Guidelines

Our final story raises an interesting discussion; should you decide which browsers to support based on popularity or capability?

Apparently, the UK government believes we should test on the basis of popularity. In a draft document advising public sector websites, it suggests that if a browser appears in visitor logs as being below an arbitrary percentage of total “unique visitors”, then it should not be listed as being “fully supported”.

On the surface this appears very sensible. However, as Jon Hicks points out on his site, this can create problems. He writes…

It isn’t clear how the supported browser list would be enforced, but I’m concerned that this approach will encourage browser sniffing, a move that will exclude browsers like Omniweb, Shiira and iCab, simply because their name isn’t ‘Safari’. They share the exact same rendering engine, and therefore require no further testing. You can be more inclusive without spending any extra resources.

In other words we should be defining our list of supported browsers based on capability rather than popularity. This is the approach used by Yahoo! and it is one that I would fully support.

The Yahoo model supports all browsers through progressive enhancement and graceful degradation, without the need to test on every browser. Its a neat solution but one that the UK government guidelines specifically say they do not advocate…

These guidelines do not advocate specific development methodologies, for example graceful degradation or progressive enhancement. However, it is widely accepted that sites conforming to open web standards such as XHTML and CSS are more likely to work well across a wide range of browsers.

How come if they are widely accepted, do they not advocate them?

Fortunately there is an opportunity to change things before this is set in stone. I recommend reading the WaSP article on the recommendations and then sending some polite feedback to the powers that be.

Back to top

Interview: John Resig on javaScript Libraries

Paul:Joining me today is John Resig, who is famous for jQuery and the work that he has been doing with jQuery. John, it is great to have you on the show.

John:Well, thanks for having me.

Paul:I have to say this at the beginning. I have to get this out of the way. I absolutely love working with jQuery, and it’s an absolute pleasure. I remember twittering just a few days ago that every time I start doing anything in jQuery it makes me smile, so that’s got to be a good sign.

John:Well that’s good. I’m glad to hear it.

Paul: What I wanted to do today is get you on the show and not just for me to suck up and say how great jQuery is, but to kind of look a little bit broader at the subject of JavaScript libraries. Because I have to say from a personal point of view my opinion has changed quite a lot about JavaScript libraries and I’m kind of interested in your perspective on things as somebody that’s actually created one. I think the place I want to start is for a long time I had the attitude that you shouldn’t use JavaScript or indeed any library and that you should know the underlying code yourself and all of this kind of thing. Let’s start with the question of how do you know if it’s appropriate to use a JavaScript library? When is it appropriate to use it? What’s your opinion on that?

John:Well, I guess my opinion is it’s always appropriate, and I mean the simple fact of the matter is that there’s two things. One is that when you’re developing, you’re trying to support, generally a large number of browsers simultaneously. This is the same as if you are doing CSS development, JavaScript development, you want to support a large enough market share and you want to make that development process easy. The problem is twofold that you’re going to be encountering weird browser bugs and the APIs, the different utilities the browsers provide, will be different. For example, Internet Explorer provides different ways of handling events from all the other browsers. So what libraries do is that they remove you away from dealing with browser bugs, which is huge. And at the same time they provide a simple interface that you can interact with that will just work ubiquitously.

Paul:Is there a problem there in the sense of, you know, somebody came along and they basically learned to write jQuery for example from scratch, but never learned the kind of underlying JavaScript? Is there a problem there, do people need to know JavaScript before they start using a library?

John:It depends on the library, but I don’t think you do. I don’t think you have to know JavaScript. In a lot of ways, at least in my experience with jQuery directly there’s a lot of people who have used jQuery who have never done any programming whatsoever. jQuery does embody a lot of advanced concepts but you don’t necessarily have to know them in order to make good use of jQuery. I know this sort of translates well into some of the other libraries but one point of concern you brought up was what if someone learns a library but doesn’t learn JavaScript? I used to be more concerned about that, if someone only knew a library and I guess from a purist perspective, that’s a bad thing. Fundamentally, you want people to be getting better at programming JavaScript, not this specific thing. However, I think the reality of it is, is that so many people are just using JavaScript or CSS or doing web design, they just want to get their job done. It’s not really a matter for them of becoming an excellent JavaScript programmer or awesome CSS user, you want to get from A to Z and finish their work in an effective manner that works everywhere. So I think it’s important to realize that this market, so to speak, exists. It’s a very large one. And that ignoring it completely will just leave users frustrated and going back to the simple cut and copy paste scripts that they used to use. So, I think what libraries are doing is they are instilling good standards, they are instilling good practices, even though the users don’t necessarily know about it. And then eventually what’s good is that since these libraries have these good practices that users can always open up a library and read about it and try to understand better what’s going on.

Paul:I guess that’s always been a little bit of my concern with relying heavily on a library is that if you come across something that’s a problem or a bug or something like that, you can’t fix it yourself because you don’t necessarily know your way around the library. What’s your response to people that say stuff like that?

John:Well by the same token if you encounter a problem with a browser you are far less capable of fixing that issue. There’s really no way about it other than that ultimately it would be good to have that knowledge, absolutely. I fully support people who want to do that and I’m writing a second book now encouraging people to do that, to dig into libraries, to learn more, to build their own. What’s important here is that you just don’t, you can’t force people to do it if they, one if they don’t want to or if they’re just not capable. There’s no reason I feel to force a designer, someone who’s a designer by trade to learn the fundamentals of object oriented programming, or functional programming. Theoretically that can help them some way in the future but what’s more important to them is doing good design and I think by helping people keep their focus where it should be. Obviously if a library is able to help programmers program better, that’s good as well. It’s all about helping people keeping their focus and making sure they aren’t down a rabbit hole getting sidetracked.

Paul:I think that’s the thing that really attracted me to jQuery is as a front-end interface designer was the fact that I could pick it up and run with it very easily. The conclusion I came to is, “OK. Well if I do by some chance find a major problem with it, there’s a massive community of very clever people out there that I can ask and I can get help from.” So, that kind of reassured me, I think. If then, we’ve kind of come to terms with the fact: “OK we want to use a library.” There are so many different ones out there. Run us through some of the different options available and the pros and cons and how do you go about picking which library is right for you?

John:Well it really depends a lot. There’s a coupe questions you need to answer. Probably the most important of which is you need to ask yourself, how do you want to write JavaScript? Because libraries end up augmenting or really changing the style of how you write JavaScript. So, finding a library that you like how it looks. It sounds very superficial, but you like how it looks, you like how the code feels is a great place to start. There’s obviously a lot of libraries to choose from. There’s a select group of libraries whose quality is generally above the others and the popularity of those libraries generally reflects the quality as well. Out of those I pick generally jQuery, Prototype, Yahoo UI, dojo, then also MooTools and sometimes XJS. What’s interesting is all those libraries are open source and they are all the most popular JavaScript libraries. I don’t think that’s a coincidence. It’s just a matter of fact that in the web these open source frameworks are going to improve better and attract more users and generally have better community to surround them. So out of these libraries though you break down into a lot of different paradigms for development. I’ll try to summarize as best I can, but it really is not substitute for trying it out yourself. Looking and seeing some examples you can have a pretty good feel right away. So, Prototype and MooTools, they both extend the native objects of the language. They both try to improve the JavaScript language itself. So they add new methods to arrays, they make strings better, at the same time they provide things like object-oriented code
, and all the way out to doing things like events and AJAX. The normal things that you would expect. But at a very broad level they are trying to improve the overall quality of the language and of the experience. Then you have Dojo, Yahoo UI, and XJS and they are generally very modular, very package oriented and they have components you can easily snap in and out with nice ways of handling dependencies and it can end up being a very cleanly architected style of coding. They really support object-oriented code, and additionally events, AJAX, all the normal stuff you would expect. I would tend to group jQuery a little bit differently in that jQuery is more oriented toward improving the relationship between JavaScript and HTML and that it’s highly focused on searching through an HTML document, modifying some things, just getting in and getting out. Unobtrusive, and it doesn’t provide any language features, it doesn’t provide any object-oriented code writing features, it’s just hyper-focused at the task on hand.

Paul:It strikes me from my experience with jQuery that it’s very much a tool that’s primarily focused at helping front-end interface people implement the kind of functionality that they require from a usability point of view rather than necessarily doing, I mean would you build massive applications in something like jQuery?

John:It’s absolutely possible and people do it all the time. For example, T-Mobile’s T-Online in Germany, they built their entire user area so like their mail, their calendar, and everything using jQuery. So it’s absolutely used for very large projects. What I think is very interesting for jQuery at least is that while we don’t explicitly provide the object-oriented styles that most hardcore developers are used to we provide some very interesting alternatives especially they way it, like functional programming that I think actually end up suiting development very well. It’s very different, I will completely grant that, but it’s still very capable of scaling quite large.

Paul:So if people go out there and they have a kind of play around with these different libraries and try each of them out as you say to kind of find what fits their style of coding, once they’ve found something that kind of codes in the way they would like to, for example for me the similarities between jQuery and CSS made it a very natural fit, but what are the kind of things that you should look for from a functional perspective? What kind of things should be included in a JavaScript library? Does that make sense?

John:At the very core there should be a set of features. Of the libraries that I listed previously they all have methods for doing DOM traversal, so traversing through an HTML document, modifying an HTML document, events, so handling user interaction, animations and AJAX. All of them have some support for that to one degree or another. You can be fairly safe in knowing that if you pick a library you will have that base level. In my opinion those sets of features are probably the most important features and the ones that you end up using the most with your applications. Some people might say in their particular case that maybe animations aren’t as important, or maybe that they aren’t using AJAX, it really depends but for most of the time that set of features is fairly comprehensive. On top of that you really have to start to, once you’ve tried to use it, and once you’ve played around, there’s a whole set of secondary features that you kind of have to dig into, ones that aren’t immediately code-related. Things like the community around a library, the documentation for a library and even the health of the projects themselves.

Paul:What do you mean by that last one, the health of a project?

John:There’s a lot of things. In health, do they have an active development team? Are there developers? Are there multiple developers? It’s the famous hit by a bus; if a developer is hit by a bus will the project still continue? Is there a team will continue? Can you view the source code? Is there a repository where you can go? Is there a bug tracker where you can submit bugs? And finally is there a test suite, is what you’re going to be using going to be tested and analyzed to make sure it stays working. Another point that’s important to bring up is that a lot of browsers now are starting to integrate the test suites of these libraries into their test suite. So for example actually this is a lot of my work at Mozilla, was integrating the test suites of Prototype, Scriptaculous, jQuery, MochiKit, a bunch of libraries into our test suite such that if we ever added a change that caused a regression to happen in a library we would catch it and we would fix it on our end. Obviously we would do this in a very smart way, we wouldn’t just blindly be like, “Oh something broke!” We would communicate to the library what the issue was or whatever and this has been very big because now you can, there’s an extra level of safety and security here, in that you’ll know that if you’re using a library like this that it’s going to continue to work going forward in these browsers. That’s an extra level of safety that your personal code can’t provide. I think that’s very interesting. I want to jump back here really quick to the other issues I mentioned.

Paul:Sorry, I distracted you there and we took you off topic.

John:It’s OK, it’s OK, of community and documentation. So community, it can be usually be pretty easy to determine the health of the community. All these libraries will have some sort of a mailing list or a forum that you can go to. Just hopping on there, seeing how many messages are posted, seeing what the typical response is like, how they treat new users, just stuff like that it can be really useful because if you’re just starting out, you know you’re going to have some pretty basic questions. Do they understand your problems? Do they help you out? Doing some searches on Google for example to see how many people are talking about it, or using a service like Technorati or something. Are people blogging about it? Is it positive? Are they having problems? The other thing is documentation. This is also pretty easy to tell. If you are starting out with a library, you’re probably going to start out by doing a quick test, running a simple application just to get a feel for it. When you’re doing that you’re immediately going to be in the documentation trying to figure out how things work. I think you’ll be able to determine pretty quickly if the documentation quality meets a standard that you, because if you aren’t, if the documentation just isn’t that good, you’ll immediately have problems and I guess you will have to resort to the mailing list or the forums or whatever. Secondary is, do they have good examples? Do they have books if you want to learn from a book? Do they have books that you can buy to learn from? So again there’s a whole lot of issues here but what a lot of it boils down to is looking at the libraries, looking at their style of code, does it seem alright with you? Then just doing a quick test with each of the libraries that you’ve picked out, building like a menu or just a basic form of interaction. How easy is it? How hard is it? Does it in fact mesh with you well? This is something you can do over the course of a single day and it definitely shouldn’t take you any longer th
an that. If it’s taking longer than that then you probably want to try a different library. Ultimately you should be trying to use these libraries to make your development simpler and easier. If it doesn’t improve your productivity, if it doesn’t improve the quality of your code then you probably shouldn’t be using it to begin with.

Paul:Tell us a little bit about the kind of plug-in architectures that exists around many JavaScript libraries. Certainly I know there’s a strong plug-in architecture with jQuery. Does the same kind of thing exist with other libraries?

John:It depends. What jQuery has is a little bit unique in that we provide a number of plug-in points that plug-ins can snap into and extend how jQuery works. So they can add in new CSS selector behavior, or they can add in new events or all sorts of intricate additions. Other libraries have things that aren’t quite of the same vane, in that they’ll have modules or packages that you can use. Also another thing that varies is how do the various projects treat these plug-ins? At least with jQuery there’s a dedicated plug-in repository that’s used that plug-ins are listed in that you can browse through, you can see ratings, comments, discussions and things like that. Currently no other framework has something similar to that to the best of my knowledge. It’s much looser, just people uploading, putting things to their websites or Google code or some such. So again, at least to me, what makes plug-ins, jQuery-style plug-ins important is that they are, that there’s extension points and that they are supported by jQuery fully.

Paul: The only thing that I think that I kind of struggle with a little bit about plug-ins, you know I love the idea that there are other people out there that can do the hard work for me in that they can develop something I was looking for, and I love the fact that I can go to jQuery, I can type in whatever I’m looking for and it will pull back stuff. I’m always a bit unsure mind about how reliable those plug-ins are, you know as you’ve been saying with the kind of, the core jQuery library that you’ve created I know there’s a big team of developers working on it, I know that it’s thoroughly tested, I know what browsers it’s tested against, all of that kind of stuff. Plug-ins are a bit more of an unknown entity. Is there any kind of advice that you can provide about judging whether a plug-in or module or whatever is reliable or not?

John:I mean you sort of have to use the same standards that you would use in looking at a library. Looking at, what you mentioned, is it tested? Is there good documentation? Are there, how many developers are working on it? Like for example in the jQuery project we started a sort of, sub-project called jQuery Glide in which we’ve taken a whole bunch of plug-ins and actually blessed them and proved them, given them themes, excellent documentation, examples, all this stuff and made them sort of official. We’re doing this more and more, trying to bring in more plug-ins, improve their quality and make sure that they’re up to our standards. There’s still tons and tons of plug-ins that are just excellent, but the issue comes down to that you have to sort of train your eye to look at, and be able to spot when something has good quality. The thing that’s easiest for a plug-in author or a library author to do is to just set up a page that has their code on it and has a basic example. At the very least every single library is going to have that. If you dig in and see that it has documentation, that it has tests, you begin to realize that that plug-in is a much higher quality, at the very least. I think it’s really starting to dig in to these side issues, that you begin to get a better picture of how, of the true nature and of the true health of a particular library.

Paul:Excellent! That’s really useful and I think it’s easy to just look at these libraries and indeed the plug-ins as well and ask, “Well do they have the basic functionality that I require?” But, like you say, looking at things like the community and documentation and things like that are equally important. It’s been very useful John. Thank you for taking the time to come on the show. No doubt we will get you back in the future to talk about some of the specific things going on with jQuery and maybe this book that you’re writing as well, sounds very good. Thanks for your time.

John:Thanks for having me, Thank you.

Thanks to Todd Dietrich for transcribing this interview.

Back to top

Listeners feedback:

Quality or Quickly?

What is more important, to reach market quickly or to launch with a quality product?

I received this question from Pete in South Africa…

I have been working on a small web application, which I hope to launch soon. My problem is that I am spending ages tweaking and improving it before launch. I fear that if I spend much longer on it somebody will beat me to market. What is more important, getting the product right or launching it quickly?

It is a good question and one with no single answer. It is certainly something we have been struggling with as we prepare to launch GetSignOff.

To read the rest of this blog click here.

Back to top

An interview with Freelancer Magazine

I have just finished an interview for Alex Stubbs over at freelancermagazine.com. Being a clever cookie he massaged by ego and convinced me to take part even though I am on a family holiday in Scotland.

I hadn’t come across Freelancer Magazine before, but it certainly looks like a superb site. If you are a web design freelancer or are considering making the swap then definitely check it out. It has great features, useful resources and of course star studded interviews!

But before you disappear over to their site take a look at the interview.

Thank you, Paul, for taking the time to speak with us.

Absolutely!

So how are you enjoying your vacation in Scotland?

Scotland is one of the most majestic places in the world. At least if it isn’t raining. I have found it incredibly inspiring being out of the office and away from the web. I have achieved so much more here because I am free from distractions.

Getting to the meat of our discussion is your weekly podcast on Web Design, which is to date the longest running and most popular web design podcast.

I believe you started this in 2005 and it has been gaining more and more recognition since. How do you feel this medium has served you and your web presence over the years?

I was very fortunate to stumble into podcasting. I started out blogging but found that hard work. I love writing but find it much harder to express my enthusiasm and excitement for a subject. Podcasting was a natural fit for my personality.

I doubt you would not be interviewing me if it wasn’t for the show. It has done a huge amount for my personal profile and that of my web design company Headscape. It is also what has enabled me to write the Website Owners Manual too. I doubt any of that would have happened if I had just stuck to blogging. There are simply too many blogs around. You need a way to stand out from the crowd and in my case that was through podcasting.

Any future plans for video podcasting?

I have thought long and hard about video podcasting and yet I do not have an answer for you. On one hand video podcasting is hugely popular and an enormous growth area. It would also enable me to show code and designs. This is something that constantly frustrates me about audio podcasts.

However, on the other hand I am aware that many people listen to my show while walking the dog or commuting to work. You cannot watch a video podcast in such circumstances. Video demands your attention in a way audio does not.

Probably at the end of the day it will come down to return on investment. Doing a full blown video podcast is a lot of work. Unless we can make it pay for itself I doubt it will happen. For now people will have to be satisfied with the audio show and the live ‘behind the scenes’ video stream.

You also have a new project in the works which has gone live recently on boagworld.com: “The Website Owners Manual. Which from what I’ve read seams to be an evolving manual for anyone interested in running a successful website (from start to finish)….

I am really excited about the Website Owners Manual for a couple of reasons. First, there are so few books aimed at website owners or managers. They are all aimed at designers and developers. However, the client is key to the success of a project and there are certain things they need to know. Second, I am excited by the way this book is being produced. Instead of simply being published, this book is evolving through social participation. You can get access to chapters right now and have the opportunity to comment on and contribute to those chapters. I collect your feedback and adjust what I am writing accordingly. At the end of the process you get the final product. Its publishing 2.0… or something like that .

Sounds very progressive! Here at FM the bulk of readers seem to be beginning freelancers who themselves will need to know a bit of knowledge you’ve outlined in this manual… what points do you think this book would be most important to our readers?

I think the main thing will be how to better communicate with clients. The problem with most people who choose to start freelancing is that they under estimate the challenges of dealing with clients. You might be the best designer or developer in the world, but if you cannot deal with clients effectively you will fail. The website owner manual shows you what clients need to know and demonstrates ways of presenting that information to them.

So you’re the Creative Director at Headscape, you run a weekly podcast, you speak at numerous web design and marketing conferences, and still find the time to write a book. I think even David Allen himself would be proud… whats your productivity secret? Whats your daily life like?

I am a huge fan of David Allen and follow the Getting Things Done methodology closely. However being organized is only half the battle. The other half is recognizing what you are good at and sticking to that. I know I am an ideas person. I am great at starting stuff and terrible at finishing it. I therefore surround myself with people who are good at following through.

At Headscape I have three fellow directors who are expert at managing me to be at my most effective. They bring me in for short bursts of activity when a load of ideas are required and then quietly push me to the sidelines when the REAL work begins.

With the podcast, I rely heavily on the community to make it happen. There are people who transcribe the interviews, moderate the forums and even produce the show. There is Paul Stanton who helps me source news stories. Ryan Taylor produces the show by organizing guests, writing show notes and much more. Finally there is Anna Debenham who is our technician. She edits interviews, manages the site and handles the RSS feed.

These people all give up there time because they love the show. That makes me feel very honoured. I would be lost without them and feel guilty that they don’t get more out of it.

You started out as a Web Designer and evolved into other areas since, I’m guessing mostly due to your success with your podcast. How was your early experience when starting out as a Web Designer?

I started out designing for the web back in 1994. I was working for IBM producing CD-ROMs for the first generation of multimedia PCs. While doing this IBM decided to start taking the web seriously and so I got involved very early on.

I was just a junior designer which was why I was given the web stuff. It just wasn’t important back then. My career ended up growing in line with the growth of the web. As the web became higher profile so did my job until eventually I ended up working as a creative director at a dot com company in the late nineties.

Basically, I just lucked out. A lot of success is luck. The idea that successful people are in someway more talented or better is just not true. It is about being in the right place at the right time. That and having a big mouth and being willing to shout about how good you are!

What advice do you have for those looking into starting out as a Web Designer themselves?

Wow that is a hard one. Its very different starting out today compared to my experience. That said, here is my gut reaction.

First, know the basics. Focus on HTML, CSS and Javascript before anything else. Don’t get distracted by the latest fad or the more exciting trend. These are the fundamental tools you will always need.

Next, find talented people you admire and get alongside them. Don’t be shy in approaching them. In my experience they love the attention!Follow their work, ask questions and look at who they follow and admire.

Finally, get involved in the web design community. Go to meetups, conferences and other events. You will learn so much from your peers. Far more t
han from a book
or university course.

127. Context

In this week’s show we discuss taking context into consideration when designing websites and we answer your questions about video for an elderly audience and the most influential books in the industry. 

Play

Download this show.

Launch our podcast player

News and events

Working from home

The first post this week appears on A List Apart and applies to a growing number of people in the web design business. That is because it is tackling the subject of home working.

According to the home business report (PDF) published in October 2007, home based business account for 28% of all employment and have a combined UK turnover in excess of £364 billion.

No doubt that percentage is even higher among web designers. Therefore it comes as no surprise that this subject is being increasingly written about in web design circles.

This particular post is written from the perspective of a home working mother. However, her advice applies to anybody consider working from home. This advice includes:

  • How to draw the line between work and home
  • How to isolate yourself from the rest of the family while working
  • How to explain to your client the screaming child in the background of a conference call
  • How to win clients that are understanding of your situation

If you are already a home worker, I am not sure this article tells you anything you wont have already learnt the hard way. However, if you are considering making the switch for whatever reason this is definitely a worthwhile read.

British Standard for accessibility

Some time ago the British Standards Institute and the Disability Right Commission teamed up to release the first formal guide for business on website accessibility entitled PAS 78.

PAS 78 was intended to be a web accessibility guide, aimed at website owners rather than web designers . Personally I found the result somewhat disappointing. Although the advice was solid the language was hard going and it referred too often to the WAI guidelines. Although these guidelines are superb they are too technical for most website owners.

However, despite my personal opinion the document has proved very popular and is now being converted into a full British Standard. A British Standard is a common standard used across a variety of products produced in the UK. Although anybody can claim to meet these standards without external review, it is possible to be officially certified. Once certified you can display a BSI Kite Mark. This is a symbol of quality universally recognised in the UK.

Personally, I think this is a much better route for web accessibility to take. The alternative is legislation and that carries with it numerous problems. The team working on the standard is excellent and I look forward to seeing the result.

Growing your business through twitter

The next post solves an embarrassing problem I have. When sitting in the pubs with my mates, they occasionally catch me twittering. It is particularly embarrassing because I cannot really explain why I do it. Fortunately now I can thanks to a post from Tiffini Jones at Blue Flavor.

Actually the truth be told, Tiffini’s post refers heavily to another by Elliot J Stocks a few months earlier. He suggests that twitter is:

  • An ice-breaker
  • A purveyor of "ambient intimacy"
  • A broadcasting / marketing tool
  • A fount of knowledge
  • A social network

Both posts communicate well the power of social networks if used wisely. This has certainly been my experienced and without tools like Twitter this site and podcast would have been nowhere near as successful.

I know a lot of people look down their nose at twitter. They claim it is a time waster, unprofessional and dull. However, I think they are missing the potential. I believe that networking tools like Twitter will in time diminish the role of search engines. Increasingly people will turn to online contacts for recommendations about products, services and information, rather than relying on the algorithms of Google.

Smart CSS aint always sexy

My final article today, demonstrates a sea change in the web standards community. It is a controversial article on the Digital Web Magazine entitled Smart CSS aint always sexy CSS.

The article challenges some of the basic arguments of standards zealots. For example is it so bad to name a class ‘red’? Do we need to pursue semantics at all cost, even when it compromises performance or maintainability?

This seems to be representative of a growing group of designers calling for a more pragmatic approach to web standards. Increasingly I am seeing little examples of rebellion against the more extreme supporters of standards. Whether it is the posts of Jeff Croft or the twitterings of Andy Clarke, it would appear there is the beginning of a more grown up approach.

Does this mean we can throw away good practice? Not at all. It simply means we are mature enough in our knowledge to bend the rule sometimes. Before you can paint like Jackson Pollock, you first need to know how to paint traditionally.

The morale of the story is that if you are new to standards then you should stick to the rules. However, if you are more experienced, there is nothing wrong with making compromises from time to time.

Back to top

Feature: Content is dead, long live context

No, content is not dead. Yes content is important, but there can only be one king and I am beginning to wonder if it is context in this weeks feature.

Back to top

Listeners feedback:

Video and an elderly audience

Steven writes: I am currently working on a website that is going to be targeted toward an older demographic. There seems to be a large disagreement on whether video should be included on the site. The site is quite in depth and video explanation could be crucial. The main argument seems to be that people might not have the flash player and in turn not be able to view the video. On the other hand the Adobe site says that market penetration on flash player is over 99%!? Is flash video a usability issue?

One of the largest clients Headscape works with is trying to reach an elderly audience and so I have put some thought into this issue already. Unfortunately as with all of life, it is not a straight yes or no answer.

I see no reason why you cannot use video on your site. Although I do not believe Adobe when they claim flash has 99% penetration, I do believe the vast majority of your audience will have it installed. In my experience those who do not have flash are those behind a corporate firewall.

Although you can expect the vast majority to have flash I don’t believe you can design solely for it. The elderly develop visual, physical and cognitive c
onditions that can make it hard to interact with flash in some circumstances. Although a well designed application can minimise these problems, it will still affect a significant number of users.

I am afraid that although you can use flash, you will have to also provide an alternative. This could either be in the form of a transcript or captions (depending on the nature of the video), but additional work is required.

Most influential books

Teifion asks: What are the two most influential books you have read. Not just for web design but work and life in general.

I think this is possibly the hardest question I have ever had to answer. Choosing just two books has been horribly difficult. In an attempt to cheat slightly I have changed the rules to reflect BBC Radio 4s Desert Island Discs. This means I get the Bible and the complete works of Shakespeare for free! My choices are therefore…

  • Getting things done by David Allen – I know I have spoken endlessly about this book before but that is because it has had such a profound impact on me. It is an easy book to dismiss with statements like "I don’t need to read it because I am already organised" or "it just tells you to write lists". In fact it is about a lot more than that. Getting things done has made me radically rethink my life and what I spend my time doing. It has made me question my priorities and change what I spend my life doing. Yes, I do write a lot of lists now and yes I am more organised but that is not what I got from this book. It taught me to take control of my life and decide what I want to achieve.
  • Designing with Web Standards by Jeffrey Zeldman – I bought this book entirely by accident and yet it set my entire career in a new direction. Before reading this book I was feeling uninspired and stagnant in my career. I was bored with web design and felt that I had gone as far as I could. Reading this completely re-inspired me and introduced me to the web standards community. Without this book I doubt I would still be doing web design and certainly wouldn’t be doing this podcast or speaking around the world. Thanks Jeffrey!

119. Fluid Elastic

On this week’s show Ed Merritt joins us to discuss fluid, elastic layouts and we take a look at PHP Designer, a feature rich code editor.

Download this show.

Launch our podcast player

Watch the behind the scenes video

News and events

Harness the power of "frilly bits"

I love watching design trends come and go on the web which maybe why I love Patrick McNeil’s Design Meltdown so much. One trend that has caught my eye is the move away from the Web 2.0. look to something more ornate.

This style makes use of what can only be called "frilly bits". You know the kind of things, those swirls and ornaments buried in typeface sets but rarely used. They have been around for years, used by blacksmiths and typesetters alike. They turn up on everything from wedding invitations to architecture, and now it would appear, the web.

One of the first sites I saw them was Cameron Molls blog. He is an amazing designer with a very ornate and delicate style (about as far away from my own as possible).

Recently one of Cameron’s readers asked him where he sourced such beautiful ornaments and he has been kind enough to share 25 different sources of similar frippery.

Unfortunately, simply knowing Cameron’s sources will not grant us the ability to design as well as him. However, it is an extremely useful list and definitely worth perusing at your leisure.

The cure for content-delay syndrome

Returning from the world of creativity to the realities of project management, our next post tackles the frustrating subject of clients failing to deliver content on time.

Entitled the cure for content-delay syndrome this article addresses once again the subject of copy-writing.

We have talked about the need for a copywriter many times before. I have encouraged you of the need to engage a professional to craft your sites copy, while at the same time struggling to convince my own clients of the need.

The problem is that ultimately many clients believe they can write their own copy. After all they are experts in their field and know their own audience. Some argue that it takes as long to brief somebody as to do it themselves. When budgets are tight, these sound like convincing arguments and are hard to dispute.

This post suggests that the answer in not to promote the use of a copywriter but an editor. An editor refines the clients text rather than writes it from scratch. This is considerably cheaper but still brings improvements in continuity, accessibility, usability and SEO. What is more, the client no longer needs to worry about the quality of his writing. Instead he can concentrate on "bashing it out" and let the editor improve its readability later.

Its a persuasive argument and gives me hope that I might soon be able to encourage my clients to engage a professional to work on their copy.

The roles of a web entrepreneur

From the role of an editor to the many roles of a buddying web entrepreneur.

We haven’t spoken much about developing web applications on the show (this is definitely something we should try to do soon). Traditionally web design has been a service industry and for the vast majority that is still the case. However, a growing number are looking to add a product line to their offering or make the switch entirely. Certainly this is something we are doing with getsignoff.com

But what does it take to be a web entrepreneur and build web applications? Well, unless you have a lot of venture capital it requires you to wear a lot of hats as explained in this post on Think Vitamin.

From marketeer to customer service representative, you are required to fulfil many more roles than you are used to. Its a challenging undertaking but the benefits are substantial. Get it right and you have a regular income without the overheads associated with a service based business.

Intranets revisited

Another subject that we have neglected on the show is intranets. They continue to grow in importance and yet have fundamental unresolved problems.

In two great posts Gerry McGovern exposes these flaws including the tendency for intranets to become dumping grounds for information and their lack of decent search.

Both posts in their own way focus on the fact that intranets should be about "getting things done". They should provide tangible productivity benefits but often fail to do so. Each post identifies a reason for this being the case.

The first points to the way intranets are perceived. Many see them as an information repository. This appears to be a fancy way of saying "where information goes to die". Viewing an intranet in this way, McGovern argues, is to miss the point. We should only be distributing information if it aids productivity or encourages collaboration.

The second post argues that intranets fail to aid productivity because information is just downright hard to find. In particular Gerry targets search but he also argues there is a wider problem of find-ability. Why is it he asks, that even in the largest of organisations nobody is dedicated to ensuring employees can quickly access the information they need to do their jobs?

If you have an intranet or are involved in developing them, then these are an excellent read.

Back to top

Feature: Fluid Elastic Design

When it comes to planning the layout of your new website there are just three commonly used website layout structures to choose from: Fixed; Fluid & Elastic width layouts. None of these are perfect; each comes with its own advantages and disadvantages and in this weeks feature we have Ed Merritt with us to disuss them.

Back to top

Review: PHP Designer 2008

This week’s review is on PHP Designer 2008 has actually been submitted by Simon Jones of Zako Media. He writes…

As a web business, I needed stable coding platform or IDE which would allow me to be as productive as possible. Money was no object so I researched everything available from open-source packages to expensive commericial software. I discovered phpDesigner from www.mpsoftware.dk and was blown away. It’s much quicker than Zend and has most of the same features. phpDesigner has all the usual code highlighting and auto-completion for PHP, CSS, HTML, Perl, XML, Javascript, along with easy buttons to tidy this code on the fly. We all know how hard it is to keep code tidy… now we don’t have to. phpDesigner also allows you to arrange files by project without disrupting the standard windows folder system. If you ever want to transfer away from this software, you don’t need to worry about compatibility.

The smaller features I find most useful are: bracket matching, code explorer (to jump to functions, variables and arrays), code snippet library to store your most commonly used functions from project to project. Tooltip syntax reminders for PHP and rightclick to view PHP.net help page for that function. Finally it validates your syntax on the fly, without affecting performance… all other editors stalled, slowed and chugged away as they scanned the whole file every time a character was added. phpDesigner offers the same ability with very little processor time, as soon as you’ve finished a line, it hilights unobtrusively to show missing semi-colons, brackets etc. A more detailed error message can be accessed. This saves valuable Alt-Tab, Control-F5 time. (or for apple users, switch task and refresh browser) as you know the code is error free before you start.

The software offers links to internal ‘browsers’ for phpmyadmin and php help, has an inbuilt ftp client or allows you to call an external one like filezilla. It helps integrate nicely with Smarty templates and works with phpDocumentor for instant php documentation.

On the longer term projects, it has built in bug tracking information, project and global todo lists.

One of the most important and major strengths with this software is it’s stability. It has a few issues sometimes closing down if it’s travelled through a laptop’s standby mode, but otherwise it has never crashed or lost data in the years I’ve been using it. mpsoftware is obviously passionate about this product as updates are available very regularly offering additional functionality and fixing minor bugs.

This is by no means the full feature list, but more information can be found at www.mpsoftware.dk where they have a free cut down non-commercial version and sell the full version. Compare to other available software and it sounds expensive, but mpsoftware.dk is charging a ridiculously low €39 for a single license with further discounts for groups of 10.

Thanks to Simon for that review.

Back to top

Listeners feedback:

Can you set up a web design company in the evenings

John Bullock asks: Hello boagworld team, my name’s John and I’ve got a question for you. Basically I’m starting up my own web design company and I’m in what I think is an unusual situation of trying to do it along side my 9 to 5 job which has absolutely nothing to do with computers, it’s actually an engineering job so I actually have no chance at all to work with computers in my normal job. Now I know trying to set up a company alongside your 9 to 5, while obviously tiring, is a very sensible and safe way to do it, is it actually possible? Do you think it’s a realistic way of setting up a company or do you think I would have been better going with the freelance option? It’s great to have the show back after what seemed like a decade and keep up the good work.

Yes it is definitely possible. In fact it is the way the vast majority of freelancers begin. That is not to say it is easy. However, it is the most sensible approach. If you don’t your options are fairly limited…

  1. Wait to be made redundant and hope you get a payoff
  2. Live off the kindness of friends and family (a guaranteed way of losing friends)
  3. Borrow money from the bank

Personally, I am very much against borrowing money. It substantially increases the risk. If you setup loan free then you can get another job if things go wrong. With a loan you are left in debt and struggling to pay the rent.

Build up a freelance business on the side and save the money to pay for the first few months. Also if you are able, land some regular customers. This will give you an existing client base to bring in much needed cash. At the very least you will have a portfolio of client work to show off.

We were fortunate. The web design company we worked for folded. Although we didn’t get any redundancy payment we were able to take several of the clients with us. These not only provided valuable income in the first few months but also allowed us to attract other clients.

Domain names

Robert Prior asks: Hello Paul and Marcus, my name is Robert Prior and I am from Waco Texas, i’m currently a beginner web designer but in the future I would like to set up a small web design agency here where I live and my question is, when you’re trying to get the URL for your company name, how important is it to get different extensions like .net, .info, .tv are those important at all? Or do you just need to get the one main one like the .com name? Really enjoy the show, appreciate all the hard work you guys put into it and looking forward to future episodes. Thank you.

In my opinion your domain name is incredibly important. You should definitely try to get the domain extension for your country and .com as well. We have never managed to get headscape.com but as the vast majority of our business is in the United Kingdom headscape.co.uk has been adequate.

However a good domain is about a lot more than the extension. Personally I am not a fan of these new web 2.0. urls (flickr, del.icio.us, digg). They are hard to spell and hard to remember. In my opinion a good url should be a well known word (or words) even if not directly associated with your product. Headscape for example sounds more like a hair dressers than a web design agency, but at least it is memorable and easy to spell.

Another common mistake is to go for a domain name with hyphens. This never works well as it is hard to tell somebody. For example "headscape dot co dot uk" is much easier then "head hyphen scape dot co dot uk". Also users often later forget that it contained a hyphen.

The ideal domain is also descriptive of the site. For example we were blown away to discover getsignoff.com was available. It describes exactly what we do and is memorable too. That said more recent studies suggest that a brand name (Amazon.com) is more valuable than a generic name (books.com), so if you are forced to choose pick the former.

Finally, be careful to avoid words with multiple spellings especially if working internationally. For example don’t choice a domain like colorTheory.com because it could equally be spelt colourTheory.com.

Many claim that there are no good domain names left. Although it is harder these days getsignoff proves they are still out there. With a bit of lateral thinking (or using one of the domain suggestion tools) they can be found. There is no reason to start randomly start dropping vowels.

Boagworld is back

On the 20th March I logged off. No podcast, no twitter, no facebook, no posting, no nothing. But now I am back and this time I mean business!

What a crazy month. I have hosted both the Highland Fling and the Future of Web Design. I have re-built the Headscape website and re-launched boagworld with a new site and new team.

All of this has only been possible by completely cutting myself off from the web design world. But has it been worth it?

An interesting experiment

I dare to think how many hours I spend talking with people via Twitter, reading RSS feeds and adding friends to the latest social network. To be honest I don’t think I want to know.

However, what I can tell you is that going cold turkey for a month and a bit has been an enlightening experience. Without a doubt I have got a huge amount done. Productivity has been outstanding and I am pleased with the redesign of both Boagworld and Headscape.

Despite that, I am glad to be back. Life is about more than increased productivity and I have missed the social interaction of twitter and felt ignorant about some of the big web design stories of the last few weeks.

Time to think

Although I have been busy, the time away has given me an opportunity to think about my job and the podcast. Producing the podcast is demanding and I spend more time talking about web design than doing it. If I continue down this track I am in danger of becoming out of touch with what most of my listeners have to deal with.

Getting my hands dirty with both Headscape and Boagworld has reinvigorated me and given me loads of ideas for the show. In fact, I am intending to use the two sites as a case study over the coming weeks.

If I want the show to remain relevant I have to do either one of two things. Reduce the content or get some help.

The new Boagworld team

Although I am intending to curb the length of the show (I have said that before!), I am more attracted to the idea of getting some help on board. It is time that we produced the show in a more professional manor. With that in mind I would like to introduce three new members of the boagworld team…

Ryan Taylor – Ryan is going to be our producer. He is responsible for arranging guests, writing show notes and ensuring everything runs smoothly.

Paul Stanton – Paul is our researcher and he will work with me to find the best news stories and subjects for each week’s show.

Anna Debenham – Anna is our technician and will be responsible for making the show live each week and doing some of the audio editing.

They are all volunteers and I am incredibly grateful for their help. To learn a bit more about each of them check out our about us section.

The new site

Finally I want to quickly mention the new site. As you can see we have done a complete overhaul and tried to bring it more inline with Headscape (without becoming too corporate). However, I should confess that it was done in a rush. So, if you spot any bugs or problems that need fixing please drop me an email via our new contact us form.

P.S. All good websites have an easter egg. Mine is a page that allows you to stalk me (because I am that vain). See if you can find it. I might even be able to scrape up a prize for the first to succeed.

Lessons learnt at SXSW 08

Marcus shares his impressions of SXSW and the lessons we can all learn.

Looking back at my
notes, I didn’t realise how much I actually took! So, I have decided to focus
things a bit and look at talks given by people from three big interactive
agencies. These presentations were fascinating to me as they gave me an insight
into how these companies run their businesses, their projects and make
decisions about their futures.

Respect!

This was a great start
to the conference, really got me in the mood. What I expected was a Zeldman criticism of the corporate world’s misunderstanding /undervaluing/general
disdain of all things ‘web’. I think this was what he was trying to do but what
we got was a run down of how Happy Cog works or more particularly how it runs
it projects – great for me!

It was quite
reassuring in that they do pretty much exactly what Headscape does:

  • Stakeholder interviews – though there was
    a wonderful description of when you really know that you’re about to get to the
    bottom of an issue with a client – that ‘close the door’ moment
  • User testing/requirements
  • IA
  • Design – they still do multiple concepts (which
    we very rarely do now) though try to avoid ‘Frankensteining’ the design
  • Build

The big thing, for
them, missing from this list is content and copywriting. They employ a
specialist copywriter who has a wide-ranging remit from kicking off the content
process to completely writing a site’s content. However, usually they
concentrate on editing ‘raw’ content into one styled voice.

Zeldman says that the
content is the most important aspect of any site. He has a point – we
don’t go to websites to enjoy the design or appreciate the usability of the
navigation.

This is, I expect, the
next big thing for Headscape.

Ten things we’ve learned at 37
Signals

Jason Fried telling
everyone 10 things they’ve learned at 37 Signals. I found his delivery a little
grating, which is why I probably don’t have too detailed notes on this talk.
But, again, this was interesting stuff from my point of view, learning about how
a small company operates particularly because we are about to go down the
product road.

The general theme of
his biggest messages were:

  • Keep it simple – otherwise you won’t ever
    release your product.
  • Don’t plan – plans tend to have a habit
    of becoming ‘sacred’. That is, people tend to stick to a particular goal
    religiously, rather than adapting to what is the best way.
  • Don’t expect your next thing to be way better
    than the last. If you’ve had a hit it doesn’t necessarily mean that you’re next
    offering is going to be as well.
  • Don’t talk to each other! I really wasn’t sure
    about this, but JF basically felt interrupting people through talking was the
    key productivity killer. Methods of communication that can be ignored -
    IM, email, Basecamp etc – are fine.

10 Tips to Managing a Creative
Environment

This was the best talk
of the lot for me. With most of the ‘famous’ agencies, I feel that what we do
is not too far away from what they offer. However, these guys felt like they
were in a higher league.

The talk was given by
Bryan Mason (CEO) and Sarah B. Nelson (Design Strategist) of Adaptive Path.

They had looked at
(and interviewed) a number of other organisations that they felt there was some
similarity with a design agency. These included:

  • Theatres
  • Restaurants
  • Orchestras

They are all highly
creative places (probably more so than the design agency), they have absolute
deadlines (again, probably more so than the design agency) that mean highly
regimented processes are required while keeping creative staff focused.

These are the tips
that they have learned:

  • Cross-train the entire team – not easy, but it does build
    understanding and therefore empathy towards other people’s jobs and the effort
    required to deliver them.
  • Rotate creative leadership - makes people value others’ decisions
    because they know that they will get their turn.
  • Actively turn the corner – meaning make a specific decision to go
    from ‘thinking’ to ‘doing’ and make sure that everyone knows which phase
    they’re in. The thinking phase being the point where there are no bad ideas or
    questions with people moving into their specific roles (see point 4) for the
    doing phase. They described this process as divergence to convergence.
  • Know your roles - once the corner is turned everyone
    needs to know what is expected of them and when.
  • Practice, practice, practice - they mean ‘practice as a group’ i.e. keep
    familiarising (and improving) processes. This ensures quality under pressure.
    Look to bring new people in at quiet times or on internal work.
  • Make you mission explicit - to the entire team so everyone knows
    where the team is supposed to be going and what they stand for (i.e. what it
    means to be a ‘Headscaper’ instead of just a ‘designer’ or ‘developer’). Cut
    out stuff that isn’t part of the mission – be ruthless.
  • Kill your darlings - but do it respectfully e.g. for the
    young chef – "we won’t use that recipe, it’s not for us. You put it on
    your menu when you get your first restaurant!" AP hiring decisions are made
    without discussion – thumbs up, they’re in, thumbs down, they’re out.
    They only discuss if it’s neither.
  • Leadership is a service - leaders should talk to everyone about
    their involvement. For example, a creative director should provide space not
    enforce their vision.
  • Generate projects around the groups’ interest - in other words, only take on work that
    you want! Easy said. However, maybe a watered down version would be to dish
    work out based on personal preferences rather than just who’s available. BM
    said "any time that AP has taken on work for the money or the kudos of a
    particular client, it has bombed. If there’s no interest internally in a pitch
    - drop it".
  • Remember your audience - what you’re doing isn’t for you, don’t forget that and don’t
    forget who your specific audience is. They used the kitchen analogy where the
    restaurant manager’s audience is their existing customers. He needs to make
    sure that the guy who loves liver and onions gets the same every time. The chef
    doesn’t care about this. His audience is the new customer.
  • Celebrate failure – creativity
    doesn’t always work. Carry out project post mortems but call them ‘after
    parties’! Discuss what worked, what didn’t and what was learned. Don’t
    apportion blame. You want your creative team to take risks and to feel that
    they can take risks. If you have a blame culture then safe and boring (and
    eventually stagnation) is where you’ll end up.

Hiring new staff

Marcus’ shares his advice on finding new staff

Got this from long-time Boagworlder, Paul Bond (man of impeccable musical tastes as well ;-)…

Hi Marcus and Paul, still loving the show even after all this time.

My questions to you are: how would you advise I go about taking someone on and should I take someone on full time or on a freelance basis? Also where should I start looking to find someone? And there’s the financial side, I plan to have a couple of months wages in the pot to cover an extra person’s backup, does that sound enough? Also, whoever I take on needs to make the business money obviously so I was wondering if there was some sort of magic ratio or formula that I could use to see how my business model will fare against employing a new person?

You guys regularly employ new designers so I would be interested to hear your criteria for hiring someone new. Keep up the good work, if for nothing else, so that Rissington podcast can continue learning from the masters!

Ok, there’s a lot here! I think the first thing I need to discuss is whether Paul is looking for an employee or a partner. He mentions that whoever he takes on needs to make the business money. If he means for the new person to actually bring work in, and assuming he’s not looking to take on a sales person, then I guess he’s looking at a partner. That is, someone that fulfils a similar role to him. This would effectively be two freelancers deciding to pool their talent (and client list) with a view to expanding that client list but particularly, taking on bigger jobs.

Finding the right person for this type of role, I believe, takes a lot more than just advertising. You need to know and trust this person, so I would expect only an ex-colleague would fit the bill.

However, if you’re looking to take someone on to pump out the work while you’re out there getting more, then that’s a different kettle of fish. You can’t expect this person to make the company more money per se. Rather, you are looking at having more resources available so you can take on more work thereby raising the monthly bottom line.

There’s no real magic formula; just simply, can you make more than this person’s salary every month. If you can feed the extra mouth then you’re in a strong position to grow the company. If not, then you might want to run with it for a while anyway (if you can afford to) because staying solo does limit your options – for growth and for expanding the work you can take on which eventually leads to more work etc etc.

A couple of months ‘break even’ is what I would recommend you hold in reserve. So that adds up to your salary, the new salary plus any bills you’ve got.

I’m jumping around a bit, but let’s move on to the working together option. Not even 6 months ago I would have been indifferent to this. Basically, the pros of being able throw the net wider and the fact that a lot of people (particularly designers) like to lock themselves away (and therefore potentially make the position more appealing), meant that we tended to err towards people home working. However, my mind has definitely changed on this lately. Our development team have demonstrated that working together brings huge productivity benefits in that people constantly share problems and help each other out. This has worked out so well that we have moved the design team over to a similar model.

Ok, moving on to who to take on – taking on freelancers can often mean the difference between being able to deliver a job or not. However, they are expensive and will badly erode your bottom line if you do it all the time. So, ask yourself – if I had an employee instead of a freelancer over the past X months, how much would I have saved?

Employees are a responsibility though and need looking after. One thing we have learned over the years is that happy staff make for more productive and more effective staff.

With regard to finding staff, there are a number of options:

  • Employment agencies – these can be good and are often the quickest way to find suitable staff. But… they add a huge cost to the whole process.
  • Websites like ThinkVitamin or 37 Signals can be a very good way of finding the right people too. However, this has been very hit and miss for us.
  • Ex-colleagues are often an excellent bet as you know them well. I guess on this one – don’t be afraid to ask.
  • And, of course, advertise on your own site.

Finally, how do we decide when to take someone new on? Well, we don’t really have a set method! Usually we start to notice that workloads are getting beyond the point of just ‘busy’ and we wrangle over whether we need permanent or freelance help. Often a new client or job will tip the balance.

HTML snippets

If you are part of a web design team or skip constantly between projects, then you might want to consider an alternative approach to writing your HTML.

At Headscape efficiency is king. If you are efficient, you increase profit margins and keep prices competitive. You can only charge as much as the market allows. If you want to increase your profits you need to complete projects faster, while avoiding lowering quality.

As part of our efficiency drive we identified 4 problems…

  • Designers have to work with each others markup. We all code in different way and this creates a learning curve when a project gets passed between designers.
  • Integration HTML markup into server side applications was time consuming. Because designers coded in a different way and change their markup for each project, it was time consuming to apply that code to web applications like our in-house content management system.
  • Designers were constantly reinventing the wheel. Each project was built from the ground up with little reuse of markup across projects.
  • It was confusing switching between multiple projects. In order to ensure the most efficient use of time, designers are expected to work on several projects simultaneously. Unfortunately, switching between project is confusing because each had different markup.

We required some way to standardise tour markup.

Templating doesn’t work

At first, we produced templates for the different types of pages. For example, we had news listing, text and FAQ templates. Although this worked, they were not very flexible. As soon as the content or functionality began to deviate from the norm the templates had to be heavily customised. This undermined the benefits they provided. They also didn’t allow flexibility of design. Although content and design should be separate, it rarely works that way. Sometimes content needs to be marked up up in a particular order. Other times extra divs are required. The templates didn’t accommodate either scenario.

We needed a more flexible approach.

Using snippets

The solution was HTML snippets. Content such as news listings, forms, navigation and FAQs appear in a vast majority of websites we build. By coding these in a consistent way each time they appear, we solve all of the efficiency problems mentioned above.

Take for example news listings. Most news listings look the same. They have…

  • Title
  • date
  • link
  • description
  • and sometimes an image

Because of this consistency you can code in the same way each time. Content will change, each will have its own unique id and sometimes an element might be dropped (e.g. the date or image). However, fundamentally the snippet is consistent

This consistency allows…

  • A designer picking up the code to instantly understand what is happening.
  • A developer to quickly integrate it with server side code because the integration is consistent every time.
  • Pages to be built faster because you are dropping in pre-generated markup

In affect all the designer has to do is build an HTML framework. This consists of the overall containers (main content, secondary content etc.) He then drop snippets into that framework in whatever order he requires.

However, the benefits don’t stop there. You can also associate CSS with each snippet of HTML.

CSS fragments

If your HTML snippets are consistent, you can also build up a library of CSS fragments to support them. Take for example our news listing. Not only does it often contain the same content it is also often laid out in the same way. The image sits to the left while title, date and description sits next to it on the right. Because we know what the markup looks like, we can create this layout as a CSS fragment that can be dropped in whenever this HTML snippet is used.

We are not limited to a single CSS fragment per HTML snippet. Over time you can build up a variety of different CSS layouts for each snippet that can be used as the design dictates.

This approach provides a huge productivity benefit as the HTML and CSS can be built up in a ‘pick and mix’ fashion. However, you can also take the principle one step further and apply it to Javascript.

JavaScript functions

Each HTML snippet can have associated Javascript functions. These can be dropped in just like CSS fragments. These functions carry out common behaviour associated with that HTML snippet.

Take, for example, a FAQ snippet. A common behaviour with this snippet is to only display the answer when a question is clicked. Because we have consistent code in the snippet, it is easy to build a function that works with it and can be dropped in as required. Where possible keep your functions generic and not tied to a particular HTML snippet. However, where that cannot be done, we have standard HTML that allows us to reuse functions across projects with no editing.

Conclusions

In many ways this approach is a cross between microformats and frameworks and so in itself is not groundbreaking. However, from an efficiency standpoint, the impact is overwhelming. Without a doubt it will speed up development times and allow you to turn around projects quicker.

Top Geek Gifts

So this holiday season (previously known as Christmas), what gifts would you recommend others buy for the geek in their life? Here are my top 10…

These are products I own myself and would happily recommend to others. They are not in order and I have tried to pick things that suit varying budgets.

1. A mac

2007 was the year I moved from a PC to a mac and I have never looked back. Best of all if you have the budget they make great gifts. They look cool, are a pleasure to setup (no swearing on christmas day when something doesn’t work) and if you give him a week he will be insisting that you have one too so he no longer has to provide technical support for windows. Buying a computer can be scary if your not technical yourself so I suggest going along to an apple store. Those guys will be able to help you with selecting the model that best suits the geek in your life.

Prices start at £700 and are available through the Apple Store.

2. An ipod touch

I actually don’t own an ipod touch but I do have an iphone. However, I thought it was unfair to suggest something that has a £35 per month contract associated with it! I love my iphone and can’t imagine anybody not being pleased with an ipod touch. They are sexy, fun to use and definitely a cool toy for christmas day if they haven’t played with one before.

The 16GB version of the ipod touch (which is the one you should buy) costs £269 and is available through the Apple Store.

3. The Jawbone

The Jawbone is a bluetooth headset unlike any other. I have awful hearing and have trouble with mobile phone conversations. The Jawbone however has amazing noise cancelling technology that makes calls crystal clear no matter how noisy the surroundings. Best of all it looks cool and you almost don’t feel ashamed to wear it in public (unlike most headsets). In my opinion the Jawbone is the best headset on the market.

You can buy the Jawbone in pretty much any mobile phone shop and I have seen prices as low at £64.

4. Getting Things Done

Most geeks I know live a life in chaos. Getting Things Done is a superb book that has transformed my life and made me a more organised person. If the geek in your life does not read then buy it as an audio book and pre-install it on his new ipod touch!

You can buy the book for £7.14 on Amazon or for $12.60 as an audio book from Audible.com

5. Moo Cards

Moo Cards are cool little cards similar to mini business cards. You can print 100 cards for £9.99 and each card can have its own unique photo. You can either upload photos or just grab some random photos from his flickr account.

6. A flickr pro account

Talking of flickr why not upgrade him to a pro account this christmas. Flickr is the most awesome photo sharing site around and although it has a free account it is definitely worth upgrading. For just $25 the geek in your life can upload a limitless number of photos.

7. A Tom Tom

My sense of direction sucks and I couldn’t live without my Tom Tom GPS. Chances are the geek in your life doesn’t get out much, but when he does he wanders around looking lost and confused. A cool GPS in your car might encourage him to venture out of the house more. You never know.

They seem to sell Tom Toms pretty much everywhere these days from Halford to Currys. Prices seem to start at the £149 mark. To be honest the lower end models seem perfectly good from what I can tell.

8. A DVR

A DVR is a Digital Video Recorder such as the TiVo in the states or Sky Plus in the UK. These clever little boxes let you record programs to a hard drive, pause live TV and series link an entire season of a show ensuring you never miss it again. Having one of these babies will change the way he watches TV forever.

If you buy Sky Plus online at the moment you can get the box for £49. Of course it does require a sky subscription which starts at £16 per month.

9. A Duct Tape Wallet

Okay admittedly a wallet isn’t the most hi tech gift but Duct Tape Wallets are cool. Basically they are… well… wallets made out of duct tape. I know that sounds strange but they make a great stocking stuffer. Mine has lasted forever, it always generates discussion and its easy to repair (stick more duct tape on it).

I bought mine from Ducti and it cost about £15.

10. A Wii

I know there is world wide shortage of these babies but try to get one. The geek in your life may sneer at it but they are strangely addictive. The novelty will wear off after a while but not before you have had many hours of fun watching your geek actually taking exercise and socialising with others!

Good luck finding one of these. Prices seem to range from about £270 to Millions on Ebay at the moment.

Actually looking back through this list I think I would recommend most of those gifts for pretty much anybody. However, the real question is what would you recommend? Add your suggestions to the comments.

104. Give us your money

On this week’s show: Paul shares 10 tips for getting designs signed off. Marcus looks at how to present to a prospective client and Michael Slater introduces us to Ruby on Rails.

Play

Download this show.

Launch our podcast player

News and events | Marcus: How to present to a prospective client | Paul: 10 tips for design sign off | Michael Slater talks about Ruby on Rails | Question of the week

Housekeeping

All change

I have a bit of housekeeping news before we go any further with the show. I am changing things around a bit with my podcasting line up. After a chat with Dan Oliver from .net magazine we have decided that I will no longer be doing their show. They have some great plans for it in the future but it just didn’t make sense for me to keep doing two very similar shows. Before people start emailing, no we haven’t had a falling out and I still love Dan very much… if only I wasn’t already married.

The good news is that this allows me to introduce some more guests onto this show and bring in a bit more discussion. In order to accommodate this we will be having just one feature section each week instead of my bit and Marcus bit. Some weeks I will do it and other weeks it will be Marcus.

The final aspect of all of this is that we are going to start recording the show together rather than over skype. This should deal with the audio problems we have been having as well as making for a much better dynamic.

Christmas giving

I thought it might be nice to use the mighty power of the Boagworld listeners to raise a bit of money this Christmas and wondered if you might all be so kind as to help.

We have been doing this show for well over 2 years and have never charged or done much in the way of advertising. We are therefore wondering if just this once you would dip your hands into your pockets and give a bit of cash.

I want to raise some money for a charity I have been personally supporting for a while. A friend I grew up with now runs a school and orphanage in a very rural part of India. The kids they work with have far from the best background and the school is the only hope they have of breaking out of their circumstances.

I wont emotionally blackmail you with sob stories (because I know you are hardened cynical geeks) but simply ask that you give me some cash in return for the two years of free shows I have given you.

Because I am unorganised and only thought of this a couple of days ago we are going to simply use my paypal account to collect donations. I will then pass the money on to the charity. So to give a donation just use the bottom below (be warned its not the most intuitive system ever but you are all clever chaps. I am sure you will work it out).

Give to the Boagworld Christmas Appeal

News and events

24 ways is back

My first story of the day is actually 12 days late because it is the re-launch of 24 ways. In case you haven’t come across 24 ways before I should explain that it is an advent calendar for web designers.

Each day in December leading up to Christmas they publish an article written by some of the leading lights in web design (oh yes, and me). The articles are somewhat random but also incredibly practical and hands on. Articles range from creating a never-ending background to working with online maps.

But don’t panic that you have missed the first half of advent. You can access all of the previous days. In fact you can even access the last 2 years of articles. Ample to keep you amused while we are away over Christmas.

Tips for development and design

If 24 ways isn’t enough to quench your thirst for knowledge then let’s throw two more articles into the mix both of which provide some top tips.

The first is for all you developers out there. The guys at Blue Flavor have shared their top 10 tips for a successful development project. The article includes great advice like, always create a functional spec and talk to your clients. Interestingly one of the suggestions is to use a version control system. This is also a tip in our second article which is aimed instead at designers.

Jina Bolton has written an interesting article for Think Vitamin entitled “creating sexy stylesheets“. Like the blue flavor article this one lists 10 tips. However this time they are for producing better stylesheets. Now, although I would argue that nothing makes CSS sexy this is still a very useful list. The tips for organising your CSS file and building your own framework are particularly good.

So if you are into top 10 lists then you should be happy this week whether you are a designer or a developer.

24 wayswhich post articles on web design over the Christmas period. Well, I was asked to contribute to the site so I wrote an article entitled 10 tips for design sign off. Although some of the tips have been covered on the show I thought generally it would make a good segment for the show.

The problem is that getting design sign off can be one of the most challenging parts of the web design process. It can prove time consuming, demoralizing and if you are not careful can lead to a dissatisfied client. What is more you can end up with a design that you are ashamed to include in your portfolio.

How then can you ensure that the design you produce is the one that gets built? How can you get the client to sign off on your design? (Question of the week

What tips do you have for getting designs signed off?

 

Intranet delusions

Every business can benefit from some form of intranet whether it is a collection of online tools or a large corporate system. The problem is that many organisations make fundamental mistakes in how they approach their intranet.

I have been asked a number of times to talk about Intranet development and I have always avoided doing so. This is partly because I am not an expert in the field (although that doesn’t normally stop me talking about something!) However, it is also because intranets are a massive area and one in which so many mistakes are made. There seems to be a huge amount of naivety about developing and running Intranets. Against such a backdrop I am somewhat unsure where to begin.

In the end I have decided to take 5 of the most common misconceptions about Intranets and see if we can shed some light on why they are wrong.

A money pit

“The intranet is not important like the website. It doesn’t generate a return on investment”

This seems to be a common perception especially among senior management. Unlike a website, the intranet isn’t perceived as business critical. Instead it is seen as nothing more than a hole into which money is poured. The problem is that an intranet doesn’t typically generate revenue. However, it does generate a return on investment.

The real benefit of an Intranet is in productivity gains. If used a correctly it can:

  • dramatically reduce the time to access key information
  • act as an effective method of disseminating information
  • be a way to manage workflow
  • become a key component in improving communication

Accessibility free

” I don’t need to worry about accessibility because I know exactly who is using the site”

The perception that you don’t need to worry about accessibility on an intranet is naive. Just because you don’t have users with disabilities at this stage doesn’t mean you never will. Moreover, accessibility is about a lot more than the disabled. By building your intranet with accessibility in mind you can offer up the chance to deliver it to other devices such as mobiles.

Finally, many people who are not registered as disabled have accessibility issues. This is especially true with an elderly user who may have poor eyesight or arthritis. Building your intranet with accessibility in mind can improve the usability for everyone.

Browser specific

“We only need to design for Internet Explorer 6 because we use that across the entire company”

Single browser support on your intranet is a risk. Building for the peculiarities of one browsers can easily come back and bite you later. A company wont stay with the same browser forever. Even an upgrade from IE 6 to IE 7 could easily break your site. Build from a solid base of web standards and you have the confidence that changes to the browser platform will have a minimal impact.

The other advantage of this approach is that it is entirely possible to open up parts of your intranet to suppliers even if they do not share the same IT infrastructure as you.

Employee motivation

“Its not like a website, people are required to use the Intranet as part of their job”

It is true that people are expected to use things like the intranet as part of their job. However theory and reality are very different. I have seen many intranets effectively abandoned because they were just too difficult to use. It is quicker to use other methods (such as the telephone or email) to find the information required.

An intranet will only succeed if it:

  • has the right information
  • is easy to use
  • is engaging

Some of the most successful intranets are those that work as hard to be sticky as any website would. Adding social features is a good way of doing this as well as making sure your site has the right “killer” applications. However, most importantly you need to ensure that the site is easy to use and people can quickly find the content they require.

Unregulated content

“The idea is that everybody adds and maintains the content. It doesn’t need a web master”

In a utopian world an intranet should not need a web manager. Each employee should add and maintain their own information on the system. However, the reality is that this doesn’t happen. Some people are simply too busy to “mess around with the intranet” while others upload far too much erroneous “stuff”.

An intranet needs a web manager in the same way as a website does. It needs somebody to be a guardian for the content ensuring that the right stuff is online and organised in a logical manor.

Conclusion

Developing intranets is a huge subject and one that I shall return to in the future. However, hopefully these few misconceptions have helped challenge your thinking of how to approach their design and build. Although designing an intranet is very different to designing a website, it is actually surprising how much they have in common too.