RSS
 

Archive for the ‘Google Reader’ Category

Endurance Exercise Has Stem Cells Make Bone over Fat

02 Sep

Hi. I’m running. I’m also telling some of my stem cells what to do right now. Well, I probably am, based on a new study with mice.

We have what are called mesenchymal stem cells. This type of stem cell goes on to become either fat or bone. Researchers found out that endurance exercise triggers the stem cells to preferentially mature into bone. And having more bone cells means improved blood production, which means a higher oxygen carrying capacity, and better immune reaction and better wound clotting. The research appears in the Journal of the Federation of American Societies for Experimental Biolog y, commonly known as the FASEB Journal . [J. M. Baker, Michael De Lisio and Gianni Parise, " Endurance exercise training promotes medullary hematopoiesis "]

[More]
 
 

52 Types of Blog Posts that Are Proven to Work

02 Sep

This guest post is by Karol K of Online Business Design blog.

Blogging is not only about putting together 400-2,000 words of text and publishing them on your WordPress site. As a blogger, you can choose from a much bigger variety of possible blog post types (and content in general).

Let me be honest and admit that I’ve wanted to compile this sort of list for a long time. Coming up with new ideas for posts every couple of days might lead you to a hard stop on a brick wall very quickly… I believe writer’s block is the more politically correct name for such a situation.

One of the most effective ways of fighting writer’s block is having a big resource file, containing lots of ideas and frameworks for new posts. Besides, writing standard, old-school blog posts can get boring very quickly. That’s why every blogger needs some variety in terms of content if they want to be doing this for a longer period of time.

This list is divided into a couple of sections depending on the purpose and characteristics of each content type. Feel free to treat it as a resource file ≠ñ you don’t have to go through the whole list at once.

Article style posts (aka standard blog posts)

1. How-to/tutorial posts

This is one of the most popular post types and one that arguably brings the most value to the reader. The most important thing to focus on while writing it, is to give some specific information on how to do/perform/attain/reach whatever is promised in the title of the post. Videos and images work very well as additional resources for how-to posts.

2. News posts

Typically used by bigger blogs, leaders in a given field that have their finger on the pulse at all times. They are usually short (less than 500 words) and share an important piece of news in a given market. There are a couple of downsides if you want to make them an important part of your publishing schedule: you have to be fast (there’s nothing worse than yesterday’s news), news has a short expiration date (it’s hard to turn a news post into a piece of evergreen content), and finally, you have to be publishing them at least once a day.

3. Definition posts

A.k.a. Wikipedia-style post. What you basically do is choose a term that has a significant importance in your field and define it using simple language, so the term is easy to understand for someone who’s new to the topic.

4. Standard list posts

List post is one of the most popular post types in use today (you’re reading one right now). The basic idea is that you take a topic or a problem and you try to come up with a number of separate solutions to it. List posts are so popular because they are extremely easy to follow. Each point is usually not related to the other ones, which means that even a distracted mind can get a lot of value from the whole post. List posts are also great for bookmarking or sharing with friends—precisely because of their reader-friendly construction.

5. Resource/link list posts

Very similar to standard list posts. The difference is that now you’re not coming up with the content on your own, but searching for valuable information elsewhere and, in the end, sharing links to what you have found. This type of list post is very popular lately and many successful bloggers are using it as one of the most important elements of their publishing schedule. This kind of posts tend to get a lot of backlinks due to the fact that people who have been featured often like to let their readers know about that fact, so they go ahead and mention it on their blogs.

6. Profile posts

A profile is a post focusing on a specific person, usually someone famous or important in a given field. Profiles usually cover things like: why the person in question became famous, what’s so special about them, what they have accomplished, and what’s their history and background. There are no specific rules of creating a good profile post. You have to choose your target, find as much interesting information about them as you can, and combine it into an article.

7. Case studies

Case studies present a way of solving a problem based on a real-life example. They are usually constructed in a step-by-step manner presenting each step in a detailed way, and explaining why this specific solution has been chosen. Case studies usually end with a roundup of everything that has been done and present the final results.

8. Problems-and-solutions posts

This is similar post type to case studies, only here, the solution doesn’t have to be one that has already been applied. It can be a description of a theoretical solution to a problem, or an idea worth considering for other people struggling with the same problem. For example, let’s look at amateur bodybuilding as a topic. One of the most common problems in that field is gaining lean (fat-free) body mass. A bodybuilder-blogger might create a post targeting this specific problem by giving a number of possible solutions, like introducing a special diet, different workout regime, different hours of sleep, and so on.

9. Comparison posts

Every field has some specific characteristics or problems that can be solved by many different means. Comparison posts take two or more possible solutions and compare them to one another. Various aspects of these solutions need to be taken into account if the whole post is to be valuable. It’s also good to point out a winner at the end. Some of the things you can compare against each other are: software, books, courses, companies, etc.—even people.

10. Stories

There’s nothing like a good story. Stories are ones of the most reader-friendly types of blog posts. We ñ humans ñ are used to hearing stories ever since we were children. The power of stories lies in their ability of disguising certain messages while describing seemingly unrelated situations. You can create a story about someone who wanted to do something but failed because they didn’t know the most important elements of X, where “X” is the thing you want to share with your readers… Just an example.

11. Controversial posts

The truth is people like to read controversial articles even if they don’t agree with the author. That being said, not every author has enough balls to write such a thing. Interestingly enough, creating a controversial post is not that difficult. The easiest way of doing it is to pick a topic, write down your thoughts about that topic, and then sharpen them up to the point of absurd. You can use some sarcasm while doing so. Here’s an example. Instead of saying “some Internet marketing tips published online have very few possible applications in real life,” say “every Internet marketer knows nothing about real-life business”—strong, to the point, and easy to disagree with.

12. Inspiring posts

Usually an inspiring story about someone (hopefully, an underdog) achieving something. The main message here is “if he can do it, so can I.” The only problem is that it’s not that easy to find something interesting enough to be turned into an inspiring post.

13. Research posts

A step-by-step guide on how you are (or someone else is) researching a specific topic. For example, you can share how you’re doing your keyword research, or how you’re searching for a virtual assistant to hire, or how you’re doing market research to come up with a list of potential partners and competitors.

14. “What others are saying” posts

This is a combination of a research post and a link list post. The main idea is to find a topic and find other people sharing their opinion on that topic. Sometimes it’s better to not pretend that you are the most knowledgeable person in a given field, but share the opinions of other experts instead. It’s the thing Napoleon Hill was famous for.

15. “What if” posts

A hypothetical post about something—”What would happen if X?” kind of thing. To start, choose an interesting topic, find an element that’s certain to exist in that field, and try to write a post about what might have happened if that element never existed. For example: “What if WordPress was never invented?”

16. Parody posts

A satirical view on a given topic. The easiest way of coming up with such a thing is to choose another publication about something, note down some of the ideas presented in it, and extend them to the point of absurd. For example, many building-a-successful-blog gurus tell you about the importance of commenting on other blogs. In response, you could write a post on “why you need to comment on 1,374 different blogs a day if you want to be successful.”

Unconventional blog posts

17. FAQ (Frequently Asked Questions) posts

