Many of the mistakes that can be found in software products have their origin in the requirements definition and preliminary design stages; likewise, the correction of these demands a greater effort than those generated in the following stages. The lack of effective and transparent communication between those involved in the process (users, experts in the business domain, analysts, developers, etc.) is one of the main causes for the introduction of these errors, which is why a well-defined method and information exchange are necessary. In this way, a validation and early correction of the requirements could be done with the help of those involved, so that the functionalities implemented can be verified in later instance. Through the process of systematic mapping of the literature, fifteen research studies that consider the use of mind maps as facilitators in the exchange of communications of ideas developed in the requirements engineering processes were selected. Concluding that, the inclusion of the development of mental maps is evidenced more frequently in the processes of elicitation, analysis and validation of the requirements, this as a result of the activities developed in these processes involve a constant interaction and communication between expert users of the business domain and the analysts.