dancingmango

Is there any reason to navigate around the Apple website using traditional navigation mechanisms when you’ve got search functionality so elegently implemented?

It sounds clichéd and old hat, but it is true. Truer now than ever before; the web is an enabler for new ideas. It provides you with the tools for disruptive innovation. Sadly for too many organisations it has become a hindrance.

A recurring theme with many organisations is the length of time it takes to take an idea to market. Especially in retail financial services, where you would expect lead times to be short it is not unusual for innovations to take a year to implement. This seems crazy, it’s not as if there is a physical product to manufactured.

So where are the hold ups? More often than not, they are rooted in the organisational structure. Innovative products often cross business boundaries; whilst customers only see the a single brand, different product teams only see what they are responsible for. They have own objectives that often conflict with other parts of the business; gaining agreement and consensus across all parties can often be a time consuming and painful experience that slows and often kills innovation.

Then there is the technology. Changes to systems have to be scheduled (along with every other request). Unproven ideas are put to the back of the queue. The business starts to perceive IT as a hindrance rather than an enabler and lines of conflict are drawn up.

Channel is the next hurdle to cross. Typically a face to face channel or telephony will be easiest, but getting something on the web? Now a new area of the business needs to be involved, the Internet Channel Team who interface between the business and IT. They’ve got to design web pages, get the creative done, produce requirements for technology to build (and schedule into deployment for which the dates are even further into the future), do usability testing… Long lead times are inevitable.

And then, before the innovation sees the light of day, someone new comes in to rationalise the product portfolio, the innovation doesn’t quite fit in with their new priorities and it is quietly ditched. This half hearted attempt at innovation has taken a year, cost in excess of a million and has come to nothing.

There has to be a better way.

There is. Do things at speed. You can start by sticking some amphetamines into ideation phase. Someone’s got an idea; identify who has a vested interest in it succeeding (or failing) and get them into a room to thrash it out. This doesn’t need to take long. Workshops are best limited to 90 minutes at a time (after that people get Blackberry withdrawal symptoms and loose interest). But if all the stakeholders are geographically dispersed, a structured day’s off-site might be the best solution. Avoid letting people dial in or video conference, this is one meeting where people have to be there in physical presence. Also avoid having too many people in the room, especially when forming ideas (there is a trade-off between having the right people and too many people to make the process unmanageable). Start with the users, the customers, the people whose lives will be changed by the idea. Scribble out personas -describe who they are, what their goals are, the perceptions of your company, of technology. Print out pictures of people that represent the personas, rip out photos from magazines, anything to bring them to life. As the idea takes shape, turn it into pictures. Draw out the customer experience. What would the persona do at each stage. Far better to do this than write it down in a document that can be open to interpretation. Illustrate the touch points. What does technology need to do. (Can we be pragmatic and use roller skate implementation rather than getting bogged down in an integration quagmire?)

Now is where it gets interesting. There once was a time when you would need to invest time and money into producing a heavyweight business model and business case for the innovation. You still need a business case, but at this stage it probably doesn’t need to be too robust; make some basic assumptions then test it. All too often business cases are built on flaky assumptions; build something quick, test it and get real data to build your models on. Again, this is about doing things at speed; a couple of weeks after the first workshop there is no reason why a small team of developers can’t be actually building something to bring the idea to life. So the team is using Ruby on Rails to build a proof of concept. There may be disquiet that this doesn’t fit into the current technology stack - doesn’t matter, it is a proof of concept. Six weeks later the proof of concept is done. It is not a static, prototype that demonstrates linear page flows, it is fully featured and fully functional. It can be usability tested (but more likely you were doing that on wire frames alongside the build). What then? In two months you’ve taken your idea and turned it into something tangible.

Why not put it into the market for real. Whilst IT might not want this Ruby “thing” on their stack, that doesn’t mean it isn’t possible and can’t be done. Large organisations have a testing ground of consumers inside a secure environment - their staff. Use them to beta pilot the idea? Friendly customers are delighted to be part of product development - put it out to a small and selected group of customers, and have some smoke and mirrors processes to handle fulfilment. The objective is to prove the viability of the idea, get data to make informed decisions and make your collective mind up quickly. To fail fast or succeed cheaply.

The traditional pattern for the on-line banking “make a payment” GUI is:

• What you are about to do (text)
• Select “From account”
• Select / enter “To account” (Beneficary)
• Enter Amount
• (Optional) enter “when” (you want payment to be made
• Confirmation (“you are about to pay this amount from this account to that account. Are you sure?”)
• Post process confirmation (“You have paid this amount to that account from this account”)

So here is a question. Are those confirmation screens really necessary. What if you made your payment, hit the “OK, make the payment” button and it is done. An alert appears (like when you do something with google) that says what you have just done with an “undo” call to action (“I’ve made a mistake, I don’t actually want to make that payment afterall”). The assumption there is that the user knows what they are doing – we assume a happy path with the opportunity to go back rather than placing “confirmation” barriers to completion which are probably unread anyway. There will be considerations of when the payment is actually made; does it hit the clearing systems when the user hits the pay button (not that it ever does anyway). Does the undo option disapear after a period of time (i.e. five minutes), or when the user navigates away from the page the alert appears? But let’s leave the implementation to one side.

I like the idea of undo instead of confirmation. However, I have a hunch that it will not fly when we show it to customers, because people are so ingrained with the “confirmation” dialog. I’m waiting for the response “I’m not sure I like that” from customers who use the current website, because it different, unexpected and is wholly inconsistent with what they have today. But what they have to day is based upon legacy technology and the immaturity of the platform.

So a suggestion. Let people undo. Tell them what they’ve done after they’ve done it (positive feedback), with the opportunity (in the banking environment in a time boxed period) to rectify their errors or change their minds. Do away with confirmation dialogs. Everywhere. (Do you want to save this document? - instinctively I say “no”. It is only later that I realise my mistake…) Here’s to a web that places minimal barriers to task completion.

A couple of weeks ago the share price of BP plummeted because the CEO “did a Ratner” and criticised the company. Essentially he was criticising his company for being inefficient. “There is massive duplication and lack of clarity of who does what”. Yet is this so uncommon? Spend some time in most FTSE 100 company and I’m sure you’ll soon discover duplication, inefficiency and waste. It seems to be the consequence of scale; a growing company gets organised around business units and these inevitably become inwardly focussed and support a silo mentality. These silos soon cease to have a single minded focus upon the stakeholder that matters most, the customer, and instead focus upon the good of themselves.

For example, the organisation may have a number of different products. These are organised into product lines with each product having its own targets. The product lines then start competing against each other; it is not in the product managers interest to consider anything outside increasing the profitability of her own product line. So if this means cannibalising the market share from other product lines so be it. Her bonus depends upon the success of her products.

Undoubtedly she needs IT support. Here comes more inefficiency. Whilst a similar technology may be used by another part of the business, it does not entirely meet her requirements. So a new product is built. Throw in outsourcing and inefficiencies are abound. It is not in the interests of the vendor to strive for simplicity. (Read PG’s excellent analysis of the problem with outsourcing IT).

Then you’ve got “channel” The Web Team, the Mobile Services team, Telephony, Retail Stores… Again, each has their own P&L and targets, each competing against each other. The talk may be of a seamless cross channel experience, but when the staff in the Stores are remunerated based upon sales they make, what is the incentive to direct the customer to the website to complete the transaction? Better loose the sale than do that.

Once a product has been sold it requires support - another bunch of stakeholders with their own (muffled) agenda. Customer acquisition is more costly than customer retention, yet the focus is usually upon the former, regardless of how wasteful this may be.

And what of the “Gold” team, looking after our “best” (read most profitable) customers. Another bunch of stakeholders with their own priorities, requirements and bottom line. All different parts of the organisation competing against each other. It’s not a team effort with a common goal (maximising customer and shareholder value), it’s a battle lining business unit against business unit with a common enemy of IT.

Is there an answer to organisational inefficiencies? There’s a solution to everything if you’ve got enough time and money. But for a start I’d love to know of a company that has scaled and has maintained a true focus upon the customer. That doesn’t internally compete for their customers share of wallet. That is transparent and shares knowledge effectively, where duplication is unknown. That uses IT strategically to support the business meet its common goals. An organisation that remunerates according to total value earned regardless of where it was fulfilled. An organisation that, regardless of the fluff in the annual report really does deliver value for the shareholder and customer, and waste is the common enemy.

SEO is high on any on-line marketeers agenda. There’s plenty of agencies about that can give advice on how to leapfrog up the google rankings, but before you do that, take a look at Website Grader. A neat tool that grades your site, gives you insight into the search engine world and tips on how you could improve your ranking.