I’m sure you know very well what this is about. The only problem with coming up with these kind of posts is the “frequently” part. If you want to create a FAQ style post you need to have an audience to get the questions from. Creating a fake FAQ containing only some imaginary “frequently” asked questions is the biggest sin of them all.

18. SAQ (Should Ask Questions) posts

A similar type to the previous one, but this time you, as the expert, provide a list of questions and answers your audience should be asking you. The trick here is that frequently asked questions are not always the ones that are the most important (that’s because people don’t know what they don’t know), so in a SAQ post you can present your expertise and deliver much value to your readers.

19. Reviews

There are tens of blogs that focus solely on reviews of various products and services, mostly in the tech/gadget niche. I’m not telling you to start posting only reviews from now on, but submitting one every now and then surely can’t hurt you. In addition, you can include your affiliate links and make some money along the way.

20. Interviews

I’m sure there’s a lot of potential people you can interview: experts, celebrities, ordinary people who have managed to do something significant, people sharing their success stories, companies, other bloggers. Just look around your niche and I’m sure you’ll find someone interesting.

The interview itself can be done in a couple of different ways. You can meet with someone in person (the traditional way). You can mail them your questions and they will mail you back the answers. You can call them via Skype or phone. You can do a twitter interview (tweeting back and forth questions and answers). Basically, there are no limits. Sometimes being creative pays a lot, so try to come up with your own ways of doing interviews.

21. Ebooks

Whenever you have a big library of resources, your own posts, notes, etc. you can combine them and turn into an ebook, and then announce its launch in a standard blog post. One of the best examples of using your existing blog posts to create an ebook is the work of Darren Rowse in 31 Days to Build a Better Blog. Once you have your ebook ready, the best way of delivering it is, of course, as a PDF download. In fact, creating ebooks can be fun—something I found out for myself when putting together my own ebook.

22. Special reports

It’s like an ebook, only smaller, usually focusing on just one aspect of a given field, and in most cases delivered free of charge. Other than that, you can approach it the same as creating a standard ebook, and once you have it ready, announce this fact in a blog post.

23. Cheat sheets

As Wikipedia defines it, “a cheat sheet is a concise set of notes used for quick reference,” and that’s exactly what it is. I’m sure that you can find many rules, tricks, methods of doing/using something that relates to your field or niche. You just have to put it all together in a neat PDF file and share it with your readers. Just to give you some examples of nice cheat sheets: Cheat Sheets & Quick Reference Cards for Developers.

24. Checklists

A checklist is a set of specific steps that need to be taken in order to complete a task. Next to the headline of each step there should be an empty box where the person using the checklist can put a tick once the step has been completed. This forces you to use the PDF format once again. Once you have the checklist ready, write a post describing what it’s for and how to use it.

25. Infographics

Infographics are very popular in today’s Internet. They are cool to look at, present information in an easy-to-digest manner, provide a lot of value, and have a high share-with-a-friend factor. The only downside is that they are very time consuming to create. And in most cases you have to delegate this work to someone (or work together with someone) if you want the final result to be exceptional. Nevertheless, they are worth to consider if you have the time and the resources. Here are some examples of great infographics: Infographics for Web Designers: Information You Ought to Know, 12 Amazing SEO Infographics.

26. Projects

In my opinion this is one of the biggest things you can do for your blog once you have a moderate readership. By “moderate” I don’t necessarily mean the numbers, but people’s engagement with your posts.

The basic idea is this. You announce a project that you will be participating in (or are an author of) and invite your readers to take part in it, and share their results. A great example is what Pat and Tyrone have done with the Niche Site Duel project.

27. Open questions to your readers

This is usually a very short post. Just a single question to your readers about whatever topic. But, of course, it has to be something related to your niche, and it has to be something that actually interests you, something you want to know … maybe as part of research for your upcoming post. Publishing this kind of post can help you tighten the relationship with your readers and encourage some of the quiet ones to speak up. The only downside is that you have to have a moderate readership in order to make this work.

28. Starting a debate

Similar to publishing an open question, only this time you are saying what’s your opinion at the beginning of the post, and let your readers pick a side, so they can share their own arguments in favor or against. One more time … you have to have an audience for this to work. Once you consider the debate finished you can shut down the comments and write a follow-up post pointing out some of the most important parts of the debate.

29. Presenting an existing debate

Let me just give you an example. A while ago, Corbett Barr published a post presenting a debate between Pat Flynn and Everett Bogue on whether or not you should allow comments on your blog. The debate has been prepared earlier by interviewing both sides giving them the same questions, and then letting them take a look at each other’s answers so they could react to them. This is a great idea and I have to implement it myself in the near future. I encourage you to do the same.

30. Surveys and polls

Yet another way of connecting with your audience. This time again you are the one asking questions. A simple poll consists of one question with a number of possible answers. For example: “Which member of the A-team do you like the most? 1. Hannibal, 2. Face, 3. Murdock, 4. B.A.” There’s a number of different WordPress plugins that can provide you with a possibility of creating a poll.

A survey is usually something a bit bigger. For instance, a questionnaire containing a number of poll-styled questions as well as essay questions, and simple fill-in-the-blanks. You can search the WordPress plugin directory to find an appropriate plugin for this too. Surveys surely provide much valuable information about your audience, which makes them worth considering once you have an engaged readership.

31. Crash courses/gathering posts

This is a kind of post consisting of links to other post within the same topic, and maybe some additional comment or content. For instance, this guitar blog sharing information on how to learn guitar chords. Each chord gets its own post, and at the end of the series there’s one big gathering post featuring the links to all the other posts and some additional tips and resources. In the end, the whole post looks like a kind of crash course on learning guitar chords.

32. Twitter posts

In order to create such a post what you need is a topic, preferably a trending/popular one, and some time. Just go to twitter search and find some interesting tweets about the topic. You may search by keywords or by hashtags. Once you have a set of 20+ tweets you can combine them into one “what people are saying” post. This may sound like an easy way out, but in reality these posts can be very informative and, in many cases, very funny.

33. Income/traffic/expense reports (monthly)

Very popular lately. Some of the best examples can be seen at Think Traffic and Smart Passive Income. What you do is simply take a look at your Google Analytics account as well as your bank account and report any changes comparing to the previous month. Of course, you have to be comfortable with sharing this kind of information. The other problem is that telling people that your traffic is at 346 per month and you income at $12 per month might not be the best social proof possible.

34. Contests

Contests are a great way of connecting with your audience or even getting an audience in the first place. The most important element of a contest is the prize. It has to be something worth competing for, which mean it involves spending some money or finding a sponsor. The theme of the contest can be anything. For example: “whoever sings the highest note wins an iPod”—you get the point. Entries can be submitted via email or, preferably, via a comment below the post. It’s up to you.

35. Draws

Something similar to a contest. The only difference is that the winner is not chosen by someone, but gets drawn randomly. Other than that, same rules apply.

36. Races

Another idea that’s similar to a contest. The main idea of a race is to give your audience a specific task to do, and the first person to complete it wins. It might be something like: “first person to publish 20 comments this month on my blog wins an iPod.” The main benefit of such a thing is that apart from the winner submitting 20 comments you may get the runner up submitting 18, two people submitting 17, and so on. So in the end, running a race might bring you many more comments than 20. Just an example. The rules of running a contest apply here too.

