Any large content migration can drag you into almost endless complexity – keeping up with conflicting and rapidly-changing requests and trying to make progress efficiently according to schedule. Here are four best practices to guide your approach to collecting requirements for a large content migration. When are requirements not a moving target? You need a Requirements Repository. Publish…
Cloud Services, especially for document management, present interesting legal and regulatory issues, such as national jurisdiction over the stored information. I’ve posted a few musings about the issues but I am not seeing obvious conclusions yet. Rather than posting minor comments one-per-link, here is my collection to date.
An email policy is crucial to define clear limits to personal use of a firm’s email system, and to establish the right to monitor email. This post describes several key points and summarizes best practices.
Adoption problems? Don’t assume it’s all “about the training.” When a consultant or IT starts to blame a user’s lack of training, it’s often a warning that the system is not accommodating that user’s way of working. It should be possible to have it both ways – minimal retraining and also meeting the business needs with the software deployed. Along the way, you balance the three aspects of project effort, user impact, and business value.