Tailoring your message is an essential project management tool that for some comes natural, but can prove to be a difficult task for others. We’ve all been in ‘business meetings’ that have been hijacked by an IT person who goes way too in depth on programming logic, database design, and architecture plans. On the flip side, I’m sure many of us have also been in ‘IT meetings’ where a business stake holder goes way to in depth on financial trending, changes in legislation, and marketing initiatives.
If this is your first time on this site, take a second to subscribe to this blog so that you can be updated when new Data Governance articles are posted by entering your address in the box below. We won’t sell nor spam your email address… just good Data Governance information.
Projects and Programs fail for a variety of reasons. Data Governance is a particularly tough program, and I’d like to see as many programs succeed as possible. Below are the top reasons I’ve seen that have caused Data Governance programs to fail.
1. No Success Shown
A good way to kill your program is to show no success out of the gate. Very quickly people will become disinterested, restless, and you’ll notice participate will wane. To prevent this, get a quick win that really excites upper management as well as the stewards. Fix a pain point for them or clean up something that everyone knows is a problem. Whatever you do, get a quick win.
2. Loss of Executive Buy-in
This can happen for a lot of reasons, including the other 7 listed here, so the key to this is to keep your executive sponsors up-to-date and engaged. You can do this through traditional status reporting as well as drop-in meetings and updates when you have success. Have a communication plan that keeps your executive sponsor and interested upper management engaged and updated.
3. Not Having a Proper Foundation
A recent article that I blogged on stated that 80% of Data Governance projects fail. Now, I’m not knocking the authors or anything, but the conclusions that were drawn were pretty obvious. If you start Data Governance before you have the proper foundation you are going to fail. A proper foundation includes proper data management for your organization, data models, metadata, etc. Basically, you need to at least have the basic foundation for what Data Governance will indeed govern. If you don’t have metadata, for instance, wouldn’t you first start a Metadata project to build up your data dictionary before starting your Data Governance Program? I would.