Maturity assessments are easy to produce and easy to ignore. The output is a set of stage ratings that everyone agrees with and nobody acts on, because a rating is a description and a description does not tell anyone what to do on Monday.
This was three connected pieces of work against one organisation, deliberately arranged so the assessment could not stop at description. Assess the current state against a capability model, derive the talent strategy the gaps require, then convert both into a change plan with a sequence, an owner and a date attached to each step. The third piece is the one that makes the first two worth doing.
The supplied case was Finserv, a fictional mid-sized financial services firm with a head office and four autonomous divisions, whose corporate strategy named analytics as an opportunity while the organisation had no formal analytics strategy at all. That gap is the whole situation in one sentence.
Scored against the capability maturity model, almost everything sat at stage 1 or 2 against a target of stage 3. Divisions were each running their own analytics to their own requirements, policies were informal, staffing covered critical projects only, and decision-making ran on descriptive analytics, which is to say on reporting what had already happened. The trap in that picture is that it looks like a technology problem and it is not. Culture at stage 1 and human capital at stage 1 will defeat any platform purchase. An organisation cannot buy its way from stage 1 to stage 3, because most of the distance is in how people work.
There was one asset worth more than the whole gap analysis: the Marketing department had run a pilot and cut report processing time by 50%. Internal proof, in the organisation’s own language, that the thing works here. The transformation plan used it as the second half of the urgency case, paired with competitive benchmarking showing 20 to 30% EBITDA improvement in analytics-mature organisations, because an external benchmark and an internal proof point do different persuasive jobs and both were available.
What the plan committed to is the part that matters: four falsifiable targets at month 18. A transformation plan that promises improved capability cannot fail and therefore cannot succeed. One that commits to 90% tool adoption by a named month can be checked, and being checkable is what makes a plan a commitment rather than a position.
In brief
- Analytics capability assessed across twelve dimensions against a published maturity model, with every rating tied to a specific documented fact about the organisation
- Current state at stage 1 or 2 on every dimension against a stage 3 target, with culture, structure, human capital, integration, analytical tools and business focus all at the floor
- Marketing pilot’s 50% reduction in report processing time used as the internal proof point, paired with external benchmarking of 20 to 30% EBITDA improvement
- Analytics Centre of Excellence recommended as the structural answer to fragmented divisional analytics, chosen to consolidate capability without removing divisional autonomy
- Kotter’s 8-step model selected on stated grounds, with Lewin and Beer and Nohria’s Theory E and O evaluated and rejected on record
- Month-by-month implementation timeline mapped to Kotter’s steps, with a stakeholder communication matrix and a risk register naming an owner per risk
- Four falsifiable targets at month 18: 30% faster decision-making, 25% shorter reporting cycles, 40% higher data literacy, 90% tool adoption
- Two-year budget of $5.7 million across 55 full-time equivalents, with a 15 FTE Centre of Excellence at its centre
- Context weighting justified by the gap between 92% of organisations investing and 72% failing to build the culture that makes the investment pay
The report as submitted
Three assessments against one organisation: a capability assessment, a talent strategy, and a transformation plan.
Part one, the capability assessment
Current state
Finserv operates without a formal analytics strategy and works predominantly with descriptive rather than predictive analytics. The problems interlock. There is a trust gap between technical and business stakeholders (Capgemini 2020), initiatives are fragmented across divisions, and divisional executives view centralised analytics as a threat to their autonomy. Talent scarcity compounds it, since data scientists remain rare precisely because the role requires technical and analytical skill in the same person (Shah 2019).
The industry context sets the stakes. While 92% of organisations are accelerating analytics investment, 72% still struggle to build a data-driven culture (Bean & Davenport 2019). A data-driven organisation treats data as a strategic asset rather than a by-product of running the business (Reichental 2024), and uses it in decision-making, innovation, risk management and growth. The second of those two statistics is the operative one: nearly everybody is spending, and most of the spending does not produce the culture change that makes it pay.
Maturity assessment
Assessed against the RMIT Capability Maturity Model (RMIT 2023), on a five-stage scale, with each rating tied to a documented fact rather than an impression. Ratings that cannot be challenged on their evidence are usually ratings nobody believes.
| Dimension | Current | What the rating rests on | Target |
|---|---|---|---|
| Strategic alignment | 1 to 2 | No formal analytics strategy, though corporate strategy names analytics as an opportunity | 3 |
| Leadership engagement | 2 | IT project direction shared at senior management level | 3 |
| Culture | 1 | Reactive decision-making, acknowledged resistance to change | 3 |
| Organisational structure | 1 | Divisions each driving analytics to their own requirements | 3 |
| Governance | 1 to 2 | Informal policies and processes only | 3 |
| Human capital | 1 | Staffing provided for critical and high-risk projects only | 3 |
| Infrastructure | 2 | Some collaborative tooling in place | 3 |
| Data integration | 1 | Limited collaboration and information sharing across divisions | 3 |
| Ease of use | 1 to 2 | Basic operational tooling; the Marketing pilot is the exception | 3 |
| Analytical tools | 1 | Decision-making informed mainly by descriptive analytics | 3 |
| Technologies | 2 | Collaborative tools used on some projects and programmes | 3 |
| Business focus | 1 | Silos limiting the sharing, access and use of data | 3 |
Stage 3 requires standardised leadership practice, defined structures and integrated data management (Lasmanis & Stauffer 2024). The target was set at stage 3 across all dimensions within two years.
Barriers and enablers
Barriers: structural data silos, limited data literacy, and a risk-averse decision-making culture. Enablers: board-level recognition of the competitive gap, the managing director’s commitment, and the Marketing pilot. Transformation of this kind requires attention to the social as much as the technological dimension, particularly to how analytics capability changes what different roles are for (Ojanperä, O’Clery & Graham 2018).
Best practice analysis
Three core requirements recur in the research on analytics-driven organisations: infuse analytics into decision-making processes, organise capability enterprise-wide, and deploy analytics talent effectively (Accenture 2013). Procter & Gamble’s Business Sphere environment places analytics at the centre of operations and reports a 50% reduction in time-to-insight and 35% improvement in decision-making efficiency.
Successful organisations ensure high-quality trusted data, make it accessible to the right people, and make it findable and understandable in an actionable form (Reichental 2024), balancing those objectives against privacy (OECD 2019). Barton and Court (2013) identify three mutually supporting capabilities: managing multiple data sources, building advanced analytics models, and transforming organisational management capacity.
The pattern across industries:
- Organisations with strong data governance frameworks are 2.5 times more likely to report financial benefit from analytics initiatives (Capgemini 2020)
- Companies that integrate analytics into core business process see 23% higher revenue growth than peers (OECD 2019)
- Firms with established analytics centres of excellence achieve 45% faster time-to-value on new initiatives (Accenture 2013)
- Financial services organisations implementing these capabilities report 25% faster product development and 40% better risk assessment accuracy (McKinsey 2018)
Gap analysis
Against those benchmarks, five gaps (Lasmanis & Stauffer 2024): no standardised definitions for key figures and unclear use cases in business management; limited visibility of data quality and inconsistent cross-divisional provision in data architecture; misalignment between technology architecture and business requirement; no defined analytics support organisation; and insufficient promotion of data literacy.
Recommendations
Establish an enterprise-wide analytics governance framework that centralises strategic direction while preserving divisional autonomy. Comparable models report a 25% improvement in decision-making speed through balanced centralisation (Accenture 2013). This is the direct answer to fragmented execution and to divisional resistance, because it creates accountability without removing operational independence.
Implement a data integration programme to break the silos. Similar initiatives in financial services have returned within twelve months through reduced operating cost and improved data quality (Capgemini 2020), and this targets the stage 1 to 2 data management ratings that everything else depends on.
Expand the Marketing pilot into an analytics Centre of Excellence. This builds on demonstrated success rather than on a proposal, and the Centre of Excellence model has worked particularly well in organisations with a similarly decentralised structure, reporting 40% improvement in cross-divisional collaboration (McKinsey 2018).
The implementation was structured in three phases over two years, aligned to Kotter’s framework from the outset: creating the climate for change in months 0 to 6, engaging and enabling the organisation in months 6 to 18, and implementing and sustaining change in months 18 to 24. Success metrics followed SMART principles: a 30% reduction in report generation time in year one, 80% standardisation of core data elements at 18 months, and 70% of management decisions supported by analytics by year two.
Part two, the analytics and talent strategy
Assessment of the proposed strategy
The proposed strategy has a clear vision, executive sponsorship and a validated pilot behind it, which is more than most. The gaps are specific: limited focus on data governance with unclear processes for data ownership and quality management, ambiguity about how analytics integrates with existing business process, and insufficient weight on change management, which is where the failure mode actually lives.
The underlying research is uncomfortable reading. Organisations typically use less than 50% of their structured data and less than 1% of their unstructured data in decision-making (DalleMule & Davenport 2017). Around 70% of employees have inappropriate data access and analysts spend roughly 80% of their time preparing data rather than analysing it (Barton & Court 2012). Less than 20% of companies achieve analytics at scale (McKinsey 2018).
Five enhancements followed: an enterprise-wide governance framework implementing a single source of truth with named data ownership; standardised quality measures covering both technical metrics (accuracy, completeness) and business metrics (usefulness, timeliness); a technology roadmap addressing current scalability limits through cloud and hybrid solutions; stronger change management with stakeholder engagement and communication; and success metrics tied to business objectives with a review cadence that allows the approach to be adjusted on evidence.
Talent strategy
Human capital and organisational structure both sat at stage 1, which points at a structural answer rather than a hiring answer. The Analytics Centre of Excellence gives the fragmented divisional efforts somewhere to consolidate without stripping divisions of autonomy (Eckerson 2019).
The leadership layer is a chief analytics officer, analytics directors and a data governance lead. Three core teams sit under it: data science for advanced analytics and predictive modelling, business intelligence for delivery and communication of insight, and data management for the underlying infrastructure. Embedded analytics staff inside business units act as the bridge between capability and requirement, which is also the mechanism for knowledge transfer.
The capability gap is real and widening. While 78% of analytics professionals believe their organisations use data effectively, only 57% report having the talent to execute the strategy (MicroStrategy 2018). Demand for data scientists in financial services grows around 43% a year against a supply increase of 19%, and 67% of analytics professionals prefer larger institutions or technology companies (Ready, Hill & Thomas 2014), which is a specific disadvantage for a mid-sized firm.
Career progression was defined across four levels so that the pathway is visible before someone is hired into it.
| Level | Role | Core responsibilities | Development focus |
|---|---|---|---|
| Entry | Analytics professional | Data preparation, basic analysis, reporting, documentation | Technical skills, domain knowledge, communication |
| Senior | Analytics professional | Advanced analytics, project leadership, stakeholder management, solution design | Leadership, delivery, mentoring, innovation |
| Lead | Analytics manager | Team management, strategy execution, technical direction, cross-functional leadership | Team leadership, strategy, stakeholder management |
| Executive | Analytics director | Strategic direction, innovation leadership, enterprise transformation | Executive presence, strategic vision, enterprise change |
Around that, three retention mechanisms. Attraction positions the firm on flexible working and technical culture rather than competing on compensation alone, since compensation is the axis on which a mid-sized firm loses. Development runs technical certification alongside business domain training with structured mentoring, and allows both technical and managerial progression so that good analysts are not promoted out of analysis. Retention rests on recognition for business impact as well as technical work, plus innovation projects and industry engagement. Organisations with frameworks of this kind are around 60% more likely to retain analytics talent (Ready, Hill & Thomas 2014).
Targets: 80% of critical roles filled within six months, 70% of staff completing basic analytics training in year one, 85% analytics talent retention, 90% on-time project delivery, and 25% improvement in operational efficiency through analytics.
Part three, the transformation plan
Choosing a change model, and saying what was rejected
Kotter’s 8-step model was selected over two alternatives, and the reasons were put on record rather than assumed. Lewin’s three-stage model is simple enough to explain in a slide and too coarse for a cross-divisional transformation with four autonomous business units. Beer and Nohria’s Theory E and Theory O frames the tension between economic value creation and organisational capability development well, and offers an implementer very little guidance on what to do about it. Kotter’s emphasis on urgency, coalition-building and cultural embedding matches the actual problem, which the maturity assessment had already established was cultural rather than technical (Kotter 2012).
The implementation timeline
Each Kotter step was attached to months, activities and named deliverables, because a step without a deliverable is a slogan.
| Months | Kotter step | Key activities | Deliverables |
|---|---|---|---|
| 1-2 | Create urgency | Market analysis, stakeholder briefings | Business case, engagement plan |
| 2-3 | Build coalition | Leadership alignment, team formation | Steering committee, project charter |
| 3-4 | Create vision | Strategy development, success criteria | Vision document, strategic roadmap |
| 7-8 | Empower action | Launch training programme, deploy infrastructure | Training materials, technical platform |
| 9-10 | Generate wins | Pilot projects, success metrics | Quick wins report, benefits case |
| 11-12 | Consolidate | Scale successful pilots, enhance capability | Scale plan, progress report |
| 13-18 | Consolidate | Cross-divisional integration, advanced analytics | Integration report, capability assessment |
| 19-24 | Anchor | Embed in process, continuous improvement | Process documentation, sustainability plan |
Urgency in months 1 and 2 is not a slogan either: it is competitive benchmarking showing 20 to 30% EBITDA improvement in analytics-mature organisations (McKinsey 2023) presented alongside the Marketing pilot’s 50% efficiency gain, plus workshops on the disruption risk and metrics tracking whether engagement is actually rising.
Success metrics by month 18: 30% improvement in decision-making speed, 25% reduction in reporting cycles, 40% increase in data literacy scores, and 90% analytics tool adoption across divisions.
Governance and resourcing
Three levels. Strategic: an executive steering committee owning direction and resource allocation. Tactical: the Centre of Excellence managing implementation and coordinating cross-functional teams. Operational: divisional working groups handling execution.
Resourcing is 15 full-time equivalents in the Centre of Excellence, 40 across divisional teams, plus external consultants, on a budget of $2.5 million in year one and $3.2 million in year two covering technology, training and personnel. Delivery runs in three phases: foundation in months 1 to 6 establishing governance, core infrastructure and pilots; implementation in months 7 to 12 rolling out platforms, scaling training and implementing data governance; and scale in months 13 to 24 expanding capability and building advanced applications.
Stakeholder communication matrix
Stakeholders were categorised by influence and interest (Deshmukh 2019), with the message, the success indicator and the risk factor stated per group rather than a single communications plan issued to everybody.
| Stakeholder group | Key messages | Success indicators | Risk factors | Frequency and channel |
|---|---|---|---|---|
| Board of directors | Strategic value, competitive positioning, return metrics | Investment returns, market position | Governance oversight, risk tolerance | Monthly, board papers |
| Divisional executives | Operational benefit, autonomy preserved, growth opportunity | Divisional KPI improvement, staff engagement | Change resistance, resource allocation | Bi-weekly, executive briefings |
| Analytics teams | Career growth, technical excellence, innovation | Skill development, project delivery | Resource availability, retention risk | Bi-weekly, technical forums |
| IT leadership | Integration roadmap, security, scalability | Platform stability, integration success | Technical complexity, legacy systems | Bi-weekly, sprint reviews |
| Business units | Efficiency gains, process improvement, support | Productivity metrics, adoption rates | Workflow disruption, training needs | Weekly, team meetings |
| End users | Productivity benefit, support, skill development | Adoption rates, satisfaction scores | Learning curve, resistance to change | Ongoing, training sessions |
Note the second row. Divisional executives are the group whose stated risk is change resistance and whose key message is autonomy preservation. That is not a communications problem to be smoothed over, it is the central design constraint on the whole programme, and it is why the recommendation is a Centre of Excellence rather than a central analytics department.
Risk management framework
Risks were registered with probability, impact, mitigation and a named owner, following Heidmann’s (2019) framework across technical, organisational and strategic categories.
| Category | Risk | Probability | Impact | Mitigation | Owner |
|---|---|---|---|---|---|
| Technical | Data quality issues | High | High | Quality monitoring framework, governance standards, regular audits | Data governance lead |
| Technical | System integration complexity | High | High | Phased deployment, end-to-end testing | IT director |
| Technical | Data security breaches | Medium | High | Enhanced security protocols, regular audits | Security lead |
| Technical | Infrastructure scalability | Medium | Medium | Cloud architecture, capacity planning | Infrastructure lead |
| Organisational | Change resistance | Medium | High | Stakeholder engagement plan, support networks | Change manager |
| Organisational | Key personnel turnover | Medium | High | Knowledge management, succession planning | HR lead |
| Organisational | Insufficient training uptake | Medium | Medium | Targeted learning programmes, progress tracking | Training lead |
| Organisational | Cross-divisional conflict | Medium | High | Governance framework, clear escalation paths | Change manager |
| Strategic | Market disruption | Medium | High | Regular strategy reviews, agile response plan | Strategy director |
| Strategic | Budget constraints | Medium | High | Phased funding, benefit tracking | Finance director |
| Strategic | Regulatory changes | Low | High | Compliance monitoring, regulatory engagement | Compliance lead |
Regulatory compliance gets specific treatment given the sector: a dedicated data governance committee, automated compliance monitoring, and standing engagement with regulators rather than periodic submissions.
Conclusion
Success depends on balancing technical implementation against organisational change, with executive sponsorship, clear governance, stakeholder engagement, risk management and progress monitoring as the critical factors.
The three assessments also demonstrate something a single report cannot: a maturity score is only useful if something downstream consumes it. The assessment fed the talent strategy, the talent strategy fed the transformation plan, and each stage had to survive being used by the next one.
References
Accenture 2013, Building an Analytics-Driven Organization.
Australian Government 2013, Implementation Toolkit, 5. Monitoring, review and evaluation, Department of Industry, Innovation and Science, Canberra.
Australian Government 2021, Australian Data Strategy, Department of the Prime Minister and Cabinet, Canberra.
Barton, D. & Court, D. 2012, ‘Three keys to building a data-driven strategy’, McKinsey Quarterly, vol. 4, no. 1, pp. 36-41.
Bean, R. & Davenport, T.H. 2019, ‘Companies are failing in their efforts to become data-driven’, Harvard Business Review.
Beer, M. & Nohria, N. 2000, ‘Cracking the code of change’, Harvard Business Review, vol. 78, no. 3, pp. 133-141.
Capgemini 2020, The data-powered enterprise: why organisations must strengthen their data mastery.
DalleMule, L. & Davenport, T.H. 2017, ‘What’s your data strategy?’, Harvard Business Review, vol. 95, no. 3, pp. 112-121.
Danairat, P. & Thawesaengskulthai, N. 2019, ‘A framework for implementing data analytics in a big data project’, International Journal of Information Technology Project Management, vol. 10, no. 4, pp. 45-63.
Deshmukh, P. 2019, ‘A data science leader’s guide to managing stakeholders’, Towards Data Science.
Dodgson, M., Gann, D. & Salter, A. 2009, The Management of Technological Innovation: Strategy and Practice, Oxford University Press.
Eckerson, W. 2019, ‘How to organize data analytics teams’, Eckerson Group Research Report.
Elving, W.J.L. 2005, ‘The role of communication in organisational change’, Corporate Communications: An International Journal, vol. 10, no. 2, pp. 129-138.
Health Catalyst 2016, Using Analytics to Drive a Culture of Continuous Improvement.
Heidmann, L. 2019, ‘Managing risk in data projects’, Dataiku Blog.
Johnson, K.J. 2017, ‘The dimensions and effects of excessive change’, Journal of Organizational Change Management, vol. 30, no. 1, pp. 2-16.
Kotter, J.P. 2012, Leading Change, Harvard Business Review Press, Boston.
Lasmanis, A. & Stauffer, J. 2024, Data Analytics Maturity Assessment: A Framework for Organizational Transformation.
McKinsey 2018, Building an Effective Analytics Organization, McKinsey Digital Report.
McKinsey 2023, The Data-Driven Enterprise of 2025, McKinsey Digital.
MGI 2016, The Age of Analytics: Competing in a Data-Driven World, McKinsey Global Institute.
MicroStrategy 2018, Global State of Enterprise Analytics Report, MicroStrategy Incorporated.
MindTools 2024, ‘Lewin’s change management model, understanding the three stages of change’.
OECD 2019, Data in the Digital Age, OECD Publishing.
Ojanperä, S., O’Clery, N. & Graham, M. 2018, Data Science, Artificial Intelligence and the Futures of Work, The Alan Turing Institute.
Ready, D.A., Hill, L.A. & Thomas, R.J. 2014, ‘Building a game-changing talent strategy’, Harvard Business Review, vol. 92, no. 1, pp. 62-68.
Reichental, D. 2024, ‘The role of data-driven culture in digital transformation success’, Forbes.
Rever, H. 2008, ‘Five key elements to process improvement project success’, ASQ Six Sigma Forum Magazine, vol. 7, no. 4, pp. 24-28.
Rigby, D.K., Sutherland, J. & Takeuchi, H. 2016, ‘Embracing agile’, Harvard Business Review, vol. 94, no. 5, pp. 40-50.
RMIT 2023, Data Analytics Capability Maturity Model, RMIT University.
Shah, S. 2019, ‘What does the future data scientist look like?’, Raconteur.