Skip to main content

Conspicuous in their absence

If you're a tester then you'll no doubt of heard phrases to the effect of "That's pretty unlikely", "Our users don't do that" or "Thats a fairly minor browser". Its been blogged about before, and elsewhere. The argument is many users are niche, novice, confused or from different backgrounds / viewpoints / languages. These are realistic and probably correct hypotheses, for many situations.

From my experience, thats often where the discussion ends, someone makes a judgement call, and the issue is fixed, mitigated or ignored. More often, than not, its ignored. That decision should probably be a business decision, its their money. But can they make such a decision safely? We are asking for consent to 'not operate' or 'operate' on their software. To come to the right decision, they need to be fully informed. i.e.: Are we sure that the issue is indeed rare? Are they making a properly informed decision?

For example what if the issue is: that a website has several serious issues when viewed in a particular web browser, but not in a more 'mainstream' browser. When this issue is presented to the decision maker - How could it be presented?

A) Users of Browser XYZ ... can't play/view the video
B) A browser used by < 1% of our users ... can't play/view the video

Option (B) appears to give more information. But we are also including a reporting bias here. The users maybe only make up 1% of our users - because - the video doesn't work. They tried to use the site but gave up in frustration or found a competitors site had fully working video - and so took their custom there.

Whenever we try to quantify a user's behaviour as it appears to us - we need to remember that we are not seeing the full picture. Rather we are glimpsing just the tip of the iceberg. The users probably haven't complained about how the system crashes, when you use that feature, because they've learned not to use that button "as it's flakey". They'd love to use that button - if only it worked.

This survivorship bias is endemic in the world around us, not just in software development. How many times have you seen adverts that read something like "90% of our customers would recommend us to a friend!". The adverts fail to mention that most of the customers ran screaming away to a competitor, or failed to even get through a tortuous ordering process - leaving the rest who love the -one- working feature. Now that those other 'disgruntled users' are out of the picture, the few remaining customers may generally be happy.

Many companies even make it harder still to get the feedback they need. Rather than a Help page or Help button having an easy to find web-form to submit problems or questions - they hide or remove this functionality altogether. Thats free testing - by real users - providing details of actual real world bugs and requirements - being ignored in the belief that they are saving the company money.

From a testing standpoint, we provide information, and its important not only to provide the facts, but maybe some context and explanation as to how the issue reports might relate to real world applications e.g. for the above there is an option (C): iPhone users won't be able to view the video. Or: these users make up 1% of users here, but Google/Microsoft etc has them at 10% of its users, Why don't we see all of those users?

Comments

  1. Splendid piece, as usual.

    A related bias is in thinking about the symptom as being the problem, when the problem is something poorly understood and potentially far bigger. (I wrote about that here.

    Mark Federman wrote a wonderful piece related to the your notes on survivorship bias. You can find that here .

    ---Michael B.

    ReplyDelete
  2. It's hard for some stakeholders to listen to testers when profits are louder than our concerns.

    ReplyDelete
  3. Second link in the first comment is giving 404 error because it has quote symbol at the end . I removed the quote and this seems to be correct link
    http://individual.utoronto.ca/markfederman/VoiceoftheCustomer.pdf

    ReplyDelete

Post a Comment

Popular posts from this blog

A h̶i̶t̶c̶h̶h̶i̶k̶e̶r̶'s̶ software tester's guide to randomised testing - Part 1

Mostly Harmless, I've talked and written about randomisation as a technique in software testing several times over the last few years. It's great to see people's eyes light up when they grok the concept and its potential. 
The idea that they can create random test data on the fly and pour this into the app step back and see what happens is exciting to people looking to find new blockers on their apps path to reliability.
But it's not long before a cloud appears in their sunny demeanour and they start to conceive of the possible pitfalls. Here are a few tips on how to avert the common apparent blockers. (Part 1) Problem: I've created loads of random numbers as input data, but how will I know the answer the software returns, is correct? - Do I have to re-implement the whole app logic in my test code?
Do you remember going to the fun-fair as a kid? Or maybe you recall taking your kids now as an adult? If so then you no doubt are familiar with the height restriction -…

Betting in Testing

“I’ve completed my testing of this feature, and I think it's ready to ship”
“Are you willing to bet on that?”
No, Don't worry, I’m not going to list various ways you could test the feature better or things you might have forgotten.
Instead, I recommend you to ask yourself that question next time you believe you are finished. 
Why? It might cause you to analyse your belief more critically. We arrive at a decision usually by means of a mixture of emotion, convention and reason. Considering the question of whether the feature and the app are good enough as a bet is likely to make you use a more evidence-based approach.

Why do I think I am done here? Would I bet money/reputation on it? I have a checklist stuck to one of my screens, that I read and contemplate when I get to this point. When you have considered the options, you may decide to check some more things or ship the app. Either could be the right decision.
Then the app fails…
The next day you log on and find that the feature is b…

Software development is in the Doldrums

"Don't get off the boat."

"Seriously, never get off the boat," The instructor said, leaning forward and looking at each of us in turn.

"But surely if it's sinking..." We reply, somewhat confused and slightly incredulous. We've seen Titanic, we think to ourselves, we know how this sea survival stuff works...

"OK" He concedes, If things get really bad, "Get on the life raft if you can step-up from the boat to the life raft".

"But, But... the yacht is like 37ft long, Do we want to wait until that whole boat is lower than the life-raft? When less than 1ft of the yacht is above the surface? Meanwhile all the time the life raft is just there... floating happily alongside."

"Pretty much, yes," he said nodding.


That was about 15 years ago. Not much has changed since. The reasons are manifold. Firstly, the yacht is a decent shelter. The thin plastic of a legal minimum life-raft isn't going to protect you fro…