As a CEO and founder, I help customers rescue Impossible Projects. The reality of software development is brutal. Only 16.2% to 30% of IT projects are fully successful, delivered on time, within budget, and with the expected scope \[S1\]. I have watched organizations pour millions into digital transformation. Over 50% of their IT projects exceed budgets or schedules, while approximately 20% are completely terminated before completion \[S1\]. Costs for large IT implementations can be exceeded by as much as 200% \[S5\]. We need to stop pretending that slightly better agile ceremonies will fix this. The root causes run much deeper. The advent of artificial intelligence forces us to completely rethink project risk.
Thesis: why traditional software projects fail and how AI rewrites the rules
The traditional IT outsourcing model is fundamentally broken. We keep repeating the same mistakes. The technology landscape shifts beneath our feet.
The communication gap: why traditional IT projects still fail at a high rate
IT projects often fail when requirements are unclear or change frequently, leading to work destabilization and costly reworks \[S3\]. We try to capture complex business needs in static scoping documents. By the time the code is written, the business reality has already changed. This is a fatal error.
Furthermore, we misunderstand what clients actually value. Clients prioritize a sense of control over strict contract adherence, and a lack of control is unacceptable to them, even if minor delays or problems occur \[KB1\]. A mismatch in communication preferences can negatively impact the perception of project progress and control \[KB1\]. We fail because we manage contracts instead of managing expectations.
The AI shift: how next-generation tools change the nature of project risk
Generative AI changes the game entirely. We are no longer bottlenecked by the sheer speed of typing code. But this introduces a new risk landscape. Currently, 37% of AI projects fail, primarily due to low organizational maturity, inadequate data quality, and a lack of meaningful use cases \[S6\].
To be blunt, AI shifts project risk from execution to validation. We are moving from managing development timelines to managing the semantic gap between business logic and AI-generated output. This requires true Human-centric IT leadership.
Arguments: how AI-driven development and senior expertise eliminate risk
If I could lead every past project again, I would hire a small team of highly experienced specialists and rewrite the system entirely \[KB3\]. Today, AI makes this exact approach highly scalable.
Supercharging delivery: accelerating development 5 to 8 times with Claude and MCP
Experienced and brilliant architects design systems that are superior in every aspect, being more flexible, easier to integrate, and having a much lower production cost \[KB3\]. When we pair these senior architects with modern tools, the results are staggering. Leveraging advanced next-generation AI tools, such as Codex, Claude, knowledge graphs, or Model Context Protocol (MCP), has accelerated development in our own projects by as much as 5 to 8 times \[S4\].
Strong and talented programmers write code significantly faster, require fewer corrections, and create easier-to-maintain systems \[KB3\]. By connecting Claude directly to local environments and enterprise knowledge graphs via MCP, we give these senior developers a massive productivity multiplier. The knowledge graph acts as a single source of truth. This leads to fewer architectural corrections throughout the project \[KB3\].
Rapid prototyping: closing the feedback loop before writing production code
Because AI accelerates coding, we can instantly generate working prototypes. This completely changes the feedback loop. Experienced teams are aware of their capabilities, know how to estimate tasks, and allocate sufficient time to solve problems \[KB3\]. By putting a functional prototype in the hands of stakeholders on day one, we align expectations immediately.
A fundamental management error is the lack of investment in the business and technical competencies of the development team, which once led to a key module being rewritten six times in one IT company \[KB3\]. Rapid prototyping with AI prevents this. Only people with a long-term vision can predict how a component will be used in the future and design it to keep maintenance costs low \[KB3\].
Counterarguments: addressing the new risks of AI-assisted development
We cannot treat AI as a magic bullet. Deploying AI in software development introduces serious new variables. These require strict governance.
The dark side of AI: security vulnerabilities and code quality degradation
| Risk Area | Traditional Risk | Traditional Mitigation | AI-Driven Risk | AI-Driven Mitigation |
|---|---|---|---|---|
| Security | Data breach, unauthorized access | Access control, encryption | Model poisoning, adversarial attacks | Robust AI, data validation |
| Code Quality | Inconsistent code, bugs | Code reviews, standards | AI-generated errors, hallucinations | Human oversight, AI code review |
| Scope/Requirements | Scope creep, unclear specs | Detailed specs, change control | Unpredictable AI behavior, rapid tech | Agile methods, iterative dev |
| Skills/Expertise | Skill gaps, resource limits | Training, recruitment | AI specialist shortage, complex tools | Upskilling, AI literacy |
| Ethical Concerns | Human bias in design | Diverse teams, ethics | Algorithmic bias, lack transparency | Bias detection, Explainable AI |
| Maintainability | Technical debt, poor docs | Refactoring, documentation | Complex AI models, difficult debugging | AI testing, model versioning |
Generative AI introduces concerns regarding ethics, privacy, data security, and system hallucinations \[S6\]. Unchecked AI-generated code can introduce subtle vulnerabilities and massive technical debt. If developers treat AI as a black box without understanding the underlying logic, the system will eventually collapse.
Let’s not kid ourselves regarding quality assurance. The misconception that testing is simple and can be performed by anyone is incorrect. A lack of understanding of the business domain by testers results in additional bug-fixing iterations and substantial, avoidable costs \[KB3\]. AI amplifies this risk if we lack domain expertise.
The human-in-the-loop necessity: why senior oversight is more critical than ever
Technology alone does not guarantee success. Success in AI-assisted development requires combining high-class specialists with AI tools \[S4\].
Managing risk in the AI era necessitates rigorous control over generated code, including implementing secure coding procedures, strict AI model control, and mandatory human code review to prevent the deployment of erroneous or dangerous machine-generated code \[S4\]. It is more effective to have a smaller team of highly experienced and adequately paid individuals than to manage a group twice as large with insufficient competencies \[KB3\]. Team leaders operate on the front line, directly managing the work, and thus have the greatest influence on risk identification and project plans \[KB3\].
Position: the outcome-based ownership model as the ultimate safeguard
If we can build software 5 to 8 times faster using AI and senior developers, the traditional Time and Material billing model becomes completely obsolete.
Aligning incentives: why selling developer hours is a broken model
The traditional sales process often leads to delays because salespeople promise unrealistic deadlines and budgets to win the client \[S3\]\[KB3\]. Salespeople, influenced by performance evaluation systems, may propose ambitious or unrealistic schedules and underestimate costs to meet client expectations \[KB3\].
When vendors sell developer hours, they are financially rewarded for inefficiency. This misalignment of incentives often leads to bloated timelines and scope creep. A holistic approach to offering is essential to balance easier sales with an optimal configuration of scope, time, and general contract conditions for the supplier \[KB3\].
Outcome-based ownership: securing measurable business results in the AI era
A radical shift in the software development paradigm is necessary, where the supplier assumes full responsibility for measurable business outcomes, rather than merely delivering code \[S4\]. This is the core of modern Managed Services.
To ensure project delivery, every participating part of the organization must take responsibility for its area \[KB3\]. Sales and consulting should not independently make decisions regarding cost optimization, scope, or schedule \[KB3\]. A holistic sales process should define decision gates where various unit managers and top management have access to consistent data, including detailed cost breakdowns, proposed schedules, and risk assessments, to consciously accept or reject an offer \[KB3\].
Call to action: how to restructure your next IT project for success
You cannot simply buy AI tools and expect your project failure rate to drop. You must restructure your delivery model. Agility vs. Scale is no longer a trade-off.
Auditing your current development workflow for AI readiness
Start by evaluating your current maturity. Remember that 37% of AI projects fail due to low organizational maturity of companies, lack of appropriate data quality, and absence of meaningful use cases \[S6\]. Assess how your team currently manages requirements and feedback loops. Instead of organizing costly MBA training for high-level management, companies should invest in training at the team leader level, teaching them fundamentals of people management and progress control \[KB3\].
Partnering for outcomes: steps to transition to a risk-mitigated model
Look for partners who offer outcome-based ownership and bring senior-level architectural oversight. Projects can achieve significantly more valuable business results at a lower cost and sooner by changing the order of stages and optimizing the scope of individual deliveries \[KB3\]. Legacy Modernization and Intelligent Automation require this exact approach.
Stop waiting for perfect conditions. Waiting and avoiding decisions lead to greater problems and delays. Any decision is generally better than none, and focusing on progress, pragmatism, making objective data-driven decisions, and fostering an open culture are crucial for project success \[KB2\]. Combine human-centric IT leadership with AI acceleration, demand outcome-based contracts, and take control of your digital future.
CEO | People More | Impossible Projects | Book author
Marcin Dąbrowski
