Why Business Analysis Fails the User Experience


We live in a world of opposites, or at least that is how people view the world. Previously, I talked about those that prefer either traditional, sequential waterfall software development or the more flexible agile approach. You also tend to find two polar opposites in the development of business applications in contrast to websites and e-commerce applications.  IT tends to attract those people that like to work with technology – and not people; whereas Marketing, where the whole point is to engage customers and interact with them, tends to attract those that like to work with people.  Yes there are exceptions but as generalisations they are true; I’ve worked on both sides of the fence and seen the differences consistently.  No wonder then that we find different worlds and tensions.  To get their websites done Marketing would sooner get their own team or outsource to design agencies who know the importance of getting across the right message, or customer experience in the fullest sense. This is all well and good in e-commerce but who will champion the corporate customer, the poor staff member with no choice but to be served by IT even when some of the systems they have to use look like they were designed by children?  We end up with a split between the user-oriented web/e-commerce sites that can delight their users (as well as sometimes frustrate them in their careless execution and lack of attention to detail) and business applications where the requirements are gathered and delivered to in a way that frequently fails to deliver to expectation. Have you noticed that the main difference in personnel is the presence of UX designers on the one hand and business analysts on the other?

Software development is full of business analysts whose job it is is to gather requirements, analyse them and propose solutions in consultation with technical staff.  It’s a very logical, rational process.  Business analysis is great because good analysts ensure a good coverage of requirements and system needs.  The problem with analysis is that it does what it says it does – pulls things apart, strips the engine to its component pieces to be comprehensive – but focuses less on how these parts are assembled and how people will make sense of them.  Business analysts are a bit like police – just the facts, ma’am.  In the functional specification (if there is one) there may be a flow diagram or two, clarification of fields on a form and so on but the design responsibilities often end up with the developers if only because no one has done the work up front.  In other words, a key part of the project hasn’t been done.  This approach is unthinkable in most product development practices where working hard to assess needs and validate designs is imperative.  The UX approach is to look at who the types of users are, their aims, their preferences and so on and what tasks these users need to do.  Personas and scenarios are modelled visually so that all project stakeholders can understand and comment on them.  This typically moves on to an information architecture/wireframing/visual design phase where key parts of the solution are prepared visually, again by designers who understand the requirements. These deliverables can also be reviewed and signed off by stakeholders before commitment to build so the users know what they’re getting and the developers know what they’re building.  Any scenarios can be reused to test the final deliverable which tops and tails the project quite nicely, ie testing the deliverables with the requirements.  In contrast, the traditional software approach is to test a list of functions individually.  Whilst this should also be done to ensure full coverage, what it fails to do is to evaluate how these functions work together, ie the user experience.

So, business analysts need a sea change in their approach and need to work alongside UX specialists to deliver user centred design.  Conversely, it would be good to see business analysts more consistently involved in the web/e-commerce world to ensure the job is done comprehensively (a lot of design agencies can’t be bothered to test in different web browsers for example – too boring I suppose).  The fact of the matter is that good software and web projects require both the detailed approach of business analysis and the holistic approach of user experience design to ensure that user needs are met both comprehensively and in alignment with real users in real life scenarios.

Advertisements

Innovating in Technology: Connecting the Old with the New Through Metaphor


Heavy!  But if you stop and think about it, the whole of our technological world is pervaded with metaphors, both verbal and interactive.  Metaphors aren’t just for writers but with technology it’s the hook with the now that takes people into the future and that’s the clever bit so I’ll call these ones ‘innophors’ (innovative metaphors) for now.

I’ve previously emphasised the importance of convention and familiarity with user experience but doesn’t this sound at odds with technology and innovation?  How can we innovate or differentiate if people don’t like change, if they only seek the familiar?  Familiarity comes in many flavours and the charge of technology and computing is so often through metaphor – to such an extent that the metaphor becomes the new reality*.  Think how much we scroll, cut and paste every day without paper, scissors or glue?  Does anyone care about that publishing metaphor?  How many people know?  Last time I talked about Excel and the spreadsheet metaphor that goes way beyond the balancing acts of accountants.  Maybe some of it was chance but I do wonder how many Excel spreadsheets are actually used for accounting purposes these days.  The keyboard is a metaphor for the typewriter and in 50 years most people that remember what the return key meant will be dead and gone – maybe along with the keyboard!  Now people expect to consume information in different ways and explore information spatially through touch.

In user experience design the lovely wireframe (a plain, low fidelity mockup of a web/system screen) is a metaphor for the initial shape of something, like a sculpture, before it gets built out.  Some metaphors are a bit unusual and you wonder at their effectiveness given how many people knew what wireframe meant in the first place!  It doesn’t matter in this case as the end user does not care so much as the ux practitioner but it does emphasise the importance of the creative concept and getting it right and knowing when to name it right.  Tim Berners Lee’s hypertext concept for the web is one of the greatest innophors ever invented and people quickly caught on to the idea of hypertext links and the implications for a highly connected network of information.

