Add your comments
DLS Archives
May 2012
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||
Essential Windows Apps | Do Not Track | Microsoft Office | SayNow | LibreOffice | Zeam Android Launcher | Dead Space iPhone | Firefox 4 Mobile | Firefox 4 Release | PlayStation iPhone App | Excel Tips | Android Launcher | Google One Pass | Dead Space | Google Cloud Print | Songbird for Android | NBA Jam | Internet Explorer 9 | Windows 7 Connector for Mac | Office Mac 2011 | IE9 RC
Reader Comments (Page 1 of 1)
(Unverified)Apr 29th 2006 10:21PM
At my company (Fortune 10) we have a CMS that has a publishing workflow that is so tightly regulated and over-complicated that well...I don't actually know how to add documents. And its in my job description. Reading isn't too bad (Livelink engine).
But I came to the conclusion that the tool just discourages people from writing documentation, which is a very bad thing. A wiki would be an obvious knee-jerk fix. I don't know however if the total lack of enforced structure would work in many corporate environments. But the lowered barrier to entry would sure help. Well who knows, maybe the people who today manage the workflow of Livelink and our change management process would instead be lurking 'Recent Changes'...