37. Quizzes

How is it any different from a poll or a survey? Well, a quiz is not a tool for you to find out something about your audience, but a tool for your audience to find out something about themselves, usually in a funny and entertaining way. A great example is a quiz that can be found at theoatmeal.com, titled How long could you survive chained to a bunk bed with a velociraptor?. It turned out to be a big link bait for theoatmeal and resulted in #1 ranking in Google for the phrase “bunk bed”, whether it was intended or not. Plus, at the end of the quiz you receive a cool badge which you can include on your blog or share on Facebook. I’m sure you too can came up with something quiz-worthy in your niche.

38. Software, tools, scripts, plugins, themes, services

You can use a blog post to announce your new software, tool, plugin, service, etc. Share some information about the thing—what it can do, who it is for, how and when to get it, and so on. This might be a good way of notifying your readers of what’s going on in your business, what you’re up to, and what’s in it for them. You can get some ideas for new services or products by doing a brainstorm and researching what your audience might be interested in. Of course, to make it happen you have to know your audience first.

39. Comics

Every day more bloggers start to publish comics as a constant element of their publishing schedule. Take a look at Web Designer Depot. If you are, or can get, someone who can create the actual comics, it might be a good way for you to expand your audience and give them something that’s very easy to digest. It can be a nice link bait as well. Two examples of comics-only blogs: xkcd and Wulffmorgenthaler.

40. Jokes

No further explanation needed. Obviously, it’s not a good fit for every niche, but who knows? Maybe it’s perfect for yours.

41. Icons and other graphical freebies

This is something that works well in the design niche, which is not very surprising. Designers are always on the hunt for some fresh, preferably free, icons/buttons or other graphical tools. Try to adjust this strategy to your niche. For example, if you have a photography blog you might share some free stock photos on Creative Commons license. If you’re in the business development niche you could get some Microsoft Word templates designed for you and then share them with your audience. It’s not just about icons.

42. Presentations

If you’ve ever given a presentation on whatever topic I’m sure you still have the slides somewhere on your computer. You can upload them to Slide Share and then embed them in your blog post. Inside the post you can describe what the presentation is about, mention when and where you gave it, and encourage your readers to re-embed it on their own blogs.

Audio blog posts

43. Mp3 files (as a podcast)

First things first: what is a podcast? Quoting Wikipedia: “a podcast is a series of digital media files (either audio or video) that are released episodically and often downloaded through web syndication.” Translating it into plain English, a podcast can be a series of mp3s launched in a sequence. Probably the best idea is to register your podcast in iTunes and get some recognition there.

When it comes to the content itself, a podcast can contain whatever you want. You can give tutorials on various topics, tell jokes, even read poetry. Feel free to browse the iTunes directory to get some ideas.

44. Interviews

These are similar to text interviews, only this time you conduct them over the phone or Skype and record everything along the way. Then you share them as an mp3 on your blog or turn them into a podcast if you’re planning to release more than one interview.

Again, some people you can interview include: experts, celebrities, ordinary people who have managed to do something significant, people sharing their success stories, companies, and other bloggers in your niche.

45. Talks

Something similar to an interview, but this time you’re getting a number of people (three or four) on the line or Skype, and give them a topic to talk about. Of course, you record everything so you can share it with your audience later on. This kind of talk is more focused on a specific topic rather than on the people participating in the talk. This is a good idea if you have the possibility to convince a couple of influential people in your niche to take part in it.

46. Teleseminars

In order to pull this one off you need an engaged audience, or good marketing. The main idea is that first you announce you’ll be conducting a teleseminar on topic X and give people a link where they can sign up for it. Then when the time comes you give the seminar to a live audience. Of course, you can also record it and share as an mp3 later on.

The most popular way of running a teleseminar is to focus on a how-to topic. It should be something you can explain to your audience—something that’s really important to them, yet it’s not so easy to master alone.

Video blog posts

47. Talking head video

All video post types on this list have one thing in common: once you have the video made you can embed it in a normal blog post, or share it with your audience as a video podcast.

Now, the talking head video. It’s the simplest video to make. What you basically do is sit in front of a camera and talk about something. One of the most famous examples is Gary Vaynerchuk and the posts on his personal blog. Of course, the topic needs to be interesting if you want to have any kind of impact, and you have to be comfortable with the camera—something many people find challenging at first.

48. Screencast

Screencasting is another name for recording what’s happening on your screen. It can be done with software called Jing, for example. It’s a very easy-to-digest way of giving a tutorial on some technical things, like setting up WordPress or doing something in Photoshop. Sometimes it’s much easier to do a screencast than explain such things via text content. Usually the same amount of information can be delivered in a five-minute screencast as in 3,000 words of text. And the problem of you being uncomfortable with being in front of a camera doesn’t apply here, so it’s actually easier to make.

49. Presentation video

This is basically a kind of screencast. But it’s made by first creating a PowerPoint presentation (of course, you can use other software too), then firing it up and recording everything while you talk the viewers through the presentation. It’s very easy to make and the results can be great due to some of the PowerPoint’s fancy features.

50. Interviews

Nothing new here, except this time you’re not writing or recording audio, but shooting a video instead. Video interviews always look more professional because they have that TV-like feel to them.

51. How-to video

Shooting a how-to video is a good idea if you’re in a niche where it’s easier to actually show something than it is to describe it with words. The guitar niche is a great example. It’s much easier to show people how to play a specific chord than it is to describe this to them. The main problem here is that you have to be comfortable with being in front of a camera. If you’re nervous, people will notice.

52. Webinars

Similar to teleseminars, webinars use video as the main medium. Other than that, the same rules apply.

Recycling

The final advice I want to give you in this post is to recycle your content. Now, what do I mean by that? Whenever it’s possible and makes actual sense, try to take a piece of your content and repurpose it by turning it into a different medium.

For example, you can get your videos and mp3s transcribed and then share them as a regular blog post. You can also go the other way around: create an article first, then turn it into a script, and in the end shoot a video and upload it to your YouTube channel. Another idea is to take your email newsletter series, read every edition out loud and share the whole thing as an audio podcast on iTunes. I’m sure you get the idea by now. As you can see, the possibilities are endless.

What’s on your list? Do you have any interesting blog post type ideas you want to share? What’s your favorite type? Speak up in the comments: your input is more than welcome!

Karol K. (@carlosinho) is a 20-something year old web 2.0 entrepreneur from Poland and a grad student at the Silesian University of Technology. He hates to do traditional business but loves to train capoeira. Tune in to get his advice on blogging and starting an online business.

Originally at: Blog Tips at ProBlogger
DMS_468x60_LS_banner4.gif

52 Types of Blog Posts that Are Proven to Work

 
 

Reliable Cross-Browser Testing, Part 1: Internet Explorer

02 Sep

Advertisement in Reliable Cross-Browser Testing, Part 1: Internet Explorer
 in Reliable Cross-Browser Testing, Part 1: Internet Explorer  in Reliable Cross-Browser Testing, Part 1: Internet Explorer  in Reliable Cross-Browser Testing, Part 1: Internet Explorer

