What Really Makes Analytics Projects Succeed? New Study Maps 24 Critical Factors

Analytics and data mining projects promise to transform how organizations make decisions, yet a striking number of them fail to deliver meaningful business value despite heavy investment in business intelligence, predictive analytics and machine learning. A new open-access study published in the International Journal of Data Science and Analytics tackles one of the most persistent questions in the field: which conditions actually determine whether these projects succeed? Rather than adding yet another independently named list of success factors to an already crowded literature, researchers led by K. S. Vindya of Nitte University and Visvesvaraya Technological University set out to harmonize decades of fragmented research into a single, coherent framework, and then tested it against the judgments of 350 working practitioners.

The core problem the team confronted is one that will be familiar to anyone who has tried to compare studies in this area. Conceptually identical conditions appear under wildly different names: top management support, executive sponsorship and project championing often describe the same underlying reality, yet they are treated as distinct findings. Levels of abstraction vary just as wildly, with one study presenting a single broad construct where another splits it into multiple narrow subfactors. This terminological chaos makes cumulative theory-building nearly impossible, and it also obscures a deeper gap: very few studies have asked practitioners directly whether the factors identified in the literature are actually prioritized and implemented in real projects.

To build their evidence base, the researchers conducted a systematic literature review following PRISMA 2020 reporting principles and Kitchenham-style guidance, searching Web of Science, IEEE Xplore and Scopus as of October 14, 2025. After rigorous two-reviewer screening, which achieved 98.15 percent exact agreement and a Cohen’s kappa of 0.962, 32 primary empirical studies made the final cut. Each study was assessed for methodological quality on twelve criteria, with normalized consensus scores ranging from 66.67 to 100 percent and a mean of 91.93 percent. From these 32 studies, the team extracted 449 verbatim critical success factor entries, which expanded to 457 mappings after splitting compound entries, and were then harmonized through retention, renaming, merging and splitting into 51 generalized candidate factors.

The harmonization process was deliberately conservative, preserving the conceptual meaning of each factor rather than forcing superficial word-matching. For example, the term standard-based BI architecture was generalized to scalable and flexible analytics technical architecture, while synonymous expressions of strategic alignment were merged under clear business vision and strategic plan. Conversely, a compound factor combining business-centric championship and balanced team composition was split into two distinct constructs: business project champion and project team competency. Every one of the 449 original entries was linked to a traceability sheet recording its verbatim wording, extracted label and dimension assignment, allowing future researchers to audit or re-code the entire synthesis. Twenty-three canonical factors survived the confirmation checks, organized into five conceptual dimensions: strategic, organizational, people, project and technical.

The five dimensions capture complementary layers of a socio-technical system. The strategic dimension covers business case and value justification, business project champion, clear business vision and strategic plan, and top management support. The organizational dimension includes adequate resource allocation, data quality management and governance, organizational culture, user-focused change management and vendor support quality. The people dimension encompasses internal expertise and cross-functional collaboration, project team competency, user participation and user training. The project dimension holds clear system requirements, incremental delivery and feature prioritization, project management and structured processes, stakeholder coordination and user-solution alignment. The technical dimension covers analytics system integration and interoperability, effective data management, high system quality, scalable architecture and supporting technology.

Then came a twist that says a great deal about how the field is changing. During pilot testing with 12 experienced practitioners, participants insisted that data security, privacy and compliance deserved recognition as a standalone factor rather than being buried within other constructs. The researchers agreed, bringing the final practitioner-informed taxonomy to 24 factors. That addition proved prescient: in the full survey, data security, privacy and compliance earned one of the highest mean importance ratings of any factor, at 4.3714 on a five-point scale, second only to clear system requirements at 4.3857. A condition absent from the canonical literature core had become, in the eyes of practitioners, nearly indispensable, a signal that regulatory and governance concerns now weigh on analytics work in ways the older literature never anticipated.

The survey itself reached 350 eligible respondents recruited primarily through Prolific, with a small supplement from LinkedIn, collected over ten days in March 2026. Respondents rated each factor’s perceived importance and its level of implementation in their organizations, selected their top five priorities in a forced-ranking format, and answered open-ended questions. Most had direct experience with business intelligence, dashboards and reporting projects, followed by data platform, decision support, big data, predictive modeling and text analytics work. When forced to prioritize, practitioners put clear business vision and strategic plan first, selected by 48 percent of respondents, followed by data quality management and governance at 44.57 percent, top management support at 43.14 percent, data security and compliance at 37.14 percent and project team competency at 36.57 percent.

Perhaps the most practically useful findings came from the importance-implementation gap analysis. Five factors showed statistically significant positive gaps after Holm correction for multiple comparisons: user-solution alignment, business case and value justification, data security, privacy and compliance, effective data management, and clear business vision and strategic plan. In plain terms, practitioners consider these conditions more important than their organizations actually deliver. The effect sizes, however, were modest, with Cohen’s dz values ranging from 0.164 to 0.198, suggesting small but real implementation shortfalls rather than organizational crises. Notably, top management support and data quality governance, though heavily prioritized, did not show statistically significant gaps, illustrating that a factor can be foundational without being substantially under-implemented.

The final analytical stage applied exploratory factor analysis to the importance ratings, and the results complicate the tidy five-dimension picture. The data proved highly suitable for factor analysis, with an overall Kaiser-Meyer-Olkin value of 0.9401 and a significant Bartlett test. Rather than recovering five distinct dimensions, the analysis yielded three correlated empirical factors accounting for 43.22 percent of total variance: strategic governance and delivery capability, blending strategic justification, governance, data foundations, resources, team capability, requirements and delivery discipline; leadership, stakeholder and adoption alignment, covering sponsorship, culture, change management, user involvement and vendor support; and technical infrastructure and capability enablement, which notably absorbed user training alongside integration, architecture and system quality. The inter-factor correlations of 0.553 to 0.601 reinforce the study’s socio-technical framing: practitioners experience these conditions as interdependent capabilities, not isolated silos.

The authors are careful about what their findings do and do not establish. Project outcomes were not directly measured; the study assessed perceptions of importance and implementation, not causal links to success. The sample skewed toward practitioners with fewer than four years of experience and technology-sector projects, and the three-factor structure remains exploratory pending confirmatory factor analysis with independent samples. Still, the practical implications are concrete. Organizations can use the five dimensions as a diagnostic checklist at project initiation, governance reviews and post-implementation evaluation, then combine importance ratings, forced priorities and gap analysis to target improvement efforts. The three empirical factors offer a template for structuring interventions into integrated workstreams spanning governance and delivery, leadership and adoption, and technical enablement. As analytics investments continue to balloon worldwide, this practitioner-informed taxonomy offers something the field has lacked: a common language for asking not just whether a project succeeded, but which conditions were in place to make success possible, and which were quietly missing.

Subject of Research: Critical success factors for analytics and data mining projects, harmonized into a taxonomy and assessed by practitioners

Article Title: Critical success factors for analytics and data mining projects: a harmonized taxonomy and practitioner assessment

Article References: Vindya, K. S., Shetty, S., Prabhu, N. N., & Shetty, N. (2026). Critical success factors for analytics and data mining projects: a harmonized taxonomy and practitioner assessment. International Journal of Data Science and Analytics, 22(1), Article 330. https://doi.org/10.1007/s41060-026-01309-0

Image Credits: AI Generated

DOI: 10.1007/s41060-026-01309-0

Keywords: critical success factors, analytics projects, data mining, business intelligence, project management, taxonomy, practitioner survey, exploratory factor analysis, data governance, data security and compliance, socio-technical systems, systematic literature review