So who is actually going to do the work?

When faced by a problem with their site most website owners turn to a web designer for the solution. However, in many cases they should be looking closer to home.

After 16 years in web design you would think I have the solutions to most website problems. However, I cannot solve the biggest reason most websites fail.

Sure I can make a website more usable, accessible or visually appealing. With the help of Relly I can also establish a good policy for the production of content. By working with Dave, Craig and their team I can ensure the site can be easily updated and integrates tightly with other business processes.

However, the one thing I cannot do is ensure the website is adequately resourced and updated regularly. That falls to you the website owner.

Cartoon showing a web designer frustrated by lack of content

Next time you redesign your website don’t think it is enough just to employ a web design agency. You also need to consider your own responsibilities.

A relaunch requires new content

Ask any web designer and they will tell you that the single biggest point of weakness in any redesign project is late delivery of content. As a website owner it is easy to forget that although your web designer can create you a new website they cannot populate it with content.

Rewriting all of the content on your existing site is a major undertaking and without adequate resources it will simply not happen. What happens instead is that content is copied and pasted from your website, printed material or any other ad hoc source that can be found. This not only leads to a horrible Frankenstein mix of content, it also makes relaunching the website pointless.

Frankenstein monster website

Without new content essentially all you are doing is re-skinning the old site. This does nothing to reposition your organisation or provide any kind of tangible return on investment. Design in isolation is worthless. It needs to be accompanied by a review of the sites content.

Ask yourself who is going to be involved in writing the new content for your website? It is a big job and you’re going to probably need several people. Who are those people going to be and do they have time to do the job? Questions like this need answering before you undertake any significant rebuild of your website.

But these questions do not end once you have relaunched website. You also need to consider your ongoing content production requirements.

Ongoing editorial resource

Unless you are happy for your website to stagnate it is going to need somebody constantly updating the content. Do you have a clear idea of who is going to do this job?

Many organisations think that a content management system is the answer. However that is not the case. A content management system is not going to write the content for you! Although it does allow for the work load of ongoing content production to be spread across the organisation that does not mean people will embrace that additional work.

I think it is also important to be realistic about just how much people can take on. I often hear website owners say “so and so can be responsible for that section of the site” without considering whether they really have the time or the inclination to do the job. Do not take people’s participation for granted but instead ensure you have their buy in before listing them as a content provider.

Employee being overwhelmed by the boss

Unfortunately in many situations all a content management system will do is ensure that nobody feels fully responsible for the content production. Instead content production is tagged on to existing roles and responsibilities. This means it is often the bottom of people’s priority list, well below their “proper job”.

If you want people to take content updating seriously you need to ensure that it is written into their job description and expectations are set about their responsibility. It needs to be seen as just as important as other aspects of their role.

Editorial oversight

Another solution to this problem of who is responsible for the site’s content, is to appoint a website editor. Because this individual would be ultimately responsible for the content on the website they will take responsibility for chasing content providers and ensuring that they regularly update the site.

Another benefit of a website editor is that they can bring a single voice to the website. One of the problems of having multiple content providers is that it can lead to contradictory information and radically different writing styles. This can give any website a slightly schizophrenic feel. However having an editor who can issue style guidelines and check peoples work will help prevent this from happening.

The web team worries about the different writing styles of contributors

Of course the question is: “who is going to do this job?” This is a significant role and not something that can be easily tagged onto somebody’s job. It either needs to be a full-time position or taken on by a passionate individual who is given adequate time to work on the site. What is more this time should be ring fenced to ensure the website does not stagnate.

Can you honestly say you know who this person should be? If you do not then I would warn against biting off more than you can chew with a website that requires constant updating. Instead you are better creating a small, self-contained website that does the minimum required rather than having something larger than is obviously neglected.

Other solutions

The issue of creating and maintaining content is massively challenging and I would be interested to hear how others have solved this problem. Do you have a full-time web editor? How do you ensure your content providers actually take time to update the site? Does anybody have website content production as part of their job description? Let me know in the comments below.

What does your site say about your organisation's personality?

Are users seeing you in the right light? Are they seeing the real you or a phoney persona? In this post I show you how to let your users look behind the corporate facade.

For many users your website is the only glimpse they get of who exactly you are. Most do not meet you face-to-face or even chat with you over the phone. Your website is all they will ever see. If you find that prospect scary then you are not alone. Many organisations not only view their website as unrepresentative of their services but also their personality.

In this post I endeavour to provide some practical advice on how to honestly project your personality online. However to do that you need to have a clear perception of who you are.

Understanding your organisations personality

It’s amazing how few employees have a clear grasp of what their company does, let alone the personality that best represents them. One of the first questions we ask our clients is to summarise what their organisation does in one or two sentences. Many people simply cannot do that.

The second question we ask is “if your company was a person, who would that person be?” Think about it for a minute. Which famous person best represents your company? It’s a hard question to answer. Yet I believe that if your website is to accurately reflect who you are then you need to be able to answer it.

Don’t pretend to be somebody you are not

However the problem does not end with simply identifying who you are. It is also a matter of being confident enough to honestly project that personality. I often encounter organisations who dislike their corporate culture and would prefer to be somebody else. There is nothing wrong with being aspirational in the way you wish to project yourself. However it is important to recognise that if you intend to be aspirational online this also needs to be represented off-line as well. This requires nothing short of a cultural shift.

Overcoming your corporate inferiority complex

In most cases it is better to just “be yourself”. Many organisations suffer from a collective inferiority complex. Instead they need to embrace who they are and be willing to project that online with confidence. I think this lack of confidence is borne from a fear of alienating users. They believe that some of their corporate characteristics may be unpalatable to certain audiences. They might actually be right.

An employee ashamed to work at Microsoft

dragon_fang, Shutterstock

However in my opinion it is better to accept who you are than be something you’re not. You may alienate some users, but your honesty and openness will attract many others. The web is a big place and there are plenty of people out there who see the world in the same way as your organisation and will be drawn to you if only you stand up for what you believe.

That brings me nicely on to the need for transparency and openess.

Be transparent and open

As well is not hiding who your organisation really is, it is important to be open and transparent in the way you communicate with your customers both online and off. Too many organisations harbour the belief that they cannot or should not admit to their mistakes. There also appears to be a culture of secrecy that surrounds many organisations. Although this may work for companies such as Apple the majority of us do not work for Apple and so need to consider a more open attitude.

Stop worrying about the competition

I think much of this closed off mentality comes from a fear of the competition. Organisations believe that to admit their mistakes shows weakness. Although there is an element of truth in this, the benefits outweigh the weaknesses.

Take for example Flickr.com. In their early days they suffered from serious performance problems that angered many of their paying customers. They might have concluded that to admit the problem would have been a sign of weakness. However instead they chose to publicly acknowledge the problem and apologise for their failings. This turned a potential PR nightmare to their advantage and they won a lot of fans because of their honesty.

flickr blog post entitled: Sometimes we suck

Many organisation also worry that making their company too transparent will allow the competition to copy them. Although true, I would argue that it is better to give away some of your intellectual property than it is to work in obscurity. Take for example my own situation. I know for a fact that a large number of my competitors read this blog. No doubt they learn a lot about the way that I work and win business. However I also know that the Boagworld community wins approximately 90% of Headscape’s new business. At the end of the day it is perfectly possible that my competitors will copy some of my ideas. However ultimately they are just going to be playing catch up and I will always remain one step ahead of them.

Another important part of being open and transparent is to recognise your organisation is more than a corporate facade. Instead it is made up of many individuals who all have an influence over the corporate culture.

Recognise that your organisation is made up of people

Why is it that the marketing department within so many organisations actively discourage their employees from talking about their work online? In my opinion employees are one of the best assets a company has in projecting its personality online.

Take for example Microsoft. Among certain segments of the developer community Microsoft is perceived as evil personified. In particular many web developers despise Internet Explorer with a passion. For the longest time the team at Microsoft who worked on Internet Explorer were forced to remain silent and this just added to people’s dislike of the company. However eventually Microsoft began to open up and allow its employees to talk about their jobs and the decisions they made in the development of Microsoft products.

For those of us who have read these first-hand accounts by Microsoft employees on blogs like Channel 9, it has transformed our attitude towards the company. We may still dislike Internet Explorer but although it is easy to despise a corporate body like Microsoft, it is much harder to dislike the men and women who work on the products.

Channel 09 blog

Not only is it much harder to dislike people than corporations, we also feel more drawn to individuals rather than faceless companies. This relationship with people (rather than companies) is particularly important if you are a service based business. At Headscape we actively encourage our employees to blog, tweet and generally participate in the web design community. This is because we know that our clients hire us based on the skills and likeability of our staff. Most people are not impressed by corporate brands, but they are impressed by likeable, highly skilled individuals.

Of course I’m not suggesting that there is no place for corporate branding. After all I fully recognise that first impressions count.

First impressions count

When we meet a person for the first time we make certain judgements about their character and personality based on the way they look, what they wear and their body language. With little else to make judgements on, users take a similar approach online. They make judgements based on the visual appearance of your website and come to conclusions within a matter of seconds. It is therefore important that the design of your site reflects the personality of your organisation.

Because users make judgements about your character based on the way your site looks it is important that the designer has a good handle on your organisation’s personality. That is the reason we ask “if your organisation was a person who would it be?” This allows the designer to picture a particular person when designing the site.

However it is important to stress that it is not enough for just the design to reflect your personality. Your copy needs to reflect it to.

Don’t allow your copy to make you schizophrenic

Content management systems have solved many problems. However the way they have solved some problems has created other more subtle challenges. For example, the introduction of content management systems has meant that a website will probably have multiple content providers. This overcomes the problem of content bottlenecks. However each content provider has his or her own writing styles and this can make your organisation’s character seem schizophrenic.

Image of serious business man holding an image of himself in casual wear looking happy

Worldpics, Shutterstock

As with design it is important that your copy reflects your organisation’s personality. This means that your copy needs a single tone of voice. In an ideal world this would mean that your website had a single web editor ensuring that everything published have that consistent tone. However this is not always possible due to budgetary constraints.

If you do not have a web editor then your organisations website should at the very least have a content style guide. This document should not only ensure consistency in the use of grammar, product names and sector specific terminology. It should also provide guidance for writing with the correct tone of voice.

This kind of editorial control has existed in the print world for years. For example if you compare different newspapers you will find each has its own unique personality that differentiates itself from the competition. This personality is maintained across the publication despite the fact that each issue is written by a variety of different journalists.

The Sun website

The Guardian website

You might think this contradicts my comments earlier about giving different employees within the organisation a voice. I have no problem with employees writing in their own style for content that is specifically associated with them as an individual (e.g. a corporate blog where the author’s name is highlighted). However on more generic pages I believe that the personal style of the writer needs to be secondary to the personality of the organisation.

Conclusions

I find it concerning that so few websites seem to have a consistent tone of voice that extends through both design and copy. Without a strong personality and will within the organisation to express that personality online, websites end up looking bland and generic. This explains the prevalence of ‘corporate blue’ and unintelligible marketing copy across the web. Designers and writers who fall back on these cliches do so because they have no clear image of their organisation’s personality.

Could you easily explain to a third party what the personality of your organisation is? If not then maybe it is time to ask which celebrity best represents your organisation. Why not post your ideas in the comments below letting us know why you selected the person you did.

Controlling the website animal

Has your website grown into an out of control monster? Does it consume your time and energy with its mountains of legacy content? If so its time to put it on a diet.

Ask any in-house team whether their website is bigger than it should be and the answer will always be yes.

The bigger the organisation, the bigger the website. However, just because the company is bigger does not mean its website should be. Most of the time the site is bigger because there are simply more people who want their say!

Unfortunately big sites, with lots of legacy content, create serious problems.

Why monster sites suck

Monsters demanding to be fed

Cristian34, Shutterstock

There are in fact a plethora of problems. However the big five are:

  • Time consuming to maintain – When your website comprises of many thousands of web pages, it takes considerable man hours to update and maintain. Rarely do web teams have sufficient resources to stay on top of the sheer number of updates required.
  • Often out of date – Because there is just so much content, it becomes next to impossible to keep everything up-to-date. If a product line is dropped or a key member of staff is replaced, you may need to review thousands of pages to find every reference and correct it. Admittedly most sites of this size are managed by a distributed team of content providers, but realistically you cannot rely on them to keep their content current.
  • Difficult to migrate – With different pages built on different systems and using different code it becomes a nightmare if you wish to update the sites look and feel. In fact the task is so overwhelming that in-house teams often only update the central site vowing to ‘get around to the rest’ as soon as they can. This creates an inconsistent user experience of undermines the professionalism of the site.
  • Hard for users to find content - If finding a needle in a haystack is hard, imagine trying to find a needle in a barn of straw. The bigger the site, the harder it is for users to find what they want. Navigation and information architecture becomes increasingly complex while search returns an overwhelming number of results. Content providers put up content because ‘somebody might want it’ but all they are doing is making it harder for users to find what they really need.
  • Creates a lack of strategic thinking – Because the web team is spending so much time just staying on top of the existing website they have no time to stop and take stock. They never have the chance to step back from the site and plan its strategic direction. In essence they cannot see the wood for the trees. They work on the micro rather than macro level.
  • Little quality control – Finally with a website too big for any web team to successfully manage the quality begins to slip. Content providers do not present content in a consistent manner, they make unwise design decisions and their copy is bland and uninspiring. Without some central group overseeing the output of content providers, the quality of the site will inevitably suffer.

If the drawbacks are so obvious, why is it that so many websites have grown out of control.

Why things don’t change

Large organisations suffer from two evils, bureaucracy and politics.

Two monsters representing politics and bureaucracy

Cristian34, Shutterstock

Bureaucracy says certain things have to be done whether or not they make sense. For example, university research groups have to have a website in order to secure funding. These sites have to exist even though many researchers don’t care about them and they receive next to no traffic.

The problem is that nobody has the time or evidence to challenge these bureaucratic rulings, or think of alternative approaches.

The bigger problem however is politics. In the grand scheme of things most web teams rate fairly low in the pecking order. When somebody comes along requesting an update to an unused webpage, they simply don’t have the authority to say no. They certainly cannot get away with arbitrarily removing unused, irrelevant or out of date content.

How then can we control the growth of monster websites?

Avoiding politics, create policy

In many cases organisations turn to companies like Headscape to solve these issues. They know that calling in an outside specialist (especially one experienced in dealing with company politics) will get stuff done. Strangely senior management will pay more attention to an outside consultant than their own in-house team.

An outside consultant can also get away with asking naive questions and suggesting unacceptable solutions because they “don’t know how things work”. It is amazing how powerful the question “why?” is in challenging long held political decisions.

That said, there are things you can do yourself without outside help.

Large organisations like rules and structure, so create some. Instead of turning every change into a political or personal battle, make it a policy instead.

People are much more likely to buy into a policy that isn’t directly targeted at them, than to a direct confrontation. Confrontation forces people to depend their position and that never leads to a good place.

What am I talking about in practice? I am suggesting you let the numbers do the talking. Here are three policies you might want to introduce at your organisation…

The link on the homepage that receives the least clicks will be automatically replaced.

If you think about it this makes a lot of sense. Everybody would agree in theory that the most important content should appear on the homepage. They also believe that their content is the most important. This is why so many homepages become a battleground.

By implementing a policy like this you are ensuring that the content most crucial to users floats to the homepage. More importantly the web team is not the group making the tough decisions and dealing with the internal politics. Instead it is a policy that everybody has agreed to.

Pages that do not meet a minimum thresholds of page views and dwell time will be unpublished until rewritten.

Depending on the threshold this could dramatically reduce the size of your website.

By combining page views and dwell time you ensure that any content remaining is both popular and useful.

Admittedly this one is going to be slightly tougher to sell which is why I have softened the consequences. I could have suggested that such pages are just deleted. However, instead I propose they should be rewritten. This gives you the opportunity to help whoever published that content to improve their copy so it meets the threshold next time.

Webpages that has not been update in the last six months will be unpublished until the content can be reviewed.

This is my favourite. In a single stroke you have dealt with out-of-date content on your website. What is more everybody will agree that content needs keeping up-to-date.

The only possible argument against such a position is that some content does not need updating every six months. That is true. However, all the content providers needs to do is review their pages in the CMS and the page will remain online. If they can’t be bothered or forget then the page is only unpublished, not deleted.

Softening the blow

Boxer

Cristian34, Shutterstock

I know what you are thinking. You are not sure if you could get this through. You are also thinking about all of the external and internal links that lead to the pages we have just unpublished.

Fortunately you can soften the blow if necessary. Instead of unpublishing the pages you can remove them from the main navigation and search results. This means that navigating and finding content becomes easier, but the page still exists for those who desperately need it.

I would however add one caveat to this suggestion. Because these pages could be out-of-date, misleading or downright bad, I think it is important to add a notice to them which reads…

This page could contain out of date information or no longer reflect our organisations current position. The page is currently under review and will either be updated or removed.

I would then set a time limit for content providers to review the page and update it accordingly. If they fail to, then the page will be unpublished.

So what do you think? Could this work? Let me know in the comments below.

Need help overcoming internal politics so you can improve your site? Give me a call (+44 7760 123 120) or drop me an email, I would be glad to help.

Web Design News 11/05/10

This week: Engaging and helping your users, the power of habits, why business writing is so awful and things to do at the beginning of each project.

Engaging and helping users

For the longest time usability was the mantra of the web design community. However simply making our websites usable is not enough. We also need to make them engaging too. We need to build a relationship with our users so they are passionate enough to spread the word.

However, engaging and motivating users is still in its infancy and has proved a learning process. This is beautifully demonstrated by three posts this week.

If you are new to the idea of engaging and enthusing users I recommend you start with Simple Strategies for Engaging Your Visitors. This post on six revisions lays out the basic principles of engaging visitors. In particular it looks at…

  • The ability of great content to engage
  • Engagement through giving users status
  • The power of letting your personality shine through
  • The use of humour
  • The need to communicate regularly
  • And the importance of usability

Although a great article it does not delve very deeply into the subject and has relatively superficial suggestions. However, Mashable has released a post entitled HOW TO: Cultivate Your Brand’s Super Users that delves a little deeper.

Image of a lego man streaking

Image Source: balakov

Instead of asking the question “How can get users to pay more attention” it suggests…

[We] flip that traditional marketing question around and ask, “How can we pay more attention to our users?”

The post then goes on to give four example case studies of websites that have done exactly that.

However according to Kathy Sierra in her recent talk at Business of Software 09, even that is not the right question. She proposes we should be focusing instead on how to empower users by creating sites that allow them to do things better, faster and smarter.

It’s a superb presentation that I recommend it to anybody with a desire to service their customers/clients/users better. If you don’t have the time to watch the entire presentation at least  read the summary on Konigi.

The power of habit

My second news item this week isn’t really directly related to web design even though it appears on A List Apart. Habit Fields is a fascinating post about how we form habits around objects. Here is how the author explains it…

Every object emits a habit field. When we sit down at the desk in our office to work, we shape its habit field into a productive one. When we sit down in a lounge chair to watch our favorite TV program, we nudge the chair’s habit field toward relaxation and consumption. The more we repeat the same activity around an object, the stronger its habit field gets. And the stronger its habit field gets, the easier it is for us to effortlessly fall into that mode of behavior the next time we’re around the object.