In a perfect world, cross-browser testing would be straightforward. We would download a legacy version of a browser, run it, and be able to instantly test our pages and scripts without a single care in the world. The reality of cross-browser testing, though, is very different. Issues such as runtime conflicts when running multiple versions of the same browser and inaccurate third-party testing tools mean we can spend hours just evaluating whether a testing set-up is anywhere near reliable.

I’m a user-interface developer at AOL (yes, we’re not dead yet!), and in this multi-part post I’ll take you through the exact set-up we use to accurately test content that will be potentially viewed by up to millions of users with a very diverse set of browsers. This set-up is similar to the one used by some of my colleagues at Opera, Mozilla and Google, so, fingers crossed, we’re doing this optimally.

A quick note before we begin. Setting up accurate testing for Internet Explorer as outlined in this post requires a bit of effort. So, please check your website analytics first to ensure that a sufficient number of IE users visit your website in the first place to warrant this effort.

Internet Explorer 6 To 10

Let’s begin with our old friend, Internet Explorer (IE). As most of us know, running multiple versions of the original Internet Explorer executables on the same system is very difficult due to issues ranging from runtime version conflicts to operating-system incompatibility. In truth, I don’t think Microsoft ever considered a scenario in which developers needed a way to achieve this back when it was first conceiving IE 6, 7 and 8.

This has left developers in a chasm of uncertainty, forced through trial and error to discover a way to accurately test what is (for better or worse) the world’s most widely used set of browsers.

In this section, I’ll take you through some IE testing options that you may be using or have heard of before. I’ll explain why they might not be reliable; and then I’ll present the solutions we currently use at AOL for production websites.

In case you’re interested, our team generally uses IE 7 as a baseline, although we do also test stable, beta and preview or dev-channel versions of Chrome, Firefox, Opera, Safari and, of course, IE 8 to 10.

Our reason for using IE 7 as a baseline comes down to our global website analytics: IE 6, 7 and 8 are the most common browsers used to access our websites. However, we stopped supporting IE 6 as of a few months ago. The reality is that IE 6 has major compatibility issues with modern technologies, and our team has found that we are able to deliver projects up to 20% more quickly when we don’t have to worry about catering a basic experience to it.

Most Third-Party IE Testing Tools Are Unreliable

A Google search for third-party IE testing tools will result in at least ten different options, nine of which are likely to be unreliable. Let’s go through a sample of them, in case you’re using one of them to test against staging or production websites at your work.

The following reviews may sound a little harsh, but the purpose is to stress the importance of using approaches that have been well engineered, tried and tested over time.

IETester

Unfortunately, IETester is probably the most popular third-party tool that I see designers and developers use to test multiple versions of IE. When I first tried it, I too was drawn by the promise of a single application that would solve all of my IE testing woes. However, all that glitters is not gold.

Ietester in Reliable Cross-Browser Testing, Part 1: Internet Explorer

The tool has a number of inconsistencies when testing IE 6, 7 and 8, with none providing a 1:1 experience of the original browsers. Our and many other teams have confirmed not only that the rendered output of IETester varies significantly from any real version of IE, but that pop-up interactions cause failures, Flash and CSS filters don’t work in user mode, conditional CSS comments often fail, and switching between versions makes it very prone to crashing.

In short, it’s unreliable, and this should be enough for any developer to consider alternatives.

Multiple IE

TredoSoft’s Multiple IE is another tool that often shows up when searching for an IE testing solution. Unfortunately, it too suffers from a number of issues, including inaccurate rendering. One common complaint is that people experience IE 5.5 rendering bugs even when they’re just testing IE 6; this certainly is not something we want to deal with at a time when many of us are trying to ditch IE 6 completely.

Multiple IE isn’t updated regularly either, and if the long thread of user issues experienced with it since its release doesn’t put you off, then consider that the tool’s IE textboxes actually break in a number of circumstances.

Multipleie in Reliable Cross-Browser Testing, Part 1: Internet Explorer

To the best of my knowledge, both IETester and Multiple IE rely on an exploit known as DLL redirection in order to bypass issues with DLL naming conflicts, allowing the tools to attempt to run standalone copies of IE. I would recommend avoiding such tools, because implementing a completely sandboxed environment for IE that is as accurate as running the originals independently is very difficult.

Expression Web SuperPreview

Next up is Microsoft’s Expression Web SuperPreview, which claims to simplify the process of testing and debugging layouts across multiple versions of Web browsers.

Expression in Reliable Cross-Browser Testing, Part 1: Internet Explorer

Unfortunately, you won’t be able to test complete user interaction, JavaScript, DOM manipulation, animation or much else with this tool. We live in an age when the Web can be very dynamic and, in some cases, highly interactive. A tool like this might work for baseline testing, but not for accurate cross-browser testing.

BrowserLabs, Browsershots, BrowserCam

I personally use Adobe’s BrowserLabs — or sometimes Browsershots, if a static layout test is absolutely necessary. But again, neither of these options allow you to test interactions with your pages. The same goes for BrowserCam. These services simply weren’t designed for this purpose, but we still regularly see designers and developers using them as if they were.

I’m not in any way saying to flat out avoid these services, but rather that they’re inadequate for complete cross-browser testing. Designers and developers need to know exactly what a user sees when they interact with their website. No visitor will be using a static page renderer, so why rely on one yourself?

Windows Virtual PC

One other solution you’ll probably come across is Microsoft’s Virtual PC, with time-bombed images for IE6 to 8.

For a brief time this was considered to be the answer to cries from developers for a better solution. Unfortunately, it is by far the most inadequate (and demanding) solution to testing that I’ve seen proposed in the past few years. At least 12 GB of disk space is required to install all of the images, and the images regularly expire during the year.

A cross-browser testing environment for legacy browsers should have reasonable system requirements and, for the most part, not require regular manual updating in order to continue using it. Because the Virtual PC option fails these criteria, I can’t recommend using it either.

Browser And Document Modes

We’ve looked at third-party tools, but what about Microsoft’s current solutions to these problems?

Both IE 9 and IE 10 PP2 support switchable document and browser modes via the F12 Developer Tools for cross-version compatibility testing. To be specific, browser-version testing here is made possible using a kind of emulation.

Browsermode in Reliable Cross-Browser Testing, Part 1: Internet Explorer

“Document mode” determines what features a page has access to and what can be adjusted based on the page’s doc type, X-UA-compatible meta tag and headers. For example, the standards document mode allows the page to take advantage of IE’s implementation of ECMAScript 5 (ES5), while the IE 7 and 8 standards modes offer an alternative experience.

“Browser mode,” on the other hand, emulates different IE browser version behaviors and can be changed directly from the IE Developer Tools. Emulation is achieved in a few different ways, but it includes altering both the document mode and the user-agent string. In case you’re wondering, the UA string is adjusted here to ensure that code that relies on UA sniffing functions as though the correct version of the browser were being used.

Modes in Reliable Cross-Browser Testing, Part 1: Internet Explorer

