re: Why Tech Projects Fail: 5 Unspoken Reasons
I have to very whole-heartedly agree with point 3. It's not necessarily about multi-year projects, but about finding the proper solution when a need is identified.
For example, one organization that I'm quite well acquainted with has multiple "Enterprise Knowledge Management Platforms". Okay, so what's the problem with that? Cohesiveness, or lack thereof. Let's start from the beginning - when a new user gets on-boarded, they're bombarded with a list of URLs and sets of credentials for all of these platforms. As they progress, they start using the platforms and keep asking questions about where to find X, Y and Z. Meanwhile, X, Y and Z are on different platforms, but the user has to gather all of the information together, synthesize and report - thereby creating more content and having to choose which system to use to store it, since it has to be somewhere that everyone can get to. Now, wasn't the whole idea behind using an Enterprise Knowledge Management Platform to have a SINGLE place in the enterprise where all users can find and store all of the information that they work with? Instead, you have users who have to search through multiple, disparate knowledge sources - even ones that are considered depricated, legacy, "soon to be retired", etc. Meanwhile, all of them keep getting used and worker productivity drops like a stone.
What it boils down to, in this case, why worry about choosing a system to implement if you know that you're not going to be directly responsible for that choice by the time the organization realizes it wasn't the right one? If you're not going to be held accountable for a decision in three years, should you really be empowered to make that decision?