He goes on to explain how this can be problematic for a productive working environment especially in regards to computers. Its easy for you to ‘nudge’ the habit field of your computer so that you associate it with checking email, IM and tweeting rather than actually getting stuff done.

All of this sounds a little fanciful but the article does suggest some useful ways of controlling your environment in order to generate more productive habits.

Although it is an interesting article from a productivity perspective, it also got me thinking about how users form habits around our websites. Consequently small changes and decisions we make can nudge those habits in different directions. We certainly need to be careful when changing an existing site. Yet more evidence that large design changes are not always a good idea. Beyond that I don’t have any great insights but the article was certainly inspiring.

Have a read and let me know in the comments below whether you can see parallels with site design too.

Why is business writing so awful

It would appear that Jason Fried of 37Signals is jumping on the content bandwagon with a couple of posts on the subject.

The first is for Inc. Magazine and is entitled “Why is Business Writing so Awful?” His conclusion – because it all sounds the same. He writes…

When you write like everyone else and sound like everyone else and act like everyone else, you’re saying, “Our products are like everyone else’s, too.” Or think of it this way: Would you go to a dinner party and just repeat what the person to the right of you is saying all night long? Would that be interesting to anybody? So why are so many businesses saying the same things at the biggest party on the planet — the marketplace?

He then goes on to highlight some great examples of well written copy.

He concludes with this…

I can already hear some of you saying, “Sounds great. But I can’t write.” So hire a writer.

I have said it before and I will say it again, it amazes me why businesses invest so much in design and so little in copy.

Tired woman are sleeping and holding cup. Laptop is situated on the table.

Tokar Dima, Shutterstock

Of course writing isn’t just limited to website copy. It also applies to the emails we write in response to user enquiries. On the 37Signals blog Jason gives an example of how important it is to be positive when saying no to a customers question. He concludes by saying…

Tone makes all the difference in the world.

I couldn’t agree more.

Things to do at the beginning of each project

I want to end today with a nice little checklist from Leah Buley at Adaptive Path. “Things to do at the beginning of each project” does exactly what it says on the tin with a list of things to remember when starting work on a new project.

Photo of the A Team

This is a worthwhile read for both web professionals and website owners. Although written from an agency perspective the list is applicable from both sides of the fence.

Some of my favourite items include…

  • Plan for a mid-point triage period. Even if you think things will go swimmingly, you’ll need it. Treat this as unstructured time for resolving lingering design questions. If possible, this should be face-to-face time when you get the the whole team together (including clients) and poke a stick at the designs (in the interest of making them better, of course!).
  • Create “this week” and “next week” signs. Pick a prominent spot on the wall and put up 2 signs: one that says “this week,” and one that says “next week.” As the weeks roll on, put whatever you’re supposed to be working on this week in the “this week” spot. And put whatever you’re supposed to be working on next week in the “next week” spot. When you feel overwhelmed by the amount of work left to be done, look at the “this week” sign and feel calm.
  • Communicate a lot. Use the back channel. Call people up and ask them how they think it’s going. If you have important information, try to think of everyone who will be impacted by it, and then try to share it, in whatever form is appropriate. Give senior or influential people previews before any “big reveals” to avoid unpleasant surprises during the Big Presentation.

Do you have a project checklist like this? If not it is definitely worth creating one. Rolling out a web project is extremely challenging and complex. It is not the kind of thing you can easily hold in your head. Make a list!

Design and copy pirates: Should you care?

Websites like Copyscape make it easier than ever to find other sites who have stolen your copy. However, should you care and how can you stop thieves.

Dylon Garton recently contacted me with the following issue:

I have been affected by the issue of plagiarism. I really struggle to write good web copy so when I manage to get some good copy into one of my web pages I am quite pleased. I am less pleased when I discover several other websites have lifted the copy word for word.

I am wondering how you guys deal with content theft. I have discovered a great site called Copyscape and this is how I have managed to find all of the sites that have ripped me off. I will be interested to hear how you guys deal with it.

There is no doubt that plagiarism is widespread within web design and across the web as a whole. Sites like Copyscape make it easy to find copy thieves. However, the problem is just as prevalent in design.

Copyscape

Our work has been ripped off a number of times and I know many other designers have experienced the same thing. Elliot Jay Stocks has been particularly vocal on the subject after suffering himself.

Let me be clear…

Ripping off somebody else’s work is wrong. Its lazy and it’s damaging. Not just damaging to the reputation of the individual who you ripped off, but damaging to the thief too. And I am not just talking about when you get caught. It is damaging because it leads to unimaginative thinking. Your own creative skills atrophy over time to the point where you can no longer create original work.

That is not to say you cannot be inspired by other people’s work. However, there is a line, and although we may pretend otherwise, we all know when we have crossed it.

The unfortunate reality

Although plagiarism in all its forms is wrong, it is not going to go away. It has existed before the web and will exist after it. The only difference is that because the web is such an open platform it is incredibly easy to copy work. However, in my opinion that is a price worth paying for an open web.

Once you accept that plagiarism cannot be defeated, it fundamentally changes you attitude towards it. There is little point in getting indignant or angry. You learn not to waste too much time or energy on people who are essentially just rude.

Does that mean that I ignore plagiarism? Not at all.

How I deal with it

99% of the plagiarism I have been confronted with has been resolved with a simple email. I write to the individual involved drawing attention to the problem and asking them to rectify the situation. I don’t make any legal threats and keep things as civil as possible. I make the presumption that the person I am writing to is unaware of the problem.

The reason I take this approach is because it doesn’t put people on the defence. They can easily write back blaming somebody else, apologise profusely and remove the offending content. However, if you start making legal threats they are forced to defend their position.

On the rare occasion when people do dig their heels in I shrug my shoulders and move on. If they want to continually follow in my wake that is fine. I will just move on to the next thing and produce something new. I am not going to waste my time on them.

The Ultimate Website Prelaunch Checklist

All of a sudden the site you have been working on for months is approved and the client wants it live. However, things can still go horribly wrong if you are not prepared.

We’ve all been there.

After months of development, meetings, conference calls, protracted arguments over typography, photography, colour ways and copy. All of a sudden the site is approved and the client wants it live.

Do you think to yourself, ‘I know every pixel on this site inside out’ and put it live?

Hopefully not. You’ll have a printed checklist which you complete before you go public.

By no means is this an exhaustive list. Neither is it presented in any particular order. Your own checklist will be very much tailored towards your own individual clients and the type of project you are delivering. Be sure to add your thoughts and suggestions to the comments at the bottom of the page.

Either way, get your team together, get out the red pen and start ticking them off.

Copy Checks

Check your spelling.

If it comes down to a web designer to highlight the smelling pistakes of a copywriter then so be it. Show the world you are no slouch and run a spell check. Better still, get your copywriter / project manager to do this. Be sure you check for widows or orphaned items in important paragraphs too.

Check your tone of voice.

Ensure this is consistent across all your pages, that your audience is being addressed the same way throughout the site. If your services include ‘Research & Development’ ensure it is expressed using ‘&’ everywhere it appears, always with capitalisation, and if you display times and dates be sure to express them the same way throughout. This is a cornerstone of well-crafted, easily scannable copy.

Copywriting on the web workshop

Check your details.

I’m quite serious about this. Phone all phone numbers you have been supplied. Do they work? If you’re building a site for The Royal Albert Hall, do they answer? And are they aware you are shortly going to launch a site, with their number on it, inviting thousands of people to call for more information? These are crucial checks to ensure that the entire marketing process, right down to (phone) calls to action are prepared for the site going live. Check email addresses you have been supplied and make sure they work and are being received by someone. Oh, and check they are not still pointing at you for testing – make sure the clients email address is specified when the site goes live.

Check through any ‘hidden’ copy on site.

Look at ALT text and ensure it is descriptive and not just ‘XXX’ – read through any text within Javascript functions, failure or alert messages, and also and remove anything potentially embarrassing or plain unnecessary.

Make sure you are not going live with any test copy on your site.

Check for instances of ‘For more information call XXXX,’ or worse still, ‘At ACME and Co we pride ourselves on [Dave, has the client approved the mission statement yet]‘ You get the picture.

SEO

Check your keywords.

Ensure you have your meta description in place, and that any keywords are suitable for the site. Do the keywords appear in your site copy where appropriate? Turn off your style sheets and read your site as a search engine will, and check your keywords are written in HTML and not all contained within images.

Check your titles.

Do you pages have relevant and descriptive title tags, and are your page names suitably descriptive.

Check your URL structure

Google has taken considerable steps within Webmaster Tools to reward site owners for declaring, and being consistent about canonical URL’s. That is to declare to Google which URL structure you will maintain on your site, to avoid the duplicate content penalty. So if you choose example.com/products over www.example.com/products, then check to ensure the links within your pages follow this convention.

Check you have a sitemap.

Generate an XML sitemap and submit it to Google, Bing, and Yahoo. Gsite Crawler is a great tool to help create these automatically for you.

Set up analytics on your site and schedule any weekly reports that might need sending to your clients, and also set up any statistical alerts you might need to notify you of any spikes in traffic that might signify malicious activity. Stats packages worth your attention are listed in the URL’s below.

haveamint.com

Standards and Validation

Clearly this is not something that should be left until the last few days prior to launch. But you should always make one final sweep through your content to check for validation issues. You should be checking your HTML, CSS, Accessibility and your Javascript. Quite often you can encounter validation issues late in the project with the addition of javascripts from a third party if a client has reporting software they wish to use, or if you are carrying advertising or inviting referrals from an affiliate network. As these are so often just thrown in to the code at the last minute it is vital to check that they don’t interfere with functions that were (up until then) working just fine. The Developer Toolbar for Firefox is a great time saver when it comes to validating your HTML and CSS, with the WAVE toolbar being similarly indispensable for checking against WCAG guidelines. That said there is no substitute for a good working knowledge of the WCAG guidelines as so much of them cannot be checked against by a plug-in, and requires common sense and a keen eye to avoid problems.

Web Developers Toolbar

Site Functions

Does everything work?

Again, this should have been tested long before now, but don’t go live without checking it. Often you will have moved a site from a development server to a production server in the run up to putting it live, and that may have upset your file structure. Maybe you have an API which relies on the address of a development server to work and will need altering if it is to work at the live address.

Check your search facility

Check your search facility if you have one and make sure that is pulling in results. Also check for dead links across the site with something like Xenu’s Link Checker.

Screenshot of Xenu

Check all browser variations

Check all browser variations that you promised to support, all screen resolutions and ensure that your site degrades gracefully without the support of Javascript and Flash. Your site should be easily interpreted by a screen reader with CSS switched off, and this can be checked by downloading a text only browser such as Lynx for the PC.

Think about common web conventions and whether your site breaks them. Are all your links consistently styled? If all links are underlined, check that no text is underlined for presentational reasons that people might mistake for a link.

Don’t forget to set up a print style for your site.

It is stunning quite how often this ignored. Insert this line into your <head> tags and create your print style sheet.

<link rel="stylesheet" type="text/css" href="print.css" media="print" />

Security

Ensure you have your site files backed up, but assuming that this is something you do as a matter of course, ensure that you are backing up any databases on the website that might contain important customer data. There are services and applications who can automate this for you such as Site-Vault and Iron Mountain, providing you with the peace of mind that only a reliable backup can bring.

Screenshot of Site Vault website

Check your form fields against SQL injections, and test any anti-spam functions you have in place to prevent spam bots.

Protect any sensitive pages

Protect any sensitive pages or folders from being indexed on search engines by putting in place robots.txt files and by excluding them from within Webmaster Tools / Bing / Yahoo Site Explorer and also consider whether you need to use an htaccess file to disable folder view within directories.

Performance

Increasingly this is becoming more an issue. With rumours of Google rewarding faster sites with better rankings it is crucial that your pages load as swiftly as possible.

Safari 4 has a great tool within its developer menu which checks the speed of your pages downloading, and highlights which elements take the longest and therefore might need attention.

Check your image optimisation with a tool like Smushit.

Smush.it website

Check you have caching enabled if appropriate.

If possible consider the use of image sprites to reduce http requests to your site. SpriteMe.org offers simple online solution that might get you started.

Minify your Javascript and CSS files using a tool such as YUI or YSlow from Yahoo to ensure your code is delivered as swiftly as possible. Firefox add-ons such as Dust Me Selectors can help to remove unused selectors from style sheets, helping to keep file sizes down.

Legal

Those lawyers get everywhere. Links to legal policies are so often added to a footer element on a website and then given no further thought until moments before go live.

Copyright

Check that this is set to automatically refresh from the time stamp on the server, and that the copyright owner stated is correct. It won’t always be the client or brand who should be credited.

Terms and Conditions

If your site has a promotional element or takes payment then you will need to make available t’s and c’s. Always consult either the Institute of Sales Promotion or a lawyer for the best advice on these, or if they are supplied to you then make sure they have been checked.

Privacy Policies

If you use cookies, capture data, or distribute data, then you need one. The best advice is always to be honest, and to state clearly what you collect data for, how it is stored, and to whom might it be passed. So if you this might be you then be sure you have a clear statement explaining all of this, or least provide details of how you can be contacted for further information.

Company Registered Information

If you are a registered company then you must display on your website the registered company name, number, and address. Simple, but so often forgotten about. For more information visit either Companies House or Business Link online for more information.

Companies House website

Add icons and error pages

Add your favicon.

And while you’re at it, do you need one for mobile devices such as iPhones? Add this into the <head>

<link rel="icon" type="image/x-icon" href="/favicon.ico" />

And this for an iPhone

<link rel="apple-touch-icon" href="/favicon.png" />

Create 404 pages.

Crucial for so many reasons. If the project is a re-design then search engines will have cached links to pages that will no longer exist. Use 404 pages to present users with links to where that information is now located. Webmaster Tools provides an easy way to produce 404 pages if you aren’t an experienced developer, but ignore these at your peril.

Example error page

Further reading

Smashing Magazine wrote an excellent post entitled “45 Incredibly Useful Web Design Checklists and Questionnaires” that contains many more checklists worth reading. They have other launch checklists, web standards checklists and even a checklist for improving site performance.

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.

182. North and South

On this week’s show: Molly talks about the future of web standards. Paul explains the differences between print and the web, and Ryan asks if job titles matter.

Play

Download this show.

Launch our podcast player

News

Being a better blogger

These days blogging has become an important tool for most organisations. Although I have written about the Harsh Truths of Corporate Blogging, I have said little about how to actively improve your corporate blog. I therefore want to draw your attention to two excellent articles that were published this week:

  • A Simple Way To Funnel New Traffic & Sales From Buried Blog Archives – One of the problem with blogging is that old posts get buried over time. Because of the way blogs are structured older posts normally receive very little traffic. This article suggests a couple of good solutions. First it recommends editing older posts so they are suitable for republishing via sites like Ezine Articles. Second, it recommends turning your better posts into PDF reports. Strangely this seems to significantly increase their creditability.
  • Do Long Blog Posts Scare Away Readers? – One thing I struggle with is the length of my blog posts. After all copy for the web should be short, right? Well not according to this article. Using movie lengths as an analogy, this post argues that it is not length that matters but ‘tightness’. A good blog post should be exactly the length it needs to be in order to effectively communicate its point. Not a word more.

If you are a blogger, both of these posts are definitely worthy of your attention.

Demystifying the “duplicate content penalty”

So Google have posted an article in the attempt to put peoples mind at easy about duplicate content on their websites, and whether or not Google penalises you for doing so.

The article goes through how Google filters duplicate documents by grouping them together reduce redundancy when searching.

They summarize with:

Having duplicate content can affect your site in a variety of ways; but unless you’ve been duplicating deliberately, it’s unlikely that one of those ways will be a penalty. This means that:

  • You typically don’t need to submit a reconsideration request when you’re cleaning up innocently duplicated content.
  • If you’re a webmaster of beginner-to-intermediate savviness, you probably don’t need to put too much energy into worrying about duplicate content, since most search engines have ways of handling it.
  • You can help your fellow webmasters by not perpetuating the myth of duplicate content penalties! The remedies for duplicate content are entirely within your control.

The general gist of the article is, if you deliberately post duplicate content in an attempt to rank higher on Google they will penalise you, but otherwise you don’t have anything to worry about.

7 common design mistakes that clients love

Although our next post is aimed at web designers I think it is just as important that website owners read it too. Entitled “7 Common Design Mistakes That Clients Love” it puts together a series of carefully constructed arguments tackling the more common design mistakes requested by clients. The list includes:

  • Scrimping on photography
  • Wanting a Flash intro
  • Too much information
  • Using white text on a black background
  • Wanting the logo bigger
  • Ripping off someone else’s logo
  • Wanting a terrible font

The arguments against each of these atrocities are a nice mixture of referencing research, quoting stats and simple effective communication. If you are a designer this article will help you better articulate why these things are wrong. If you are a website owner it may go someway to explaining why your designer gets so grumpy when you suggest any of them!

How To Give A More Exciting Presentation: A Note To Speakers

Our final story is courtesy of Inayaili de León over at the Web Designers Notebook and it’s stemmed from her recent attendance at dConstruct.

Yaili shares her advice to conference speakers on the do’s and don’t of a good presentation.

She goes into these points in detail so read them in detail there, but to summarise her do’s are:

  • Make us Laugh
  • Ask questions that we had never asked ourselves
  • Make controversial remarks
  • Be practical
  • Sprinkle your presentation with interesting facts
  • and use multimedia

She then goes on to explain her don’t and offers a selection of emergency tips to recover a dieing talk such as bashing Micrsoft and loading up a LOLCat (which always get a laugh).

It’s a thorough article offering good advice and she also links to some examples of well presented talks to learn from, so if you’re planning on presenting in the future it’s well worth a read.

Back to top

Interview: Molly Holzschlag on the future of web standards

Being transcribed…Thanks goes to Todd Dietrich for transcribing this interview.

Back to top

Listeners feedback:

Moving from print to web

Jake Knight writes: What are 5 things you would want any print graphic designer to know first and foremost about designing for the web?

I think the differences between the web and print causes a lot of confusion, not just among designers but also clients. The problem is that in the early days of the web a lot of work went into making the web behave like print and this led to the table based designs that have proved so problematic since.

In reality, although there are some similarities between print and the web, there are also a lot of differences. Narrowing down the list to just five things is hard. However, here are the issues I believe cause the most confusion especially among clients:

  • Lack of control – When developing a design for print you can guarantee that everybody will have the same approximate experience. Each copy of a design will be identical. However, that is not true of the web. Differences in browser, resolution and countless other factors means that everybody will have a slightly different experience. Accepting that is key to producing a successful website.
  • The scrollbar – Print designs do not come with a scrollbar. Typically a reader of printed design can view the entire design in one glance. Even if they cannot the designer knows exactly the point at which readers will need to turn a page or unfold the design. On the web, designers do not have this luxury. There is no way of knowing what the user can see in a single glance and this has a fundamental influence on the way we design.
  • Lower resolutions – Print designers are mostly used to working at 300-600dpi. On the web we are limited to 72dpi (generally speaking). This seemingly minor difference has profound consequences on the selection of imagery, use of typography and application of logos. An image, font or logo that works beautifully in print can become unreadable on the web because the lower resolution pixelates graphical elements at smaller sizes.
  • Colour – While colour in print is produced by the application of ink on paper, on the web it is produced through projected light. This means that colour will be reproduced differently on screen. Typically this means that dark colours become darker and light colours become lighter. This can often mean that corporate colours need to be adapted to work online. For more information on this read Jason Santa Maria’s excellent article Cheating Color.
  • Interaction – Finally it is important to remember that the web is an interactive medium with more in common with software design than print. Users are required to click links, enter data and interact with applications. It is not the passive experience of reading. Although print and web design share a lot in common, a print designer will have to considerably expand his skill set to accommodate these interactive elements. Learning about user experience design is key to the role of web designer.

