Oracle Communications Customers: What Kind of Documentation Do You Need?
By joesciallo on May 09, 2013
Oracle Communications Customer Advisory Board (CAB) Provides Some Answers
In reading Scott Miller's Road Trip! InfoDev Goes to CAB post, I was struck by one of the answers he got to the age-old question from techwriterdom, "Just what exactly does a customer want in documentation?" Answer: More info on "operations."
In my mind, when customers talk about "operations," they mostly mean this in the context of the operations end of the business: having a document that contains common administrative tasks for their operators on the corporate help desk, who need to quickly triage and resolve "operations" issues that come up. Indeed, the idea of creating a Communications Suite "operations" guide has long been in the back of my mind.
So, let me put Scott's question out to Unified Communications Suite customers: "Just what exactly do you want in documentation?" If your answer concurs with what Scott found out at CAB, that you do want something more along the lines of "operations," perhaps we should start a dialog.