When talking to our clients about focus groups and customer panels they invariably reply, ‘there’s a difference?’. Indeed there is, and it can have a lot of impact on the type of research you can do and the feedback you will receive.

If you conduct a focus group, you get a one shot deal. They will tell you what they think of your site or product, and then go away. All the data you get from them is received in isolation of any other factor. This might be good when asking about something definitive like a brand name or logo and asking ‘what do you think?’

A panel, on the other hand, offers a way of evolving your ideas and receiving feedback from the same people through the changes. A panel can be reconvened at regular intervals to monitor progress of, say, a new shopping site page, to see how their opinions have changed and if those changes are for the better or worse.

Naturally, the latter is more expensive, as the subjects need paying or rewarding for their time, opinion and loyalty over the course of a project. But, the information that your regular panel members provide can help bring a project from its origins to conclusion in a meaningful and structured manner.

So, you can see that the two distinct groups can serve very different purposes. For example, anything that is being researched as a concept, such as an advert or cosmetic site refresh, can go to the focus group for a snapshot of opinion and some yes/no answers to design questions.

On the other hand, when you need some ongoing feedback, turn to the consumer panel and you will see how their opinions evolve with your product. The downside of the panel is that you need some guarantee of open mindedness and a willingness to share opinion.

Another difference is that while both are traditionally run as face-to-face events, it is now easier to run a quick focus group over the Internet, allowing for the rapid collection of data. A long-running consumer panel is still best run as a face-to-face exercise to allow for a more detailed approach and the ability to observe the reaction of subjects.

Someone who starts out with negative thoughts may well harbour them through a project, no matter how it progresses and you might find that your panel runs out of love for the project long before you do. This is where companies that run these panels and groups try to find the right people, a task that would be tough for most businesses.

So, there can be a fine line between when to call in the consumer panel or when to get a focus group to do some opinion forming for you. Or, if your project or product is easily adjustable, why not try evolving it in front of the focus group and see their reactions and impressions change live on the day to try to shorten the timeline and development process. It’s amazing what some hard focus and nimble evolution can do.

What type of group do you think would benefit your company or product better?

Related services: Focus Groups & Customer Requirements Capture

For many in the retail industry a regular shop walkthrough is an essential part of the manager’s role to ensure the environment is clean, the products are in the right places, and the shelves are stocked. Do you do the same checks on your website?

Your website is just like a retailer’s shop floor, it’s your front of house. How much time do you spend reviewing your website in a week? How often do your staff, or other team members, spend on the website every week? Ask them. You may be shocked to find that no-one is regularly checking the site. What are you waiting for? Customers to complain? Sales to drop? Traffic to plummet?

Stop waiting and start implementing a set of regular and very simple tasks to ensure that your site is checked on a weekly basis. Websites grow organically and although there’s no substitute for regular usability testing, there are methods you and your team can do adopt to keep a check on your site to ensure usability issues don’t develop as the site grows. After we work with a client to improve the usability of their website we provide them with a checklist to use which helps them maintain usability, you can download it here for free.

Download our Weekly Usability Checklist for you and your team to maintain good usability on your site. Feel free to pass it on to colleagues

Some of these may seem overly simplistic, but many companies are not carrying out these fundamental checks on a regular basis. If you and your staff were to spend 10 minutes a day or an hour a week just running through some of these simple checks you can be confident that you are keeping your front of house in check and giving your site visitors no encouragement to go back to Google to visit your competitors

Are you keeping your site in check?

Related services: Usability testing, and User experience audit

We’re seeing a lot of people talking about conducting their own usability tests in house. The topic of DIY testing has been around for some time now with advocates such as Steve Krug and Jakob Nielson. The general principle being that any testing is better than no testing which is an idea we fully believe in.

As a company who offer usability testing it will probably come as no surprise that we would put forward an argument against companies doing their testing in house. But, before I do that I’d like to add that I think its excellent that people are taking user centredness so seriously these days and if teams feel that they want to take testing in house then that can only be a good thing for the future of the industry. If internal development teams feel so strongly about getting usability and user experience right, then of course we would fully support them in doing so.

My concern with what appears to be a rise in DIY usability testing is one of bias. One of the main benefits our clients get from using us is that we’re independent (combined with the fact we’ve been usability testing for nearly 10 years now).

Our word of warning to all those people looking to test their own projects is don’t underestimate the power of bias when testing your own stuff. When we come into a project and observe users interacting with a product or service we don’t have any of the baggage of internal politics, why it has been designed the way it has, who made the decision to put that button there, why its not possible to do this. We simply see things from a fresh, independent perspective which allows us to really see what’s going on.