Obviously this is only the tip of the iceberg but hopefully it demonstrates just how different the experience of designing for the web is. Something that clients in particular need to be aware of.

The importance of job titles?

Hi Paul and Marcus, I work for a 8+ people studio that develops websites. My job title is “developer” and I do tasks from chopping up a design and turning it into HTML, then adding it into our CMS, and then adding content. I will then help clients by supporting them on their website and helping them add future content.

I am quite happy in my job, but I know that if I ever want to apply for a new job, the job title I have is very important. I am worried that my job title is not specific enough to my skills, do you think I should change it to something that sounds more representative, as “developer” could lead someone to believe I only do small tasks.

I think the question of how important job titles are is one for much debate, however there is an obvious requirement for people in any industry to have an appropriate title that describes what they do, the problem is peoples definitions of what a particular title means can be extremely varied.

To add to the confusion there are often multiple variations of the same title. For example my definition of a Front-End Developer is someone who codes HTML, CSS and javaScript, however this same role is often labeled as:

  • Front-End Engineer
  • Client-Side Developer
  • Client-Side Engineer
  • or simply Developer

The same goes for Back-End Developers i.e. people who code in a server side language such as PHP or Ruby. Again the list of variants can be endless:

  • Back-End Engineer
  • Server-Side Developer
  • Server-Side Engineer
  • or again simply Developer

So if your job title is Developer, which discipline are you or do you do both?

I don’t have a definitive answer to this question, however things certainly become much clearer when you specialise in a certain area, for example:

  • javaScript Developer
  • PHP Developer
  • Front-End Developer

To answer your question though, your job title isn’t as important to potential employers as you may think. When you apply for a new job they will look firstly at your portfolio and whether you can demonstrate the skills that they require. Instead of picking a job title that you think potential employers would like to see, pick one that is actually relevant to what you do and have a good portfolio to back it up.

Back to top

178. Bad Blogging

On this week’s show: We look at the harsh truths of corporate blogging, ask how luxury products can be sold online and discuss whether it is the role of a web designer to challenge a client’s business model.

Play

Download this show.

Launch our podcast player

News

The Do’s and Don’ts of Dark Design

“Users will spend considerably less time viewing a website with a dark background than one with a light background” – When you hear statements like that you may dismiss the idea of using a dark design. However in reality, I believe there are a place for dark designs. Dark designs can look elegant and extremely striking. And although not always appropriate, there are times when they are the right solution for a site.

Screen shot from Trozo Gallery

The question therefore arises – how do you get a dark design right? How do you avoid dwell time plummeting? The answer lies in a post from Web Designer Depot entitled “The Do’s and Don’ts of Dark Design.”

The post identifies several techniques for ensuring that a dark site is both readable and appealing. These include:

  • Including more white space (or should I say dark space)
  • Ensuring text has ample kerning and leading
  • Getting the text contrast right
  • Choosing the right fonts
  • Using minimal colour schemes

The post also asks when a dark design is appropriate. The conclusion – if you require your site to appear elegant or creative. The author then goes on to show some stunning examples of both.

If you are considering using a dark design or do so already, this article is definitely worth a read.

The Content Conundrum

Sometimes I feel like a stuck record. On last week’s show I talked about Art Direction (again!) and I have also written about the importance of copy-writing many times before. This week I want to highlight a post from Boxes and Arrows entitled “The Content Conundrum.”

In some ways this article feels like a rehash of many previous posts and repeats the same old mantra:

  • Include copy editors from the beginning of a projects life cycle.
  • Do not use dummy Latin text.
  • Work closely with content providers.
  • Start treating content as important.
However, there are a couple of ways this post really stands out from the crowd.
The first is that it shows a brilliant example of where things can go wrong. It compares a signed off design comp with what was actually built. The difference is striking and one that will resonate with any designer. The amount of copy has doubled and the usability breaks down as a result.
A comparison between an approved page design and the final page live on the website
However, the most striking thing about this post is that instead of simply moaning about the state of art direction, it actually proposes some solutions that can be practically implimented by any designer. These include:
  • Look for ways to remove unnecessary content.
  • Endeavour to use information graphics and visualisations instead of copy.
  • Write some content yourself even if it isn’t perfect.
  • Seek ways to collaborate with content providers.
  • Use real content (even if it is not the final content) in visual mock-ups.

This article recognises that we are facing big challenges but instead of offering big solutions that cannot be practically implemented it suggests little changes that all designers can make to improve things.

So You’re Thinking About Becoming a Designer

I know a lot of those listening to this show aspire to be designers. If that is you check out “So you’re thinking about becoming a designer” that catalogues the responses of a number of designers, when asked to complete the following statement:

So you’re thinking about becoming a designer? If I could tell you only one thing about going into the field, my advice would be…

The answers really resonated with me and I would wholeheartedly agree with everything said in this post. They basically fall into three categories…

  • Focus on empathy and understanding problems
  • Embrace the unfamiliar to innovate
  • Be passionate

Each category is accompanied by some choice quotes and a short video from the person being quoted. My favourite quote is by Jennifer Bove who says:

Being empathetic helps designers create things that move people.

I think empathising with users is by far the most important skill any designer should have. Without it they may create something very pretty but it will serve no meaningful purpose.

Adobe AIR Apps for Designers

Our final news item in this very designer centric section is “18 Adobe AIR Apps for Designers.” As the name suggests this Sitepoint post lists 18 AIR applications that maybe useful when designing a site.

Unsurprisingly the list is dominated by tools to help with colour selection. From Kuler to ColourLovers it would appear every colour site has to have an AIR app.

Screen capture of Adobe Kuler

However, that is not the end of the list. There are also lots of other tools including:

  • Measuring tools that allow you to measure on screen elements
  • Flex tools
  • Vector editing programs
  • Image resizers
  • Image editors
  • Font tools
  • Icon generators
  • Screen capture tools

Its a great list and it is amazing to see what can be done with Adobe AIR.

Back to top

Feature: 10 Harsh Truths of Corporate Blogging

Every company in western civilization seems to have a blog these days. But are they worth it, and why are so many terrible?

Read the 10 Harsh Truths of Corporate Blogging

Back to top

Listeners feedback:

Business model advice

Ashley Hart writes:

As a web designer you come across a lot of start up companies, sometimes you can see that by altering their concept slightly they might be more successful. Is it your place to do so? would it help? or just annoy them?

Yes! Absolutely! We should be offering advice about business strategy. Clients are paying us for our knowledge of the web, not just our skills in Photoshop. That means we need to tell them if we think their business plan needs tweaking to work online.

It is also a great way of differentiating yourself during the pitch process. Clients tend to warm towards suppliers who are full of ideas and willing to work with them rather than just providing exactly what they ask for. In fact at Headscape we like to refer to ourselves as partners rather than suppliers. This gives extra value to our clients.

However, it is important to draw a line. Definitely offer advice, but ultimately it is down to the client to decide whether to accept that advice or not. Always remember that as the web designer you might not know all the fact. There can often be good reasons why a client chooses to ignore your advice and do things differently. And even if there isn’t its their business at the end of the day.

Does ecommerce work for luxury goods

Bruno writes:

Luxury brands reluctantly build online shops and are quite shy about investing in eCommerce since there don’t see any ROI. What more should they do to make real income from the internet?

The answer to this question very much depends on the product. For example, I maybe reluctant to buy a new bed online because I wouldn’t have been able to try it. However, I would happily buy a new macbook.

But it isn’t just about the product. Its also about the purchaser. Although I would happily buy a macbook online I know that my dad (who is about to buy his first) would not.

I think ultimately it is about risk. There is a higher risk buying a luxury product online because it comes with a higher price tag. There is more to lose if things go wrong. Equally, if you are missing key information about the product (like the comfort of a bed or the differences between a mac and a PC) then the risk is also higher.

Therefore selling luxury goods online is about two things – removing real risk and reassuring users who perceive false risk.

Removing real risk is relatively easy. Money back guarentees and detailed information will often do the trick. Making returns easy also makes a huge difference.

Reassuring users who perceive a false risk is trickier. Ultimately that is where the human touch comes in. Often with luxury goods it is neccessary to backup the online transaction process with human customer service. A 24 hour telephone help line is important as is email support and even live chat. Basically people need to be able to speak to a real human being to reassure themselves and get answers to their questions.

So, selling luxury goods online is not impossible. You just need to work that little bit harder.

Back to top

10 Harsh Truths About Corporate Blogging

Every company in western civilization seems to have a blog these days. But are they worth it, and why are so many terrible?

I have reached the conclusion that most organisations have a blog simply because they feel they should. Many marketing departments fail to ‘get’ blogging and have poorly visited blogs with few comments. Because their blog fails to perform they conclude that blogging is an ineffective marketing tool and either remove it entirely or leave it to languish.

However, it does not need to be this way. Corporate blogs can be a powerful communication tool that builds brand awareness and nurtures a sense of engagement. You only need to look at the vibrant community surrounding the 37Signals blog to know that corporate blogging can work.

A screenshot of the 37Signals blog showing a large number of comments

This post asks the questions – why are most corporate blogs failing and why do the few succeed? To do this we need to face a few harsh truths.

1. A blog does not magically generate traffic

When companies first started launching corporate websites they perceived them as a marketing channel that would generate leads. They had a ‘build it and they will come’ mentality. Over time they realised that a website is more like a storefront. A few people might wander in off the street, but most of the time you need to advertise to attract trade.

Many marketing departments are making a similar mistake with corporate blogs. They perceive them as a way to generate new traffic, when that is not their primary role. Admittedly the keyword heavy nature of a blog will help your organic rankings, but that is a secondary benefit.

The real role of a blog is to generate repeat traffic which is considerably more likely to complete a call to action. A successful blog has a regular readership who is being constantly reminded of your brand and products.

Of course building up a readership takes time.

2. Blogging takes long term commitment

Building a readership is a long term commitment. It can take months for users to recognise your blog as a consistent source of useful information. Only then will they start visiting it regularly and recommending it to others.

It doesn’t just take time, it also takes commitment. That means posting regularly and to a schedule. Users are more likely to visit your blog if they know you release a post on a certain day each week.

Of course ultimately you want them to subscribe so they don’t need to continually check your site for new content.

3. Teaser feeds are a wasted opportunity

Users can subscribe in a couple of ways. They can either sign up to receive email notifications or subscribe to an RSS feed. This is a crucial step in engaging readers. That is because users are effectively giving you permission to  remind them about your site and brand.

However, it is remarkable how many organisations fail to grasp this opportunity. Instead of using the chance to push content to users, they only provide a teaser of blog posts. This means users have to click through to view the whole post.

This practice is born out of a false belief that users need to see your site. They don’t. Unless your revenue is driven by site advertising, there is no need for users to click through to read your blog.

The purpose of most corporate blogs is to build and maintain brand awareness while motivating users to engage. None of that needs to happen on site. The blog post itself builds and maintains awareness, while requests for comments or calls to action motivates users to engage. Users do not need to see the rest of your site to respond to the copy of a blog post. Of course for that to be true, posts need to be engaging.

4. Your not ‘engaging’ anyone

The most successful blogs are more than a broadcast tool. They are a dialogue between the individuals within your organisation and your users. It is important to listen, as well as speak.

Unfortunately the majority of corporate blogs fail to engage. Instead they focus on telling readers how great their products and services are. Rarely do they ask for feedback or ask questions. In fact it is not unusual for companies to disable comments for fear of criticism.

Instead you should be encouraging users to contribute to your blog through comments and constructive criticism. It is a superb opportunity to get free feedback from your customers, something many organisations pay market researchers for.

Part of the problem is that most corporate blogs offer nothing more than rehashed press releases.

5. Press releases shouldn’t appear on a blog

Let’s set aside the debate over whether press releases  have a role in today’s web centric world. Whether they do or don’t, you need to realise that a press release preforms a different role to that of corporate blog.

As the name implies a press releases is meant for professional journalists. It is designed to encourage journalists to write about your product or service. It is not designed for your customers.

A blog on the other hand is meant to be read by prospective and existing customers. It should be engaging, informative and helpful. When writing a blog post you should always have the end reader in mind. What will they learn? What insight will this give them into who we are? How will it help build our relationship with the reader? You should never simply copy and paste press releases or news stories.

The other problem with press releases is that they are corporate statements. A blog should have a more personal tone.

6. You sound like a faceless corporation

People don’t like interacting with organisations, corporations or machines. People like conversing with people. One of the things I have learnt about selling web design services is that once people have established that you offer a good service at a reasonable price, the next thing they care about is you. Do they like you? Do they trust you? Do they think they can work with you?

People don’t like, trust or want to work with corporations. We associated those feelings with individuals, not companies. It is therefore important that a corporate blog is about the people within your organisation, not the organisation itself. Your blog should focus on different people and the role they perform with your company. They should be able to demonstrate some of their personality as well as share their expertise.

A blog is a place to let readers see behind the marketing spin and glimpse the real people within your organisation.

7. You need to show the warts and all

If you are a marketeer this may all sound a little scary. Its hard to control ‘the message’ when you are blogging. You have multiple bloggers from across your organisation who are effectively becoming corporate spokespeople, and you are allowing users to publicly criticise you on your own blog. This is a long way from traditional marketing.

However today’s consumers are very savvy. They are distrustful of traditional marketing and can sense when they are being sold at. A softer approach is required, one that is more ‘real’ and less managed. One part of that is admitting when you make mistakes.

A screenshot of GetSatisfaction.com

Dell constantly ignored criticism they received about poor customer service. They ignored the voice that the web provided their customers, until eventually a single disgruntled user stirred up a major PR nightmare with a single post entitled ‘Dell lies. Dell sucks.

Contrast this with the ‘warts and all’ approach adopted by photo sharing site Flickr. When faced with community criticism over the poor performance of their website they wrote a post on their blog entitled ‘Sometimes we suck.’ They acknowledged the problem and laid out a plan for correcting it. This non traditional approach to their brand image allowed Flickr to quickly defuse a situation that could have grown out of control.

A blog post on flickr entitled 'Sometimes we suck'

Perhaps when it comes to corporate blogging, marketing is not always best equipped to handle the task.

8. Marketeers often make bad bloggers

Let me be clear. I am not saying that all marketeers should be banned from blogging. What I am saying is that traditional marketing skills are not always best suited to the medium. Because blogging should be personal, transparent and not shy away from an organisations flaws, it can seem an uncomfortable communication tool for some marketeers. Also the traditional writing style of many marketeers does not fit well with the informal style of a successful blog.

If you are a marketeer responsible for the corporate blog, look for ways to encourage others within your organisation to blog. Think of yourself as an editor rather than an author. Target people who are particularly knowledgeable or already act as spokespeople for your organisation. Encourage them to blog and act as a copy editor tweaking and refining what they write.

You may find it hard to encourage others to blog. If that is the case try interviewing them instead. You can then turn those interviews into blog posts and hopefully encourage them to respond to comments. But remember, whether you are posting an interview or an article, do not expect too much from your readers.

9. You expect too much from your readers

Most of the corporate blog posts I have read are long, text heavy and boring. They take considerable commitment to wade through. In short, they ask too much from readers.

With so many blogs online you need to make your posts stand out from the crowd. Always ensure users can get the gist of what you are saying by just scanning the post. This can be achieved using a number of techniques…

  • Summarise a post at the beginning and in the title. Don’t leave users guessing what the subject is.
  • Be controversial to grab users attention.
  • Use headings as a way of grabbing attention and summarising content.
  • Use images to break up the copy and communicate key points.

Do not feel all of your posts need to be an essay. Short posts that propose a question or draw the readers attention to another site are just as engaging. Anything that is of value to the user is worth posting.

Finally, remember that not all blog posts need to be textual. Consider buying a flipcam and recording some video interviews with people around the company. Record an audio interview or post some photographs of corporate events. Just don’t expect users to read lots of copy. The only people who do that are your competition.

10. Your competitors will read your blog – Get over it!

I am amazed at how many organisations will sensor their corporate blogs because they are worried their competition will read it and rip off their expertise and ideas. Although it is true that your competition will do exactly this, what is the alternative? One the primary opportunities a blog provides is the chance to demonstrate your expertise. People will be motivated to buy from you because they understand you ‘know your stuff.’ However, if you don’t talk about your expertise, how will they know? You might be the best in your field but if nobody knows it then what is the point?

I write about my knowledge of web design all the time. I know that many of those who read my posts are competitors and learn from what I share. However, I know a lot of prospective clients read the content too. Should I silence myself for fear of being copied or should I prove to my clients that I know what I am talking about? I think the answer is clear.

Conclusions

Many organisations are still finding their voice online and corporate blogging is one way they can achieve this. It is not surprising that they are still making mistakes. The secret to success is accepting that a blog is not a traditional marketing tool. In my opinion, it has more in common with a customer services. Once you realise that and release it from the shackles of press releases and corporate news, it will begin to generate return on investment.

174. Twitterverse

On this week’s show: The entire boagworld community shares its thoughts on web design and Megan Fisher gives us practical advice on building a mobile website.

Play

Download this show

Launch our podcast player

Housekeeping

We have two pieces of housekeeping this week…

Charm Clients, Win Pitches

I am running a workshop on the 23rd of October that you maybe interested in attending if you are a freelancer or involved in selling web design services. The workshop will teach you how to sell yourself to prospective clients, how to generate sales opportunities and how to work effectively with your clients in long term partnership.

If you are interested in attending or want to find out more visit the ‘Charm Clients, Win Pitches’ web page.

As an added bonus, enter the code CWPB_09 at checkout you receive 15% off.

dContruct Competition

Good news if you are in the UK. Very unusually there are actually a few tickets left for this years dcontruct conference on the 4th September in Brighton.

Normally this conference sells out in minutes due to its amazing line up of speakers and subjects that will leave you feeling like a beginner!

However, we actually have even better news because we have two tickets to give away each worth £115+VAT. To win a ticket you have to complete the following sentence on Twitter…

My perfect web conference would include…

Tweet your answer by the 1st August for a chance of winning. The guys at Clearleft will then pick the two most inspirational/funny/entertaining answers and contact you by email.

Back to top

News

The importance of microcopy

I have learnt a new word this week – Microcopy. Microcopy is a small piece of text that reassure users and nudges them in the right direction. It is different to the instructional text criticised by Steve Krug in “Don’t Make Me Think“. This copy does not just state the obvious. Instead it clarifies and reassures.

