So, What Went Wrong and Your Project Failed?
This isn’t a question from a game show. The format of the question may resemble a well-known game show where unexpected outcomes intrigue and entertain spectators, but the question itself investigates an under-the-surface truth; why efforts to develop a promising digital product or service fail.
Let’s look at a common and frustratingly frequent timeline in the journey of developing a promising digital product:
- I identify a widespread need surrounding a market problem.
- I envision an idea that serves as the answer to that problem.
- This idea is materialized into a SaaS (Software as a Service) product.
- Initially proposed structure and functionalities of the SaaS stem from my personal understanding of how the problem is addressed and how the tool I’m designing improves users’ daily lives.
- I proceed with development.
- I end up off track regarding both the schedule and the budget.
- The day has come and I finally release my SaaS to the market.
- I realize the market doesn't share my view that the product effectively solves the problem, and users hesitate to adopt it.
- At this point, I have no idea where to start or what changes to make to achieve the desired Product-Market Fit. Then, I’m starting to get caught up in a vicious cycle of questions:
- Was I wrong with my initial diagnosis about the need?
- Did market needs change in the meantime?
- Does the product lack sufficient functionality?
- Was the early testing group the wrong audience?
- Is my SaaS too difficult to use or hard to understand?
- Is it just too early to tell, and the perceived value will emerge later?
- Is this a marketing or sales failure?
- Did I run out of promotion budget because development ate it all?
- The Nightmare Scenario: Is it all of the above?
Do projects fail often?
The short answer is YES.
According to data from The Chaos Report (2020), 69% of digital product development projects fail in the following ways:
- 50% of projects struggle: They fail to finish on time, stay within budget (which usually doubles), or deliver the full promised functionality.
- 19% of projects are cancelled: Resulting in total failure.
This leaves a mere 31% of projects that end up as true success stories.
Data from the 2024 report shows slight improvement, with a rough 39% success rate, but the general picture remains the same.
How can you prevent your project from failing?
Both The Chaos Report and other prestigious sources (such as Asana "Why projects fail: 7 reasons and their solutions", CIO Magazine "Why IT projects still fail") consistently point out five core, well-documented reasons for failure:
- Unclear Requirements
- Poorly Defined or Unattainable Goals
- Changing Requirements (Scope Creep)
- Limited Resources
- Poor Communication
Unfortunately, there is no guaranteed solution for point #5, because it depends entirely on human factors. However, points 1 through 4 have a recognized antidote: Requirements Analysis.
1. Solving Unclear Requirements
The primary reason for analysis is to define goals clearly. By interviewing stakeholders and defining what "success" looks like, we transform vague desires into bounded, detailed requirements.
2. Fixing Poorly Defined Goals
Human expectations only become realistic when details are clear. Analysis allows us to set SMART goals: Specific, Measurable, Achievable, Relevant, and Time-bound. SMART isn't just a buzzword.
3. Managing Scope Creep
Scope Creep happens when requirements aren't locked down, allowing new features to "creep in" under the cover of "clarifications". This keeps moving the goalposts and delays the finish line. A quality analysis phase sets a strict scope baseline, making it easy to flag new requests as "out of scope".
4. Addressing Limited Resources
A key deliverable of requirements analysis is identifying exactly what is needed to reach those SMART goals. This prevents failures caused by a lack of person-power, skills, budget, or even organizational culture.
The Crushing Cost of Skipping Analysis
The financial consequences of skipping the analysis phase are massive and well-documented:
According to The Chaos Report, most software development projects derail significantly in terms of their projected time and cost. The average cost overrun is estimated at 189% of the initial projected cost. When it comes to schedules, the average delay is estimated at 222% of the initial projected time. Furthermore, the reduced functionality that many companies resort to in order to stay within budget and on schedule invariably translates into an additional future budget, often at higher rates, as market prices for product development rarely remain stable.
According to the IBM Systems Sciences Institute, the exponential increase in the cost of addressing bugs as a project progresses reveals some staggering figures:
- Fixing a bug during implementation costs 6 times more than if it had been caught during the design phase.
- If the same error goes undetected until testing, the cost can jump to 15 times higher.
- If the bug is only discovered after the product launch, the cost of remediation skyrockets to 100 times more than if it had been identified earlier. Dealing with the operational consequences has never been a cheap game.
Historically, data from the field of product design and development (eg, When Bad Requirements Happen to Nice People) show that redesign typically requires a budget ranging from 30% to 50% of the total development cost.
Furthermore, 70% to 85% of this redesign budget is attributed to failures in the initial requirements.
The Massive ROI of Quality Initial Design
Let's end with the good news. According to Forrester’s report The UX ROI for B2B Tech Vendors, it is estimated that every $1 invested in initial UX design yields a return of $100.
That is a staggering 9,900% ROI.
For entrepreneurs, the takeaway is clear: effectively protecting your investment in a digital product starts with a smaller, yet crucial, initial investment: Requirements Analysis. It is the digital equivalent of a "satisfaction guarantee" for your development process.