It is worth noting that IE 9 shipped with a newer JavaScript engine, called Chakra. While the browser itself supports a number of compatibility modes, because the JavaScript engine itself differs significantly from what shipped with IE 6, 7 and 8, there are acknowledged differences between the experience in IE 9 and testing in a standalone browser.

That aside, there are, unfortunately, a number of quirks in the way that both document mode and browser mode function. Our team has run into scenarios where IE returns the wrong user-agent string to the server; and, as with the third-party tools, there have been several instances of inaccuracies with the expected rendering when tested against the original browsers.

Finally (and rather strangely), these modes have a number of issues of their own that are not present in IE 6, 7 or 8, making it even more difficult to establish whether the issues experienced are specific to a browser version or just the mode being used.

For these reasons, I would urge developers not to rely strictly on document or browser mode for their cross-version testing needs.

Accurate IE Testing Solutions

Option 1: Virtual Machines + IECollection

We’ve reviewed a number of solutions that don’t provide an accurate means of testing multiple versions of IE. So, what does work? The answer lies in using dedicated virtual machines (VMs) and a tool called IE Collection.

Iecollection in Reliable Cross-Browser Testing, Part 1: Internet Explorer

Out of the box, Utilu’s IE Collection offers the following:

  • A tested collection of standalone versions of IE, including versions 1 through 9;
  • Confirmed support for accurate rendering when compared against the original IE executables;
  • Confirmed support (to date) for the correct IE JavaScript engine implementations that shipped with the originals;
  • Confirmed support for the correct UA strings being detectable (not that you should be UA-string testing in the first place — however, if needed, it’s there);
  • Support for both the 32-bit and 64-bit versions of Windows XP, 2003, Vista and 7;
  • Access to the IE Developer Toolbar, which comes with the standard IE Collection set-up; this is compatible with IE 5 and above, but you also have the option to install Firebug Lite if you prefer that.

Although the majority of IE versions are supported and function reliably within the collection, there are known issues with versions of IE 7 when used under Windows Vista or Windows 7 (as noted on Utilu’s website). I’ll discuss how we handle this limitation shortly, but let’s first briefly go over virtual machines.

Virtual1 in Reliable Cross-Browser Testing, Part 1: Internet Explorer

A virtual machine (VM) is a sandboxed “guest” operating system that run within a normal “host” operating system. It effectively enables you to install and run a dedicated copy of almost any other operating system on your current one and to share a configurable set of memory and disk resources between the two. For example, a Windows 7 VM could easily be run on Mac OS X, as could an Ubuntu VM be run on Windows, and so on.

You’ll need two things to get started using VMs: a virtualization tool to create VMs on your OS, and a CD or image of the operating system that you wish to run as a virtual machine. Your company should be able to furnish you with Windows licenses relatively easily (… famous last words). If you’re a college student, you could probably get licenses for Windows XP SP3, Vista and 7 for free through the MSDN Academic Alliance program.

You could set up a number of different configurations to test Windows and IE, but if you’re using IE Collection, I would generally recommend the following:

  • Windows 7 for IE 6, 8, 9, 10;
  • Windows XP (SP3) for IE 7.

You shouldn’t need to support anything below IE 6 nowadays, but IE 4 to 5.5 also work fine on XP SP3.

At AOL, we use a combination of VirtualBox, Parallels and VMware for our virtualization needs. I prefer Sun’s VirtualBox because it has the following advantages:

  • It’s free, providing a lower barrier to entry for developers who cannot afford commercial licenses for Parallels or VMware;
  • In my experience, it tends to perform more optimally than Parallels or VMware under the same configuration settings;
  • It has a marginally better UI than the alternatives.

That said, VMware is considered better if you’re working with a standalone server. At the end of the day, all three options are equally valid, and both Parallels and VMware come with trial versions that you can easily evaluate. Choose whichever option best suits your needs.

Pro tip: Remember to configure your VM to use the minimim amount of memory needed to test, unless you are using a dedicated testing box. By default, not all virtualization tools are configured to do this. This will simply ensure that the rest of your OS runs more smoothly.

Here are the three steps to setting this up:

  1. If you’re a Mac user, I recommend using a 32-bit Windows 7 Pro or Ultimate image (or installation CD), with a minimum of 17 GB of disk space allocated for the installation. 512 MB of virtualized RAM (which can be adjusted in the settings panel) should work fine for testing on a non-dedicated testing machine, but use more if feasible. You can create this as a new VM using VirtualBox, which I have configured to run at a resolution of between 800 × 600 and 1024 × 768 pixels. Windows users have two options. If you’re already running a version of Windows 7, skip to step 2, where we’ll begin installing IE Collection. If you’re running a different version of Windows and would like to run a virtualized copy of Windows 7 on top of it, then follow the steps above for Mac users. Mac and Windows users should boot up their VM or desktop Windows installation before proceeding to step 2.
  2. Next, download IE Collection from Utilu’s website, and then install Windows 7 on either your VM or your primary system, depending on your set-up. This will give you access to IE 6, 8 and 9. I usually install IE 10 for testing purposes separately, but bear in mind that it is only in the platform preview phase at the time of writing. Ideally, install only the bare essentials to test on any VM in order to avoid excessive start-up times.
  3. Mac and Windows users: to address the issue of IE 7 not working on Windows 7, you’ll have to create another virtual machine with Windows XP installed (ideally with SP3). Because no reliability issues have been reported for running either IE Collection’s IE 7 or the original IE 7 on this OS, your bases should be covered here. As stated in my previous instructions, obtain a Windows XP image or installation CD, and create a new VM using VirtualBox. Boot it up, install IE7 through the link above, and you should be good to go.

That’s it really! Some developers prefer to run IE 6 and 7 on XP (step 3) rather than on Windows 7 or Vista, because XP accounts for the majority of users who have yet to upgrade to IE 8 or 9. This, too, is completely valid; the set-up is flexible enough to support a little personal preference.

Next, for the sake of being thorough, let’s look at some alternatives to the set-up I’ve recommended above.

Option 2: Dedicated VMs for Each Version of IE

Pragmatic developers might wish to maintain a dedicated VM for each version of IE being tested. On these VMs, rather than using any third-party tools, they would install the original, official IEs instead.

Multivm in Reliable Cross-Browser Testing, Part 1: Internet Explorer

The reasoning behind this is that it potentially minimizes the risk of individual browser configurations or overrides from interfering with one another, and it ensures that you get only the exact version of IE that you wish to test (and, in turn, the corresponding JavaScript engine in that version).

If you’re setting up dedicated VMs for individual releases of IE, I recommend the following set-up:

  • Windows XP (SP3) for IE 6,
  • Windows Vista (SP2) for IE 7,
  • Windows Vista (SP2) for IE 8,
  • Windows 7 for IE 9 and 10.

Knowing now about dedicated VMs, you might be wondering why we don’t use this set-up at AOL. I can only speak for my team, but we moved away from this approach because running three to four VMs on the same system and still using it efficiently for other tasks can become unmanageable.

With a minimum configuration of 512 MB of RAM per VM, we would be looking at around 2 GB of RAM (if not more) just for testing purposes. This set-up might work if you currently have 8 GB or more of system memory. But if not, there’s still hope.