In his post “Writing Microcopy” Joshua Porter provides a number of examples of Microcopy in action.

  • When signing up for a newsletter, say “this low-volume newsletter”
  • When people add their emails, say “we hate spam as much as you do”
  • When subscribing for something free, say “you can always unsubscribe at any time”
  • When selling an paid-for web application, be sure to let people know if you have a free trial.
  • When storing customer’s information, say “You can export your information at any time”
  • If offering optional account creation, say “If you create an account, you’ll be able to track your package”
He also cites a case where he cut credit card processing errors to near zero by adding a single sentence – “Be sure to enter the billing address associated with your credit card.”
Almost all of the examples given in the post have one thing in common – they help alleviate the concerns of users by answering the questions they already have in their heads.
As Joshua concludes: “Don’t be deceived by the size of microcopy. It can make or break an interface.”

Content templates to the rescue

In someways it seems almost pointless to discuss Microcopy when most website owners are having problems generating any quality content at all. Its not that they are doing a bad job. It is simply that they are under resourced. They are relying on ‘experts’ within their organisation to provide copy and either these people are too busy or are terrible writers.

That said, the copy is what users really care about, and one way or another we need to ensure it is as consistent and of a high quality.

One thing that might help is a List Apart article on ‘content templates’. These are not the kind of templates found within a content management system. Rather they are templates that can be given to content providers to help them write better content.

In essence a content template is a form content providers can fill in. It will suggest what kind of content they need to provide and even advice on how to write and present that content.

In the article the author gives an example of a content template for product pages. The template asks for information such as…

  • Product name
  • What is it?
  • Who is it for?
  • What does it do?
  • Why does the reader need it?
It also gives examples of how the copy might be written and advice on how to lay it out (using bullets, data tables etc.).
Its a good concept and one that is easy to adopt. Although it won’t solve your content woes it will increase the quality of copy you receive from content providers.

Being original

In 2003 Cameron Moll wrote “Good Designers Copy, Great Designers Steal” in which he explored where designers draw their inspiration. It was not the first article to tackle the subject and neither was it the last. In fact only this week the Web Designers Depot released a similar post entitled “Great Designers Steal?

What is interesting about this new post is that he defines three levels of designers…

  • The designer that copies – This is normally a designer who is starting out and who learns from visiting website galleries and lifting designs in their entirety, making only minor alternations.
  • The designer who steals – Generally more experienced, these designers find inspiration in website galleries but will not copy directly. They will be inspired by a theme or specific detail. However, these elements will be heavily customised and altered.
  • The designer who seeks originality – This designer actively avoids looking to other sites for inspiration. They turn instead to sources such as print, art, architecture and nature. Their desire is to create something entirely orginal on the web.

The idea of looking beyond the web is far from new but there is something inspiring about the post. His conclusions are particularly ponient…

The pursuit of originality on the web is not a lost cause. The web industry is still young, and some things have yet to be attempted.

Once you understand the basics of design, try to think outside the box, and try new and different things. Be atypical and unique. Experiment. Don’t be afraid to design from the heart. But keep this in mind:

“Things which are different in order to be different are seldom better, but that which is made to be better is almost always different.” —Dieter Rams

Theories and conventions are always being questioned, challenged and broken, and they should. If you believe a better way is possible, you will often find your way to it.

Tools for testing mobile websites

On this week’s show we have Megan Fisher talking about practical ways you can start building a mobile version of your site. It therefore seemed appropriate that we featured a post from Sitepoint entitled “Six Tools For Testing Designs On Mobile Devices” in our news section.

The six tools featured are…

  • Device Anywhere is a commercial operation, allowing customers to sign up and test “Any Device. Any Network. Anywhere.” There are a range of subscription plans but you can sign up for a free trial.
  • MobiReady is tests mobile-readiness using industry best practices & standards. After testing you receive a free report outlining how well your site performs.
  • Opera Mini is a live demo of the Opera Mini browser that functions like it would when installed on a handset.
  • W3C Mobile OK Checker performs a range of tests on a Web Page to determine its level of mobile-friendliness. The short report produced will tell you where you’re going wrong.
  • dotMobi Emulator emulates a real mobile phone Web browser. It’s a bit limited as you can only choose from two different phones you like as a skin.
  • iPhoney, as you could imagine, is specific to iPhone testing. It’s a downloadable application that is precise to the pixel, so useful for the designer working on iPhone apps.

With the number of internet enabled smartphones rocketing, this is an area of increasing importance and these tools will become incredibly useful. Check out the post for more details.

Back to top

Interview: Megan Fisher on starting building a mobile website

Stanton:Alright so we’re here with Megan Fisher, Hello Megan.

Megan:Hi Guys!

Stanton:Hiya, how are you?

Megan:I’m well thanks.

Stanton:Good, we’ve just seen you onstage talking about designing for mobile.

Megan:That’s right.

Stanton:Designing effective mobile interfaces.

Ryan:Paul checks his badge as we speak, just to double check, you are Megan Fisher aren’t you?

Megan:Yes I am.

Stanton:So I really enjoyed your talk.

Megan:Thank you.

Stanton:So we’re just really asking you about it for all the Boagworld listeners

Ryan:I suppose first of all do you want to tell use who you are, where you’re from so the people who don’t know who you are have a bit of an understanding.

Megan:Sure, I’m Megan Fisher I work for SimpleBits with Dan Cederholm and we’re based in Boston, Massachusetts, small little web design shop.

Stanton:Do you want to give us the overview of what you talked about today.

Megan:Sure, so basically where I’m coming from is I’m a designer for desktop browsers first, and that’s what I’ve being doing for the passed several years, and kind of ignoring mobile web because it seems intermediating and there are so many devices out there with all different resolutions and different CSS support so, it seemed rather scary, but recently Dan’s been working on this new application he’s launching and I decided to take on the challenge of doing a mobile web site for it, so my talk was kind of covering how you get started when you’re first approaching mobile web design.

Stanton:Ok and you gave us three distinct levels of mobile support you can role in, the easy with little work and the benefits with that, and then progressively the more work you put in then the better experience.

Megan:Right, and I think that’s the key with starting with mobile web design, is that you can do it in small steps, it can be iterative, the first step can be showing your markup and that’s obviously the easier step, and then slowly adding a little style so it kind of enhances the site for mobile users and eventually it would be great if we could all design our own mobile specific sites.

Stanton:So in your kind of day to day client work, is this something that you try and roll in to the client saying we can build you this mobile interface, I can tell it’s probably one of the things that’s often gets cut from the budget if you say we can built this fantastic mobile interface for you, or we can give you just the basic level of support.

Megan:Yes, that’s funny. I haven’t had a lot of clients actually requesting mobile sites, and normally I’ll just kind of, you want to make sure your markup is well written and I’ll do a quick little mobile style sheet, sort of when you do your print style sheet that’s like a standard step, and I actually haven’t really offered to do a full on mobile interface yet, that’s kind of a big task and working on dribble is the first step, when you work on your own project you can do these things and not worry about budget and just have fun with it.

Ryan:You talked about three steps in your talk, do you want to take us though those and give us an overview of each.

Megan:Let’s see if I can remember them without the slides

Ryan:I can remind you, I’ve made notes.

Megan:No no no, so the first step is you just want to make sure your markup is always standards based and semantically correct, hopefully most of your viewers, or listeners are already doing this, the benefits of using web standards are well known, they’re faster to load and accessible for a lot of people. So the first step is writing clean and accessible markup, there’s a lot of benefits to doing this as we well know, but for mobile devices specifically they’re going to load a lot faster and if you’re not using tables for layout and you’re using correct semantics in terms of headline tags, and unordered lists and strong tags for emphasis then you’re going to have a much better shot at getting your site to render correctly on a mobile browser.

Stanton:You also talked about mobilising the layout and reordering the content based on the device, and the context in which the site will be used.

Megan: Right, so the first step you can do is making sure your sites one column, and disabling floats is an easy way to do that, and then you want to, display: none is your friend, you want to hide content that’s not going to be useful for mobile users, especially things like flash and all that sort of added stuff, and making sure the most important content comes first and it’s easy to navigate and you can get a clear picture of what the site does, disabling images is another good step because that improves load times of course.

Stanton:And finally it was staying with your brand.

Megan:Right, so a lot of people thing maybe, or maybe people assume because you’re designing for such a small screen space and you want to keep your load times fast that this means you can’t have all your cool branding stuff that would have on your regular web site for your desktop browser, but that’s necessary true you can still incorporate background images and if you use small compressed graphics that are relevant to your branding that would still work, keeping the colour scheme consistent with what you have on your normal web site and the typography you can kind of play with that, and there’s fairly good support for that.

Stanton:You got this asked in the Q&A at the end but I’m going to hijack it and ask you again for the benefit of our listeners, with the adoption of devices like the iPhone and the BlackBerry and consistent UI’s with WebKit and Safari coming into the mobile browser and being able to use jQuery and all that jazz, can you see it getting easier to develop these things and how would you go about testing for different devices.

Megan:Sure, so it’s kind of a two parter, when you’re considering things like the iPhone there’s still a lot of advantages to creating a separate mobile site for these devices, and really the biggest thing you want to think about is the resolution, in the old days of web design we had to design sites that were for 800 by 600 resolution, obviously that was something you considered in the design process, so just because the iPhone renders using WebKit and it looks like it would in Safari, it doesn’t mean you don’t want to design for that screen size, as far as testing for different devices, most of the major devices out there have a rendering engine that you can look at, there’s lots of great tools, one that I used mobify.me and they have support for something like 4,000 devices and they’ll let you test on those and also they have a script you can use that will automatically direct those browsers to your mobile site.

Ryan:How consistent are they between devices, are some devices majorly inconsistent in the way they render sites or are they quite, are we nearly there?

Megan:It’s definitely gotten better especially with things such as zooming, there’s a lot more support for different styles, it’s difficult to say because it really varies in places like Africa they’re using older devices maybe with smaller screens and obviously the iPhone is hugely popular in the States so, that’s what I use to test, it’s difficult with consistency and there’s been a lot written about it, I mentioned in the talk the article on A List Apart about the return of the mobile style sheet is what the article is called, and he kind of goes over that and the consistency and support for handheld CSS.

Stanton:Are there any books or articles that you would recommend people that are wanting to know more about this to check out?

Megan:Yea absolutely, so like I said if you go on A List Apart and just search mobile, obviously A List Apart is a great resource for designers and they have excellent articles on the mobile web as well, Cameron Moll has written a fantastic book called mobile web design and it’s available as a PDF download it’s fairly inexpensive, and that’s what I used when I first started doing my research, also if you go on Delicious and search the tag FOWD09 research you can see all the resources I used for putting my talk together.

StantonOk, well thank you very much.

Megan:No problem guys.

Thanks to Ben Everard for taking the time to transcribe this show.

Back to top

Listeners section: Web design advice from Twitter

This weeks listener section is going to be a little different to normal. Instead of answering a listeners question, I decided to ask my Twitter followers to help me write a blog post. I posted the following Tweet…

I am writing a post on web design words of wisdom - think 'confusus says'. Post yours to Twitter in 140 characters or less. #webwisdom

The answers I received formed the basis of my latest blog post ‘Web Design Wisdom from Twitter‘.

169. Type

On this weeks show: Paul talks about the power of story telling and shares some tips for “getting in the zone” and Mark Boulton joins us to talk about web typography.

Play

Download this show.

Launch our podcast player

Housekeeping: Jobs and Projects

Whether you are looking for a freelancer to build your latest web project or a permanent addition to your web team, the Boagworld forum is now the place to go.

We have added a new jobs category which lists web design projects and jobs free of charge. So, whether you are looking to post a job or pick up some work you should take a few minutes to check it out. Right now there are jobs for…

  • A web project manager
  • A joomla expert
  • ASP.net developers
  • PHP developers
  • And much more.

Back to top

News

Coding like its 1999

This week Cameron Moll has posted “Coding like it’s 1999“. The reason for this witty title is his decision to return to using HTML 4 and pixel font sizes, both of which were best practice in 1999.

The post is essentially a justification for these two decisions and he puts forward a very convincing argument for both. He credits his decision to move back to HTML 4 to Dave Shea who recently wrote a compelling argument to drop XHTML. Dave writes…

Six years ago, many of us thought XHTML would be the future of the web and we’d be living in an XML world by now. But in the intervening time it’s become fairly apparent to myself and others that XHTML2 really isn’t going anywhere, at least not in the realm that we care about…. I’m not ready to start working through the contortions needed to make my sites work with an HTML5 DOCTYPE yet, which leaves me with the most recent implemented version of the language…. [U]ntil I get a better sense that HTML5 has arrived, 4.01 will do me just fine for the next four or five years.

As for the decision to move back to pixel based typography, Cameron writes…

However, recent versions of every major browser — Safari, Firefox, Google Chrome, Opera, and yes, Internet Explorer — now default to page zooming instead of text scaling… What does all this mean? It means px can again be considered a viable value for font-size. It means the difference between setting text with absolute units or setting text with relative units is negligible for users. For you and me, however, the the difference is substantial. The burden of calculating relative units throughout a CSS document is replaced by the convenience of absolute units — 14px is 14px anywhere in the document, independent of parent elements whose font-size may differ.

Although at Headscape we still work with XHTML, we have moved back to pixel base typography and I suspect will do the same with HTML. I do not think it will be long before most web designers follow suit.

The power of words

Problogger has published a post that demonstrates the importance of our words. It shows how the words we pick can have a real effect on how users act. Word your copy carefully and you could substantially increase conversion.

Interestingly the post does not demonstrate this through example of good website copy. Instead it looks at the language used by successful waiters. The article takes three phrases often used by waiters and explains why they are so powerful. The phrases are…

  • “Our chef recommends”
  • “Everyone else has ordered… and they love it”
  • “So gentlemen, is everything delicious?”
From these three phrases he raises the following points…
  • Invoking the power of a higher authority will influence decisions - For example using a testimonial from an influential figure.
  • People believe in safety in numbers - “If others like something then surely I will too”. For example highlight your most popular products or articles.
  • Positive wording generates a positive feeling – For example “Thanks for subscribing to my email feed! I hope you find every post as exciting as the one that made you subscribe”.

It is an excellent article and there is a lot more detail than I have covered here – make sure you check it out.

10 tips for creating a more usable web

The Web Designers Depot has published “10 Tips to Create a More Usable Web“. Its not exactly the most original post and we have seen similar posts from Smashing Magazine in the past. That said, it is still a worth while read.

The problem is that it is so easy to forget best practice when it comes to web design. There is just so much to take into account as we design a website that we can easily overlook things. Articles like this may not necessarily teach us anything new, but they do bring to the fore best practice that may have been pushed out by more recent issues such as WCAG 2 or web typography. We can never be reminded enough of the principles of usability.

This particular list includes…

  • Creating active navigation
  • Clickable labels & buttons
  • Linking your logo
  • Increasing the hit area on a link
  • Adding focus to form fields
  • Providing a useful 404 page
  • Using language to create a casual environment
  • Applying line height for readability
  • Utilizing white space to group elements
  • Being accessible

As with all good list posts, each point is accompanied by a brief explanation and some nice examples. Check it out.

Four quick tools

I conclude today with a quick round up of various tools that have been released this week. Its a bit of an eclectic mix but they are all worthy of note…

  • Google Page Speed – Page Speed is an open-source Firefox/Firebug Add-on. Webmasters and web developers can use Page Speed to evaluate the performance of their web pages and to get suggestions on how to improve them.
  • EntityCode – HTML entities are HTML code that is used to display special characters such as the £ sign. However, remembering them all can be tricky. EntityCode is a useful reference that lists some of the most commonly used HTML entities in a very swish AJAX driven format.
  • Google Web Elements – Google Web Elements allow you to easily add your favorite Google products onto your own website. Widgets include calendar, conversations, custom search, maps, news, presentations, spreadsheets and Youtube news. All of these widgets existed previously but have now been brought together on a single site.
  • Adobe BrowserLab – Adobe BrowserLab is a browser compatibility service that provides designers screenshots of their pages on leading browsers. There has been a lot of excitement around this one, but I was not overly impressed. Sure the interface is nice and Adobe are a big name. However, the service only offers screengrabs (not interactive sites) and only for a limited number of browsers. In my opinion there are better services out there such as Litmus’ Alkaline.

Back to top

Interview: Mark Boulton on web typography

Paul: So, the next in our series of interviews from the Future of Web Design is with Mark Boulton. Hello, Mark.

Mark: Hello there.

Paul: So… we interviewed you on boagworld, didn’t we, about… quite a while ago.

Mark: It was a while now, January?

Paul: Yeah

Mark: Something like that.

Paul: Something like that, yeah.

Marcus: What, that long ago?

Paul: Well, in internet terms, that’s forever.

Mark: That’s forty years ago.

Paul: So, at the time, you were just embarking on this odyssey of doing a redesign with Drupal, or you were part-way through it. And we were talking about this very unusual approach of ‘Hey’, you know, we normally discourage people, don’t we, from doing any kind of, don’t show your design to a group and you were showing it to thousands of people.

Mark: Yes, yes.

Paul: And you talked about how great it was going to be and there was this slight fear and trepidation in your voice at various times. How’s it gone?

Mark: It’s gone really well.

Paul: Has it?

Mark: It has. It’s gone really well. It’s been terrifying on a daily basis. Posting comments for… you know, registered users on drupal.org are about 400-500 thousand.

Paul: Right.

Mark: A fairly active, passionate community; a lost of these people have invested time, money and have businesses riding on Drupal. So, however, the vast majority are really in favour of what we’re doing.

Paul: So what, how did it work in practice? You know, were you uploading designs to a blog and just saying: ‘Hey, have your say’ or was it more structured than that?

Mark: It was more structured than that; it wasn’t initially, I mean we’ve learned some painful lessons along the way. But it was a very distributed approach, so we’d have a Twitter group, we have, sorry a Twitter account, we’d have a flickr group, YouTube groups, our own blogs – mine and Leisa Reichelt’s.

Paul: Right.

Mark: We’d have drupal.org, which is the main kind of Drupal page, but we’d also have groups.drupal.org where you can create your own little groups and we’d have a group there.

Paul: OK.

Mark: The view is that, so if we just posted things to Drupal, if we just spoke to the Drupal audience, we’d get a very slanted feedback on what we were doing.

Paul: Of course.

Mark: So, the idea was that we would touch on all sectors of the, kind of all bits of the audience. And then we’d, we were working weekly iterations on a 12-week schedule.

Paul: Right.

Mark: Which was killer.

Paul: Yeah.

Mark: We would not do that again and we would release material, whatever that would be; mostly it was HTML prototypes, fairly lo-fi, and we’d release them on a Thursday and then we’d sit on our hands

Paul: And watch.

Mark: And watch, yeah, with trepidation.

Marcus: Dealing with hundreds of thousands of comments.

Paul: How did you deal with that?

Mark: Yeah, we, we…

Marcus: Ignore them!

Mark: At first, I mean, there’d be the odd occasion where you’d get flamed and things could get personal and nasty and the&helllip; of course, the natural, human reaction would be to get in there and defend yourself and, but we, after a couple of times of trying that, which didn’t work, we didn’t, we really had to walk away from the computer and…

Paul: Yeah, I think that…s a good lesson for anybody running a community or interacting with people.

