We just celebrated eleven years of growth and leadership in the field of user experience, with a party for our staff and clients.

Since we've recently redecorated our offices, we thought we'd host the party there. It gave us the space to create a mural about the history of Flow and put up photos of past projects. A game of PS3 Rock Band provided a great interactive experience too.

Clients and staff enjoy drinks in Flow's newly-decorated offices

A lot to celebrate

Flow was set up by Meriel Lenfestey in 1997. From humble beginnings in Meriel's house in Stoke Newington, Flow has grown to a team of over 40 people with an annual turnover of £4 million and offices in London and South Africa.

In her speech at the party Meriel stepped us through the early years.

"In the 1990s, I could see companies jumping on the interactive bandwagon with websites that were often visually stunning, but virtually impossible to navigate - and therefore not commercially viable. I set up Flow to introduce User-Centred Design (UCD) to my clients. I'm proud to say that we're now one of the leading UCD consultancies in the world."

Lola and Ian. Mimi and Louise (on guitar). Flow's history in mural form.

User experience for a competitive edge

Next, Flow's Managing Director, John Thew, looked to the future.

"We've faced a challenging economy before and we emerged unscathed from the dotcom bust. In a risk-averse economy with tightening budgets, user experience becomes even more critical for organisations looking for a competitive edge. It reduces risk, increases loyalty and returns and reduced costs. Flow is well placed to ride through new challenges this and next year."

Thanks to everyone for coming. Thanks to all our clients for choosing Flow. And thanks to the talented folk who delivered great results and helped make Flow a success.

Designing an effective Microsoft Fluent/Ribbon toolbar is not for the faint of heart. You need to understand your users' activity in detail and plan a consistent overall experience.

I'm working on two WPF applications at the moment. For both, we have to decide whether to use traditional File/Edit/View menus or an MS-Office-style ribbon. It's not an easy decision...

A piece of the Ribbon, from MS Excel 2007

Pro: It appears to be built on a sound theoretical basis and Microsoft tell us they've researched it to death with hordes of real users. They also say they're planning to use it more widely.

Con: Key players on both the teams I'm working with are against the ribbon. They say "I use Office all the time and I really don't want one of those things on MY software."

Con: Jakob Nielsen raises an eyebrow that a number of the best new applications of the year use ribbons. He points out that Microsoft have not always come up with the best interface innovations in the past. Pro: But he grudgingly admits that maybe "the Ribbon has legs".

Con: Some surfing around yields plenty of blogs posts from frustrated ribbon users.

Pro: The techsmith team implemented a ribbon on snagit 9 and say their research showed it worked well.

Con: And a couple of bits of software that allow you to replace the ribbon in MS Office 2007 with a more traditional menu bar. That's a sign that there's a potential market of people desperate enough to pay to get rid of the ribbon.

So what's going on?

Good if used with UCD

My analysis: The ribbon is a decent piece of interface, but like most things in UX, it's hard to design it well. And to design it well you really have to understand your users' needs, behaviours and work practices.

That's because the ribbon tries to show commands grouped together based on what users are most likely to want to do. So in Word 2007, for example, there's a tab for mail-merge, and one for page layout and one for referencing, whereas in Word 2003 those features are pushed lower down in a more generic menu structure. If you get the groupings right, your users will always find the selection of controls they need right there in the ribbon. But if you misunderstand what they need to do, they'll get an irrelevant list and you'll get complaints.

Microsoft have got a lot of it right, but a bit of it wrong. And with Office's massive user base, an angry, vocal minority is still a million people or more.

Three ways to get Ribbon design wrong

1. Choose groupings that don't mirror real-world workflow. Read more

Drawing ideas in real time helps workshop teams imagine the future more effectively.

In concept design projects, we help our clients to envision how people will use technology in the future. But people who are experts in particular subjects (like their current customer experience or business process), are often less comfortable imagining or describing how things might become. Sometimes, Flow uses client workshops with graphical facilitation to help everyone get a solid grip on abstract ideas.

Augmented conversations

The idea of a graphical facilitation is simple to say, but harder to do: Draw everything that's being said in real time on gigantic sheets of paper. For maximum effect, paper the whole room, so that all ideas remain immediately available throughout the workshop.

An extract from a large mural created during a workshop

Here's some rationale...

• People have new ideas through conversation. Well managed conversations provide inspiration, as well as tests and checks that can help new ideas take shape.
• Conversations about complex things stop working well unless they are recorded as you go. A visible, running record of the ideas helps the team reach agreement and accept new ideas as building blocks for the next iteration of the discussion.
• Images are a very powerful record. Most of us can scan images quickly and find things again efficiently. They're also very information rich.
• Some concepts are more easily expressed in terms other than words. Mathematicians and physicists use mathematical notation. Architects use sketches, models and blueprints. Describing a building or a law of physics in words alone would be exhausting. Expressing complex, interrelated ideas behind a vision of the future will always be easier in pictures.

Visualising the presentation of a new system

The effects of thinking in pictures

I asked a couple of Flow's user experience consultants about using graphical facilitation.

"The future is unfamiliar territory, and that can be unnerving. Real time graphic output helps make everyone comfortable," Simon Hatch told me. "In a recent workshop, there was visible, engaging output even before we broke for lunch on day 1, and that really helped people feel they were making progress."

But as well as helping people see progress, the imagery on the walls helps people to think more effectively.

"It enables us to uncover and unpack things in a different way," explained Stuart Penny. "Seeing everyone's words represented on the wall helps each team member to absorb everyone else's ideas. And thinking in pictures reduces the effort of working an idea through and visualising its impact and consequences."

Smaller scale

Images are a great way of summarising and communicating the contents of a meeting too. We've been experimenting with writing up some of our meetings using images. You could see it as putting doodling to constructive use!

For fabulous drawing talent, we like to work with Cognitive Media.