Summary
Barriers to taking up a product or language are much smaller than people think, like the almost-invisible height difference in a sidewalk (pavement) over which you trip.
Tool vendors and proponents of languages find themselves staring in disbelief at an apparently irrational rejection of their favourite.
Advertisement
G'day
As an Aussie of British origin, I have to confess that American is a second language for me. Whilst I will try to choose familiar words, expect to see the odd bit of Queen's English colouring my writing. I will also try to provide translations where necessary.
I thought I'd start this blog by discussing one of my pet theories, known around most of my workplaces of the last few years as Andy's Theory of Barriers but which I'm now going to name publicly as the hopefully-more-memorable The Sidewalk Tripping Theory of Product Adoption. (TSTTPA)
The basic principle is very simple and I suspect anyone with a marketing background will recognise it. I came to the idea through my readings in software usability coupled with some marketing (driven by micro-ISV needs).
It is common human behaviour and seems like a very trivial issue but I think our community suffers from a particular hubris that makes us very vulnerable - geeks hate to seem irrational.
So, when you catch someone in an apparent irrational dismissal of XX, the worst thing you can do is point out the irrationality. With all of their superior intelligence, said geek will start inventing reasons for their rejection.
The more you push, the greater the pile of negatives heaped upon this hapless product.
When you have run into a case of TSTTPA and inadvertently triggered a defensive reaction against Product X, to get the defendee to try X again you have to:
go away for a while
come up with an unrelated set of rational reasons why it is worth them trying the product
find a way to get buy-in so they are emotionally invested in your set of reasons from 2. without realising they are related to Product X
wait
make them aware of how Product X is a great example of 2's rational features and might therefore be worth investigating, despite their completely legitimate reasons for rejecting it in the first place.
Whew! what a lot of work (and faintly distasteful manipulation it may seem too).
The simple answer is to look ahead for potential barriers on which your community may trip. The sort of nose that works for this is a bit like you need to develop for user interface design, anticipating areas that will confuse users.
There's a formal name for this kind of thinking, which I came across a few years ago and which won Kahneman a (joint) Nobel Prize in Economics. He calls it Prospect Theory and it is also also known as Behavioural Economics, illustrated often with the story:
Suppose that you are planning to drive across town to a
hockey game when a huge snow storm hits. You have paid $35
for the ticket so you decide to go to the game anyway. Two
weeks later the same team is in town playing the locals and
you again plan to attend the game, when another storm rages
into town. This time you have been given a $35 ticket by
a friend, and you decide not to go. Since the gains
(enjoyment of the game) and costs (driving across the city)
are the same in both cases, traditional theory suggests you
should make the same decision in both cases.
Welcome, Andy! I'm glad to see you here. I remember you from OOFile and - was it THINK Pascal? - it's been a long time. I remember finding your developer diaries very helpful.
Previous Topic