Mark: Absolutely, I mean the first lot, you know, if you post something up to a community, your first day’s worth of comments are setting the scene and then the following days from that trends will start to emerge &endash; repeated themes &endash; and that’s what we were watching for. So, we’d spend maybe four days, through till the Monday, just watching, you know, over the weekend, which was quite nice because we could do other&emdash;have a life…

Paul: Which is always good.

Mark: Yeah. And then we’d go back over the comments on the Monday and try and establish some themes that we agreed with and we put forward into the next iteration.

Paul: Right.

Mark: But it’s probably worth saying at this point that it was not a design by demo… it was not a, kind of, a democratic process.

Paul: No.

Mark: Because you just end up with mediocrity, I mean, kind of a little bit of a dissing WordPress here, but what WordPress are doing with the voting.

Paul: Right.

Mark: That’s not really our approach. Our approach was… we had a clear design vision.

Paul: Right.

Mark: And we pretty much stuck to that, but it was the way that you presented the material and gathered the feedback, that’s kind of steering that vision.

Paul: Yeah, so did you learn lessons about presenting the material and how to do that?

Mark: Yeah, we’re still doing that, we’re still on a kind of weekly basis.

Paul: Because that’s always the big thing isn’t it? You know, you can’t just take a design, show it to people and say: “What do you think?”

Mark: No, just go: “Here you go” No, which we did early on and it was a disaster.

Paul: Yeah, I can imagine.

Mark: Yeah, it was. It was like: “What do you think of this? I’ve got some ideas for the logotype.” “It’s rubbish!” You know, hundreds of comments.

Marcus: And they all start arguing with each other, no doubt?

Mark: Yeah, and it was… so, you have to put something in place to ask for specific feedback; that’s where we got to. So, it was, if you’re posting up an iteration which involved heave change to the masthead design, we’d steer it like: “What are your thoughts on the navigation? You know, do you think this works, do you think that works?” And wherever possible, we’d validate our design direction with testing and research anyway.

Paul: OK.

Mark: But, recently we’ve been starting doing videos.

Paul: Right. Which is quicker, I’m guessing.

Mark: Kind of, a little, er… yeah, it is. It’s been good.

Paul: I guess, I mean, the videos, did you, so you’re talking over the top of the videos and…

Mark: No, no. I mean, it’s literally we’d… so, I’d come up to London and I’d work with Leisa in the British Museum, or whatever, and after a morning, we’d have a Flip and I’d just video the two of us talking about stuff.

Paul: See, I think that’s really good, because it makes people think twice before criticising, because there are real people behind them.

Mark: They see you as a real person. Absolutely.

Paul: So, there’s probably a benefit to that.

Mark: I think there is, I think… a lot of people hated it. And a lot of people hate the…

Paul: Yeah, but a lot of people hate everything.

Mark: Yeah [All laugh] A lot of people hated the distributed approach because they couldn’t keep track of everything, but i’s not…

Paul: Which I can kind of understand.

Mark: It’s not really their job to keep track of it, they can if they want, they know where everything is and, sorry if it’s difficult, but that’s the way it is. So, this time around we set up a bunch of Yahoo pipes, and things like that to aggregate everything from all over the place and just pop it in a WordPress blog.

Paul: Right.

Mark: That’s the approach that we’re doing for redesigning the back-end, and that’s working pretty well, because people have a framework in which to feedback, they’re not going hunting for everything all over the place.

Paul: I’m guessing that people are even more opinionated about the back-end than the front-end?

Mark: Oh, massively! A lot of people don’t really care about the drupal.org website, I mean it’s looked terrible for years and it’s not done them any harm, so a lot of people are saying like: “Well, why bother?” But Drupal’s almost, kind of, on a tipping point, I think; there’s a lot of big commercial companies using it and it’s important, but the back-end is been developed by developers for developers.

Paul: Ooh, painful.

Mark: Yeah, so to go in there and say that the user experience is broken, which is what we have said, has been interesting.

Paul: Right.

Marcus: Because they know it backwards, I guess.

Mark: Well, they know it backwards and they’re comfortable with it. THe thing with the Drupal, as a system is that you download it and you install it and then you hit this brick wall really hard and then you have to spend six months of a pretty steep learning curve to even get a rudimentary site online. And that’s, we’re trying to flatten the curve. But a lot of developers don’t really understand the need for it.

Paul: That’s developers for you!

Mark: That’s fine. [All laugh] I’m fine with that.

Paul: So, I mean, this is quite an unusual approach that you’ve taken here and it makes a lot of sense because, you know, Open Source software, it has to be an open and collaborative process and all the rest of it. Do you, would you ever do this again and if so, would you only do it with Open Source stuff, or do you think there’s a value in doing it with non-Open Source stuff?

Mark: I think there’s a value doing this with communities, where communities have a vested interest, either financially or with time spent in the community to take that community on board and redesign it for them; I think it’s pretty disrespectful. So, I think it would work for communities, you know, the social side of the web is ever increasing and I think this approach would work for the majority of that, but it takes a certain type of thick-skinned designer to take it on the chin, because it goes completely contrary to the way that designers are schooled and the way that we practice our craft every day, is that we’re the problem solvers with the years of experience and we’re the experts and here’s our solution, it doesn’t work in this sense.

Marcus: Can I ask a sales-y question?

Mark: Yeah.

Marcus: Because I don’t know how you won this work. Was that the differentiation that gave you the… this is what we’re proposing to do?

Mark: Er, yeah, I believe so, yeah. It was the kind of the loose, almost by the seat of our pants agile approach and the fact that we were not ingrained in a process and we were quite happy and willing to break it apart and completely.

Marcus: Because it’s going to take a long time, isn’t, and most clients want it, you know, can you do it in a week?

Mark: Oh yeah, the drupal.org redesign isn’t due to go live for another few months and our involvement was four months.

Marcus: Sure.

Paul: Right.

Mark: So, yeah, it takes a long time, it’s a lot of effort but, from a sales point of view, we’ve now taken on more of a, so we use to work pretty strict waterfall, like a lot of agencies did, and now we don’t, we work, I wouldn’t say we were agile because agile can be as restrictive as waterfall, just a different name. But we work a very iterative design process now and are finding that our clients are loving it because they’re getting involved right away, there’s no time wasting on functional specifications and weeks and weeks and weeks of scoping; it’s getting in and solving the problem, and from a financial and a business point of view, it’s a very scalable model, so you have x number of days at a certain price on a sprint and you can expand and contract that process according to scope and budget. It does require quite a leap of faith by the client, to say: “what, you mean you’re not giving me a fixed price?”

Paul: Yeah, that’s the hard sell.

Mark: I’m like: “No” And that is hard but I’ve found that a lot of clients you sit down and you talk them through it; they can see the advantages.

Paul: Because we’re not at that point, are we?

Marcus: Er, not with new clients. Old, you know, existing clients will accept it because they trust you, but it’s always this… I mean, I don’t know, would I… say, if I owned a business and I was going to hire someone I didn’t know, even if I could see that they’d done a lot of good work etc. etc. it would be like: “Ooh, I don’t know if I could do that” You know.

Paul: Difficult.

Mark: So, a lot, so, in those instances and there have been a few, then phasing comes into it, you know and let’s see how a few sprints go and if you like how it’s going at this price, let’s expand it out and…

Paul: Yeah.

Marcus: Interesting stuff.

Mark: So, yeah, it’s interesting.

Paul: So, you like to do things different, don’t you [all laugh] you know.

Mark: Wherever possible.

Paul: Yeah, and talking of which, you’ve just given an interesting talk about web typography that’s got a bit of a different slant on the whole subject of web typography. Talk us through a little bit, you know, give us a potted version of your talk.

Mark: A potted version is 20-25 minutes. So, this week there’s been a lot of discussion online, based on Comic Sans.

Paul: Right.

Marcus: Right.

Mark: Comic Sans is evil, apparently.

Paul: Yes.

Mark: I don’t think it is evil.

Paul: OK.

Mark: I think it’s the victim of being used in the wrong context for years and years. And I think that, so there’s also been a lot of talk about font embedding, you know people are crying out for it, it’s why sIFR exists, and all of that. The technicalities of how it’s going to work with browsers and manufacturers and the font foundries aside, is it actually a good idea?

Paul: OK. [all laugh]

Mark: And I mean that from the point that the majority, the vast majority of typefaces have been designed for a particular reason and they are primarily designed for print usage first and screen usage doesn’t get a look in beyond the preview of the screen font. Now, Georgia and Verdana and a bunch of the Microsoft ‘c’ fonts have been designed the other way around. They’ve been designed for screen first and print second. Now, we’re constrained by those typefaces and that’s actually a good thing.

Paul: Because it makes sure you’re using typefaces designed for the purpose.

Mark: It makes sure you’re using the right tool for the job. Font embeddign could be opening the floodgates to a whole world of pain, I think, in terms of type, and it’s not the designers that will be at fault, it will be, you know, the people who are going to suffer are the users of the sites.

Paul: So, is there a… I mean, surely that shouldn’t preclude font embedding, but perhaps there is an opportunity here, I don’t know, to limit font embedding to fonts that are enabled for the web, and open up a whole new business.

Mark: Could be, exactly, could be. I haven’t really thought beyond my twitchiness of this being a good idea. I haven’t really, I would like to think: “I don’t think this is good” but, I think the crux of my point is moving beyond font embedding, is to actually, the reason why fonts in other tools, which has led to the usage of Comic Sans is because the tools that people can use don’t allow them to make good design decisions.

Paul: Right. While some constraints do.

Mark: So, with some constraints and some steering, can help, so why not as designers, why don’t we get our heads together and think about how we can, kind of, scaffold that experience for people. How can we make, because every one’s a designer now.

Paul: Yes, for better or worse.

Marcus: Even me.

Paul: Yes, Anna wants to talk to you about your design for your band website, we won’t dwell on that now, in the middle of an interview.

Mark: Everybody’s a designer and everybody’s, you know, someone who uses Comic Sans because they think it’s fun and quirky is right in doing so, but what they’re not considering is their audience, and the context that it’s used and all of that. So, that’s pretty much the, my talk in 3 minutes.

Paul: The crux of the argument. I mean you did in your talk go on and discuss the role of typography more generally, which I thought was quite interesting as well, share a few of your thoughts about that.

Mark: About how I see typography as a craft and that kind of thing?

Paul: Yeah, and how it fits into the whole process and the relationship between design and content and that kind of thing.

Mark: So, it was split down into 4 really. This talk was quite good, it was quite therapeutic, in a way, because it made me really answer a lot of tough, ask a lot of tough questions of myself as to what do I think typography is, on the web, to me, what is it personally. With that is type as kind of structure, which, you know, is a lot of information architecture, really, that to me that is typography; it is type as language, how typography is married with content and how the, we’re in a world on the web where designers are designing systems for content to go into.

Paul: Yeah, template-based design.

Mark: Exactly, and they’re divorced from the content, you know, divorced from the language, in that sense, typography’s quite hard to do, good typography anyway; then there was, what else was there? Type as process, so the Jesse James Garrett’s levels of user experience, with the idea that typography in that instance is relegated to the surface plane, which is the visual plane, you know, it’s: “make this look nice” typography; to me that isn’t typography.

Paul: So, what is typography?

Mark: Typography goes deeper, typography goes deeper than how something looks, it is how information is structured, it is how information in understood, it is how words and language is conveyed.

Paul: Can you give some examples of that, because that’s quite, you know, it sounds very good, but it’s quite hard to get your head around maybe.

Mark: Yeah, OK, so it’s, what’s that quote: “You cannot not communicate”

Paul: Right.

Mark: No matter what you do, you’re saying something to somebody, so your choice of typeface says something about the words that you’re writing.

Paul: Yes, it does.

Mark: If, as a designer, you don’t know what those words are, how can you communicate the message?

Paul: Yeah, I mean it goes back to Comic Sans.

Mark: To Comic Sans, exactly, and that’s one of the difficulties, there’s been a lot of talk about art direction on the web, and I see that as the biggest barrier to art direction is that designers are divorced from the content.

Paul: I mean, this is almost quite depressing.

Mark: Yes, really I…

Paul: It’s not really happening.

Mark: Sleepless nights!

Paul: It’s not happy idea, because, I mean, fundamentally, that isn’t going to change, we’re not going to get into a situation, you know, because rightly want to be able to change and update and alter content on their own website and that makes a lot of sense, which means even if you have the content up-front, it may change further down the line. I guess maybe the tone doesn’t.

Marcus: I was going to say you’re looking at tone here.

Mark: The tone, you’re looking at branding and you’re looking at designers being involved right at the offset.

Marcus: And I think that is better now than it was even two years ago.

Mark: Oh, it is, yeah, it is, yeah, absolutely.

Marcus: I mean, we are looking now at involving copywriters, we are pulling copywriters, we’re talking to our clients about employing copywriters through us, that’s new.

Paul: And from the start of the process as well.

Mark: Yes, right. So, we’re doing the same, we’re looking at employing content strategists rather than actually writers, more from a branding perspective, because that kind of stuff, you know, doesn’t really change, depending on the words that you, the values of the client are still communicated and it’s aligning, it’s the designer’s job to align the typography, not just the font, but the way the information is structured and working with a copywriter to make sure the typeface matches the tone of voice. and all of that is a package. So, that’s what I mean about the surface plane; typography shouldn’t be relegated to: “choose a typeface and away you go”

Marcus: Yeah, I mean, that’s the big thing isn’t it, that’s for me, what I’ve taken from this is your, is the font, the typeface has to match the message, basically.

Mark: Yeah, absolutely.

Marcus: It has to fit with the branding.

Paul: OK, good stuff. I mean, that’s yeah, you’re doing some really interesting stuff. I love the way you’re pushing, kind of, what is the conceived wisdom in lots of areas, which I don’t suppose you think you’re doing, you just stumble into these things, obviously.

Mark: Yeah, I did. Getting together this talk was one thing, this talk did not pan out the way I thought it would and to question the very notion of font embedding is quite a…

Paul: Because our whole culture really is built around the idea of choice, more choice is better, but actually that’s not always the case.

Mark: Yep, so I mentioned that in my talk.

Paul: Oh, did you?

Mark: About the jam stall, have you seen this?

Paul: Yeah, yeah. That classic, tell that story, that’s a good one.

Mark: So, there’s a couple of psychologists, a few years ago did a study where they had a jam stall and they had 26 varieties of jam and nobody bought any and then they reduced the jam varieties down to six and sales increased by 10 and it’s just the choice.

Paul: You could almost be overwhelmed.

Mark: Well, yeah.

Paul: Even as a designer you can, you can open up Photoshop, look down that font list and go “crap!”

Mark: So, this is where I showed a screengrab of TinyMCE and that, out of the bag, has 82 choices for a user, so WYSIWYG isn’t great in those terms, but there’s something within there which is, as designers and the design community could build on, which is this notion of styles and how you can use the styles to create a cascade, through your typography, through your design, so we’d limit the end-user’s choices, but not in a bad way, constraints are good.

Paul: No, I mean, the way we now work, because we use our own content management system with our own adapted WYSIWYG editor it, we’ve taken a third party’s and messed it around, that basically we only allow, by default, obviosuly sometimes clients disagree, but we only allow them to mark up the content semantically, so they’re not at any stage picking fonts, because that’s the designer’s job, they’re just describing what the content is, whether it’s a heading or a sub-heading or whatever else, which, you know, obviously, you know, ensures that design style goes through, but also makes it much easier to use for the user as well, they’re not having, you know, a plethora of options and buttons to deal with, so…

Mark: But it goes beyond the web, I think, and this is what I was thinking as I was going through this, the reason why Comic Sans is all over the place is because Word makes it easy for you to make those bad design decisions, so it goes beyond that and content management systems in 10-20 year’s time could look nothing like what we’ve got now and if we don’t think very carefully about this notion of choice, then we could be in a real mess.

Paul: Yeah. Well, certainly we’ll be in a real mess anyway.

Mark: But, you know, a lot of people would push back on that and say: “What’s your problem? That’s fine. Mess is fine.” I don’t agree.

Paul: A little bit of mess is alright. No, I see where you’re coming from and, you know, I think there is a lot of value in that. I think I would personally still like to see font embedding, but I wouldn’t object to that being limited. I mean, one of the big problems to font embedding, as I understand it, and I’m not as knowledgeable on it as you, but is a licensing problem. So, if we have a new generation, I just look at the font industry, you know, the people that produce fonts and go: “Look, you’re missing a trick here, you know, you could create a whole new range of fonts, designed for screen, licensed for the web, and there we go.” So, if that’s what we end up with, I mean, that’s great.

Mark: That would be great, you know, if we got the calibre of typefaces like the new Microsoft ‘c’ fonts, and we got, you know, a library of 40 of those to use, 50, that would be awesome. If we ended up with a way of embedding up to, you know, Bitstream’s library’s what 28000 fonts, you can choose what you like, I don’t see that as…

Paul: Not so good.

Mark: Not a good thing.

Paul: I mean, even as somebody, I mean, I went to art college and, you know, obviously I had to study typography as part of that, I still feel overwhelmed. When I, I know some people absolutely love, you know, going to some of these foundries with all these different fonts and they spend hours picking through and it’s like buying shoes for, no I won’t say women because that will be sexist but, you know it’s almost like an addiction. For me, it just overwhelms me.

Mark: Yeah, no, I’m the same, I’m never, and this is one of the great things about the web is the restrictions in the typeface you can use because it makes you think more about typography beyond the font choice.

Paul: Yeah, which is only a tiny part of typography.

Mark: Exactly, and it makes you really push typography, and people are still pushing Georgia and Verdana and there’re still pushing it and they’re still making great looking sites. Font embedding can only confuse all that, unless it’s done in a pretty structured way, but like you say, the licensing is one big hurdle to get over.

Paul: Well, that was probably the most eclectic interview we’ve ever done, covering lot’s of random subjects,but very good, thank you for coming on the show, Mark.

Mark: No, thank you very much for having me.

Thanks goes to Simon Douglas for transcribing this interview.

Back to top

Listeners feedback

Storytelling

Mark from Taunton writes:

I run a rather dull corporate website for a company who builds and sells pre-fabricated timber houses. It is a competitive market and although a lot of users visit hardly anybody contacts us for a quote. To be honest, I have lost any enthusiasm for the site. Can you help!?

I could answer this question by focusing on the importance of repeat traffic on conversion rates. We could look at generating repeat traffic through the use of articles, newsletters and offers. However, we have covered nurturing repeat traffic before. Instead I want to look at the power of story telling as a way to engage with users.

Users considering purchasing high value products and services have a number of generic questions…

  • Can I work with these people?
  • Are they experts at what they produce?
  • Can I trust them?
  • Is the product or service of sufficient quality?
In short any corporate website that sells a product or service should be about the product and the people. One way of focusing on these two things is to tell the story of the product/service. In Mark’s case this would progress through the process of designing, manufacturing and building a pre-fabricated timber house. At each stage you would introduce key people involved in the process – the account manager who deals with the customer, the architect, the project manager, the builder etc. The story could even be the experience of one particular customer and so end with a testimonial from that customer. These people could be interviewed on video or profiled in the copy. Either way it gives the user the chance to see the expertise and personalities behind the business. It builds trust and demonstrates the quality of your product and people.
Finally, the story based approach helps the user imagine themselves going through the process and therefore helps them picture working with your organization.

