The Data Roundtable
A community of data management experts
As I explained in Part 1 of this series, creating a strategy for the data in an organization is not a straightforward task. Two of the most important issues you'll want to address in your data strategy are data quality and big data. Data quality There can be no data that is
One of the challenges my clients struggle with is figuring out how to execute against a proposed data strategy. The visionaries are always happy to participate in the process of assessing the current state and proposing a vision for the future. And adding business justifications and quantifiable metrics for success
Back before storage became so affordable, cost was the primary factor in determining what data an IT department would store. As George Dyson (author and historian of technology) says, “Big data is what happened when the cost of storing information became less than the cost of making the decision to
Creating a strategy for the data in an organization is not a straightforward task. Not only does our business change – our software solutions also change before we can ever get done with a data strategy. So, I choose to understand that a strategy has a vision, and my vision may change
In my previous post, I discussed the characteristics of a strong data strategy, the first of which was that a formal, well-defined strategy exists within your organization. This post discusses how often (and why) your organization’s data strategy needs to be updated. While strategy encompasses and sets the overall direction for
In my two prior posts, I discussed the process of developing a business justification for a data strategy and for assessing an organization's level of maturity with key data management processes and operational procedures. The business justification phase can be used to speculate about the future state of data management required