Why do web projects fail?

We have probably all heard of authorities ordering web solutions for millions of kronor, which result in delay after delay and poor quality. This is certainly not only a phenomenon in the public sector, but is at least as common in the private sector.

The phenomenon is not only common in the IT industry, but also in business in general. It is usually discussed that web projects run a high risk of being significantly more expensive and delayed than expected. But there are also horror stories where the web solution even has to be scrapped due to poor quality.

With the next ten years of experience in the industry, we can confirm that this unfortunately happens in all kinds of organizations and industries. Even in the most well-known agencies and companies. During our ten years, we have ourselves been involved in projects where the web solution has had to be scrapped and reworked.

But back to the problem and the essence of this post – why are web projects often delayed and more expensive than planned?

Of course, it can always be due to a lack of competence within the project team, or an uninterested and ignorant client. But based on our experience and academic studies, the biggest reason for failed web projects is a lack of preparatory work before the project starts.

What does preparatory work for a web project mean?

Preparatory work is simply the work that is done before the project starts. This includes all the documentation that affects the implementation of the project. Usually, a failed web project can be traced back to an incorrectly written requirements specification that generates a chain reaction of errors.

If the requirements specification is incorrect, this can lead to the choice of the wrong technology, an incorrect perception of the scope of the project and thus also a misleading schedule and budget. It is thus clear that an incorrectly written requirements specification increases the risk of a failed web project.

How do I write a requirements specification?

Writing a proper and correct requirements specification is more difficult than many people think and requires knowledge of requirements management. It is common for businesses to produce requirements specifications as bulleted lists of thoughts about the intended website or web system, but unfortunately this is not enough.

A requirements specification must be well-structured and clear in order to provide an accurate picture of the intended web solution. It should include functional and non-functional requirements, which must also be written in a correct manner.

If the project is not described in detail at an early stage, it is likely that the project team and the client will have different expectations. Unfortunately, it is common for web projects to be started despite an incorrectly written requirements specification with a lack of necessary requirements. This is a mistake that we also made before we changed our offering.

An important aspect to remember is that what is written in a requirements specification is what is developed. This means, for example, that authorities that have received a slow web solution because the performance was not specified in the non-functional requirements are still legally bound to pay the supplier. That is why it is especially important to do solid preliminary work and produce a well-developed requirements specification, in order to avoid this type of situation.

Why don’t all suppliers offer feasibility studies?

We also wonder that if we are honest, but at the same time we have been in the same situation. It is usually about wanting to row a project to port. Instead of urging the client that a feasibility study is required to produce a well-formulated and correct requirements specification, they instead choose to quote on a requirements specification that is not detailed enough.

This is because it takes courage and energy to tell the client that the basis is not good enough. It is a risk that you must be willing to take to guarantee a successful web project. It is only through properly carried out preparatory work that the risks of a failed web project can be reduced.

An investment in a preliminary study to obtain the right basis even before the project starts usually costs a few percent of the total cost of the project. The problem lies in the fact that most people in the industry are focused on starting the “real” development work, and that they skip informing the client about the shortcomings in the preparatory work.

We have been in exactly the same situation. But we have thought differently to create the necessary conditions for successful web projects and thereby reduce the risk of web projects being delayed and more expensive than planned.

Do you need help ensuring that your upcoming web project does not end up in this classic trap? Get in touch and we will help you further!