When a project team comes to observe us testing their product or service with users, at the end of the day when we talk about the findings what they saw is often quite different to what we saw. They saw the detail rather than the bigger picture, they picked up on evidence to strengthen their own pre-existing beliefs, they played out discussions and arguments they’d had when designing it. We didn’t. We had the luxury of seeing what was really happening.

Not being able to see the wood from the trees is something we can all identify with at times. When we are in the day to day detail its really hard to step back and see things from a new perspective. Testing the project you’ve been working on carriers the danger that you may just see what you want to see. You may see things that you instantly dismiss because of the history of how it has been developed, but the real key to improving the experience may be hidden here and you simply can’t see it. Sometimes it takes someone else to spot the patterns going on right in front of your eyes.

Overall the increase in DIY testing has to be a good one because ultimately the winners will be the users. An increase in awareness and appreciation for improving user experience is something we would fully support, so for people with no budget to bring in independent consultants we’d fully recommend giving DIY testing a go. But, DIY testers must be aware of the dangers of only seeing evidence to support what they already believe to be true. Sometimes an independent expert review can be more valuable than an DIY usability test, but that’s a post for another day.

Is your perception of usability in your product or service accurate?

Related services: Usability testing, and User experience audit

You only really notice the usability of a product when it’s not there. It’s very easy to come up with examples of poor usability, but for the most part, people don’t usually know the reasons for why one product is easy to use, and one is difficult and frustrating to use. Well, it doesn’t happen by accident! Most of the great products out there that we enjoy using have been through intensive user experience design and usability testing.

Here’s our ten most common reasons for why a product has poor usability:

1) Too much focus on features and technology

Many projects start off with project leaders and stakeholders having a strong desire to use latest technology or to develop a product with endless features. Feature development and testing are given a high priority and will often have a dedicated technical team responsible for them. The projects which go wrong are the ones that fail to balance these features against what users really need. Instead user requirements are an afterthought thrown in towards the end of development when much of the interface has already been developed.

2) Designers and developers ‘scratch their own itch’

In absence of any contact with real end users, designers and developers have no option than to use their own experiences as a guide.  They end up designing the system according to their own capabilities, understanding and beliefs. Often they will be so deep into the project that they rarely question their decisions. If it works for the way they would use it, then that is good enough.

3) No-one has considered what people really need to use the interface for

It’s easy to get caught up in the detail of a project and immerse yourself in the complexities of how to make a product work well. Sometimes, a project team can be so focused on the inner workings of the system that they fail to step back and question their design decisions from a user perspective. Understanding what users really need, and what situations they are likely to be in when they use the product can completely change the direction of the design.

4) The person with the final say has little or no interface design experience

Often, we will come across a competent and well meaning project leader responsible for the end product who has to make the call on how the product looks and operates. More often than not, this person has little or no experience of user interface design and unwittingly makes decisions without fully considering the impact on the users.

5) Too much focus on quantitative measurement

When a website is doing well, you’ll hear the project team talking about numbers. The number of unique visits, the number of conversions, the number of page views and so on. Unfortunately, the usability of a product or website is not so easily measured. Whilst project teams may know they have a problem with basket abandonment, or low page views on key pages of the site, they rarely understand why users behave the way they do which is key to understanding how to improve usability to fix the issue.

Part 2 of the 10 most common reasons for poor usability.

Do your products or services suffer from any of the most common reasons for poor usability?

Related Services: Customer requirements capture, Usability testing, and Customer experience research

I paid for a train ticket over the counter yesterday. As I completed the transaction I nearly walked off leaving my Debit card in the PIN machine. As I turned back to the machine to retrieve the card the chap behind the counter said something along the lines of, “That was lucky. We’ve already had three people leave their cards here this morning.”

Three people, this morning, have walked away leaving their card in the machine. Can you imagine arriving for a day in London and realising you’ve left your Debit card somewhere? Pretty stressful huh?

If your customers are suffering – take action

So having already experienced people leaving their cards, would it not be courteous to remind customers to remove their cards after the transaction?

Since Chip & PIN, all organisations have had to invest heavily in installing new equipment to cater to the new technology. However, I can’t help but ask myself if some of this technology either hasn’t been thought through properly, or is not being used properly.

Technology shouldn’t create customer experience issues

If the staff working behind a counter are unable to see the Chip & PIN machine it would be useful for their screen to inform them that the card has not been removed. They can then prompt the customer. Like most ‘simple’ fixes, it becomes less simple to fix once the technology is complete.

If the full customer journey and scenarios are planned and mapped out prior to build, these minor details will be catered for. And if customers are introduced to the project early, to test a prototype, the barriers will be highlight and dealt with before these ‘simple’ issues become costly fixes.

Do you involve customers in your project process early enough?

Related services: Customer Journey Mapping and Usability Evaluation & Testing