Conclusion of a Project (Meaning and Explanation)

We explain what the conclusions of a project are, how they are made, what errors should be avoided and various examples.

What is the conclusion of a project?

The conclusions of a text are the section in which the reader is offered closure, that is, in which the project ends. This means there is no more content going forward. Besides, there are the definitive findings of the projectthe interpretation of the results of the project, in light of the specialized context to which it belongs.

In simpler terms, the conclusions give the reader the perspective that the author of the project now has, after having done it and having understood what went right, what went wrong, and what it all means.

Therefore, the conclusions constitute a final reflection on the projectmore than a summary of results. In this section, the author or authors specify how they contributed to the general knowledge of humanity (or at least their specific technical area) after having carried out the project.

The conclusions and introduction, ideally, should have some type of dialogue, as an opening and closing of the project.

How are conclusions made?

The conclusions They should begin to be done when the body of the work is ready and developed. Once the point of knowledge about the project has been reached, the conclusions allow us to look at everything in retrospect and point out what went well, what went wrong, and why both things happened. Thus, to write good conclusions we must follow the following points:

TO. As in the case of the introduction of the project, The ideal is that the conclusions start from a set of questions or premises that the project itself brings to light, and for this it is possible to question it, that is, ask questions such as:

What did we learn once the project was completed? How has our understanding of your topic changed?
Were our suspicions regarding the result confirmed? Are the results obtained valuable, revealing or suggestive?
What things would we do differently if we had to repeat the project and why? What aspects of it had weaknesses and how could they be corrected in the future?
Once we have observed the result of the project, what new projects could we undertake? Where should a sequel go and why?

Common errors to avoid in conclusions

Some of the common errors when writing conclusions are:

Talk about anything. The conclusions should undoubtedly offer more general, contextualized and put into perspective information than a mere results section, but that does not mean that we can go around the bush. It is vital to have something to say as a closing, just as it is as an introduction. We cannot abandon the subject completely, although we can return to a broader perspective, less attached to the realization of the project.
Don't add anything new. The conclusions are not a space to repeat what has already been said, nor to state the obvious, but rather to add additional information that could not be understood without having already read the project. In that sense, it forms the counterpart of the introduction: if it provided what was necessary to start reading the work, the conclusions provide what is necessary to understand what was read in perspective.
Limit ourselves to a scheme. Conclusions are not necessarily a set of premises that we can summarize in a diagram. It may well be several pages of explanations, revolving around a central finding of the project. So there is no need to fill a page with items in an outline, when we can perfectly write a readable text.

Examples of project conclusions

Below we will offer some conclusion possibilities, which could be developed and appropriate to the nature of various projects:

A common trait is highlighted of all the results of the project, and it is explained by putting it in relation to other research, other theoretical texts and some background, to offer it as the central finding of the research, which justifies everything read.
Starting from the fact that the results were not entirely as expected, The reader is offered an explanation of what aspects went “wrong.” and if it is possible that, despite not being what was sought, these results are much more interesting and more revolutionary because of what they mean in the matter.
The results of the project are related to the traditional ones or those obtained by previous researchers, and an attempt is made to find the differentiating element, to offer future researchers a way to foresee them, or a new path to follow.
Based on the project experience, the method used is partially or totally questionedto try to propose a new and better one, or to discard it as invalid, at least in the specific topic of the project.
An explanatory summary of the results is provided found, establishing the similarities and differences between them, in order to finally offer a deeper or more creative reading or vision of the topic of the project, which serves as a basis for new research to come.

Introduction of a project

Unlike the conclusions, the introduction is intended to offer the reader all the concepts, contextual data, clarifications or general framework of the issue. That is to say, provides all the information necessary to enter the project topic on the right foot.

Scope and limitations of a project

The scope of the project indicates how far we want to go with it.that is, how far we will go in a topic that we know is vaster and more complicated than we plan to address it. If the project is about the enormous task of eliminating fossil fuels it is logical to explain that only some of the alternatives will be explored.

The scope of the project also depends on its limitations: budgetary, time, complexity, etc. That is to say that limitations are the factors that prevent further progress. Taking them into account, we can explain what we intend to do and within what limits.

Continue in: Scope and limitations of a project