Posted on

More features, lesser product.

Before I start let’s be clear: product development is not an easy pursuit. If it was then, as they say, everyone would be doing it.

Although at times it can feel like everyone is doing it. The number of apps and online services jostling for our attention is overwhelming. When faced with precisely 100 results (at time of writing) for “to-do app” in the App Store, where do you start? And as an app producer how do you make your product standout in such a crowded market? It’s understandable if your conclusion is that the app with the most features wins.

My favourite run-tracking app changed recently (don’t worry – this isn’t a glib excuse to squeeze in what an accomplished runner I am. I’m not. I run short distances, infrequently. And slowly.). After finishing my run, instead of simply recording the details as normal, a new message popped up. “Share with friends!” it said.

For the reasons outlined above, I had no intention of sharing the details of my run with anyone. So I bypassed the invitation with a couple of taps. And now, much to my chagrin, I have those extra couple of taps to perform every time I want to record my run and get on with recovering from my exertions. So why the extra feature that I didn’t want?

The fact is that many users will want the feature, and introducing a community aspect (or in the case of the running app, a competitive aspect) can create an additional hook that takes engagement with the product to a new level. But when does “feature rich” become experience rot, and how do we stay on the right side of the line? More is better right? Therein lies a minefield for the budding product owner to negotiate.

At Fathom, we are firm proponents of a couple of frameworks that help bring objectivity to the feature-pruning process. The first is the Kano Model, dating from the 1980’s, which applies three categories to features – dissatisfiers, satisifiers and delighters. ‘Dissatisfiers’ are features that, if absent, cause frustration. These are threshold features, must-haves. ’Satisfiers’ are central to the product’s function, the core features. ‘Delighters’ are those additional elements that differentiate the product from the competition.

By categorising potential features along these lines, prioritisation follows naturally. Make sure dissatisfiers are firmly in place, that satisfiers provide excellence in user experience, then – and only then – move on to delighters. In other words, don’t shoot for delight if you’re not providing for basic needs.

So what to do when you have a whole host of delighters? What if you have feature after feature that you are convinced will take the user experience to new heights? Well, chances are you now have a bloated product.

I have a Swiss army knife at home; great little tool to have around the house. However if I need to tighten a screw, I don’t think “now where’s my Swiss army knife?”. Similarly, next time I need to gut a fish (it could happen), I’ll be looking for a specialist tool.

And this is the dilemma. Do you want your product to be a swiss army knife, not specialising in anything particular? Or, do you want it to be a scalpel – clinical, with a singular purpose, and built for the job.

Irish entrepreneur Des Traynor is doing great things with his CRM web app, Intercom. He’s also a great contributor to the thinking around product management. According to Traynor, healthy product management is the willingness to drop features as well as add them. But which ones to drop Traynor’s approach is simple. There will be a natural scale of features which runs from those used by most users, most of the time, to those used by few of the users, little of the time. It is the latter features that need pruned in order to keep a product lean and relevant.

Whenever difficult decisions need to be made (and in the world of product development, there are very few easy ones), we don’t have to resort to guesswork. Applying some rudimentary classifications to features can help you see a product through the customer’s eyes. Not everyone loves your product as much as you. Get over that fact, and you’re on the way to better decisions about its future.

Posted on

One size fits none

Who doesn’t love easy answers? Don’t we all feel good whenever the way forward comes quickly to hand?

With less effort, pain and outlay involved, the lure of easy answers is such that we tend to place undue emphasis on initial conclusions. This cognitive heuristic is called ‘anchoring’ or focalism, where we rely too heavily on the first piece of data we’re exposed to. Where the information is in line with an existing belief or preconception, confirmation bias simply compounds the issue.

Psychology aside, often the easy answers we seek are expediently classified as ‘best practice’. Indeed, when we ask “what is best practice?”, it can often be a thinly-veiled substitute for “what’s the easiest answer?”. The same question can similarly mask sentiments such as “if it’s good enough for company X, it’s good enough for us.”

Ten or twelve years ago, whenever a tricky decision point was reached on a website project, it wasn’t uncommon to hear someone chip in with: “Well, what do Microsoft do?”. The inference was that a) Microsoft had all the right answers (it didn’t) and b) that the context was the same (it almost certainly wasn’t).

‘Best practice’ can be an excuse for all manner of evils. Less than two years ago, the use of infinite scrolling – where a webpage would continuously load new content every time you reached the bottom of the page – was running rampant. It was a trend, and one that became de rigueur for any new website that wanted to appear ‘with it’. No doubt somewhere at some point it was referred to as best practice. But like any trend it is increasingly being left behind as we discover lots of sound reasons why it is bad practice. In the case of infinite scrolling, it meant that the website footer – use of which is definitely best practice – was forever just out of reach of the user.

No sooner has one best practice established itself than extrinsic factors change, and something else (albeit not necessarily better) has come along to take its place. What we call ‘best practice’ evolves in parallel with technology, user behaviour and established norms across industries. It never follows trends blindly. Sometimes trends are completely at harmony with firmly established principles. Sometimes they are not. And so it is with best practice.

There’s an old meme in the design industry that goes something like this: Good. Quick. Cheap. Pick any two. Meaning: good, quick design won’t be cheap, and so on. To paraphrase this for user research and customer insights: “Easy. Quick. Right. Pick any two.”

Whenever best practice is referenced as rationale for decision–making, the immediate follow-up should always be: “Okay. But is it best practice for our customers?”. Context is everything. Easy answers might be cheap, but they won’t necessarily be right.

Learning from others through benchmarking, both within and outside your sector, is an important element in establishing a direction of travel. However research and validation with customers are the true path to success.

Don’t let a quick and easy path to answers under the guise of ‘best practice’ either stifle your organisation’s chance to innovate and excel, or inspire outcomes which simply mirror your organisation’s in-house desires. The path to the dark side this is.