As we wind down the 10 days of Blogging past, we get to review a rather enigmatic post in "duration not active: A Tale of Two Articles" from 1/3/13 with 91 views.
This post captures two very different My Oracle Support articles, which may not strike you as a surprise if you've been on MOS for any period of time, but it strikes me as interesting that this is in my top THREE posts all time. Why is that? I think this is another reflection on what I've been trying to do for the last year, and that is present relevant and NEW content on a regular basis! Sure, but still why would THIS get a lot of hits? Well, this was a new error that popped up after we went live with a new Exadata BP so the assumption is this is an unintended consequence that many different people have seen after getting this BP in their system as well. We never saw any negative results or impacts upon our system due to this message, so I have to believe this is not really a cause for concern but many other people have seen it and likely searched the web for experiences that others have had with it.
Additionally, this gives us a good insight into KB articles and how they can be 100% accurate but not really give any content or help to your end user. Don't let your KB articles at work get like this, or your blog posts, or your tweets, etc. Sometimes the best examples to learn from, are those that aren't the best examples in the first place.
No comments:
Post a Comment