Getting into the zone

Paul wrote a question aimed at Elliott Jay Stocks in our forum that I would like to respond to as well. Paul wrote…

As a designer, I feel times when I am very creative, others when I know an hour infront of Photoshop will be useless. So, fellow designers how do you make yourself get into the zone. I imagine this is even harder for freelancers, or maybe easier actually, as you can pick and choose hours to work.

Like most people I find it very hard to artificially force myself to be ‘in the zone’. However, I have learn’t over the years that there are some things you can do that increase the chance of it happening. These are…

  • Change your environment – If inspiration is hard to come by I often find that a change of scenery can be a massive stimulus. Go and work in a different room, a local coffee shop or even in the middle of a field. Anything to kick start your creative juices. In my younger days I was even known to work under my desk or on top of a wardrobe.
  • Use a different approach – Another similar approach to changing your environment is to change the way you are tackling the task. If you are trying to design a site in Photoshop move to pen and paper. Try designing just in black and white or reduce your design to simple boxes. Often approaching a problem from a different angle sparks inspiration.
  • Create distractions - Everybody always advices that you remove distractions to ‘get into the zone’. However, personally I find this leaves me staring at a blank page until my eyes bleed. An opposite approach that has worked for me is to actually add distraction. For example I will set an alarm for 10 minutes. After that 10 minutes I force myself to take a 2 minute break. These short spurts of creativity seem to work for me and the breaks are a frustration that make me hungry to get back to work.
  • Take a break – Proper breaks are important too. Sometimes you need to walk away from a problem before the solution comes to you. It has taken me a long time to accept that some of my best work on a problem is done when I am not consciously thinking about it. If I get stuck I find that watching some TV or going for a walk is a very effective way of putting me ‘in the zone’ when I return.
  • Go with the flow – Finally, it is important that when inspiration strikes  you run with it until it has been drained dried. Even if you find yourself in the zone at the end of the business day, do not stop working. Cancel meetings if you need to but make sure you keep going. This is the time when you need to remove distractions and just go with the flow.

Back to top

Round up of web copy posts

Our copy is probably the most important aspect of our websites and yet we give it nowhere near the prominence we do design. That has to change.

I have found myself increasingly frustrated by the lack of attention copywriting gets on the web. As a result, it is a subject I find myself constantly returning to. In fact by looking back through this sites archive I can see it is a subject I have written about regularly almost since day one.

I have continually tried to encourage others to take their copy more seriously and tried to provide basic advice about writing for the web.

I therefore it was about time I brought the best of my posts on the subject into one easy to access place. I hope you find it useful…

Effective website copy

This post is essentially a list of copywriting tips. Advice includes; avoiding jargon, keeping it short, avoid marketing talk and much more.

Managing site content

This posts asks; is a CMS really the answer to all our site management woes and why are so many organisations unhappy with the way they manage content?

Advice for CMS users

A more detailed breakdown of best practice when writing for the web. This post is an ideal guide for those who have to use content management systems regularly and contains advice not just on copywriting but accessibility too.

How much to blog?

This addresses some of the questions surrounding blogging. Questions such as, is it regularity or frequency that matters and is quality or quantity more important?

The 4 essential web writing tips

This guest post provides a professional copywriters perspective on the subject. The four tips include; write specifically for the web, break it up, make it about the reader and relax.

Copy with personality

Dovetailing nicely with my recent article about site personas this post showcases three excellent examples of copy stuffed with personality.

Your feedback?

But what about you? What are your thoughts on the state of website copy? Do you pay for a professional copywriter and if not why? Do you find website owners unwilling to invest in this area? Finally, are there some great articles that should be included in this list?

Share your thoughts in the comments.

For even more posts check out the site content section of this website.

The 4 essential web writing tips

A website without words would be like Jonathon Ross – entirely pointless and a total waste of money. So it’s crucial to get those words right.

Here are the 4 most important tips for writing good web copy.

1. Write and edit specifically for the web

Don’t lift text off a printed brochure and stick it straight on a website, especially if it’s meaningless. We call this McContent because it fills a space but ultimately doesn’t give you anything except a vague sense of unpleasantness.

Here’s an example from a holiday cottage company website:

Lose yourself. Find yourself. Discover who you are again.

I have no idea what that means, or if I need to bring towels. A better sentence might tell me why the place is so relaxing – it’s in a National Park and has a spa, if you’re interested.

How to do this: As a general rule, cut the copy in half and get rid of anything you don’t understand.

2. Break it up

Look at The Sun. It has a reading age of 12, which is what you usually need to aim for on a website. The sentences and paragraphs are short. Subheadings are used a lot. They avoid any long or difficult words (an exception being this recent headline: ‘Sex with Jordan? That is out of the equestrian.’).

How to do this: Have a look at your copy and see where you can break it. Where can you start a new sentence? Could you split that paragraph into two? Could you substitute a shorter word?

3. Try to make your copy about the reader

I think this is quite hard, because my own thoughts and opinions are so much more interesting than anyone else’s. I’m proving this point in these sentences, talking about me instead of you. A better way of putting it would be:

You might find it difficult to talk about others, instead of yourself. Your thoughts and opinions are so much more interesting than anyone else’s.

How to do this: Use the We-We monitor to see much you ramble on about yourself, and how much you talk about your customer. Then turn your ‘me’ sentences into ‘you’ sentences.

4. Relax

Chill out. Being informal is fine on the web. It’s actually easier for your reader to extract the information they need from informal copy.

Here’s copy from the O2 website:

We provide mobile, fixed and broadband services in the UK…. [blah blah] … customers know us as O2.

Compare it with this from Virgin Mobile:

As a Virgin Mobile customer, you’re entitled to a whole list of privileges and special treatment that your mates would give their right arm for.

How to do this: When you write, imagine you’re chatting to your best mate’s mum or your favourite uncle. You have to be polite still, but you don’t have to talk like a government policy statement.

About the author

Rachel has 15 years’ experience in writing and editing, and currently runs a website company with her mummy. She has won several awards for her work, although one got thrown in the bin because it didn’t go with her sofa.

164. Case Study

On this week’s show: Paul shares his experiences of working on the Wiltshire Farm Foods website, we examine the role of Twitter and Ryan Carson shares some more advice on building web applications.

Play

Download this show.

Launch our podcast player

Housekeeping

Write for Boagworld

I am constantly amazed by the intelligence of those who listen to this show. The talent and knowledge of the Boagworld community is truly staggering. If you don’t believe me spend a bit of time in the boagworld forum.

I am therefore looking to get more people involved in publishing to the Boagworld website. If you have an idea for a post that you think others will be interested in, write an outline and post it to this thread. If the idea is appropriate I will get in touch and arrange for your post to be published.

Obviously, the post will be fully credited to you and will link to your site. Hopefully that will make it a worthwhile marketing opportunity!

Back to top

News

The importance of sketchbooks

Talk to any designer and they will tell you about the importance of keeping a sketchbook. Ask that same designer whether they actually do it and the answer will probably be no.

The most common reason for not doing so is a belief that you need to be able to draw to have a sketchbook. Believe it or not most designers cannot draw. According to Jason Santa Maria’s latest post “Pretty Sketchy” that is not the case.

He argues that…

Sketchbook’s are not about being a good artist, they’re about being a good thinker.

I have to agree. However, sketchbooks have always filled me with some trepidation. Although I know they don’t need to be a work of art, I still want them to be.

That said, this post has inspired me to start keeping a sketchbook again. I know I am no longer what you would consider a designer, but Jason has made me realise that having an easily accessible place to keep ideas is worthwhile, whatever your role.

I encourage you to read Jason’s post and do the same.

Supporting old browsers

Jonathan Snook has written an interesting post about support for old browsers this week. He begins the post by establishing the importance of supporting older browsers. He writes…

When it comes to market support, I’ve often looked at it as one big pie. You may say that Opera is too small to really care about. It’s only 2%. You don’t care about Firefox 2 users. It’s only 2%. You may not care about accessibility issues. It’s only 2%. Soon enough, you’ve whittled down your potential market to 90% of what it could have been.

This is certainly a slippery slope and one that I personally take very seriously, hence my posts on Graded Browser Support.

However, as Jonathan goes on to point out, graded browser support is not without its problems. Although it is relatively easy to provide alternative basic styling to IE6 and below (thanks to conditional comments), it is much harder with earlier versions of Firefox, Opera and Safari.

Personally, I am not happy to resort to browser sniffing and I am not sure this is a massive issue. Based on stats from sites we are involved in, most users of minority browsers (Safari, Firefox and Opera) upgrade to the latest version.

In the end you can only test on so many browsers.

Approaching content on the web differently

The two articles that have most excited me this week both relate to website copy.

As we have said many times before on this show, all too often website owners are willing to invest considerable time and money in getting design right, but largely ignore their content. If you are willing to pay a designer to work on your site, you should also be willing to invest in a content strategist.

Tiffani Jones from Blue Flavour outlines the role of a content strategist in here post “Learning About Content Strategy“. When describing this emerging discipline she writes…

We kind of know that it lives somewhere between web writing, web editing, information architecture, SEO stuff, web analytics, and production.

She goes on to demonstrate that websites need somebody capable of writing good copy but also understanding SEO, wireframing, marketing and much more.

Of course, many people think they can write good copy themselves. They may infact be able to do so. However as Gerry McGovern points out in our second post about copy, good web copy writing is different from traditional writing.

Gerry argues that some of the rules of traditional writing do not apply to the web. He compares writing online copy to giving an elevator pitch…

Your customer has walked into the elevator, the doors have closed, they turn to you and say: “Convince me before the next stop to buy your product.” Design your website from the ‘I badly need to go to the toilet’ perspective. Your customer needs to act and act quickly. That’s the Web.

Setting aside the dubious toilet analogy, this is an excellent post that really makes you think about whether your copy is meeting users needs or massaging your own ego.

Improve usability through help elements

Smashing Magazine have released a helpful article on help this week.

It looks at the context sensitive help that is becoming increasingly prominent in web applications, ecommerce systems and forms. It outlines the obvious usability benefits and gives loads of examples of how context sensitive help can be implemented.

There are no major revelations in this post but it is useful to see how others have tackled this issue and to be reminded just how important help is.

It is too easy to address help as an after thought and so not properly integrate it into the design. As designers it is often not until a developer asks about error handling that we begin to start thinking about help messaging. We need to ensure it is apart of our design process and that the wording of these messages as well as their design is carefully considered.

Audible recommendation

Download a free audiobook today

This week I would like to recommend Nudge on Audible.com, a book about influencing the decisions people make. Although not directly about web design it has had a profound influence on how I build sites. If you want to influence the behaviour of users then I would highly recommend this book.

Best of all if you sign up with Audible you can get this book totally free. Simply go to www.audiblepodcast.com/boagworld and claim your free credit.

If you want to listen to it, Audible has it! With over 60,000 titles and virtually every genre, you’ll find what you’re looking for. Get a free audiobook and 14-day trial today by signing up at www.audiblepodcast.com/boagworld.

Back to top

Feature: Case Study: Wiltshire Farm Foods

One of the biggest challenges of running a successful website is balancing the needs of users with those of the business. This is especially true when an existing business model conflicts with user needs.

Read the full article

Back to top

Ryan Carson: Advice on building web apps part 2

Ryan Carson:Hey Everybody, this is Ryan Carson one of the founders of Carsonified.com today we are doing are second instalment of five minute Web App tips for Boagworld. So let’s get started, the first thing I’d say is do not build your billing system from scratch. Now, if you have a Web App that does recurring billing, so you are charging someone’s credit card every month there is quite a bit of code to write for that. When we built dropsend.com there was at least 1200 lines of php code in order to do that, and it’s a very difficult problem to solve. You have to do things like charge someone’s card if their card has been cancelled, send notifications, try to bill them again and in seven days bill them again, another seven days keep track of invoices, cancel them if they cancel their account. It is just a real headache and there is a lot of stuff that can go wrong with that. So, I would say you should outsource something like that to spreedly.com. Basically it’s an API web service that does recurring billing for you, so give it a try. I don’t work for them; I’m not being paid to say that, I just think it’s a good idea. And y’know if you ever decide to switch out of Spreedly the nice thing is that you’ll make a series of API calls out to the service and all that you’ve got to do is bill those services internally if you decide to do so later. So it’s definitely important not to waste time doing that from the beginning. Also, some people may say “Well, what about the fact they are going to take a part of your revenue?”. Well, the truth is, your bank is going to take that cut anyway, so you might as well have Spreely take that cut, there really is no loss there.

The second tip I’d like to talk about today is that you should plan on doing AB testing from the very beginning. When you do all of your site designs, especially your Home Page and your Sign Up/Payment Page, those really need to be tested with AB testing from the very beginning. Have a series of phrases or different graphics you plan on switching back and forth and make sure you measure which ones are working and increasing your paid sign ups. There is a great post on “Signal Vs Noise” about that, if you go to bit.ly/ab-test they talk about their pricing page and how they made some basic changes and they saw huge increases, 30% in sales for instance, it’s really important. On the subject of AB pricing I spoke to Jason Fried over coffee at the Future of Web Apps in Miami. I said “Can you tell me anymore about what you learned during AB testing?” and he told something really fascinating which was, When they changed the words ‘Free Trial’ (or Sign Up for free) on their Home Page to ‘See plans and pricing’, they saw an increase of 200%, so that was a real shocker. What he said was happening was that, people were afraid of signing up. Y’know they thought if they clicked on the ‘Free Sign Up’ button, then somehow they would automatically get an account that they could not get out of. Whereas if you say “Hey, Check out plans and pricing”, y’know no commitment, people are much more willing to click through and then probably
sign-up. So that was really interesting.

Okay, another tip for you is, I would suggest creating a new company for your Web App. The temptation would be to launch it as a service of your current company. So for us, when we launched Dropsend.com it was owned by Carsonified. But when we sold Dropsend it was really hard to extract out that company from Carsonified. So if we had started Dropsend Ltd. or Dropsend LLC it would have been a lot easier to do that. So I would just set up a fresh company from the beginning, it can be owned 100% by your current company which will make selling it, if you ever sell, a lot easier.

The final tip I’d like to talk about today is source control and I would highly recommend you use http://github.com it’s free, it’s a wonderful way to keep track of your repository for code and I’d highly recommend it. So, that’s it, thanks for your time today, and thanks for listening. Goodbye

Thanks goes to Ben Hardcastle for transcribing this portion of the show.

Back to top

Listeners Questions

Twitter

This week I received two excellent and related questions about the use of Twitter as a marketing tool. The first comes from Teifion who asks…

My question concerns morality and twitter, an odd combination I know. I have several bots on twitter, all day long they download RSS feeds and then tweet links to new articles. A good example would be @design_agg which reads design websites such as Boagworld, it then tweets the relevant links to the post and the post title. There are other bots like them, for example I know that @stanton maintains the @boaglinks bot.

Of course, none of these bots create content, they simply link to it. The question is, is this wrong professionally and is it wrong on a social level? For a list of the bots, just look at who @design_agg follows.

The second questions refers to another automated Twitter account…

Hello Mr Paul Boag, this is Jimmy Nightly from the Swedish online auction site jiiro.com. I’ve recently been following Amazon on Twitter and they’re using several feeds to draw traffic to current campaigns. Their feed Amazon Deals has only 8000 followers and to me it just doesn’t seem that much compaired to how big Amazon really is over here. My point is, if they only have 8000 followers do you then think Twitter is a marketing tool for the future?

Both questions revolve around the subject of automated twitter accounts. These are accounts where the posts are automatically generated rather than the thoughts of a particular individual. Our first question is concerned with their morality and the second is concerned with their effectiveness. Both valid concerns.

Let’s take each issue in turn…

The morality of automated twitter accounts

