Database Reference
In-Depth Information
sort through or consider an outdated data product. Key considerations with
respect to retiring a data product include:
How often is it used and by whom?
What product or products replace it?
What other reports or data connect to it?
Although some data products need to be retired manually (that is, someone
needs to make a decision and hit the Delete key), other data products can be
retired by inactivity. The next chapter discusses how your data ecosystem can
be designed in such a way to efficiently and effectively manage this process.
Celebrate Examples of Quality Data Products
Finally, leaders need to celebrate the best data products through public praise.
In doing so, make it clear how your organization defines “quality.” Why is this
product praised? Is it because of its utility? If so, how has it been useful? Has
it contributed to decision-making? What were the results? Making explicit
the reasons for celebrating a specific data product will go a long way toward
developing a data fluent culture.
In addition, you can celebrate quality data products by encouraging their use.
As a leader, however, there is often no better way to celebrate quality data
products than by using them in your own daily activities. The next section
elaborates on the topic of data use.
DATA uSAG E
Developing a data fluent culture in which individuals focus on the message
of quality data products is not enough: The insights gained must be both
actionable and acted upon. Leaders must encourage individuals throughout
all levels of the organization to incorporate data into their decision-making
processes. Just as there should be a feedback loop in the production of quality
data products, so too should there be an opportunity to reflect upon previ-
ous data-driven decisions. Furthermore, you should continually evaluate the
progress your organization is making in effectively using data and making
data-drive decisions.
Search WWH ::




Custom Search