Maximo Open Forum

Hi - I'm trying to take a snapshot of how most Maximo Admins set up their reference library for End Users. These are documents Maximo Admins may put together after end user training as a reference for end users - e.g. "How to create a Work Order", "How to Schedule a Report", an explanation/summary of what a custom report is presenting, etc. 

I've seen basically two styles of presenting these documents to end users: 

1. A set of all encompassing documents that includes all facets of that topic area - e.g. Purchasing Manual.
2. Indivdual documents that cover a specific topic - e.g. KB Documents. 

I'm curious what most of you have done and what challenges you've encountered with using that style of end user documentation. I've been using one of the systems above and thinking of switching to the other. I don't want succumb to a "grass is greener on the other side" trap of where I am today, so I'd like to hear what others have done. 

I can't speak as an End User, only as an implementer and what some of our End Users have preferred over the years.

Generally, I see a lot of End Users prefer Option 2. Smaller, bite-sized documents that cover specific functions within the app as opposed to thumbing through a larger manual. I've used Microsoft Publisher quite a bit to attempt to fit as much information, screenshots, text, etc. onto a single page that can be laminated and kept near the keyboard.

This is obviously more preference and not a "fits all" thing. I've seen both work. But generally, I see more preference toward the smaller, cheat-sheet style documents than larger manuals.

Hope this helps,