Don't leave your data alone with IT
Traditionally, IT has been at the core of most organizations, acting as the driver for technological innovation, and because the complexity new technology demanded on-hand expertise organizations couldn’t function without it. IT teams keep up and running, deploying, and maintaining business-critical tech tools.
Along with all these responsibilities came the data those technological solutions supported; the dominating view has been that data was also a technical problem.
The context has since change dramatically, the capability to take advantage of data insights and analytics can make or break an organization.
Becoming data-driven produces benefits across customer-facing and internal operations and even the bottom line – a data-driven business needs business driven data.
Data is no longer, if it as ever been, a technical asset. Data is a business asset.
Although, with increasing investments in analytical solutions, big data, AI, Neural Networks, Machine Learning, Deep Learning, improving processing capabilities and expanding storage capabilities, either on site or in the cloud, and even on organizational changes, building data focused structures to support data initiatives.
Yet, experience shows that frequently the results fall short on the objectives:
When this occurs, most organizations will probably accept to live with mediocre, under-performing solutions – expensive failures - often seen throughout the organization as IT vanity projects.
We see organizations struggling to collect as much data as possible (for the next 5 years the size of data available is expected to grow at a rate of 40% per year), with consistent infrastructure, storage, processing, and analysis investments also increasing.
Recommended by LinkedIn
More and more data is being accumulated across data warehouses, data lakes, and more recently data lake houses, always with the perception that more data can be collected, and with it the capability to harness the enormous potential that can be derived from it.
Overlooking the fact that the more data is collected, the more redundant and obsolete data is gathered and the harder it is to analyze it and derive useful insights to feed business decision processes – This lack of business context and purpose leads to a decreasing quality of analysis and insights.
Data strategy is business strategy
The ultimate purpose of an organizations data is to create business value, so any data strategy must be oriented towards the organization's strategic priorities and key business objectives and any data related initiative must be entirely supported on business strategy and objectives.
IT must step back and allow business stakeholders/units to drive these initiatives. These are the people who know what the business problems are, its needs and objectives.
Giving the control to the business, building the business case with those willing to defend it, those who can easily identify business pain points, while solve some of challenges usually associated with these processes, as lack of cross organization involvement or resistance to change.
Having business stakeholders that can passionately and effectively articulate the impacts and benefits of a data initiative and that will be eager to defend the project – Transforms a traditional resistance point into an evangelist, with enormous impact on the trust of the insights being produced and the capability to quickly move from insights to actions.
Failing to support any data initiative on strong business cases, anchored on clear business objectives, transforming data initiatives into technological initiatives will impact the success of these initiatives, often seen as just another siloed IT project with no perceived value from the business side.
The role of IT in this process is to find the right technology and support the business units in this journey
Global Supply Chain Leader | Transformational Operations Executive | AI & Digital Transformation Advocate | Champion of Inclusion, Diversity & Circular Economy | Driving Sustainable Supply Chain Strategies
2yTend to agree Jose Almeida. If we define Data as an IT responsibility, we may end up with a sub optimal structure and governance. As a supply chain practitioner, I still must define my data needs and objectives and then harness IT teams and solutions to deliver the objective. I am however mulling over the 'Data as a Service' concept since this requires far greater regulatory considerations that have been raised by Patrick Mutuku in the thread.
ERPs Solutions Architect-| Agile -| Scrum-|Cloud
2yI am also looking at knowledge on how to build concensus with Governance bodies/legislations..for instance..you cannot move customer identifiable data to cloud..is it a sustainable argument in the age of APIs..open banking and such?..how can you mitigate??
ERPs Solutions Architect-| Agile -| Scrum-|Cloud
2yWhat an interesting analogy.."Don't leave your data alone with IT"...but how do you decouple IT from data..they know how your data sits..how it grows and how it walks and talks?