Ok, so what…..how does this help us?  It’s important because the gateway for change and innovation is typically through metaphor, be it the interface or the name of some service that relates to some previously understood idea but breaks it into a new one.  It can be as significant as tweeting on Twitter or as specific and non-verbal as flicking through album covers on your ipod.  The point for the user experience is less about something being new and more that it must be obvious.  If people don’t get the idea or the functionality then it’s no good, try again.  But this doesn’t mean that you can’t bring about radical change, it just has to make sense by connecting with people’s current understanding.

So whatever you want to bring about, design or conceive it must link to the now but it does not stop it being new.  Look to connecting a new idea to an existing one and use innophors.  People need a hook into the idea to take them on the journey and the concept – be it a name or a piece of functionality or a device – is what makes something take.  It has to make sense.  Keep pushing the metaphor into new bounds to define a new reality and user experience.

*Curiously, the metaphor can take over the original reality so you’re more likely to see a mouse in a plush office than on the street, we’re better at fighting computer viruses than real ones, etc.  It’s that lovely word ‘simulacrum’ that French postmodern intellectuals talk about in cafes.  I once spoke to my daughter about what we decided to call ‘cocktail’ words on the assumption that the colourful drink concoctions were called such things because of peacock tails but when we talk of cocktails we first think of the drink variety or we bend the word to some new end, cocktail of drugs, molotov cocktail, etc.  These things become meta-metaphors or something like that.  Amusingly, it turns out that I was wrong and that the origins of the meaning of ‘cocktail’ are not clear – which kind of proves me right!  It doesn’t matter what a word originally meant, it’s how we use it that counts.  Language and symbols should not just be seen as systems to help us map reality in some fixed and finite way but instead are tools to help us define new realities and new concepts (a journey in understanding courtesy of Ludwig Wittgenstein).  Symbolic power is so often the key to making technological innovations and doing them in a way that people understand.

The Joy of Excel


Yes it’s unusual to talk about UX away from web and ecommerce but so what, Excel is UX on legs.  Ok that’s two gratuitous puns too many but I was writing about risk management last time and it does that to you.  If you like to divide people into two camps (I know, there are those that like to do this and those that don’t) there are those that admit they love Excel and those that pretend otherwise – but everyone likes it – or loves it.  And yeah I know about Lotus 1-2-3 and I’m old enough to have used it but that’s history, get over it.

Excel is the perfect partner to Word, as numeracy is to literacy.  In fact, they could have called it Number but maybe they were wise to the fact that the concept of a spreadsheet (the huge bits of paper that hardcore accountants used to use to do their numbers on) would become a metaphor for what is in fact tables and records and things like that.  Metaphors are a big thing in computing but more on that another time.

It feels like the whole world uses Excel, in their work but also at home, even if that isn’t quite true.  Yes people still use it for balancing accounts but also for lists, managing projects (who can be arsed with the bastard child that is MS Project anyway), databases, reporting and anything else you fancy.  In fact, this versatility creates an End User Computing risk in some organisations as smart people in the business start to build non-supportable critical applications – ok UX can maybe create risk too!  People use it at home also – for balancing accounts, managing projects…the same things actually.

So what’s good about it?  The concept is great, columns and rows, lists and records.  You sort everything out, fair and square in nice little boxes and then do clever things very easily and then get to make it look good with charts and so on.  I’d bet there’s a lot of people who avoid going to parties to spend time at home on a pivot table.  Excel is easy to use but the fundamental concept puts you in control of whatever it is you want to do.  User Experience frequently takes account of putting users in control because they are people and people like control whether they admit it or not.  You want simplicity but you want control and sometimes these things seem at odds, ie simplicity = less functionality but control = more.

Giles Colborne of CX Partners wrote a great book called Simple and Usable which describes four strategies: Hide, Organise, Remove, Displace.  I like to turn these into the ironic mnemonic, HORD.  The key thing is to get shot of what’s needed and put occasional/first time functionality out of the way to retain simplicity.  This is what control means.  Over the years, Excel has grown and grown till its groaned.  Just how many toolbars were there?  The whole Office suite was exploding with functionality and something needed to be done, hence the move to the ribbon.  I’ve heard also that Microsoft got tired of requests for functionality that already existed so they made better use of the menu space by making it context sensitive.  The move to the ribbon in Office 2007 upset the hardcore Excelers.  Why move stuff?  Users were lost, for a little while.  I trust they did a proper information architecture research job to structure and label the information in the minds of the user.  But change is change and however good it was it was a major disruption to people’s habits.  It was a big step but it highlights the power of convention in usability.  If you’re used to it, it works, warts and all.  If you use Microsoft products then getting another one makes life easy because you get the layout and look-and-feel without having to think about it.  What’s best is not always ‘best’ in the eyes of the techy purist.  I think that simple fact, alongside compatibility and integration, is one of the biggest reasons why Microsoft dominates – it’s not just slick marketing.  Go on, mention the decline in Internet Explorer but face it, the controls are more on the websites than the actual browser so who cares.

Excel is probably the best thing Microsoft has ever done – and maybe will ever do.  They were lucky to popularise a great concept but they’ve done a great UX job on it nonetheless.  Whole businesses run on Excel (even if they don’t realise it) and whole households run on it too, from a simple list to a sophisticated database/reporting engine.  Excel gives everyone control and everyone the chance to be a spreadsheet geek; maybe the only thing it’s not good for is blogging.