We could always get a dedicated box just for testing purposes, and run all of our virtual machines directly on there instead. I recently acquired a second box at work for this very purpose. But at the end of the day, both options 1 and 2 are set-ups you can rely on.

Option 3: VNC or RDP + Dedicated Testing Boxes

Remotedesktop in Reliable Cross-Browser Testing, Part 1: Internet Explorer

A few companies (such as ZURB) prefer to use a form of remote desktop access to allow designers and developers to log into a dedicated testing box or set of boxes for cross-browser testing, over a network. The benefit of this is reduced demand on memory for each client. And this can be implemented in a few ways; VNC and RDP are the first that come to mind.

Virtual network computing (VNC) is a platform-independent desktop sharing system that allows you to remotely control another computer. It transmits both keyboard and mouse events from one system to another, relaying screen updates back in the other direction over a network. Similarly, RDP allows users to access applications over a network, but it is a proprietary protocol developed by Microsoft. If you happen to be running Mac OS X, VNC is already built in, but a number of VNC clients are also available in the wild, such as RealVNC. On the RDP side of things, Mac users can use Apple’s own Remote Desktop and Remote Desktop Connection by Microsoft.

You might be wondering what the differences are between VNC and RDP. RDP is semantic and is more aware of controls, fonts and other graphical primitives, while VNC is a little “dumber” in this regard. VNC, though, permits a session to be shared on the target machine, which might be useful for multi-user demos; whereas RDP does not, as far as I’m aware.

With the decreased memory requirements, you might then wonder why we don’t opt to use remote desktops for testing at AOL. The primary reason is that, in some cases, testing over a network can result in packets (effectively, frames) being dropped, which can affect our ability to test highly interactive applications or websites. Also, websites that make use of rich-media experiences based on canvas, SVG or otherwise aren’t reliably tested over networks for this reason. But don’t let our experience put you off. I know of teams in other companies that haven’t run into these issues, and remote testing might be suitable for some networks more than others.

Yet another alternative: If your team is unable to purchase or rent dedicated boxes for remote testing, there are third-party services that readily host all versions of Windows, along with historic versions of IE and other browsers, for a subscription fee. CrossBrowserTesting.com is one such option that might be worth exploring.

Conclusion

I hope this guide has come in handy. Please feel free to share your own stories and experiences of cross-version testing IE, because they may help other readers decide which option to try out first.

In part 2 of this post, we’ll look at cross-browser testing modern browsers. See you then!

(al)


© Addy Osmani for Smashing Magazine, 2011.

 
 

Futurama Monopoly lets you own Robot Hell [This Is Awesome]

01 Sep
If we can't have Game of Thrones Monopoly in real life, then this is the next best thing — a Futurama Monopoly set is available for preorders during the month of September, with the game shipping in November. Watch out for the Hypnotoad! More »
 
 

One in 25 business leaders may be a psychopath, study finds

01 Sep

Psychopaths use charm and manipulation to achieve success in the workplace, according to a US study

One out of every 25 business leaders could be psychopathic, a study claims.

The study, conducted by the New York psychologist Paul Babiak, suggests that they disguise the condition by hiding behind their high status, playing up their charm and by manipulating others.

Favourable environmental factors such as a happy childhood mean they can function in a workplace rather than channelling their energies in more violent or destructive ways. Revealing the results in a BBC Horizon documentary, Babiak said: "Psychopaths really aren't the kind of person you think they are.

"In fact, you could be living with or married to one for 20 years or more and not know that person is a psychopath.

"We have identified individuals that might be labelled 'the successful psychopath'.

"Part of the problem is that the very things we're looking for in our leaders, the psychopath can easily mimic.

"Their natural tendency is to be charming. Take that charm and couch it in the right business language and it sounds like charismatic leadership."

Babiak designed a 111-point questionnaire with Professor Bob Hare, of the University of British Columbia in Canada, a renowned expert in psychopathy. Hare believes about 1% of Americans can be described as psychopaths.

The survey suggests psychopaths are actually poor managerial performers but are adept at climbing the corporate ladder because they can cover up their weaknesses by subtly charming superiors and subordinates.

This makes it almost impossible to distinguish between a genuinely talented team leader and a psychopath, Babiak said. Hare told Horizon: "The higher the psychopathy, the better they looked – lots of charisma and they talk a good line.

"But if you look at their actual performance and ratings as a team player and productively, it's dismal. Looked good, performed badly.

"You have to think of psychopaths as having at their disposal a very large repertoire of behaviours. So they can use charm, manipulation, intimidation, whatever is required.

"A psychopath can actually put themselves in your skin, intellectually not emotionally.

"They can tell what you're thinking, they can look at your body language, they can listen to what you're saying, but what they don't really do is feel what you feel.

"What this allows them to do is use words to manipulate and con and to interact with you without the baggage of feeling your pain."

• Horizon: Are You Good Or Evil? is on BBC2 at 9pm on Wednesday 7 September


guardian.co.uk © Guardian News & Media Limited 2011 | Use of this content is subject to our Terms & Conditions | More Feeds

 
 

Darth Vader will lose a little more of his dignity in Star Wars original trilogy Blu-rays. Listen for yourself! [Video]

30 Aug
George Lucas is not satisfied with turning the puppet Yoda in Star Wars: The Phantom Menace into a CG creation. Or just fixing some of the wonky lightsabre effects in the original trilogy. He's going a bit further. More »
 
 

Vizualize.me Beta: Turning Your LinkedIn Resume in Infographics

30 Aug

vizualize_me.jpg
There seems to be a commercial market emerging around the idea of automizing the creation of infographics. Toronto based start-up vizualize.me [vizualize.me] is currently developing an online application that can automatically translate any online LinkedIn profile into an online infographic. In particular, the new service aims to overcome the issue of reading overly long or highly complex resumes by showing the same information in a more readable and attractive way. The start-up has been coding the online application only since the last 2 months, and is currently still in private beta.

First peeks behind the beta service show how this can become particularly useful for those that like to change jobs often, have a high amount of skills or know quite a lot of languages (unfortunately, my current own resume is not that compelling). The infographics are automatically generated through logging in with LinkedIn credentials. One can still edit each individual item, change the 'theme', 'colors', 'fonts' or the 'background' image. 'Themes' actually include different visualization techniques, which currently include a horizontal or vertical bar graph slash timeline and a more risky arc diagram-style approach.

While the idea seems certainly useful, one would certainly wish for the availability of more subdued visual styles, in particular for those people who appreciate more classical visual styles when applying for high-end, important jobs. I also foresee some critical comments on the color palette for the 'language' world map.

Notably, Visual.ly is also betting on the future of semi-automized online infographics, as it is currently in the process of launching an online infographics authoring tool.

 
 

Breaking Down Silos, Part 1: The Consequences Of Working In Isolation

30 Aug

Advertisement in Breaking Down Silos, Part 1: The Consequences Of Working In Isolation
 in Breaking Down Silos, Part 1: The Consequences Of Working In Isolation  in Breaking Down Silos, Part 1: The Consequences Of Working In Isolation  in Breaking Down Silos, Part 1: The Consequences Of Working In Isolation

