Building a Metric Based Data Driven Business Model - Seven Habits of Highly Effective Chief Data & Analytics Officers
Eddie Short
Chief Digital Officer. I work with People and harness Digital, Data & AI to enable a step change in results
I have seen lots of people try to define what it means to be Data Driven Business, and most have failed to encapsulate it.? Too many companies only focus on the output data, and develop insight from the ‘exhaust data’ of processes aligned to a focus on the ‘output’ metrics associated Revenue, Profit, Free Cash Flow etc.?These measures are obviously critical, but they only tell you how you have done – they are ‘backward looking’ by Design.?
A Data Driven Business is what I have called an Intelligent Business, which I define as
?The key for me here is that Data is both an Input and an Output for the operating model of the business - and data also describes the Value Drivers of the Business.?Furthermore, you can’t dynamically reconfigure your business unless you have the capability to change processes and ways of working in a truly agile way taking weeks, not months or years!
To consider a business that is truly data (and value) driven, we should consider the case of Amazon.? Their business strategy was famously written on a napkin by Jeff Bezos in 2001, using the ‘Flywheel’ concept from Good to Great.? Jeff created Virtuous Cycle is a strategy that leverages on customer experience to drive traffic to the platform and third-party sellers. That improves the selections of goods, and Amazon further improves its cost structure so it can decrease prices which spins the flywheel. (https://businesschronicler.com/business-strategy/amazon-flywheel-explained).
?The key here was also that Input Metrics driven by working backwards from the Customer Experience were (and are) used to help Amazon drive its business forwards.
?The leading businesses, look at Input Metrics as well as Output Metrics, after all Data is the fuel of the business and therefore drives the processes that operate the business.? Input Metrics could include Page Views, Stock Availability, Price, Discounts, Convenience.?
?The ‘Intelligent Business’ model is founded on the principles that put People at the top and data at the heart of the business model, with Data mastering Process and technology.? However, when Technology dominates and the purview of the Data, Analytics and AI Leader starts at the ‘exhaust’ of the big Enterprise Systems which are used to ‘run the business’, the importance of the Data Model is often downplayed, but for me it’s a hugely important aspect and is where the rubber hits the road in the relationship between the DAI, IT and the business.
I still cry (often) when people say they can’t measure the benefits of Data investments… Why, because the discipline of Data, Analytics & AI, includes Business Intelligence and Reporting!? In other words, the smart Data Leader is also accountable for providing the key reporting of business performance, so you have the absolute levers at your disposal to measure whether the initiative you’re accountable for has made a difference to the cost, revenue and/or profitability of the business!
??
The Enterprise Data Model – a Tech History
?Traditionally, an Enterprise Data Model (EDM) is an integrated view of the data produced and consumed across an entire organisation. Critically, the EDM unites, formalises, and represents the things important to an organisation, as well as the rules governing them.
An EDM represents a single integrated definition of data, unbiased of any system or application. The EDM is independent of “how” the data is physically sourced, stored, processed, or accessed.
?Despite the criticality of an EDM, Data Models and Data Architecture is often treated with limited value, and skills sit somewhere in IT, and less often in the CDO organisation.
?When the CDO only cared about what came out of the many Enterprise Systems, they would get the data dropped (from one or more systems) into a Data Warehouse, where it was normalised, and mapped against a Data Model created for Reporting purposes!
领英推荐
?With the advent of Predictive/Prescriptive and Adaptive Analytics including Machine Learning, the Data, Analytics and AI (DAI) Leader ceased being the person responsible for the ‘exhaust’ data and increasingly provided data and algorithms that became the fuel of the ERP and CRM platforms.?
The future technical operating model is Cloud based, and the agile business moves away from monolithic enterprise systems to micro services, which are connected by APIs to your Data platforms.
?Many Architects will tell you that an EDM is a legacy concept, never complete and with today's modern architectures like Data Mesh, you don't need a monolithic model. That might be true, technically, but id you want your Data Model to represent the Value Driver model of the business and actions taken in the business to roll up to the Enterprise KPIs, my advice is to still focus on having a clear EDM!
?
Building a Data Driven Business Model
The new value driven Enterprise Data Model focuses on putting the metrics and hence the data to drive the key decisions for the business at the heart.? The old ‘process-centric’ operating models could be made more efficient with systems and (robotic) process automation, but crucially reinforced ‘the way we used to work’ into tomorrows systems.?
When Michael Hammer launched the Business Reengineering craze of the 1990s he talked about ‘obliterating processes’.? Instead, most chose to merely automate what they had (with some minor changes).? In the world of today, those legacy processes do need to be obliterated and the data driven model will allow us to dynamically reconfigure those processes and technology towards the way we need to work tomorrow and again for the day after!? Of course, there needs to be a business case to implement this!
The Data model should be built by looking at the Value Drivers of the organisation, which allows the creation of a KPI /Metric Model which gives uninterrupted line of sight between your Level 1 Key Performance/Results Indicators (like Revenue, EBITDA, Free Cash Flow) you report to Shareholders, and the underlying operational metrics of the business (Customer Lifetime Value, Cost of Goods sold, Employee Costs etc etc); as well as those critical Sustainability and ESG metrics.? BUT it must also include those critical leading metrics that will roll-up to the Level 1 performance metrics and allow you to drive the business to success
The Data Model can be built around that core performance model and needs to reflect the criticality of both leading (input) and lagging KPIs.?
The Enterprise Data Model provides the overarching framework, and then sub-sets of that framework can be implemented into systems as you upgrade and/or replace them, thereby designing for change and the future.
?
Changing The Way We Work
?This approach institutes a new way of working where Data takes pre-eminence over Process and Technology.? The DAI Leader has a critical role in not just providing insights to the ExCo and Board but increasing advising the CEO in how best to run the business to drive optimum performance. ?In Banks and organisations that have a Chief Operation/Operations Officer, this means the DAI Leader becoming the natural incumbent of that role, with Chief Technology, Information and Process leaders reporting into them.? CDOs/CDAOs need to be able to fully grip Process and Technology to fulfil their role, now they need the true Leadership skills to lead over C-Suite Executives and be a genuine left or right hand to the CEO, with the CFO as their partner in crime.
Deloitte Global Strategy & Oxford Strategy Assessor Previously / Chief Strategy Officer / Head of Business Strategy / Head of Corporate Strategy / Strategy Director / Strategy Lead / Go-to-Market
1 年Really like the diagram Eddie Short - the core point is very well made! Can I add a view or perhaps two? I think humans will always spin the business strategy, but data should definitely underpin the logic behind the human spins. The business capabilities could perhaps re-ordered to be a free-flowing flywheel? E.g., marketing comes after product, and supply chain and logistics before sales. What do you think?
I'm going to continue disagreeing with you on the viability of an EDM, there isn't the possibility to define a complete EDM that is 'neutral', not just that it is difficult but that it is fundamentally impossible because local context isn't something you can be neutral from. But on KPIs I'm totally with you, and those KPIs more and more need to be multi-dimensional, particularly when looking to leverage AI. https://www.dhirubhai.net/posts/stevegjones_situational-intelligence3d-kpis-for-an-activity-7051274159837904896-pLdJ/
Chief Strategy Officer @ G.O.A.T. Foods
1 年I'm certain that this approach not only drives progress but is pivotal for sustaining long-term growth in today's data-centric landscape.
Composable Enterprises :Data Product Pyramid, AI, Agents & Data Object Graphs | Data Product Workshop podcast co-host
1 年Great post Eddie Short - love "An organisation that utilises predictive and adaptive insight to dynamically reconfigure itself, in response to the expected needs of its customers, and simultaneously anticipate and respond to changes and events in the external environment." - the dynamic measurement, respond (with actions) and continuous re-configuration is super key IMHO!
Transformation & Digital | Data & Tech | Programme Management | Data Ethics | AI & ML - adding value to processes, people and data into the future
1 年I think it’s interesting the relationship between tech data and process- somehow we can derive competitive advantage from process, process depends on data and also we have additional am data about the process so we can move to continuous improvement. So then it seems to me that it is tech we can be somewhat ambivalent about. It needs to be flexible enough to allow us our own process, and it needs to be rigid enough to allow us to connect data behind. I also think there is a big difference between having a unified data model and having unified data. Without really defining connections between data sets we limit ourselves to silos. Without defining useable enterprise wide taxonomy we condemn ourselves to endlessly translating data. So yes @eddie we need a proper measurement framework that we can evolve and that we understand the complementary nature of each individual component. Predictive, descriptive, all levels and proper measurement points that don’t mean we are constantly repurposing data and tying ourselves in knots. I like those.