ORM principle: If you create an information vaccuum, Google will fill it!
A couple of weeks ago I attempted to install the e-commerce plugin for Wordpress, developed by Instinct Entertainment.
I found it hard to understand, let alone implement it and got stuck. Like a lot of current software development and social media sites, there was a distinct shortage of simple ‘how-to’ documentation. It’s as if you’re supposed to just use Google and piece it together from the shards of information you find there.
So, I went to Google.
The first thing I learned was that there was no guide to installing and using this plugin. The plugin had loads of mentions but they fell into one of the following three camps:
1) Highly specific, technical discussions (useless to a beginner like me)
2) Requests from beginners for some kind of guidance!
3) Angry people complaining about the lack of support for the product!
Of course, none of this information solved my problem and I ended up as one of the 3rd category, blowing off steam on somebody else’s blog out of frustration. I posted in a thread where several people had made comments about the lack of support for this plugin - and in which Dan Milward, the plugin’s developer, had commented also.
The blog’s owner gave me a telling off for using her blog as a sounding board (understandably!). On the plus side, Dan came back to me as result of that posting and offered some help which, it turns out, was the solution to the problem.
But the real issue is the fact that I ended up there in the first place.
The point of this case study isn’t to be critical of Instinct. They’ve made a great plugin which I finally got working and which I recommend to anyone. However, by not documenting it they created an information vacuum that Google was only too happy to fill with stuff that was never likely to do them any favours.