Why The Model Isn’t The Hard Part, The Workflow Is
A program that started with the team, not the tool, shifted the outcome.
- According to Gartner, 85% of AI projects fail to deliver expected value, with workflow and integration challenges cited as the top cause.
- The Forbes Tech Council article highlights a program that started with team composition rather than model selection, resulting in measurable business outcomes.
- McKinsey research indicates that companies with well-defined AI workflows are 3x more likely to see revenue growth from AI initiatives.
- The shift from model-centric to workflow-centric AI is driving demand for MLOps platforms, which grew 40% year-over-year in 2025.
- Cross-functional teams that include domain experts, data engineers, and product managers reduce AI project failure rates by up to 60%.
Frequently Asked Questions
A powerful AI model without a well-designed workflow often fails to deliver business value because data quality, team collaboration, and integration with existing systems are overlooked. Workflow ensures that the model operates in the context of real business processes, with proper data inputs, feedback loops, and governance.
Studies from Gartner and McKinsey suggest that up to 85% of AI projects fail to achieve their expected outcomes, with workflow and integration problems cited as the leading causes. Only a small fraction of failures are due to model performance.
Companies should start by assembling cross-functional teams that include domain experts, engineers, and product managers. They should define clear objectives, establish data quality standards, use MLOps tools for version control and monitoring, and implement iterative testing before scaling.
MLOps (Machine Learning Operations) is a set of practices that automate and streamline the end-to-end lifecycle of AI models—from development to deployment and monitoring. MLOps directly supports workflow by ensuring reproducibility, collaboration, and continuous improvement.
Team composition is critical because AI projects require diverse skills: data engineering, model building, domain knowledge, and product thinking. Studies show that teams with domain experts integrated from the start are 60% more likely to deliver value compared to teams focused solely on model development.
Not irrelevant, but secondary. Most modern models (including large language models) are capable enough for many tasks. The differentiating factor is how the model is integrated into a workflow—how data is fed, how outputs are validated, and how humans interact with the system.
Topics
Original source
www.forbes.com
Discussion
Join the discussion
Sign in to post a comment or reply.
No comments yet. Be the first to share your thoughts!