The fact that Boagworld runs an automated twitter account posting web design related links shows that I do not have a problem with their morality. However, I understand that others do. Let’s look at two potential criticisms.

  • They are not in the spirit of Twitter – Some argue that Twitter was not created as a broadcast tool and should not be used in that way. Twitter is about community not news/announcements. Although I do agree with this point to some extent (as you will hear later) I don’t think the argument ultimately stands up. Strictly speaking Twitter was created for people to post ‘what they are doing’. In reality it is rarely used in that way. Twitter has grown to be much more than originally intended and a broadcast mechanism is a part of that.
  • They steal content from others – The second concern is that they are regurgitating content created by others. They are not in themselves creating value. Again I would disagree. Their value comes in the time saved for the reader. Instead of having to manually check sources, they are presented with all they need to know in a convenient form. In my mind it is no different from an RSS feed on Delicious or the news section of this show.
  • In the end, if people do not like these ‘bots’ they can unsubscribe. However, some do find them useful and there is no reason why they should be denied their services.

    Of course, they may provide value to the subscriber, but do they provide value for the owner. Are automated twitter accounts an effective marketing tool?

    The effectiveness of automated twitter accounts

    Jimi’s question calls into doubt the effectiveness of Twitter as a marketing tool, citing the Amazon Twitter account as proof. It is remarkable that Amazon only have 8000 followers on this account but it is worth noting that their Amazon MP3 account has over 300,000.

    However, it is not the specifics of Jimi’s question that I would challenge. It is the entire premise. To me, if Twitter is used well, it can be a lot more than a marketing tool. Companies like Amazon are failing to grasp the full potential of Twitter because they are using it as a broadcast tool, rather than a way to engage with its users.

    Twitter provides a lot more than an opportunity to broadcast your latest deals. Twitter also allows…

    • An opportunity for great customer service
    • A chance to inform your new products and services
    • A way of creating passionate evangelistic users
    • Real engagement with your users

    Unfortunately using Twitter to publish automated ‘feeds’ fails to reap these benefits. It in no way engages with followers. It only broadcasts.

    Only by engaging with their followers will organisations really reap the benefits of Twitter. Companies like Zappos or Omnigroup are leading the way in this by using Twitter to provide support, inform their future products and engaging with their community.

    Back to top

    Three secrets to simplicity

    Many website owners damage their sites by continually adding features and content when they should be simplifying. In this post I reveal why that happens and how to simplify your website.

    In my post ‘5 options when website budgets get slashed‘ I explained that many organisations waste money adding ever more functionality and content to their sites when they should be simplifying. Unfortunately it is much easier to add content than take it away. But why is that?

    The 3 lures of complexity

    In ‘10 harsh truths about corporate websites‘ I outlined 3 reasons why website owners shy away from removing content…

    • A fear of missing something – By putting everything online website owners believe they are giving users easy access to everything they need to know. Unfortunately, with so much available, it is hard to find anything.
    • A fear users will not understand – Whether it is a lack of confidence in their site or their audience, many website managers feel the need to provide endless instructions to users. Unfortunately, users never read this copy.
    • A desperate desire to convince – Many website managers are desperate to sell their product or communicate their message. Text becomes bloated with sales copy that actually conveys little valuable information.

    However, I think there is more to it than that. First, there is a general laziness. It is easy to leave content online. It takes effort to remove it. Second (and more importantly) there is a desire to please users. If a user asks for a feature or piece of content, we feel obliged to provide it.

    3 questions that encourage simplicity

    Adding functionality requested by users is not always a good idea. You need to ask 3 questions…

    • How many people are asking for it? – If only a few people request a piece of functionality, there may not be the demand to justify the time and money.
    • Who is asking for it? – If it is not being requested by your primary audience then you should probably not be building it.
    • How will it affect others? – With new functionality comes complexity. Will that functionality confuse some users? Will it distract from your main call to action?

    What then do you do if your site has become overly complex? How do you achieve simplicity?

    3 steps to achieving simplicity

    According to ‘The Laws of Simplicity‘ there are three practical ways you can simplify anything, including your site. These are:

    • Remove elements
    • Hide elements
    • Shrink elements

    Let’s look at how these steps work in practice.

    1. Remove

    Headscape Website

    The first step to simplifying your site is removing unnecessary content. This is by far the hardest step for the reasons I have outlined above. However, it is necessary as Steve Krug explains in his book ‘Don’t Make Me Think.’ He identifies two benefits of removing content…

    • It reduces the noise level of your site
    • It makes the useful content more prominent

    Removing content really does make a difference. We applied these principles to our own website at headscape.co.uk and saw a significant increase in conversions (those visitors who request a quotation for our web design services) and some amazingly positive feedback on the site itself.

    In fact we took the principle so much to heart that we went from a 40+ page site down to a single page! Of course, that kind of radical approach is not for every site. However, even removing some content can make a huge difference.

    2. Hide

    Unfortunately, it is not always possible to remove as much as you wish. Sometimes you need to keep content to serve secondary audiences. That is where hiding content comes in.

    It is important to cater for secondary users, but you do not want their content to distract or confuse your main target audience. Instead of removing their content, you can hide it deeper within your site or within the interface itself.

    Menu on the Wiltshire Farm Foods website

    An example of this is a recent homepage redesign we completed for Wiltshire Farm Foods. Most of their sales come from 6 categories of meals. However, they also offer a number of other categories. On their old homepage the 6 main categories were lost among the other categories. Users felt overwhelmed by choice and sales were lost.

    One option would have been to reduce the number of categories to focus on the 6 big sellers. However, this would upset a sizeable secondary audience. So instead, we hid some of the categories under a show more link. This meant that their secondary users could still be served, without overwhelming the primary audience.

    3. Shrink

    Finally, there are occasions when content can be neither removed or hidden. This is often because the content is of critical importance to a secondary audience and needs to accessed quickly. In such cases the content can be shrunk.

    Take for example University websites. Their primary audience is almost always prospective students. However, they also cater for staff and existing students. These people need quick access to intranet tools such as the institutions address book. The solution is to add a small inconspicuous link on the homepage that takes them quickly to this content. By keeping the link small (shrunk) the site serves their needs without distracting or confusing the primary audience.

    A similar approach was used on the Wiltshire Farm Foods new homepage. However in this case the content was actually shrunk.

    Because of the elderly demographic it was important that we provided lots of help to new users. We therefore wanted to dedicate a substantial amount of homepage real estate to meet their needs as they arrived. Our solution was this…

    WFF get started guide

    Unfortunately this became distracting once the users were familiar with the site. It became a usability hurdle. One solution was to remove it. However, this would make it impossible for users to refer back to if they became stuck. The next option was to hide the content elsewhere (for example in the help section). However, previous usability studies of this demographic showed they develop ‘habits’ in the way they navigate. If we moved these links that they relied upon, it could prove confusing.

    Our final solution was to shrink the content. So instead of moving or removing it we simply collapsed it…

    WFF get started guide, collapsed

    This meant the content continued to be accessible but did not become a distraction or take up too much real estate.

    Conclusion

    Although the ideal scenario is to remove content, it is also possible to simplify in other ways.

    This should not be mistaken as an excuse to avoid removing content. However, you could use hiding and shrinking as the first step towards removing. If these techniques do not alienate your users, then it maybe appropriate to remove that content entirely.

    Whatever the case, we should all be looking for ways to improve our sites by simplifying rather than adding more and more content.

    Our First AIR App

    With Adobe AIR now up to 100 million downloads, being utilised by big name players such as the BBC and increasingly invading our desktop Headscape decided to give it a go.

    This is a guest post by two of the Headscape developers – Craig Rowe and Dave McDermid

    Setting up

    Adobe Air is Flash + WebKit + SQL Lite on the desktop. As a Flash developer you can dive right in and use the Air extension for Flash to publish your beautifully crafted swfs and AS code into an installable cross platform desktop app. However, the flash projector has been around for a while doing similar things and we wanted to put our hard earned web development skills to productive use. So we went the HTML/Javascript route.

    The SDK is free for download but Aptana provides a rather neat eclipse based IDE in which to work. Handily the new project wizard allows you to import a multitude of Javascript libraries making it incredibly easy to get a new project up and running with your preferred initial setup (we went for jQuery).

    The Problem

    To make the exercise worth while we needed a real world problem to solve. Trivial examples usually do very little other than increase your ability to copy/paste example code and do your best fireworks night ‘ooo’ ‘ahh’ impression at it. Instead, we chose to add to our server admin experience…

    As loving, caring web developers we actively monitor all our servers, and most of our live websites. For a while this was a DOS script, this was then migrated to a Bash script on a Cron job. It worked great, but required a computer science degree to maintain. So here was our problem: we needed a pretty, maintainable and reliable app to monitor websites. All it had to do was let us know when one disappears or throws a nasty error.

    Download and try our site watcher AIR application

    The Journey

    Step 1: The wireframe

    Paper Wireframe

    A new Adobe AIR project in Aptana comes with an html file named after your application which acts as your main program window. Creating a basic layout with a few buttons, titles etc can be done in a snap. The html, css and javascript are dealt with in exactly the same way as if intended to be deployed as a website (with no browser compatibility worries as we are only targeting the Adobe AIR WebKit rendering engine).

    Step 2: The magic

    The wireframe identified the main viewer as comprising of an unordered list of sites, each with their current status and edit/check/remove links. This list needed to be persisted, but editable by the user.

    If this was a website we may be looking to server side scripting and a database of some nature. However, we had only jQuery and the air libraries. Although SQL Lite was an option we decided it was an over complication for what is a relatively simple, first AIR app. So, knowing that we could use jQuery to manipulate a DOM and the air libraries to save and open local files we opted for XML as a data source.

    <?xml version="1.0" encoding="utf-8"?>
    <sites>
    <site address="http://www.headscape.co.uk/" status="200" frequency="30">
    Headscape&#146;s website
    </site>
    ...
    </sites>
    

    Looking back into our application html file we can see that we are given a readLocalfile() function that returns the string contents. This can then be passed into a jQuery object and manipulated in the usual way.

    [The canny among you will notice that this readLocalfile() function is merely a few calls to the flash filesystem classes (using the AIR aliases). In fact at some points I directly call the flash library rather than using the AIR alias. There’s no functional difference, I’m just used to the flash namespaces]

    With this ability added to the jquery ajax capabilities the application flow could be easily envisaged as follows:

    • On DOM Ready read the local xml file
    • For each site element in the xml create an LI element with the appropriate display and action elements
    • Fire off a jquery ajax call for each site
    • Use the response code to formulate a class for the LI to change its display
    • Fire off any notifications if the response code has changed i.e. e-mail, notification window, twitter post
    • Set a timeout before checking again
    • On window close parse the unordered list back into xml and write it to the persistent file

    The Stumbling Blocks

    Viewing the source of an installed AIR app can be done by nipping into program files (or Applications for the MACs amongst us) and looking in the application name directory. Here you will see the html, css and javascript files that make up the app (so we can continue to learn from others deployments just as we would with a website).

    A brief look at the sitewatcher source and the flow described above becomes immediately clear. ‘Sitewatcher.html’ is our main form and it includes script.js as the main driver of the application with the #sites ul as the main containing element. The rest is GUI. ‘PopulateUIfromXML()’ directly completes steps 1-2 and fires off the 3-6 process via ‘CheckSite()’. However dispersed within this are the unusual non-front end website development bits, so we’ll look at those now:

    Acting as a System Tray App

    Many AIR apps, particularly those to do with notification (twitter, yammer etc) seem to want to run as system tray applications, we were no different.

    The process of doing so is relatively easy, and encapsulated in the appropriately named SetUpSysTray() function of script.js. Essentially what we need to achieve is an override of the minimise behaviour, the setting of an appropriate icon and the associated window toggling behaviour.

    Window.nativeWindow gives us access to the OS window holding our html window, and we can listen to events on it in much the same way. ‘nwMinimized’ is set to fire on display state changing and, if being minimized, instead docks (hides) the window and prevents the default behaviour.

    if(air.NativeApplication.supportsSystemTrayIcon)
    window.nativeWindow.addEventListener(runtime.flash.events.NativeWindowDisplayStateEvent.DISPLAY_STATE_CHANGING, nwMinimized);
    function nwMinimized(nativeWindowDisplayStateEvent) {
    if(nativeWindowDisplayStateEvent.afterDisplayState == runtime.flash.display.NativeWindowDisplayState.MINIMIZED) {
    nativeWindowDisplayStateEvent.preventDefault();
    Dock();
    }
    }
    function Dock() {
    window.nativeWindow.visible = !window.nativeWindow.visible;
    }
    

    This works fine but on its own will actually just hide the window from view/the taskbar leading the user to have to use task manager to close it. To ensure that an icon for your application sits in the system tray we need to set an icon for the nativeApplication (the mere presence of which will cause windows to display the app in the systray).

    Back to SetUpSysTray() and we’re using a content loader to load the icon graphic into memory, with an iconLoadComplete handler waiting to do the work:

    var iconLoader = new runtime.flash.display.Loader();
    iconLoader.contentLoaderInfo.addEventListener(air.Event.COMPLETE, iconLoadComplete);
    iconLoader.load(new air.URLRequest("../icons/AIRApp_16.png"));
    function iconLoadComplete(event){
    if(air.NativeApplication.supportsSystemTrayIcon){
    air.NativeApplication.nativeApplication.icon.bitmaps = new Array(event.target.content.bitmapData);
    air.NativeApplication.nativeApplication.icon.tooltip = "SiteWatcher";
    air.NativeApplication.nativeApplication.icon.menu = new air.NativeMenu();
    // Create Menu Items
    var openCommand = new air.NativeMenuItem("Toggle");
    openCommand.addEventListener(air.Event.SELECT,function(event){
    Dock();
    });
    var sep = new air.NativeMenuItem("", true);
    var exitCommand = new air.NativeMenuItem("Exit");
    exitCommand.addEventListener(air.Event.SELECT,function(event){
    air.NativeApplication.nativeApplication.exit();
    });
    // Add Items to menu
    air.NativeApplication.nativeApplication.icon.menu.addItem(openCommand);
    air.NativeApplication.nativeApplication.icon.menu.addItem(sep);
    air.NativeApplication.nativeApplication.icon.menu.addItem(exitCommand);
    }
    }

    We simply set the native application icon to be the bitmap data before finalising the sys tray setup by creating a menu to appear on click.

    Note for MACs: The minimised event listener is not applied if the system does not support system tray icons. This is to avoid confusion on MACs where a minimise goes to the MAC dock anyway.

    Notification Windows

    So the app can now run in the system tray and use jQuery to check the sites listed in an XML file at regular intervals. However we need a process of notification. The App could be running on an actively used machine in which case we want messenger style pop-ups. Or it could be running on a separate machine/server from where we want it to send e-mail/other notifications.

    In the case of window notifications we took a short cut and used some example code from Adobe Developer Center. This is encapsulated within the DisplayManager.js and Message.js files. Display Manager acts as a queue, dequeuing and displaying on a timed basis if the user is present. This is an important requirement as you do not want a user missing a notification prompt merely because they were away from their desk for a while. It can be easily achieved via the USER_IDLE and USER_PRESENT air events – in this case stopping and starting the poller.

    ‘CheckSite()’ simply queues message HTML when the response code received is different from the previously stored code. When the queue poller is running (the user is present) the message is dequeued and displayed via Message.js.

    At this point it is worth remembering that notification windows are no different to any other native window. It’s just a name we’re giving to the way we are using native windows. They therefore have their own events, contents, position etc and this can be seen by the Message.js code where a new chromeless, transparent native window is created and its contents loaded from the message.html template.

    The display process is then as follows:

    • Message.js stores the message content in a variable on the new window
    • MessageScripts.js, then running once the message.html dom is ready, sets a listener on the HTML_BOUNDS_CHANGE event before setting the message variable content as the body – ultimately firing the bounds change event
    • This event is handled by setting the native window height to match before firing the layoutComplete event
    • On hearing this Message.js makes the window visible, finds an appropriate resting position (in relation to any other messages) and animates it in.
    E-mailing

    A key feature of any site watcher is to let us know when something bad happens. The combination of emails and an email-to-text service allows us to be notified the minute we spot trouble. This was easy enough in the bash script, using sendmail on the Mac. Not so straight forward for an AIR app. We can’t run sys commands and there is no built-in SMTP server. The solution is to use sockets in AIR. A little hardcore, but it keeps the solution nice and tight.

    Anyone who’s sent an email with telnet will know that the principle of SMTP is, as the acronym suggests, simple. Adobe gives us plenty of clues for opening sockets and listening for messages. All we had to do was make sure we sent the right info. There are some restrictions in opening sockets from scripts outside the application sandbox, but for our purposes it worked a treat. With a little trial and error we were firing off emails left right and centre.

    The icing on the cake was adding twitter support. With a one-line AJAX call in JQuery and a little config it was a no-brainer. This allows us to keep an online audit in the form of a private tweet stream. For people who check twitter more frequently than their email, it’s handy for notifications. If Twitter let us UK folk receive updates via SMS again then we can ditch email-to-text in favour of Twitter.

    Step 3: The makeover

    One of the nice benefits to working in the web-kit world is being able to use some CSS3 styling such as rounded corners. So we went to town. The more design that is CSS based and the less that is image based the better.

    JQuery UI allowed us to make the entire list sortable in a sweep of the mouse, and the prefs popup tabbed in a blink (suddenly there was heaps to customise!).

    The End

    Hopefully this post has given you an understanding of how quick and easy it really is to make a useful AIR application. We’ve shown how you can implement a system tray application that utilises notification popup windows and sends e-mails as well as uses local files as a data store. This is not intended as a best practice discussion. It was our first AIR app and developed in a very small amount of time as a proof of concept and so that we could share our experiences with you. We welcome any feedback.

    Download and try our site watcher AIR application

    152. War?

    On this week’s show: Daniel Burka and Joe Stump from Digg discuss the supposed war between designers and developers. Paul talks about using twitter effectively and we ask ‘are you placing too much emphasis on your homepage?’

    Play

    Download this show.

    Launch our podcast player

    News and events

    How to film video case studies

    Increasingly your web strategy is about more than a website full of pretty pictures and well written copy. Video in particular is playing an increasing role, whether it is embedded in your website or shared via YouTube.

    Video can be used in all kinds of ways from product demonstrations to viral marketing. However, a growing use for video is customer case studies.

    This week 37 Signals have published a fascinating insight into how they created their customer case studies for Highrise. The article covers everything from…

    • How they chose who to interview
    • The way they shot the videos
    • What questions they asked
    • How they conducted the interviews
    • How they edited the videos
    • The time they spent preparing the whole thing

    There is little written about producing quality videos and even less about customer case studies. Without a doubt these kinds of videos are extremely powerful and so it is great to read quality advice about their production.

    Effective communication in web design

    Smashing Magazine has posted an excellent article that I would highly recommend to all website owners. No, it is not my excellent Twitter article that I will cover later. It is actually an article entitled – Clear And Effective Communication In Web Design.

    In essence it talks about how to communicate on the web through both copy and visuals. It is a comprehensive overview (if somewhat superficial) of all the key considerations of communicating effectively through your website.

    The article focuses primarily on your website, largely ignoring broader communication issues. However it does tackle…

    • The different methods of communication – Images, text, titles, icons, design styling, colour, audio and visuals.
    • The challenges of clearly communicating – This includes the curse of too much copy, the need for personality and much more.
    • What you should be communicating – Your company vision, the websites offerings, the benefits to your users and calls to action.

    It also nicely demonstrates how the design and copy work together to communicate your message. This is something I will be discussing with Jeffrey Zeldman in an upcoming show.

    Do we place too much emphasis on the homepage?

    Following on nicely from my recent post about where we invest our money, Christian Watson recently wrote about one of his clients who requested a homepage redesign.

    In the article he writes…

    Sure, I could refresh the colors and move some content around. But is this a good use of my time and her money when the home page represents 20-25% of page views?

    It is a good question. Christian goes on to argue that we often place far too much emphasis on the homepage and that in fact it is little more than a gateway page to direct users to more important content.

    He uses a nice analogy borrowed from Jared Spool. He compares the homepage with a hotel lobby…

    When visitors arrive at your hotel, certainly they should find that the lobby represents the hotel favorably. It should be attractive, spacious, with elegant lighting, welcoming colors, and the odd feature here and there.

    The lobby should make it easy for the visitor to orient themselves — to see where the front desk is and where the lifts are. It should make it easy for the guest to find out any important information at a glance — upcoming events or where the conference is being held.

    However, hotels are ultimately judged by the quality of their rooms.

    It is an excellent post that provides real food for thought.

    Back to top

    Interview: Joe Stump & Daniel Burka on War Between Designers & Developers?

    Paul: So I am really excited to have joining me today Daniel Burka and Joe Stump from Digg. Hello Guys

    Daniel: Hello

    Joe: Hey hey

    Paul: I have had both of you on the show individually and Joe you were on not long ago were you really…

    Joe: ermhh yes a couple of months ago maybe

    Paul: What can I say, we cannot survive without you. So erm but I though lets bring the two of these wonderful people together and talk about designer,developer relationships and how the two of them get on together working at Digg. I mean I have to say this is just a rip off really isn’t it, it’s a rip of a panel you did. Was that Future of Web Design (FOWD) you did that panel?.

    Daniel: Yes it was Future of Web Design in New York. I think we are rehashing the panel at South By South West (SXSW) this year so if anyone is there it would be awesome if you dropped by.

    Paul: Excellent, I need to persuade you two to come along to the SXSW live Boagworld as well, but I will hassle of of air so that you can back out if you want to without committing yourself live in a interview.(Paul laughs). OK so lets kick off by talking about the designer and developer relationship and really I think that it strikes me there is a lot of mythology around this that you know designers and developers hate one another and I am not convinced it actually works like that in practice. When you guys did your panel at FOWD you actually were agreeing on a lot of points so I though we would start of by maybe highlighting some of the differences and then look at ways of working together er mm further down the line so lets talk about to begin with what you guys see as the main differences in outlook I guess between designers and developers. How do you look at the world in different ways, do you think? Maybe Joe do you want to kick us off. How do you think developers see the world differently to designers?.

    Joe: Sure I think erh developers are definitely, their default kind of response erm is that they would rather, I always make the joke that coders by default are lazy, good coders are extremely lazy people that’s why they’re good coders because they want to automate as much of their lives as possible. Ermm so I think that erm developers tend to get a little complacent when it comes to the actual erm product sometimes because they are so busy and so interested in and so worried about the actual code or the more nerdy side of things you know like are we running the latest greatest versions of different softwares. Developers also tend to be a lot more interested in what the new hip nerdness is as opposed to what’s actually going to make the product better for users, you know so like I have been in product review meetings where people are like “well Why isn’t this new version of some strange bizarre open web specification that nobody has ever heard of ahead of some major forward user feature” . (laughs)

    Paul: (laughs)

    Joe: So ermm I think that that tends to be like a big difference. The designers you know it is their job to be curators of the website in my opinion and kind of move the user experience forward and often times developers don’t have a whole lot of interest in that. (laughs)

    Daniel: On the flip side of that if we are both going to slag our own professions ermm I think designers are often you know pushing unrealistic goals. They are interested in building you know the perfect product and you know aiming straight for that instead of looking pragmatically at doing things in steps and figuring out what is technically possible and I think there is also a gap where designers can only see sometimes what features that they can view and don’t understand, don’t see the vision, of where developers can see you know amazing things they can you know do pro grammatically that designers just aren’t envisioning.

    Paul: Yeah

    Joe: I think that’s er is another key difference that I know that there is a lot of, there have been struggles and tensions between Daniel and I in the past over this idea of a holistic approach to design where where Daniel designs his vision and his vision is normally version 10.0 and I am looking at you know the technical roadmap and things that I need to do and like I am OK well lets talk about version 1.0 and then we can start talking about 2.0 like, developers are much more focused on an iterative process as far as releasing, you know like small chunks, reducing risk etc. etc. and designers tend to kind of like go well erm you know it is like I wanna build a pyramid it’s like great well how about first we start out by finding some limestone and then we work our way up to building a pyramid.

    Daniel: So what you are saying is we have got a fantastic optimism. (laughing)

    Joe: Yes

    Daniel: But I think that’s partly it. Developers are very interested, as Joe was saying,in mitigating risk and in a lot of ways designers are very adverse to even thinking about risk and want to think about opportunity. So I think this is kind of the crux of the whole thing and what we are trying to talk about on that panel is that both of those views are super valuable and if you manage to find the right mix of those two things then you can develop a fantastic product that is both concerned about risk and pushes the boundaries of what is possible.

    Paul: Mmmm I remember one point that came out from the presentation which is one that you made erm Joe which is about the dangers of if that mix is not right. It is always the designer that’s in front of the client or the boss or whatever ermm the kind of realism of the developer is kind of left out of the process and ideally the developer either needs to be involved in those kind of meetings or there needs to be a conversation that happens between the designer and the developer before anything is ever presented. Is that kind of, do you still feel like that is that still a valid point?.

    Joe: Yeah, I feel that is a extremely valid point for two reasons erm and this is a discussion that Daniel and I just had yesterday in fact. The thing is as a developer the reason I want to be involved early on in the development or in the design and like development of the product phase you know when requirements are coming together and when you know the first kind of formations come out of the clays so to speak is because two reasons. One ermm and they all kind of come back to this same kind of problem, is that the designers and the product people don’t know the system, the actual bits and bytes that like you know go into making the product, as well as the developer like the data and the code and the actual systems and stuff like that and how they are put together. So Often times two things happen Daniel comes up with a design and there is like one small minute detail on the page that would require you know one of the largest computer farms in the world to calculate in real time. Whereas in lots and just as often as you know that happens where it is like Daniel I can’t calculate that number in any meaningful way on a regular basis so you gotta remove that. But just as often as that happens because of you know as a developer I have such like intrinsic knowledge of the relationships in the data and what data we are storing and stuff like that just as often I am like well why don’t we expose this data or do this and Daniel is like I did not know we could do that actually I totally would have done that if I had known that that was possible or feasible.

    Daniel: Yeah and that’s, especially that side of things designers often hear the first part Joe is talking about, the you know well that is just not possible or more difficult than you think. Any designer that has worked with a developer has heard that aspect of it you know and that is of course very valuable but it is the other side of things that I think people fail to leverage most frequently is the ability of developers to see different patterns than you in the data and come up with those suggestions, you know it might still be your call whether or not that is a valuable thing for the user but just hearing these ideas coming out is is amazingly valuable. That has shaped a lot of Digg.

    Paul: So would you say that is a kind of you know a common mistake that maybe designers make with developers that they don’t communicate enough with them ermm

    Daniel: Absolutely

    Paul: yeah

    Daniel: Designers often see developers as mules its like I made this thing go build it and that is a bullshit attitude, its terrible.

    Paul: mmmm what …

    Daniel: Its not just designers either all product people have a tendency to do that. In some ways, as Joe was talking about developers being involved in the process, at Digg we’ve got a pretty good structure where design actually falls under the marketing team and in some ways I see design as a bridge between marketing and business development you know product interests and the development team. Because I am often sitting over here and I hear you know someone from business development or marketing throwing around an idea and I am like “I’m no developer but I have a good sense of what the developer sees as important and you’re talking crazy talk like that is going to be nuts” and they are about to go and pitch that to a potential partner and you know like every week I put the brakes on from that kind of thing I am like listen you need to talk to Joe you need to talk to a developer because that what you are talking about is going to be months of development and you are promising it to a partner in two weeks that’s nuts and so I like that in you in some ways the design team can often be a bridge between product marketing people and the technical teams.

    Paul: Joe from your perspective what kind of, you know as your communicating with Daniel and other designers within digg looking back where do you think you’ve made mistakes in your relationship with designers?.

    Joe: Ermm I mean the mistakes that I often make ,its a not even a mistake are I don’t wanna say are what we do are like flat out mistakes it’s just more ermm you know being a bit more reserved and not necessarily defaulting your answer to no. Err You know I think that Daniel often talks about how a natural tension between design and product and development is actually good for the product because you have eventually, as long as you can keep that at a good tension and not you know bad or where things are breaking but ermm I think often times developers are quick to say no. You know they will be sitting in a meeting and it is just immediately no I am not going to discuss that when in reality if they sat back and let the idea germinate you know they would, Its kinda weird because I have in a lot of meetings where things were, where the developers were like be oh my god that is an amazing product but we will never be able to build it and so it is like they want to build it but their default is to avoid risk so they say no. So a lot of the times when I talk with Daniel now and this is something I like quit doing I try not to say no unless it is just like blatantly in black and white no way that is possible kind of thing. I might let the idea germinate more I might no say no immediately I might want to go back and spend a couple of hours thinking about it if it is actually feasible because maybe you know. That’s what engineers love doing they love solving difficult problems and if you are saying no to difficult problems then you are failing at what your passion and hobby is. Ermm so I think that ..

    Paul: There is also an aspect is there not of not just saying no but explaining why you are saying no so that the other party is kind of educated into the kind of problems you face so as Daniel said earlier that they can be the bridge to you know business development or whoever else.

    Joe: Yeah absolutely, I am the king of analogies at this point ermm but the other thing that developers erhh, this is extremely common that they utterly fail at is that they think for some reason that they are like the target demographic of the product so they will come into a meeting and say this product will absolutely fail because it doesn’t have key binding so I can keyboard shortcuts it’s like nobody uses keyboard shortcuts like in the real world, they are all mice people like you know. It is stuff like that that a lot of the time developers are like “this will never work unless you have least 14 completely nerdy niche features in it” you know and I think developers too often you know they do that and that is just silly.

    Daniel: Hey guys that’s been a special problem at digg,since we started of as the pure technology side so it was seen as by developers for developers and you know we have obviously branched out from there and now we have got other interests I want to make sure peoples mums can use the website and that’s you know certainly a , you make different choices based on that.

    Paul: I mean it is very timely from my point of view to have this interview with you because on Friday we had a internal meeting in Headscape where we talked about all kinds of production things and one of the things that came out of the development team was this desire to be involved in the process more and err to have their say more and just to be included earlier. So I am quite interested in you know because obviously you guys have been working together for a long time what kind of practical advise would you give to a , maybe this is just a question for me and not for anyone else, but what kind of practical advise would you give for designers and developers working together within the organisation. How can that relationship work better?

    Daniel: Yeah, absolutely involving your development team earlier in the process but that doesn’t necessarily mean sitting around brainstorming right at the beginning of a feature with them. I mean I try to sit down work out an idea get it 20% of the way there, you know work out some of the basic issues figure out what this thing really means what’s at the core of it you know it might be ten different features together but what are we actually trying to achieve with it right so at least get that far even throw down so basic wire frames or some really basic comps and then present it to the developers its like listen this isn’t just an idea I came up with you know last night I just want to spill my entire brain out in front of you it is something at least I have thought through you know I have put a few things through my brain and now here is this totally unformed, not totally unformed, slightly formed idea but it is not baked you know don’t wait until you have got it baked and then you are so disappointed when the development team says well that’s not possible or have you really though about this and you have got this complete package already made up in your mind but come to them with a least you know the kernel of the thought out idea and get them to poke holes in it. Get them to push it in other directions and show you what else you could be doing and then go back to the drawing board again.

    Paul: What about from your point of view Joe?

    Joe: Well yeah, So ermm I agree with Daniel in some sense on that I think it is crucial to before you take it to developers to formulate a cohesive problem or hypotheses. Like if you come to the developers with a half baked problem that you are trying to solve you are going to get like, they are just going to run wild with it and it is like you know difficult sometimes to keep developers focused when they get excited about a problem. So have a formulated problem that you know you have a small idea of how you are going to fix but not fully baked. The other thing too and this goes on both sides of the aisle it shouldn’t be get developers plural involved and it shouldn’t be get. like a lot when you are first germinating that idea and you haven’t really moved it forward start small and then continuously expose it to more and more people errmh because I find if you involve too many people early on in a the process whether it is designers, developers, product people things tend to , you tend to loose focus quickly and everyone wants you know it’s kind of like port barrel spending and major bills its like everyone wants to piggy back extra features and stuff and pet projects that they have wanted for so long into like some major new feature.

    Daniel: It is just simple death by committee

    Joe: Right

    Paul: Yeah Yeah OK That’s interesting a little random question I remember going to a talk once where, and I can’t remember who it was who was giving it, where they suggested that errmh designers and developers swapped roles for a while. Where you try and sit in the other persons shoes and I was just interested whether you two had tried anything like that?

    Joe: That would be disastrous for me. (laughs)

    Daniel: I I mean I appreciate development roles and I am you know somewhat technical for a designer but yeah I know I have never done that but I have always worked so closely with the development team like at silverorange where I worked previously to digg there was only ten of us and I sat in a room with developers all the time. I worked in their code with them and worked on problems as a group so I think I, you know I have never worked in a place like say you worked in a big enterprise and your in this classic where designers are in one office and developers are in the other office and you toss stuff over the wall yes then I think that would hold value at least go and sit in the other office, go work in the other office for a few months just hear the other discussions that are going on because there are a totally different set of concerns a totally different set of values than what you are doing and if you don’t at least appreciate and understand that, and not just understand it so you know what you are fighting against but understand it to know what is important and how you can work with it then you know you would be really missing out.

    Joe: I think I am ermhh I think I am kind of spoiled at Digg because you know I work with two of the webs brightest, you know Daniel and Mark Trammell as well so I actually push back on my developers pretty frequently where they you know we will leave a meeting and they are like I really really completely disagree with what Daniel or Mark are doing with the design and you know I tell them all the time like look you are not a designer and you definitely not at the level that those two are at and you sometimes have to defer to them and trust that they are doing their job and they are doing it well you know and ermhh I think developers don’t do that often enough they make these assumptions that you know the arty-farty designers are doing stupid shit again and that’s not the case. I mean they would not be especially where we are at at Digg and what not I mean Digg is able to be very picky with who they bring on and the people Daniel has brought in to design are extremely competent at what they do err so I am probably not qualified to answer that question because I am so spoiled at Digg but that is a common problem I see from developers where ermhh they don’t let the designers do their job and they try and be designers when in reality you know they do not have the experience or the expertise so.

    Paul: Lets talk about conflict resolutions, sounds very grandiose but basically you know how do you go around resolving a situation where you know OK you kind of respect each others skills and you respect each others competencies but you know where some feature is suggested by Daniel and you know and you Daniel from your point of view it is absolutely core to what you are trying to achieve you know it is extremely important and then from a technical angle Joe it just seems incredibly complex and very very difficult. How is the eventual decision made as to whether that feature should be implemented and in what way it is implemented? How do you go about resolving that difference?.

    Joe: Ermhh Well I mean I think as far as making the decision whether or not the feature makes it in, because there is actually two possibilities when it comes to the conflict resolution. Whether or not a feature actually makes it into the product and in what capacity does that feature make it into the product and I think in the former whether or not the feature actually makes into the product if Daniel comes to me and he’s resolute like this feature has to be in the product the feature is going to be in product. I am always going to defer to Daniel on on, if he feels that strongly and is that passionate about it you know and it is not something completely hare-brained like I want magic ponies to come flying out of the screen I am going to defer to his expertise on the fact that feature needs to be in the product. Where the conflict resolution comes into it is what capacity is that feature going to come into the product like a perfect example of I think of something where there has been we have had a recent discussion at Digg and where this has happened we have, and I talked about this probably in our last talk but, there are these little green badges on the digg buttons and they indicate one of your friends has dugg that story and when you hover over the digg button it shows like a little sample of the people that have dugg it. Ermhh So those were causing significant strain and problems with our systems and our code and on our databases so I came to Daniel and of course again as my risk aversion developer brain was coming to Daniel I was like Can we axe this feature until we can figure out how to like fix it. He was like “No” that feature cannot absolutely be axed and then we came to a resolution which was a short term solution until we can get a better solution in place where operations now have knobs they can dial down so the green badges don’t show up on stories older than 48hrs, they don’t show up on stories that have more than say 5 or 600 diggs and stuff like that. So the conflict resolution came in basically making trade-offs in how that feature is surfaced in works ermhh at our scale more often than not what that means is that Daniel has to give up the notion that everything is in real time. The feature will work it is just that it may take you know thirty seconds to a minute for an action to be distributed across the entire system, that is probably more how things are now at Digg so.

    Paul: What about from your point Daniel, when do you back down over something and when do you keep pushing on it? How do you decide you know how serious Joe is about something and whether you should keep pushing or not?

    Daniel: Right I mean it kind of comes down to you know when I am looking at the product I am not thinking of any one feature, I am thinking about the whole set and I want it all to work together and so you know I know I want to push out six different features this month and if I push and push Joe to do the one really hard one well that is going to affect the other five I wanted to get done. So any feature is tied to other features and it is also based on a time line if I want something done in a certain time line and that’s just not possible well then I have to start making compromises so you know you have to be realistic and then at the same time you have to realise developers work well with shame and so if you tell a developer well I bet a good developer could do that (All laugh) they will go back to their cube grumbling at you and figure out a more efficient way to do it.

    Paul: OK. So now we are getting into the realms of how to manipulate each other.

    Daniel: Absolutely.

    Joe: That’s definitely err one that I agree does work but is not a trick you want to pull out of your bag too often.

    Daniel: No it is the same with designers too, it is like I want to do this really complex thing, no way I can explain that to users in a way they will understand. “I thought you were good” arhh shit I will go back and try that again.

    Paul: That is quite interesting what you just said there because so far we have talked very much about you know designers initiating features and that kind of stuff I mean are there situations where the developer is the one initiating features you know just said there a developer wanted to do something really cool and you said you couldn’t explain it. Does it run that way as well? or is it always the designer who drives first?.

    Daniel: No Absolutely that happens at Digg, it happens sometimes at Digg so Joe yesterday sent me an email that had two big feature ideas in it. They may not be things we implement this month but maybe later on this year. I was looking at them and you know it is easy to disregard well he is a developer he does not understand what’s going on with the product but you look at the ideas and they are strong and they fit in with what we are doing and now I am trying to figure out you know how they make sense in the big picture I guess. So we have got a brilliant development team a lot of people over there with great ideas and we try to sit down, you know I guess Kevin has been doing those where we do meetings once a month I guess where developers if they have been working on a side project you know something they have always wanted to build into Digg they can present this at the Digg ideas meeting.

    Paul: Ah OK

    Daniel: A bunch of those products will make it into the full Digg I mean its awesome these brilliant people go and throw around crazy ideas and show you what is possible.

    Joe: I think err yeah I mean I agree with that you definitely have, it is a two way street erm largely stuff comes from product at this point the Digg ideas meetings is definitely helping that you know open that up and kind of what I would call level that playing field a bit. But one of the things I think developers are in a in a unique position just like Daniel I work with people across the entire companies so I know initiatives that are going on in marketing I know initiatives that are going on in PR and biz dev etc. and you know if nothing else developers are very good about noticing and pointing out and discovering patterns and err a recent product that made it out that err was a developer initiated product was Digg dialogue because basically I noticed this common pattern where business development and Marketing and PR were setting up interviews and then like reaching out to people to like conduct interviews using the Digg engine kind of thing and I was why don’t we bake this into like a cohesive feature that’s turnkey because you know business development like Daniel was saying earlier lots of times they are just making these one off deals you know and they don’t really recognise when there is a product to be had there erm so that is another one that recently went out. It was like I recognised a pattern and baked this into something cohesive and move it forward.

    Daniel: That is a good example of where we are being lazy some people want to do this one off thing over and over again and it is a bunch of work to don it each time well like we will just build a system to do it and we won’t have to do all the work every time. It was great.

    Paul: OK that is really good lets leave then with one final question or one thing from each of you. Which is if you could give you know one piece of advice to either designers or developers on how to kind of interact with their counterpart what would that one piece of advice be?. Lets kick of with you Daniel what would be your one piece of advice to designers about dealing with developers?.

    Daniel: My one piece of advice would be to see the big picture, you know aim for version 10 like we were talking about earlier and know what you want to build in the future but be realistic enough to back it up and build it in stages. You know waiting and building a feature over six months and eventually launching it is a terrible way to develop and it’s a terrible way to design having an idea of where you want to be in six months but realising in one month increments is so much better you’ll end up in a different place but at least you know where you are heading and you can adjust that goal as you go forward

    Paul: Yeah. Brilliant. Joe what about you?

    Joe: Ermhh I would say to the developers out there that there is different shades of no ermhh that you know there is the, the default should not always be no and remember what I said about the conflict resolution you should be deferring to the people that are experts in their field by default for the most part and to work on compromise in how the feature operates and make your concessions and have them make their concessions rather than just defaulting to saying no to the entire feature.

    Daniel: And as a developer push to be involved early in the process, even at Digg we struggle with that a lot and as a designer I appreciate when developers want to be involved I want to hear their opinions you know it is fun to have them involved I hear all kinds of crazy stuff I never even considered that’s awesome.

    Paul: Excellent. Thank you so much guys that was really good I appreciate you coming back on the show yet again. It was really good to get your perspectives together on that relationship because it is one a lot of people struggle with. So it is good to hear that it can work most of the time. Thanks for your time

    Daniel: Thanks for having us on Paul

    Joe: Bye

    Thanks goes to Shaun Hare for transcribing this interview.

    Back to top

    Listeners feedback:

    With everybody from Britney to Obama now on Twitter it is safe to say the social networking platform has gone mainstream. But what does this mean for the service and how can we as website owners use it? Read More