No man is an island entire of itself; every man is a piece of the continent, a part of the main…

– John Donne

If you’ve ever worked at a company of any size, you’ve experienced it. Isolation. That feeling of being utterly alone in what you do.

Some people love it: the determination that comes from being a lone ranger, boldly going where no one has gone before. Others hate it: the despair that comes from slaving over a design only to see it disappear down a black hole of development, whereupon it emerges onto a website months later, unrecognizable from the pixels you put on the page with such painful precision.

Island in Breaking Down Silos, Part 1: The Consequences Of Working In Isolation
Image credit: Ibrahim Iujaz

These are the perils of working in siloed environments, and it’s where many of us find ourselves today. We’re either terribly alone or terribly frustrated, depending on the particular variety of silo we find ourselves in. In this two-part series, I’ll explore the consequences of working in isolated environments, and how we can solve this problem by encouraging more collaborative cultures.

What Exactly Are We Talking About Here?

Silos in work environments usually come in two flavors:

  1. Lonely silos
    Lonely silos are made up of workers with no real connection to the outside world. This often happens at start-ups where the focus is more on getting something out the door than on doing it right. I mean, who has time for proper UX design when “we’re building [technology x] because [company y] hasn’t built it and [people z] need it?” (as Kyle Neath recently put it).
  2. Functional silos
    Functional silos feature workers who may be part of fantastic design teams. They have great whiteboard sessions, help each other out, enjoy their pizza Fridays… And yet, they have no real seat at the table when it comes to business strategy. Design happens painfully slow because it has to be signed off by 10 different people. And even then, there’s no guarantee that anything will be implemented the way the designers envisioned it.

Working in lonely silos and functional silos have two main consequences, both devastating to software development:

  1. No process
    This usually happens in lonely silos. It’s everyone for themselves. The company subscribes to the “release early, release often” approach, and so you won’t get bogged down with a formal development process, guidelines for functional specs or any of the stuff that big lame corporations busy themselves with.
  2. Too much process
    This usually occurs when functional silos get out of control. Organizations resort to putting hierarchies and processes in place to stop the “cowboy coding” madness. The science:art ratio in design shifts way too much to one side or the other. Functional specifications move into Microsoft Word templates that are 20 pages long before a single word of content is written. And sure enough, the cowboy madness stops. But it gets replaced with a different kind of madness: stagnation.

The Consequences Of Not Following A Design Or Development Process

When you work in an environment where silos result in no clear design or development process, the following often happens.

1. MVP Madness

We all know the concept of “Minimum Viable Product,” but revisiting Eric Reis’ definition would be useful:

The minimum viable product is that product which has just those features (and no more) that allow you to ship a product that resonates with early adopters; some of whom will pay you money or give you feedback.

Problem is, that last section of the definition often gets ignored. You know, the part about people paying you money. So this MVP idea can be taken too far, and a product can be released before there is a minimum viable understanding of what the thing is supposed to do (or who it’s supposed to be useful for). You could argue that the Color app is an example of this MVP madness (“It’s a photo app!” “No, it’s a data-mining app!” “Actually, it’s a local group-messaging search/recommendations app!”)

Perhaps the best example of this culture is the Lifepath sign-up page, which Dustin Curtis recently put up in what I’d like to believe is a deliberate and very effective attempt at MVP irony:

Lifepath1 in Breaking Down Silos, Part 1: The Consequences Of Working In Isolation
Lifepath sign-up page

A lot of this problem would go away if we evolve MVP thinking into what Andrew Chen calls “Minimum Desirable Product”:

Minimum Desirable Product is the simplest experience necessary to prove out a high-value, satisfying product experience for users.

I think that definition would send a lot of MVPs back to the drawing board, and rightfully so.

2. No Significant Design Focus

The second consequence of a lack of process, particularly in start-ups, is that design is often the last thing on people’s minds. I recently heard an interview with a start-up founder who gave the following overview of their staff: “We have 13 employees: 9 software developers, 2 sales people, 1 operations manager and a social media conversationalist.”

The company hired a social media conversationalist before it hired a designer. In this type of no-process world, ideas go from vision to code (and users) in one easy step, bypassing the principles of user-centered design completely. As Erika Hall puts it:

The floor of Silicon Valley is littered with the crumbling husks of great ideas — useful products and services that died in the shell before they hatched out of their impenetrable engineering-specified interfaces.

3. Endless Cycles

A third consequence of no-process development is that you never really know when you’re done. Not to make this about methodology, but this is one area where the “definition of done” concept in Scrum is extremely useful. If you don’t know when you’re ready to push something live, then the problems of MVP madness and lack of design are exacerbated.

Google Wave is a case in point. Listen to Douwe Osinga as he gives two good examples of MVPs done right before moving on to the problem with Google Wave:

Thinking big sounds great, but most big ideas start small and go from there. Google itself started from the notion that it would be interesting to look at back links for pages. Twitter started out as hardly more than a group SMS product that also works online. Facebook explicitly restricted themselves at first to one university.

Wave is a case in point. Wave started with some fairly easy to understand ideas about online collaboration and communication. But in order to make it more general and universal, more ideas were added until the entire thing could only be explained in a 90 minute mind blowing demo that left people speechless but a little later wondering what the hell this was for.

The Consequences Of Having Too Much Design/Development Process

So that’s what can happen in a no-process environment. But what happens at the other end of the continuum, where process is king of the world?

1. Org-Structure Design

When you can sketch out an organization’s structure by looking at its home page, chances are it’s hopelessly lost in functional silos. I experienced this first-hand while working at eBay. I would sometimes run into the product manager for the home page in the morning, and he’d have no idea why his page looked the way it did on that particular day. Each day was an adventure to see what had changed on the page that he “owned.”

Don’t believe me? Below is an example of the eBay home page from about a year ago, with the teams responsible for each section of the page overlaid (they’ve since gone through a redesign that fixed this issue):

Ebay-silo in Breaking Down Silos, Part 1: The Consequences Of Working In Isolation

This is unfortunately one of the side effects of functional silos. You run the risk of losing any sense of holistic design direction on the website.

2. Design Monkeys

Another consequence of an over-reliance on process is that designers could become nothing more than monkeys, cranking out efficient, perfectly grid-aligned but completely uninspired designs on an assembly line. Wondering whether this is you? Here are some instructions you might recognize as a design monkey:

Pop-1024x88 in Breaking Down Silos, Part 1: The Consequences Of Working In Isolation

Web2-0 in Breaking Down Silos, Part 1: The Consequences Of Working In Isolation

Comicsans F in Breaking Down Silos, Part 1: The Consequences Of Working In Isolation

Don’t get me wrong: I believe in style guides, and I believe in design constraints. But when an organization becomes overly reliant on design rules, creativity is often the first thing out the door. Yes, design is much more than art (we’ll come back to this later), but it’s certainly not pure science either. Without the right injection of art and creativity, science gets boring and forgotten pretty quickly.

3. Tired Developers

