Poorly executed requirements gathering leads to outright rebellion in corporate online document management initiatives.
The requirements gathering phase of a project to implement corporate online document management can make or break the initiative’s chance of success. Poorly executed, it can lead to outright rebellion on the part of those expected to use it. A new white paper – and history lesson – provides fresh insight into how to conduct a successful requirements gathering project for document management."Document Management and Mad King George: A Cautionary Tale about Requirements Gathering,” puts the importance of understanding the needs and concerns of those who will actually use an online document management system – and thus are key to its eventual success – into historical perspective.
We have many fascinating lessons from history that serve as cautionary tales for our own leadership challenges. The same bad leadership principles that have historically resulted in botching a job still apply. Sometimes we just need to be reminded of what they are and how they apply to our particular situation. None of us have time to repeat old failures.
The white paper briefly illustrates how failure to understand the needs, concerns, experiences and challenges of those who will be most affected by a new online document management system inevitably leads to revolution in the form of rebellion. Then the paper goes on to outline very practical actions to take that help assure acceptance and success.
For a free copy of the report, visit http://www.egisticsinc.com and select Media>Brochures from the Main Menu.
If you have your own insights and opinions as to what leads to success or failure in the initial phases of a document management project, leave your comments below.
No comments:
Post a Comment
We welcome your comments and expect that our conversation will follow the general rules of respectful civil discourse. This is a moderated blog, and we will only post comments from bloggers 13 years or older that relate to topics on the CloudDocs Blog. We strive to review comments for posting within one business day. You are fully responsible for everything that you submit in your comments, and all posted comments are in the public domain. We do not discriminate against any views, but we reserve the right not to post comments. We do not post comments that are off-topic, spam, or overtly self-promoting.