User Experience Design as Risk Management


Exciting stuff, huh!  There’s no gags, puns, alliteration or other clever stuff in the title of this blog because it’s time to talk risk management which is – as you know – a very boring serious matter.  This blog looks at user experience strategy as a risk mitigation tool for web and software projects.

User experience is often miscast as usability or user interface design – which sound a little bit non-essential and nice-to-have.  Yes, UX encompasses those things but it’s the whole process that is important and sometimes misunderstood.  It’s about getting the deliverable right so I’m not going to talk much about usability or user interfaces here, just plain old projects.  And with projects come risks.  Sometimes risk is all that people understand and if you’re a fan of the psychology of behavioural economics then you’ll know about loss aversion.  In plain English, that means that people are more likely to be motivated to act if they think they will lose something than if they think they will gain something and risk is usually about losing something.  Which is why everyone loves, or rather hates, risk.  That includes project managers and rightly so.  So, let’s not sell the benefits of a user experience and instead sell the risks of not doing it.

Every project pack worth its salt has a list of risks and mitigating actions to ensure project success.  Risks come in many flavours but can include issues such as poor user adoption/loss of confidence, regulatory breaches, costly errors, loss of revenue, loss of reputation and so on.  Those risks can play out both internally and externally at an organisation and everyone wants to get the project right.  So, how do you get it right?  You go to the business or customer, ask them what they want, write it up in to a 72 page document, ask them to review it (which they don’t), call a meeting to talk them through it, chase them to sign it off (which they do – because they want the project done), maybe write a functional spec, hand it to the developers, months go by and, fingers crossed, test against the functional spec and done!

That’s a cynical but not wholly inaccurate take on the so called ‘waterfall’ software development method that has a linear set of steps.  Best of luck to everyone involved.  Unsurprisingly, it often doesn’t deliver to expectations.  People are now starting to turn to ‘agile’ because of this very fact – they have concluded that waterfall doesn’t work.  Agile is an iterative, little and often, show-and-tell approach with lots of questionable terminology (‘sprints’, daily ‘scrums’, ‘war rooms’) to make the new thing sound clever.  Naturally if you show a system bit by bit to users then you can clarify the direction of development which is great to ensure correct delivery but it can be hard to control scope and get the thing finished.  It’s also fun and removes planning and documentation so those that like to avoid such things love agile.  In other words, it manages some risks but raises others.  In some cases agile might work well, especially for an innovative piece of product development but for many projects it just misses out the steps and the clarity required to get things done properly, hence it’s often dubbed ‘fragile’.

So, nothing works.  Ok ok, I’ve been rather unfair about both these methods but the methods aren’t the point – the approach is.  I know waterfall can work well and someone must have seen agile deliver to keep on doing it.  However, the fundamental issues when projects do go wrong are simple – not getting the requirements right, not getting the design right, not getting sign-off right, not doing testing right, not communicating right.  I’d love to see these risks in a project pack – instead of lack of resource and the usual ones PMs feel they ought to put in.

This is where user experience design proper is meant to help: UX is doing waterfall or agile or whatever, right.  A user experience approach entails getting into the shoes of the user, identifying the types of user you have and noting their needs and preferences, observing them using a current system or process, interviewing them, understanding their decision-making processes, etc. It doesn’t have to take that long but proper research needs planning in to the project.  Once you start to gather this information you can clearly map user types (personas) to processes and draw visual diagrams to represent this alongside written scenarios.  These are the sort of documents that users will understand – and will sign off for real.  Requirements done then you can start to design to these requirements through standard techniques such as wireframing (as well as functional specifications).  There might also be a need for information architecture to help organise and label information in the most useful way.  This information should feed into the wireframes and a site/app map if required.  A visual design exercise may then come into play (especially if it’s a web application).  Again, visual designs can be signed off by users before commitment – even if the build has started.  Use workshops to present and validate the design, not to brainstorm and put the onus on the users.  Tweak it and build it and test it, against the functional specification but also against the scenarios and get the users to run through the scenarios – and observe them.  If it’s not obvious for them to use then it’s a problem.  Dig deeper and make changes before final testing commences.  Write a Quick Start Guide to help people understand the capabilities.  Again, ‘test’ it with a few users.

What’s good about this approach is that the users are engaged throughout the process to mitigate against the risk of designing to abstracted requirements.  The users are also involved in the design, sometimes in the information architecture or sometimes in discussing options around wireframes and designs.  There will be few chances for surprise and disappointment.  Also, with a defined set of users you’re doing change management by engaging them and getting them to sign off on tangible deliverables, helping to communicate the change and helping them to own the design.  In other words, the chances of adoption are greatly increased.

So, UX helps you get the system right because website or application building is a design process that needs to go through steps.  When you use words like architecture, design and build then the clue’s probably in the metaphor – it’s not too unlike building a house.  Waterfall and agile are sort of besides the point.  Only the largest corporates are beginning to understand the need for UX for software projects but you’ll see this approach catch on hugely in the next few years so it’s worth catching on before you have to catch up.