Once process takes over an organization, the acronyms start. And arguably, the most feared of them all is PRD: the product requirements document. This usually takes the form of a Word template, with a two-page table of contents. It includes a solution to every single eventuality the software might ever encounter. It sucks the soul out of product managers and the life out of developers.

To use another example from eBay, we once had a 23-page PRD to make some changes to our SiteCatalyst JavaScript implementation. And then the project didn’t happen. I shudder to think about the hours and hours of lost productivity that went into creating this document that never got used. People could have created things during that time. Instead, they sat in Microsoft Word.

The result? Tired developers. Developers who don’t want to code anymore because coding becomes 70% deciphering Word documents, 20% going back and forth on things that aren’t clear, and 10% actually coding.

How do you know that your developers are tired? Charles Miller’s explanation of what it means when a developer tells you that something is “non-trivial” sums it up pretty well:

It means impossible. Since no engineer is going to admit something is impossible, they use this word instead. When an engineer says something is “non-trivial,” it’s the equivalent of an airline pilot calmly telling you that you might encounter “just a bit of turbulence” as he flies you into a cat 5 hurricane.

Tired developers use the word “non-trivial,” or some variation thereof, a lot more than energized developers.

4. Distrust Between Teams

When people don’t live and breathe each other’s workflows, understanding the decisions they make is hard. And if you don’t understand the reason for someone’s decisions, distrust can creep in.

Functional silos that rely on too much process serve as fertile ground for distrust in relationships. A reliance on process can instill a false sense of security and the mistaken assumption that conversation and understanding are less important than proper documentation. This is particularly true in the complicated relationship between designers and developers. As Don Norman recently put it:

Designers evoke great delight in their work. Engineers provide utilitarian value. My original training was that of an engineer and I, too, produce practical, usable things. The problem is that the very practical, functional things I produce are also boring and ugly. Good designers would never allow boring and ugly to describe their work: they strive to produce delight. But sometimes that delightful result is not very practical, difficult to use and not completely functional. Practical versus delightful: Which do you prefer?

So, when designers and developers are not in the same room from the moment a project kicks off, or when design becomes prescriptive before thorough discussion has taken place and everyone has sweated the details together, the stage is set for the two worlds to collide. Breaking down these silos is the only way to design solutions that are practical and delightful.

5. Design by Committee

Not everyone can code, so they don’t go to developers telling them that their HTML needs to be more semantic. But everyone thinks they’re a designer, or at least has a gut feeling about design. They like certain colors or certain styles, and some people just really hate yellow. Because everyone has an emotional response to design and believes “it’s just like art,” they think they know enough about design to turn those personal preferences into feedback.

One of the first things we need to do to solve this problem is to teach people how to give better design feedback. Mike Monteiro gets to the crux of the issue in “Giving Better Design Feedback”:

First rule of design feedback: what you’re looking at is not art. It’s not even close. It’s a business tool in the making and should be looked at objectively like any other business tool you work with. The right question is not, “Do I like it?” but “Does this meet our goals?” If it’s blue, don’t ask yourself whether you like blue. Ask yourself if blue is going to help you sell sprockets. Better yet: ask your design team. You just wrote your first feedback question.

And how do we respond practically to the problems of design by committee? Smashing Magazine’s own article sums it up best:

The sensible answer is to listen, absorb, discuss, be able to defend any design decision with clarity and reason, know when to pick your battles and know when to let go.

Here are four principles I use in my day-to-day work to make that statement a reality:

  1. Respond to every piece of feedback.
    This is tiring, but essential. Regardless of how helpful it is, if someone took the time to give you feedback on a design, you need to respond to it.
  2. Note what feedback is being incorporated.
    Be open to good feedback. Don’t let pride get in the way of a design improvement. And let the person know what feedback is being incorporated.
  3. Explain why feedback is not being taken.
    If a particular piece of feedback is not being implemented, don’t just ignore it. Let the person know that you’ve thought about it, and explain the reason for not incorporating that feedback. They will be less likely to get upset at you if you explain clearly why you’re taking the direction you’re taking. And if you’re not sure how to defend the decision…
  4. Use the user experience validation stack.
    Read the post “Winning a User Experience Debate” for more detail. But in short, first try to defend a decision based on user evidence — actual user testing on the product. If that’s not available, go to Google and find user research that backs up the decision. In the absence of that, go back to design theory to explain your direction.

Summary, And Where We Go From Here

Ending an article on such a doom-and-gloom note feels a bit wrong. But maybe pausing here would be good so that we can all reflect on the issues that siloed development creates in our own organizations. As UX people, we’re taught to understand the problem first before trying to solve it, right? So, let’s do that. Did I miss any consequences? Anything you’d like to add or challenge about the consequences I’ve highlighted in this article?

In part 2, I’ll explain my own journey with siloed development and go over some of the guidelines we’ve implemented to break down these silos and build collaborative teams that help eliminate the vast majority of the issues outlined in this post.

(al)


© Rian van der Merwe for Smashing Magazine, 2011.

 
 

The Hive Mind Needs More Women

29 Aug

Kevin Kelly wrote a thought-provoking post about how "the impossible" is happening more often nowadays, thanks in no small part to large scale collaboration over the Internet. In other words, the hive mind. He cites eBay and Wikipedia as two examples of things he would've thought impossible in decades past.

Collaboration over the Web is still evolving. One way it might be immediately improved is by adding more women to collective intelligence projects and by shutting up the loud mouths. I'm not idly speculating here, those were the findings of a recent study by MIT's Center for Collective Intelligence.

Sponsor

The study found that collective intelligence is not as dependent on individual intelligence as first thought. Having more women in a group improves the collective intelligence, because it raises the level of "social sensitivity." Another important factor is letting everyone talk equally, rather than having the loudest or most opinionated people dominate the conversation.

Back to what Kelly wrote. He posits that more previously impossible things will emerge thanks to "large-scale collaboration, or immense collections of information, or global structures, or gigantic real-time social interactions." He continues:

"Just as a tissue is a new, bigger level of organization for a bunch of individual cells, these new social structures are a new bigger level for individual humans. And in both cases the new level breeds emergence. New behaviors emerge from the new level that were impossible at the lower level. Tissue can do things that cells can't. The collectivist organizations of wikipedia, Linux, the web can do things that industrialized humans could not."

This thinking dovetails nicely with the MIT report. Carnegie Mellon's Anita Woolley explains the findings more in this video:

The implications of all of this for any company doing online business is clear: optimizing groups with more women and more democratic discussion is just as important as casting your crowdsourcing net far and wide. As Aaron Saenz at Singularity Hub put it: "With enough research the crowds of tomorrow may be optimized for the best possible amounts of collective intelligence. Not just huge amounts of thought-power, but efficiently organized huge amounts of thought-power."

It's also something that tech conference organizers should bear in mind. I for one could do with less loud, opinionated people dominating group discussions - as often those people are the least thoughtful.

Kevin Kelly concludes that "humanity is migrating towards its hive mind." Whether or not you agree with that somewhat extreme position, collective intelligence will continue to be a big driver of Web innovation. We just need more women and less loud mouths, don't you think?

Photo credit: I Love Milwaukee

Discuss

 
 

Screenshot of Steve Jobs’s Calendar

29 Aug