ClareNow
Search
ClareNow
Toggle sidebar
AI → Neutral

Why The Model Isn’t The Hard Part, The Workflow Is

A program that started with the team, not the tool, shifted the outcome.

Forbes 2 min read 7/10
Why The Model Isn’t The Hard Part, The Workflow Is
Key Takeaways
  • 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%.
Most companies chasing artificial intelligence are obsessing over the wrong thing. While leaders pour billions into training bigger, better models, the real bottleneck—and the biggest lever for success—is the workflow surrounding those models. A Forbes Tech Council article argues that 'the model isn't the hard part, the workflow is,' pointing to a fundamental shift in how organizations should approach AI deployment. The piece centers on a program that started with the team, not the tool, and saw dramatically different outcomes. This insight challenges the prevailing narrative that model performance alone drives value, highlighting instead the critical role of human processes, data pipelines, and cross-functional collaboration. Research from Gartner and McKinsey supports this view: up to 85% of AI projects fail to deliver expected value, not because the models underperform, but because organizations lack the operational workflows to integrate them effectively. The article underscores that companies often rush to build or buy a state-of-the-art large language model (LLM) while neglecting the infrastructure needed to clean data, manage prompts, handle feedback loops, and govern outputs. Without deliberate workflow design, even the most powerful model remains a proof of concept. The successful program referenced in the article prioritized assembling a multidisciplinary team—engineers, domain experts, product managers—before selecting a model. This approach allowed the team to define clear objectives, establish data hygiene standards, and create iterative testing procedures that turned a generic model into a tailored solution. The outcome was not just a deployed model but one that actually changed business metrics. Industry experts now argue that workflow design will become a core competency for enterprise AI. As organizations move from experimentation to production, the competitive advantage will come from how well they orchestrate people, processes, and technology—not from which model they choose. Looking ahead, we can expect more companies to invest in workflow automation tools, adopt MLOps platforms, and restructure teams around 'AI choreography' rather than model selection. The message is clear: in the race to leverage AI, the hard part isn't the algorithm—it's making that algorithm work within a messy, human-driven organization.

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.

Original source

www.forbes.com

Read original

Discussion

Join the discussion

Sign in to post a comment or reply.

No comments yet. Be the first to share your thoughts!

Sign in
Enter your email to receive a one-time sign-in code. No password needed.
Email address