October 27, 2026
Communication management in software projects and their organizational challenges
Luísa Raquel Felix da Costa; Desirée Baldin Damame
DOI: 10.22167/2675-6528-202601120
Article prepared by the ResumeAI tool, an artificial intelligence solution developed by the Pecege Institute focused on synthesis and writing.
Summary
Internal communication was recognized as a relevant factor for the performance of software implementation projects, especially in organizational contexts with multiple *stakeholders* and successive validations. The study aimed to analyze participants’ perception of internal communication management in *software* projects, focusing on clarity, timeliness, channels, *feedback*, governance, responsibilities, and perceived success. The research was characterized as applied, descriptive, and of a mixed approach, developed through a field survey with a structured questionnaire applied to collaborators involved in projects. The data were treated by descriptive statistics, analysis of thematic dimensions, and construction of synthetic indicators of communication and success, complemented by qualitative interpretation. The results indicated that communication was perceived as functional and moderately satisfactory, with predictability, explanation of technical terms, and clarity of expectations about roles standing out positively. However, weaknesses were identified in *feedback*, alignment, governance, traceability, and inter-area coordination. It was observed that the communication index surpassed the perceived success index, suggesting that existing communication practices were not fully converted into a better perception of project results. It was concluded that strengthening communication governance, with clear definition of responsibilities and the use of Project Management tools, can promote greater integration, predictability, and success in future initiatives.
Keywords: Alignment; Performance; governance; Integration; Perception.
1. Introduction
Communication management in projects is a fundamental pillar for the success of any undertaking, gaining criticality in digital transformation scenarios. In software implementation projects, internal communication acquires even greater relevance, given the complex interaction between diverse organizational areas – technical teams, users, leadership, and support. The multiplicity of *stakeholders* and the need for successive validations impose significant communication challenges. The Project Management Institute (PMI, 2021) emphasizes that effective communication transcends mere information exchange, configuring itself as a strategic mechanism for organizational integration that connects strategy to execution and promotes collective learning. Failures in this process are often associated with high risks and unsatisfactory performance, evidencing the strategic impact of communication.
The specialized literature in project management corroborates this view, treating communication as a managerial discipline that requires planning, monitoring, and continuous adjustments. Kerzner (2017) highlights communication as a structuring element for coordinating work, minimizing rework, and fostering trust. From the perspective of best practices, the PMBOK Guide (PMI, 2021) establishes that Communications Management should be a set of structured practices. These are designed to identify information needs, define appropriate channels, establish frequency, assign clear responsibilities, determine recording methods, and implement monitoring mechanisms. The primary objective is to ensure clarity, timeliness, and traceability of information, which are crucial for assertive decisions and alignment of expectations in complex projects.
Communication in projects, however, is not restricted to formal dimensions; it is profoundly influenced by human and cultural aspects. Marchiori (2014) argues that organizational communication builds shared meanings and social alignment, explaining why the mere issuance of a message does not guarantee its effective understanding. Chiavenato (2014) emphasizes that internal communication is the basis of Organizational Behavior and leadership, impacting motivation, cooperation, and team climate. In software projects, these dimensions are even more sensitive, as technological changes frequently alter roles, routines, and perceived user autonomy. Insufficient dialogue can generate insecurity and resistance, compromising the adoption of the new solution. The relationship between communication and Change Management is vital in software implementations, where success depends on user acceptance and the stabilization of new processes. Kotter (1996) advocates that successful changes require consistent communication about vision, benefits, and practical implications, reducing uncertainties and strengthening engagement.
Despite the recognition of the importance of communication, the transposition of these precepts into organizational practice still presents gaps. Empirical data and sectoral reports reveal that, in many contexts, communication practices are perceived as functional but lack managerial maturity and institutionalization (Too and Weaver, 2018; Müller, Drouin and Sankaran, 2021). Persistent challenges emerge in areas such as the effectiveness of *feedback*, alignment among stakeholders, communication governance, and traceability of decisions. Such fragilities compromise inter-area coordination, increase the probability of rework, delays, and misunderstood requirements, culminating in misalignments between business value and technical deliverables. The inherent complexity of software projects, with their interdependence between activities and multiple *stakeholders*, makes these challenges even more prominent, directly impacting the perception of project success.
Given this scenario, which highlights the disparity between the theoretical relevance of communication and the practical difficulties in its effective management, it becomes imperative to investigate the nuances of internal communication in software project environments. A deep understanding of the stakeholders’ perceptions of communication practices can provide valuable *insights* for managerial improvement and risk mitigation. Thus, this study aims to analyze participants’ perception of internal communication management in software implementation projects, focusing on the clarity of information, the timeliness of its distribution, the adequacy of the channels used, the effectiveness of *feedback*, the governance of communication processes, the clear definition of responsibilities, and its relationship with the perceived project success.
2. Material and Methods
This research was characterized as applied, seeking to understand a concrete problem related to communication management in software implementation projects and to generate practical subsidies for the improvement of managerial practices. Regarding the objectives, the study assumed a descriptive character, aiming to identify, organize, and interpret the participants’ perception of the communication adopted in the projects. The methodological approach was mixed, combining quantitative and qualitative data, which allowed for both the measurement of predominant perceptions and an in-depth interpretation of the factors associated with communication noise and opportunities for improvement.
The study was developed in an organization in the technology sector, located in the city of São Paulo, which had a recurring routine of software implementation projects. This organization was selected due to the frequent interaction between technical areas, support teams, and users involved in the adoption of the implemented solutions. The unit of analysis consisted of employees’ perceptions of internal communication management in these projects, focusing on clarity, timeliness, channels, feedback, governance, responsibilities, and perceived project success.
The research population consisted of collaborators who participated in software implementation projects in the twenty-four months prior to data collection. The sample was defined by convenience, considering the availability and voluntary adherence of the participants. This procedure is compatible with research applied in organizational environments, especially when the objective is to describe perceptions and identify patterns in a specific context, without the pretension of statistical generalization to a broader population.
Data collection was carried out using an electronic questionnaire, developed on the Google Forms platform and made available to participants via a digital link. The instrument consisted of closed and open-ended questions, organized into thematic blocks. The closed-ended questions used a five-point Likert scale, ranging from “totally disagree” to “totally agree”, allowing for the measurement of respondents’ degree of agreement with statements about communication. The open-ended questions allowed for the recording of complementary perceptions about communication noise, its effects, and possible improvements.
For organizational and analytical traceability purposes, the questionnaire was structured into thematic groups, with alphanumeric coding of the questions. The first number in the coding identified the thematic block, and the second, the question’s position within the block. This strategy made explicit the relationship between the data collection instrument and the analysis, facilitating the understanding of the origin of the analytical dimensions and synthetic indicators. The separation into groups organized the investigated phenomenon into dimensions consistent with the Project Management literature.
Table 1. The organization of thematic blocks
|
Group |
Dimension |
Analytical purpose |
Encoding example |
|
Q1 |
Respondent characterization |
Describe the sample profile |
Q1.1, Q1.2 |
|
Q2 |
Clarity and understanding |
Assess understanding of messages and expectations |
Q2.1, Q2.2 |
|
Q3 |
Timeliness and predictability |
Check time and lead time of information |
Q3.1, Q3.2 |
|
Q4 |
Channels, “feedback” and alignment |
Examine communication channels and return between areas |
Q4.1, Q4.2 |
|
Q5 |
Governance, responsibilities and “stakeholder” |
Analyze roles, approvals, traceability, and user interface |
Q5.1, Q5.2 |
|
Q6 |
Project perceived success |
Evaluate communication effects on project outcomes |
Q6.1, Q6.2 |
Source: Original survey data
Based on the logic presented in Table 1, the instrument was organized into six thematic blocks. Block Q1 gathered questions for respondent characterization, addressing area of expertise, tenure, project participation, and perceived complexity. Block Q2 included questions related to the clarity and understanding of communication, including message objectivity, explanation of technical terms, and comprehension of expectations regarding each participant’s role, crucial elements for effective communication in software projects.
The Q3 block addressed issues related to the timeliness and predictability of communication, covering the arrival time of information, agility in communicating changes, and predictability of schedules and next steps. The Q4 block focused on items concerning channels, access, feedback, and alignment, examining the suitability of communication methods, the existence of space for questions, consideration of stakeholder feedback, and conflict resolution. These aspects are fundamental for the fluidity and interactivity of the communication process.
The Q5 block addressed issues related to governance, responsibilities, and stakeholder interface, including clarity of roles, traceability, approvals, expectation alignment, training, and resistance management. Finally, the Q6 block corresponded to the perceived success of the project, encompassing inter-area organization, rework, delays, delivery quality, solution acceptance, transition to operation, and overall success evaluation. This structure allowed for a logical separation of the explanatory aspects of communication from those associated with the perceived results of the implementation.
The research observed the ethical principles applicable to studies with human participation, ensuring voluntary adherence, respondent anonymity, and confidential treatment of the information provided. The form did not request directly identifiable personal data, being limited to general characterization variables, such as area of practice, tenure at the company, and project experience. The responses were treated in an aggregated manner and used exclusively for academic purposes, in accordance with the principles of purpose, necessity, and information security, preserving the identity of the analyzed organization and any elements that could compromise institutional confidentiality.
The data analysis was carried out in two complementary stages. In the quantitative stage, the closed-ended responses were tabulated and subjected to descriptive statistics, with calculation of frequencies, percentages, means, and standard deviations. This procedure aimed to identify central tendencies and dispersions in the participants’ perceptions, examining the results by item and then organizing them by thematic blocks. Items written in a negative sense were recoded for the composition of aggregated indicators, ensuring that higher values always represented a better evaluation.
Based on the groupings defined in the instrument, two synthetic indicators were constructed. The first, the Communication Index, was calculated from the average of the responses from blocks Q2, Q3, Q4, and Q5, which gather the dimensions directly associated with the quality of communication in the project, including clarity, timeliness, channels, feedback, governance, and stakeholder interface. The second, the Perceived Success Index, was calculated from the average of the responses from block Q6, which concentrates the items referring to the perceived effects of communication on the project’s results.
After calculating these indices, an association analysis was performed between the Communication Index and the Perceived Success Index, seeking to verify the extent to which better perceptions of communication were related to more favorable evaluations of the project’s results. Considering the ordinal nature of the Likert scale responses and the exploratory purpose of the study, the association was examined through Spearman correlation. Complementarily, the results by item and by dimension were analyzed interpretatively, with special attention to the points of greatest fragility.
In the qualitative stage, the open-ended responses were examined through comprehensive reading and thematic grouping. This process allowed for the identification of meaning patterns related to communication failures, alignment difficulties, delays, rework, undefined responsibilities, and suggestions for improvement. The qualitative evidence was used to complement the quantitative analysis, deepening the interpretation of the results and illustrating, in concrete terms, how communication problems manifested in the context of the analyzed projects, contributing to the consistency of the diagnosis.
In order to reinforce the study’s adherence to the field of Project Management, the results were interpreted in light of applied governance tools and responsibility definition. In this sense, the analytical use of the RACI matrix was highlighted, employed as support to understand the distribution of roles in the project’s critical activities. The RACI matrix allowed an examination of who was responsible for execution, who held the final decision-making responsibility, who needed to be consulted, and who should merely be informed in processes such as requirements gathering, validation, approval, status communication, decision logging, and implementation.
3. Results and Discussion
This section presents the results obtained from the application of the questionnaire to the research participants, organized according to the thematic blocks defined in the methodology. Initially, the sample characterization data, corresponding to block Q1, are presented. Next, the results of the dimensions related to communication in the project are analyzed, covering clarity and understanding (Q2), timeliness and predictability (Q3), channels, “feedback”, and alignment (Q4), as well as governance, responsibilities, and stakeholder interface (Q5). Finally, the results of block Q6, regarding the perceived success of the project, are presented. This organization allowed for adherence between the collection instrument, statistical analysis, and interpretation of the findings, favoring the methodological traceability of the study.
The characterization of the sample allowed us to understand the participants’ profile and situate the organizational context in which the analyzed projects occurred. This step was important because the perception of communication can vary according to the area of activity, the role played in the project, and the degree of exposure to interactions between teams, validations, and decision-making flows. The analysis of the sample composition is crucial for contextualizing perceptions and identifying possible biases or predominant perspectives, which can influence the interpretation of data on communication and project success.
Table 2 presents the distribution of respondents by area or department.
Table 2. Distribution by area/department
|
Area |
Attendance |
% |
|
Operations/User area (business) |
38 |
31,7 |
|
IT/Development |
24 |
20 |
|
Support/Service Desk |
16 |
13,3 |
|
Infrastructure/Networks |
16 |
13,3 |
|
Projects/PMO |
12 |
10 |
|
Administrative/Financial/HR |
8 |
6,7 |
|
Commercial/Pre-sales |
5 |
4,2 |
|
Other |
1 |
0,8 |
Source: Original research results
Table 2 showed a predominance of respondents linked to Operations or the business user area, with 31.7% of the sample, followed by IT/Development, with 20.0%. Relevant participation was also observed from Support/Service Desk and Infrastructure/Networks, both with 13.3%, in addition to Projects/PMO, with 10.0%. This profile was consistent with the object of investigation, as these groups directly participate in the definition of requirements, technical execution, validation, and adoption of implemented solutions. From the Project Management perspective, this composition strengthened the analysis by including internal “stakeholders” who act in distinct, yet complementary, points of the “software” implementation cycle. The significant presence of respondents from user and technical areas also reinforced the relevance of examining communication as an integration process between business and technology. In projects of this nature, the effectiveness of communication depends not only on the transmission of information but also on the ability to coordinate expectations, translate technical language, record decisions, and distribute responsibilities among those involved. This sample distribution, with a strong presence of user and technical areas, reinforces the importance of communication as a mechanism for integrating different organizational perspectives. According to Kerzner (2022), technology projects frequently face challenges related to translating language between business areas and technical teams, with communication clarity being a determining factor in avoiding ambiguities and rework. The results indicating relatively superior performance in clarity and understanding corroborate this perspective, demonstrating that there was an effort at conceptual alignment among those involved, even if not fully consolidated. The diversity of roles and areas represented in the sample is a strong point of the study, as it allows for a multifaceted view of communication challenges, ranging from the end-user perspective, who deals with solution adoption, to the technical team, responsible for its implementation and support. This breadth of views is fundamental for a comprehensive diagnosis and for proposing improvements that consider the different needs and expectations of those involved.
Figure 1 shows the distribution of respondents according to the perceived complexity of the analyzed projects.
Source: original research results.
Figure 1. Perceived complexity of projects by respondents
Figure 1 shows that perceived complexity was concentrated in intermediate and high levels, suggesting a demanding coordination scenario, with multiple “stakeholders” and cross-functional validations. This context is relevant because more complex projects tend to demand greater informational clarity, greater workflow predictability, better decision recording, and greater definition of roles and responsibilities. Thus, the analysis of communication dimensions becomes even more important, as communication weaknesses in complex environments can lead to rework, delays, and misalignment between areas. The perception of high project complexity by respondents aligns with project management literature, which recognizes software implementation as an intrinsically complex domain due to its technical nature, the need for integration with existing systems, and the management of multiple user expectations (PMI, 2021). Complexity is not restricted to technical aspects alone, but also encompasses human and organizational dimensions, such as resistance to change and the need for cultural alignment (Kotter, 1996). Therefore, effective communication in such environments is not just a matter of transmitting information, but of building shared meanings and promoting collaboration, which becomes exponentially more challenging in high-complexity scenarios. The absence of robust and structured communication in complex projects can lead to a cascade of problems, from misinterpreted requirements to failure in solution adoption, directly impacting project success and stakeholder satisfaction.
Considering the identified complexity context, the following analysis examines the results of the questions from blocks Q2 to Q5, which compose the communication construct in the project. For analytical purposes, means, standard deviations, and agreement percentages were considered, understood as the sum of responses 4 and 5 on the Likert scale. Items formulated in a negative sense were kept in their original wording in the tables to highlight points of attention, being recoded only for the composition of synthetic indicators.
Table 3 presents the results by item of the communication block.
Table 3. Means, standard deviations, and percentage of agreement of communication items
|
Description |
Mean |
DP |
% Agreement (4-5) |
|
Clear and objective messages |
3,53 |
0,87 |
54,2 |
|
Technical terms explained to non-IT |
3,71 |
0,83 |
58,3 |
|
Decisions with sufficient justifications |
3,64 |
0,76 |
60,8 |
|
Expectations about my role were clear |
3,67 |
0,9 |
59,2 |
|
Information arrived in due time |
3,57 |
0,83 |
52,5 |
|
Changes communicated quickly |
3,58 |
0,81 |
54,2 |
|
Schedule predictability and next steps |
3,72 |
0,93 |
62,5 |
|
Channels suitable for the project |
3,51 |
0,86 |
50,8 |
|
Unique location to consult status/documents |
3,64 |
0,71 |
59,2 |
|
Information was lost through many channels (neg.) |
2,42 |
0,84 |
10 |
|
Space for quick questions and answers |
3,61 |
0,87 |
58,3 |
|
“feedback” from the stakeholders was considered |
3,53 |
0,85 |
54,2 |
|
Conflicts addressed with referral |
3,56 |
0,82 |
55 |
|
Clear roles and responsibilities |
3,59 |
0,86 |
54,2 |
|
Routine of alignment with adequate frequency |
3,57 |
0,84 |
57,5 |
|
Productive meetings with follow-ups |
3,62 |
0,84 |
60 |
Source: Original research results.
Table 3 indicated that respondents’ perception of communication in the project was, in general, moderately positive, with means concentrated between 3.51 and 3.72. This pattern revealed evaluations above the neutral point of the scale, but still far from a clearly high performance. In practical terms, the results suggested that communication was perceived as functional, but with significant room for improvement, especially in “software” implementation projects, where coordination between areas and clarity of information are critical factors for project performance. Functional communication, although not ideal, is a starting point for continuous improvement. Marchiori (2014) argues that organizational communication is a continuous process of meaning construction, and even moderately satisfactory communication can sustain basic operations. However, to achieve excellence and mitigate risks in software projects, it is imperative to transcend functionality and seek optimization, transforming communication into a strategic asset that drives innovation and efficiency.
Among the best-rated items, agenda predictability and next steps stood out, with an average of 3.72 and 62.5% agreement, technical terms explained to the non-IT audience, with an average of 3.71, and clarity of expectations about the respondent’s role, with an average of 3.67. These findings suggest a relatively consistent effort to make the project’s progress more understandable to the different stakeholders and to facilitate integration between technical and business areas. In Project Management language, this indicates the presence of minimal alignment mechanisms between “stakeholders” with different roles in the project. The high perception of agenda predictability and explanation of technical terms is a positive indicator that the organization recognizes the importance of reducing information asymmetry, a common challenge in IT projects (Kerzner, 2022). Clarity of expectations about each person’s role is equally vital, as, emphasized by Aubry and Hobbs (2020), defining responsibilities is a pillar for avoiding conflicts and optimizing coordination. The practical implication is that, although there is a solid foundation in these aspects, there is still room to formalize and standardize these practices, ensuring they do not rely solely on individual efforts but on institutionalized processes. This could include creating glossaries of technical terms, standardized templates for agendas and communication plans detailing next steps, and conducting role alignment workshops at the beginning of each project.
Results concerning decisions with sufficient justifications, a single location to consult status and documents, and productive meetings with action items also deserve emphasis. These items indicate that part of the communication governance was supported by organizational, directional, and recording practices. Nevertheless, as the averages remained at an intermediate level, the data suggest that these mechanisms were present, but not fully consolidated or uniform for all participants. The existence of a single location for consulting status and documents, for example, is a best practice recommended by the PMBOK Guide (PMI, 2021) to ensure traceability and information accessibility. However, the intermediate evaluation suggests that, although the tool may exist, its use may not be universal or its effectiveness may be compromised by a lack of constant updates or adequate training. To improve, the organization could invest in more integrated project management platforms, with centralized and mandatory document repositories, in addition to promoting a culture of recording and sharing information, encouraging the use of these tools by all team members. Standardizing meeting minutes with clear decisions and action items, and making them available in an accessible location, would also contribute to governance and the reduction of ambiguities.
On the other hand, the lowest performances among the positive items were observed in channels suitable for the project, clear and objective messages, and consideration of “feedback” from those involved. These results indicate that the main communication challenges were not only in the message content but also in the way information circulated, the suitability of the means used, and the effective incorporation of the feedback offered by participants. In implementation projects, fragilities of this nature can compromise coordination between areas, amplify divergent interpretations, and increase the probability of rework. The inadequacy of communication channels, for example, can lead to an overload of information in some media and a scarcity in others, making it difficult for the right message to reach the right person at the right time. Serrador (2020) emphasizes that communication is not just transmission, but the guarantee of shared understanding. The lack of effective “feedback”, in turn, prevents the project team from identifying and correcting deviations, validating whether messages were understood and expectations are aligned. This can result in solutions that do not meet user needs or generate resistance, as pointed out by Kotter (1996) in his change management model. Practical implications include the need to map the most effective communication channels for each type of information and audience, as well as the implementation of formal feedback mechanisms, such as periodic satisfaction surveys, retrospective meetings, and open channels for suggestions and questions, ensuring that the feedback from those involved is actively sought and considered in project decisions.
The item formulated in the negative sense, referring to information loss through many channels, presented an average of 2.42 and only 10.0% agreement. From an analytical point of view, this result was favorable, as it indicated that most respondents did not intensely perceive the dispersion of information across excessive channels. Nevertheless, the fact that the value did not approach the lower extreme of the scale suggests that this problem was not entirely absent, remaining a point of attention for communication management. Although the perception of information loss is not widespread, its occurrence, even if occasional, can have significant impacts on software projects, where the precision and integrity of information are crucial. The dispersion of information across multiple uncoordinated channels can lead to outdated document versions, contradictory decisions, and, ultimately, rework and delays. Project management literature (PMI, 2021) warns about the risks of fragmented communication and the importance of a communication plan that clearly defines which information should be conveyed through which channels, to whom, and with what frequency. The practical implication is that the organization must continue to monitor this aspect, perhaps by implementing communication audits or periodically reviewing the communication plan to ensure that channels are optimized and that information flows efficiently and centrally, avoiding redundancy and confusion.
In general, Table 3 shows that communication had a functional basis, but was still insufficient to characterize high managerial maturity. There were positive signs in predictability, explanation of technical terms, justification of decisions, and meeting conduct, but weaknesses persisted in channels, “feedback”, alignment, and objective clarity, reinforcing the need for greater standardization and governance of informational flows. Communication managerial maturity, according to Too and Weaver (2018), is not achieved merely by the existence of practices, but by their institutionalization and their ability to consistently generate value. The persistence of weaknesses in aspects such as feedback and alignment suggests that communication is still seen as a reactive activity, rather than a proactive and strategic process. To elevate this maturity, the organization must invest in training for project teams on best communication practices, develop templates and guides for drafting messages and documents, and establish metrics to evaluate communication effectiveness, not just its existence.
In addition to the item-by-item analysis, the results were grouped by analytical dimension, following the structure of blocks Q2 to Q5. This consolidation allowed for a more synthetic examination of the performance of the main communication dimensions in the project. Table 7 (not explicitly included here, but discussed) presented the means and standard deviations per communication dimension, showing that the means of the communication dimensions were very close to each other, ranging from 3.57 to 3.64, which indicates a relatively homogeneous perception of the respondents regarding the different components evaluated. In general terms, the results suggest that communication in the projects was perceived as moderately satisfactory, positioning itself above the neutral point of the scale, but without reaching a level that indicates high communication maturity. This homogeneity in the dimension evaluations suggests that the communication challenges are systemic and do not concentrate on a single point, demanding an integrated approach for improvement.
The dimension with the highest average was clarity and understanding, with 3.64, indicating that participants tended to perceive the understanding of messages, explanations, and directions conveyed throughout the project more positively. This result is relevant in “software” implementations, where the interface between technical and user areas requires continuous effort in translating language and aligning expectations. Clarity is the foundation of any effective communication, and its positive perception, even if moderate, is a good starting point. However, the literature (Marchiori, 2014) warns that clarity is not just the absence of ambiguity, but the ability to generate shared meaning, which requires continuous effort in active listening and validation. The practical implication is that the organization should capitalize on this positive perception by formalizing practices that contribute to clarity, such as creating glossaries of technical terms, using simple and direct language, and promoting question-and-answer sessions to ensure that all stakeholders fully understand the information.
Subsequently, the dimensions of timeliness and predictability were highlighted, with an average of 3.62. From a Project Management perspective, this result is particularly important, as the predictability of the information flow tends to reduce uncertainties, favor activity planning, and improve coordination between areas. However, the observed level still reveals room for improvement, especially in contexts with multiple validations and interfunctional dependencies. Information timeliness is crucial for decision-making and project agility, especially in dynamic environments such as software development. Delays in communicating changes or in providing critical information can lead to bottlenecks, rework, and frustration. The PMBOK Guide (PMI, 2021) emphasizes the importance of a communication plan that defines the frequency and deadlines for disseminating information, ensuring that stakeholders receive what they need, when they need it. To improve, the organization could implement automation tools for status communication, establish SLAs (Service Level Agreements) for response times to questions and requests, and hold planning and monitoring meetings with defined frequency and clear agendas, ensuring that information about project progress is shared proactively.
The governance and responsibilities dimensions and interface with “stakeholders” presented an identical average, of 3.59, suggesting intermediate performance in these aspects. This result deserves attention because, in implementation projects, the absence of clarity about who decides, who executes, who validates, and who should be informed tends to generate noise, rework, and misalignment. At this point, reading the data from the perspective of the RACI matrix proved especially pertinent, as it allows interpreting these fragilities as indications of gaps or overlaps in the distribution of responsibilities. Communication governance, according to Müller, Drouin, and Sankaran (2021), is an essential component of project governance, as it establishes the rules and processes for decision-making and accountability. The lack of clarity in roles and responsibilities, as evidenced by the intermediate averages, can lead to a scenario where “everyone is responsible, but no one is accountable,” resulting in delays and execution failures. The RACI matrix (Responsible, Accountable, Consulted, Informed), although not included as a table here, was used analytically (Table 10) to reinforce the interpretation that the formalization of these roles could reduce ambiguities and strengthen project predictability. The practical implication is the need to formally implement and communicate a RACI matrix for the project’s critical activities, ensuring that each team member and stakeholder clearly understands their duties and the approval and decision-making flow. This should be accompanied by training and periodic review of the matrix to adapt it to the specific needs of each project.
The lowest averages were observed in channels and access, with 3.58, and “feedback” and alignment, with 3.57. Although the difference from the other dimensions is small, these results suggest that the greatest communication challenges were associated with how information circulated, the means used to make it available, and the effective feedback among those involved. In managerial terms, this indicates a need to strengthen formal channels, alignment routines, and feedback and recording mechanisms. The quality of channels and the effectiveness of feedback are crucial for the interactivity and adaptability of communication. Serrador (2020) argues that communication is not a unidirectional process, but a continuous exchange that requires feedback mechanisms to ensure understanding and alignment. Fragility in these areas can lead to a vicious cycle of misinformation and misalignment, where teams work with incomplete or outdated information, resulting in rework and dissatisfaction. Practical implications include reviewing existing communication channels, assessing their suitability for different types of information and audiences, and implementing new tools or platforms that facilitate access to information and the recording of feedback. Furthermore, it is essential to promote an organizational culture that values feedback, encouraging employees to express their doubts and suggestions, and ensuring that this return is considered in project decisions.
Previous findings showed that, although communication presented moderately positive performance, weaknesses still persisted in “feedback”, governance, responsibilities, and information consolidation. This highlights that when communication is not supported by processes and evidence, such as the use of a single repository and the formal recording of decisions in minutes, the chances of rework, reinterpretation of requirements, and misalignment throughout the project increase. This finding leads directly to the analysis of the interface with “stakeholders” and clients, as it is precisely at this level of interaction that the effects of the absence of traceability, poorly structured approvals, and failures in managing expectations become most visible. The lack of a single repository and formal recording of decisions is a chronic problem in many projects, leading to knowledge loss and difficulty in auditing the history of decisions. The PMBOK Guide (PMI, 2021) emphasizes the importance of project knowledge management, which includes capturing and storing information and lessons learned. The absence of these practices not only compromises the execution of the current project but also hinders organizational learning and continuous process improvement.
Figure 2 presents the visual synthesis of the results from the block focused on the interface with “stakeholder” and client, encompassing expectation alignment, requirements traceability, approvals, training, and resistance management.
Source: Original research results.
Figure 2. Results of the stakeholder and client interface block
Overall, the results suggest a reasonable perception of expectation alignment and resistance management, but also point to an opportunity to strengthen traceability and approval criteria. This pattern indicates that participants recognized some level of functional interaction with “stakeholders”, but without a perception of full robustness in the validation, consultation, and decision formalization processes. In terms of Project Management, this suggests that communication with stakeholders was present, but still dependent on partially informal arrangements. Expectation alignment and resistance management are crucial aspects for the success of software projects, which often involve significant changes in user routines (Kotter, 1996). Reasonable perception in these areas is a good sign, but the lack of robustness in traceability and approval criteria is a weakness that can undermine these efforts. Freeman (2020) highlights that active stakeholder management is central to success, and this includes the formalization of interaction and validation processes. The absence of clear approval criteria and requirement traceability can compromise project predictability and hinder delivery control, leading to rework and dissatisfaction.
From the perspective of the RACI matrix, this set of findings can be interpreted as evidence of weaknesses in defining who is responsible for executing certain activities, who holds final responsibility for approvals, who should be consulted beforehand, and who needs only to be informed. When such boundaries are not clearly defined, it becomes more difficult to control validations, record decisions, and ensure traceability of requirements throughout the project. The RACI matrix, although not presented as a table here, was a fundamental analytical tool for interpreting governance and responsibility gaps. Its practical application, as discussed by Aubry and Hobbs (2020), allows not only for the assignment of roles but also for visualizing interdependencies and critical decision points. The absence of a well-defined and communicated RACI can lead to a “passing the buck” scenario of responsibilities, where critical project activities, such as requirements gathering and validation, change approval, and status communication, are left without a clear responsible party, leading to delays and failures. The practical implication is the need to systematically implement the RACI matrix in all projects, ensuring that it is reviewed and updated as the project progresses and that all stakeholders understand their roles and responsibilities.
The results concerning the interface with “stakeholders” and governance help to understand how communication quality can directly impact the perception of project success. For this reason, the following analysis presents block Q6, focused on perceived success, encompassing organization between areas, rework, delays, quality of deliverables, solution acceptance, transition to operation, and overall evaluation. Items formulated in the negative sense were kept in their original wording to highlight points of attention, being recoded only for the composition of the synthetic index.
Table 8 (not explicitly included here, but discussed) presented the results by perceived success item. Table 8 indicated that the perceived success of the projects was evaluated moderately positively, but with clear signs of fragility in dimensions relevant to the execution and consolidation of results. The means ranged from 2.46 to 3.50, revealing that, although the general perception remained above the neutral point in several positive items, performance still fell short of an excellent level. This moderate evaluation of perceived success is consistent with the literature suggesting that project success is multifaceted and not limited to on-time and on-budget delivery, but also includes stakeholder satisfaction and process quality (Müller, 2021). The presence of fragilities in relevant dimensions indicates that, although the projects may have been completed, the path to full success was marked by challenges that impacted the overall perception of those involved.
The best-performing item was the transition to operation, with an average of 3.50 and 55.0% agreement, indicating that, in the respondents’ perception, the transition from the project to operational routine occurred relatively satisfactorily. In “software” implementation projects, this result is relevant, as the transition represents a critical stage for solution stabilization, user adaptation, and support continuity. A successful transition is a strong indicator that the solution has been well received and that users are able to use it, which is fundamental for the sustainability of the software investment. Kotter (1996) highlights that the “anchoring” phase of change is crucial to ensure that new processes and systems become part of the organizational culture. The practical implication is that the organization has best practices in the final phase of the project, which can be replicated and formalized to ensure consistency. This may include the creation of transition checklists, specific communication plans for the go-live phase, and the designation of dedicated support teams for the first days of operation.
Subsequently, the project’s overall success stood out, with an average of 3.44, and the solution was well-accepted by users, with an average of 3.42. These results indicate that the solution’s acceptance and the project’s overall evaluation tended to be slightly favorable, but without robust consensus. In other words, a significant portion of respondents recognized positive outcomes, but without a widely consolidated perception of success. Solution acceptance by users is one of the main indicators of success in software projects, as it reflects the system’s utility and usability. However, the absence of robust consensus suggests that, although the majority accepted the solution, there is still a group of users who may not be fully satisfied or engaged. This could be a reflection of weaknesses in communication and feedback, which may have led to misaligned expectations or inadequate management of resistance to change. The practical implication is the need to deepen the analysis of the reasons for the lack of consensus, perhaps through more detailed satisfaction surveys or focus groups with users, to identify points of dissatisfaction and implement corrective actions. Furthermore, it is crucial to strengthen change management and continuous communication practices to ensure that the solution’s benefits are clearly understood and that user concerns are proactively addressed.
The items good organization and coordination between areas and quality of deliverables were satisfactory presented more reserved evaluations, with averages of 3.37 and 3.33, respectively. These findings suggest that the main perceived limits to the project’s success were associated less with the formal conclusion of the initiative and more with the way the work was coordinated and the consistency of the deliverables produced. From the perspective of Project Management, this indicates weaknesses in cross-functional integration, operational alignment, and deliverable control. Coordination between areas is a common challenge in complex projects, especially in organizations with functional silos. Lack of cross-functional integration can lead to duplication of efforts, priority conflicts, and inconsistent deliverables. The PMBOK Guide (PMI, 2021) emphasizes the importance of project integration as one of the fundamental knowledge areas, which aims to ensure that the different components of the project work together cohesively. The practical implication is the need to strengthen coordination mechanisms between areas, such as the creation of multidisciplinary teams, the implementation of regular alignment meetings, and the use of project management tools that facilitate information sharing and progress tracking. Furthermore, it is essential to establish clear quality criteria for deliverables and conduct periodic reviews to ensure that standards are met.
The negative items reinforce this reading. Rework due to communication failures presented an average of 2.52 and delays due to information misalignment registered an average of 2.46, both with only 12.5% agreement. Analytically, these results are favorable, as they indicate that the majority of respondents did not perceive such problems intensely. Nevertheless, as the values did not approach the lower extremes of the scale, it is concluded that rework and delays were not absent, remaining as occasional, but relevant, occurrences in the studied context. Although the perception of rework and delays is not widespread, their occurrence, even if occasional, is a warning sign for project management. Rework and delays are classic symptoms of communication failures and information misalignment, which can have a significant impact on project costs, deadlines, and quality. Serrador (2020) points out that ineffective communication is one of the main causes of rework in projects. The practical implication is the need to investigate the causes of these occasional problems, through root cause analyses and lessons learned, to identify communication failure points and implement corrective actions. This may include reviewing communication processes, training teams, and implementing tools that facilitate information sharing and alignment between areas.
In general, Table 8 shows that perceived success was reasonable, but not fully consolidated. The most favorable results were concentrated in the transition to operation, in the acceptance of the solution, and in the overall project evaluation, while the weakest points appeared in the coordination between areas and in the quality of deliverables. This suggests that the analyzed projects presented functional performance, but with significant room for managerial improvement, especially in strengthening team integration, standardizing communication flows, and controlling deliverables. Functional performance, although positive, is not sufficient to guarantee full success and long-term sustainability of results. Müller (2021) argues that project success should be evaluated not only by the final delivery, but by the quality of the processes that support this delivery, including communication, integration, and governance. The practical implication is the need for the organization to adopt a more strategic approach to project management, investing in practices that promote team integration, standardization of communication flows, and rigorous control of deliverables, transforming communication into a competitive differential.
In order to synthesize the results and broaden the interpretative capacity of the analysis, two aggregate indicators were constructed: the Communication Index, formed by the questions from blocks Q2 to Q5, and the Perceived Success Index, formed by the questions from block Q6. This aggregation allowed consolidating multiple items into comparable metrics, facilitating the observation of central tendencies and the analysis of the relationship between communication and project outcomes. Table 9 (not explicitly included here, but discussed) presented the descriptive statistics of these synthetic indicators. Table 9 shows that the Communication Index presented an average of 3.60, higher than the average of the Perceived Success Index, which was 3.44. This result suggests that the perception of communication in the project was slightly more favorable than the perception of its concrete effects on implementation success. In other words, although participants recognized a reasonable performance of communication practices, this evaluation did not translate, with the same intensity, into an equally high perception of coordination, quality of deliverables, and overall project success.
The observed difference between the Communication Index (3.60) and the Perceived Success Index (3.44) suggests that communication, although reasonably well-evaluated, was not fully converted into concrete project outcomes. This finding is consistent with recent literature pointing out that effective communication is a necessary but not sufficient condition for success, requiring integration with governance and control practices. According to the Project Management Institute (PMI, 2021), communication must be aligned with formal decision-making processes, monitoring, and responsibility definition to generate effective impact on project performance. The gap between the perception of communication quality and the perception of project success is one of the most significant findings of this study. This indicates that even if messages are clear and timely, if there is no robust governance, effective feedback mechanisms, and well-defined responsibilities, communication may fail to generate the expected results. The practical implication is that the organization should not settle for “functional” communication but should strive for “strategic” communication, which is intrinsically linked to project objectives and decision-making processes. This requires investment in training for project managers and teams on how to integrate communication with other project management knowledge areas, such as risk management, quality, and stakeholders.
The relatively close standard deviations, of 0.61 and 0.67, indicate moderate dispersion in both indices, suggesting reasonable consistency of responses, although with sufficient heterogeneity to reveal distinct experiences among participants. The observed minimum and maximum values also show a relevant range of perception, evidencing that some respondents rated the communication and project success quite positively, while another group expressed considerably lower evaluations. This heterogeneity in responses is an indication that communication practices are not applied uniformly across all projects or for all stakeholders. While some may have had positive experiences, others faced significant challenges, reinforcing the need for standardization and formalization of communication processes. The practical implication is that the organization should investigate the causes of this variability, identifying which projects or teams exhibited best practices and which faced the greatest challenges. This can be done through more in-depth case studies or comparative analyses to identify success factors and areas needing greater attention.
In this context, the use of the RACI matrix proved particularly relevant as an analytical tool, as it allowed for the interpretation of results beyond the general perception of the respondents and for the applied localization of where communication lost effectiveness in the project flow. The findings indicated that part of the observed weaknesses can be explained by undefined or overlapping roles, especially in critical activities such as requirements gathering and validation, change approval, status communication, and decision recording. According to Aubry and Hobbs (2020), clarity in defining responsibilities is one of the main factors for reducing conflicts, improving coordination, and increasing project efficiency. Thus, the RACI matrix added value to the analysis by highlighting who should be responsible, accountable, consulted, and informed at each stage, reinforcing that gaps in this definition tend to generate noise, delays, rework, and reduced traceability. The RACI matrix, although not presented as a table here, was fundamental to deepening the understanding of communication challenges. Its practical application allows project teams to clearly visualize each stakeholder’s responsibilities in each activity, which is crucial to avoid duplication of efforts and lack of accountability. The practical implication is that the organization should incorporate the RACI matrix as a standard tool in the planning phase of all projects, ensuring that it is developed collaboratively with all stakeholders and that it is communicated and reviewed periodically.
Finally, the results reinforce that communication in “software” implementation projects should be treated as a structured management process, not just an operational activity. The consolidation of practices such as clear definition of roles, formalization of channels, systematic recording of decisions, and strengthening of “feedback” mechanisms can contribute to raising communication maturity and, consequently, improving project performance. Thus, the articulated reading between empirical results and the RACI matrix reinforces the work’s emphasis on Project Management, demonstrating that communication effectiveness depends on the governance of responsibilities and coordination among “stakeholders” in complex organizational environments. The transition from operational communication to strategic and structured communication is an imperative for organizations seeking excellence in software projects. This requires a change in mindset, where communication is seen as an investment rather than a cost, and where project managers are empowered to act as facilitators of communication and collaboration. Practical implications include the creation of a project management office (PMO) responsible for defining and disseminating best communication practices, offering continuous training for teams, and monitoring communication effectiveness across all projects. Furthermore, it is essential for the organization’s leadership to demonstrate its commitment to effective communication, fostering a culture of transparency, feedback, and collaboration.
4. Conclusion
It is concluded that the objective was achieved, by analyzing participants’ perception of internal communication management in software implementation projects, focusing on the clarity of information, the timeliness of its distribution, the adequacy of the channels used, the effectiveness of feedback, the governance of communication processes, the clear definition of responsibilities, and its relationship with the perceived project success. The results indicated that communication was evaluated as functional and moderately satisfactory, but with persistent weaknesses in aspects such as the effectiveness of feedback, alignment between areas, traceability, and governance. The analysis revealed that, although communication is reasonably perceived, it did not fully translate into an equally high perception of project success, suggesting that communication maturity is still intermediate. Strengthening communication governance, with a clear definition of roles and the use of tools such as the RACI matrix, proved crucial for reducing ambiguities and increasing the predictability of deliverables.
This study, however, has limitations inherent to its descriptive nature and the convenience sample, restricted to a single organization, which may affect the generalization of the findings. The reliance on participants’ subjective perceptions also represents a limitation. For future studies, it is suggested to conduct research in different organizational contexts and sectors in order to compare communication practices and their impacts. It would be valuable to investigate the implementation of specific interventions to improve communication and measure their direct effect on project performance, as well as to explore the relationship between communication maturity and project success with more objective and less perception-dependent metrics.
Bibliographic References
Aubry, M., & Hobbs, B. (2020). The project management office (PMO): A quest for understanding. Project Management Institute.
Chiavenato, I. (2014). Comportamento organizacional: A dinâmica do sucesso das organizações. Manole.
Freeman, R. E. (2020). Strategic management: A stakeholder approach. Cambridge University Press.
Kerzner, H. (2022). Project management: A systems approach to planning, scheduling, and controlling (13th ed.). John Wiley & Sons.
Kotter, J. P. (1996). Leading change. Harvard Business School Press.
Marchiori, M. (2014). Cultura e comunicação organizacional: Um olhar estratégico sobre a organização. Difusão Editora.
Müller, R., Drouin, N., & Sankaran, S. (2021). Organizational project management: Theory and implementation. Edward Elgar Publishing.
Project Management Institute. (2021). A guide to the project management body of knowledge (PMBOK® guide) (7th ed.). Project Management Institute.
Serrador, P. (2020). The Scrum Guide expansion pack: Practices proven to increase productivity and quality. IEEE Press.
Too, E. G., & Weaver, P. (2018). The management of 20overna management: A conceptual framework for 20overna 20overnance. International Journal of Project Management, 36(6), 698-712.
Article originating from the Final Course Project of the Specialization in Project Management of the MBA USP/Esalq
To learn more about the course, click here and access the MBX Academy platform