PaperlayerView exact revision on arXiv

Source-linked AI summary

Psychological Safety in Software Engineering Teams: A Systematic Mapping Study of Team Processes and Performance

Adnan Manzoor, Muhammad Azeem Akbar, Jussi Kasurinen, Muhammad Hamza, Aakash Ahmad, Abdul Razzaq

arXiv:2610.08896v1cs.SE

TL;DR

Research on psychological safety in software engineering is fragmented across concepts, outcomes, and contexts, limiting coherent synthesis and practical intervention design. This systematic mapping study analyzes 112 primary studies and finds that psychological safety is multidimensional and context-dependent, associated with team processes and performance.

  • Problem

    Software-engineering evidence on psychological safety is fragmented, inconsistently conceptualized, and lacks an integrated mapping of its links to processes, outcomes, contexts, barriers, and strategies.

    Source: §1 · pp. 1–2

  • Method

    The study maps 112 primary studies published from 2006 through June 2026 using descriptive and thematic analysis across six research questions.

    Source: §9 · p. 44

  • Results

    Psychological safety is a multidimensional team-level construct associated with productivity, software quality, innovation, team satisfaction, collaboration, communication, and decision-making, with relationships shaped by contextual conditions.

    Source: A. Discussion of RQ1 · p. 29, §9 · p. 45

  • Takeaways & Limitations

    The mapping provides a structured foundation for research and practice, while pointing to longitudinal, context-sensitive study of interventions as a future need.

    Source: §1 · p. 2

    The study acknowledges potential threats to internal, external, construct, and conclusion validity.

    Source: §8 · p. 43

Abstract

from arXiv · show

Context: Psychological safety is an important human and behavioral factor in software development teams, supporting collaboration, knowledge sharing, interpersonal risk-taking, and learning. However, evidence in software engineering remains fragmented across team processes, performance outcomes, contextual conditions, barriers. Objective: This study maps literature on psychological safety in software engineering, examining its conceptualization, associations with team performance and processes, contextual influences, barriers, and strengthening strategies. Method: We conducted a systematic mapping study following established software engineering guidelines. We analyzed 112 primary studies published between 2006 and June 2026 using descriptive statistics and thematic analysis across six research questions. Results: Psychological safety emerges as a multidimensional, context-dependent, team-level construct characterized by interpersonal risk-taking, open communication, collaboration, learning, trust, and supportive interaction. It is predominantly associated with productivity, software quality, innovation, team satisfaction, collaboration, communication, and decision-making. These relationships are shaped by leadership, organizational culture, work environment, trust, and sociocultural and individual conditions. Recurring barriers include communication problems, organizational constraints, leadership issues, diversity and inclusion challenges, and workload pressures. Although diverse practices are reported, evidence of their effectiveness and long-term sustainability remains limited. Conclusion: Psychological safety is a multidimensional, context-dependent team-level construct associated with team interaction and performance. This study highlights the need for longitudinal, context-sensitive research on psychological safety interventions in software development environments.

1 Introduction

Software engineering depends on collaboration and human interaction, yet psychological-safety research remains fragmented and inconsistently conceptualized. This study maps psychological safety across software-team performance, processes, and contextual factors.

1 Introduction

  • The literature is fragmented across disciplines and topics, with inconsistent definitions and limited software-engineering-specific synthesis; the study maps these relationships and reported strategies.Its scope includes conceptualization, performance and team processes, contextual influences, barriers, and strengthening strategies.Source: §1 · pp. 1–2

A. Software Engineering Teams and Their Performance

  • Software teams coordinate interdependent work in agile, cross-functional, and distributed settings, with performance spanning productivity, software quality, innovation, and team satisfaction.Team outcomes depend on both technical capabilities and social factors shaping interaction, coordination, and collective work.Source: A. Software Engineering Teams and… · p. 3

B. Human Factors in Software Engineering Teams

  • Human factors include communication, leadership, trust, coordination, and cognitive load, while workload and resource constraints can shape team interaction and effectiveness.The study treats these as broader interpersonal, behavioral, cognitive, and organizational conditions around teamwork.Source: B. Human Factors in Software… · p. 3

C. Psychological Safety in Software Engineering Teams

  • Psychological safety is a shared team belief that interpersonal risk-taking is supported, enabling members to speak up, ask questions, acknowledge mistakes, and raise concerns.In software teams, it is reflected in open communication, knowledge sharing, feedback-seeking, and learning-oriented interaction.Source: C. Psychological Safety in Software… · p. 3

3 Research Method

  • The review follows established systematic-mapping phases and uses inter-rater agreement during study selection, structured extraction verification, and predefined quality criteria.The process is organized into planning, conducting, and reporting the review.Source: §3 · p. 4

A. Planning the Review

The review plan uses six research questions to map psychological safety concepts, outcomes, processes, contexts, barriers, and strategies. It searches selected digital libraries using an iteratively refined Boolean query, while noting that database coverage is not exhaustive.

1) Specify Research Questions

  • Six research questions cover conceptualization, performance outcomes, team processes, contextual influences, barriers, and strategies for strengthening psychological safety.The questions align the review objectives with its planned data extraction and synthesis.Source: 1) Specify Research Questions · p. 4

2) Identify data sources

  • The review searches five digital libraries selected for software engineering and interdisciplinary research, but their coverage does not guarantee an exhaustive literature set.The selected sources are described as sufficient for capturing a representative set of relevant publications.Source: 2) Identify data sources · p. 4

3) Formulate of Search Query

  • The Boolean query was iteratively refined through domain expertise and pilot searches after PICO-based construction exceeded several libraries’ query-length limits.It combines psychological or human-factor constructs, team-performance and process dimensions, and software-engineering context terms.Source: 3) Formulate of Search Query · p. 5
  • The final searches, conducted in June 2026, cover publications from 2006 through 2026.Boolean operators were used to connect psychological and performance-related aspects within software-engineering contexts.Source: 3) Formulate of Search Query · p. 5

4) Define Inclusion and Exclusion Criteria

The review defined scope-based inclusion and exclusion criteria, then screened database results and snowballed the final selections to assemble 112 primary studies.

4) Define Inclusion and Exclusion Criteria

  • The criteria selected peer-reviewed work on psychological safety and human factors in software engineering while excluding non-English, non-peer-reviewed, and out-of-domain studies.Methodological quality was assessed separately during the later quality-assessment stage.Source: 4) Define Inclusion and Exclusion… · p. 6

1) Select Primary studies

  • Screening proceeded from database searches through relevance, title, abstract, and full-text review, with 1,184 records initially retrieved and 647 irrelevant studies removed.Cohen’s kappa values for sampled inter-rater checks ranged from 0.68 to 0.77 across reported stages.Source: 1) Select Primary studies · pp. 6–7
  • 112 primary studies formed the final dataset after full-text screening retained 104 studies and snowballing added eight eligible studies.Snowballing continued until no additional relevant studies were identified.Source: 1) Select Primary studies · p. 7

2) Perform a Quality Assessment

The study assessed included papers against quality criteria, extracted demographic and research-question data, and combined descriptive statistics with thematic analysis to synthesize findings.

2) Perform a Quality Assessment

  • All 112 studies met the minimum quality threshold of 2.5 and were retained for data extraction and synthesis.Each study’s total was the sum of five criteria scored 1, 0.5, or 0.Source: 2) Perform a Quality Assessment · pp. 7–8

3) Perform Data Extraction

  • The extraction form separated study demographics (S1–S8) from research-question data on concepts, outcomes, processes, context, barriers, and strategies (S9–S14).A pilot extraction refined the form before full extraction, and extracted data were reviewed and discussed.Source: 3) Perform Data Extraction · pp. 8–9

4) Perform Data synthesis

  • Descriptive statistics summarized study characteristics, while thematic analysis organized qualitative findings through coding, subthemes, theme refinement, and naming.Authors collaboratively participated in theme brainstorming; the process is illustrated in Fig. 3.Source: 4) Perform Data synthesis · pp. 9–10, Figure 3 · p. 10

C. Reporting the Review

This section reports how the mapping study organizes evidence from 112 studies around six research questions, covering psychological safety’s conceptualization and its associations with team interaction, performance, and supportive team conditions. It summarizes findings on productivity, software quality, innovation, and team satisfaction in software engineering teams.

C. Reporting the Review

  • The review reports thematic findings in Section 4, discusses and interprets them in Section 5, and presents study comparisons, research gaps, validity threats, and conclusions in Sections 6–9.These sections respectively cover comparison, gap synthesis, threats to validity, and the study's overall conclusions and contributions.Source: C. Reporting the Review · pp. 10–11

4 Results

  • Results present publication trends and study distribution before findings for six research questions; thematic frequencies are non-mutually exclusive and may exceed the studies addressing a question.The findings cover conceptualization, performance and processes, contextual factors, barriers, and improvement strategies.Source: §4 · p. 11

A. Overview of Included Studies:

B. Conceptualization of Psychological Safety in Software Engineering Teams (RQ1):

  • Psychological safety is primarily conceptualized as a shared team condition enabling interpersonal risk-taking, open communication, idea expression, feedback, and discussion of mistakes without fear.Among 106 studies addressing RQ1, communication-related conceptualizations were most common (37 studies), followed by collaboration (18); the analysis identified seven themes and 25 subthemes.Source: B. Conceptualization of Psychological… · pp. 12, 14, Table VIII · p. 13
  • Productivity evidence from 67 studies associated psychological safety with productivity directly and through collaboration, communication, learning, feedback, knowledge sharing, trust, and proactive behavior.Learning, feedback, and knowledge processes were the most frequently represented productivity theme, with 24 studies.Source: B. Conceptualization of Psychological… · pp. 14–15
  • Software quality evidence from 25 studies linked psychological safety to supportive human interactions and learning-oriented processes, including error reporting, knowledge sharing, feedback, and innovation.The review characterizes these links as reported through team interaction and learning rather than as a direct technical effect.Source: B. Conceptualization of Psychological… · p. 15
  • Innovation evidence from 33 studies linked psychological safety to idea sharing, creativity, exploration, learning, and supportive climates; satisfaction evidence from 34 studies linked it to trust, well-being, and supportive interactions.Inclusive team environments were also associated with innovative behaviors.Source: B. Conceptualization of Psychological… · pp. 15–16

C. Reporting the Review

  • Psychological safety is associated with productivity, software quality, innovation, and team satisfaction through team-level mechanisms and supportive interpersonal conditions.Reported mechanisms include collaboration, communication, learning, knowledge sharing, trust, and feedback; the outcomes include both technical and human-centered performance.Source: B. Conceptualization of Psychological… · p. 16
  • Psychological safety supports productivity through collaboration, communication, learning, and knowledge sharing; quality through error reporting and problem discussion; and innovation through idea sharing, creativity, and experimentation.Quality is also linked to trust-based collaboration and effective communication, while innovation is linked to knowledge exchange.Source: B. Conceptualization of Psychological… · p. 17
  • Psychological safety improves team satisfaction through trust, well-being, motivation, positive relationships, and supportive team conditions.Thirteen studies (11.6%) linked satisfaction to clear roles, reflexivity, performance processes,,,,,,, and supportive organizational climates, norms, and systems,,,,,.Source: B. Conceptualization of Psychological… · pp. 16–17
  • Supportive leadership, an inclusive team climate, and clear team structures strengthen psychological safety and improve overall team performance.Source: B. Conceptualization of Psychological… · p. 17

D. Influence of Psychological Safety on Team Processes (e.g.collaboration, communication, decision-making)(RQ3):

Psychological safety is associated with collaboration, communication, knowledge exchange, participation, and collective decision-making in software engineering teams. Collaboration and communication receive more attention than decision-making, and trust, leadership, and relationships shape how these processes occur.

Team collaboration

  • 53 studies (47.3%) address collaboration, linking psychological safety with idea-sharing, task coordination, problem-solving, constructive conflict, and collaborative learning.Trust, positive relationships, and supportive leadership and team contexts also shape psychological safety for collaboration.Source: D. Influence of Psychological Safety… · p. 18

Team communication

  • 41 studies (36.6%) examine communication, with findings linking psychological safety to open dialogue, mistake-sharing, constructive feedback, and exploratory communication.The review also identifies information and knowledge exchange, while trust, emotional conditions, organizational context, and team processes shape participation and communication quality.Source: D. Influence of Psychological Safety… · pp. 18–19

Team decision-making

  • 17 studies (15.1%) address decision-making, associating psychological safety with inclusive participation, diverse perspectives, and higher-quality team decisions.The reviewed findings also connect it with discussing errors, constructive questioning, reduced dysfunctional behavior, and more aligned decisions.Source: D. Influence of Psychological Safety… · p. 19

Overall RQ3 findings

  • Psychological safety is associated with open collaboration, communication, knowledge sharing, participation, and collective decision-making; decision-making is less extensively studied than collaboration and communication.The review identifies these as connected team processes, shaped by human and contextual conditions including trust, leadership, and interpersonal relationships.Source: D. Influence of Psychological Safety… · p. 20

Conditions shaping team processes

  • Supportive, inclusive, and open environments encourage speaking up, knowledge sharing, and collaboration, while hierarchy, blame culture, and poor communication can weaken psychological safety.The review also identifies leadership style and organizational culture as important influences on team dynamics and psychological safety.Source: D. Influence of Psychological Safety… · p. 20

E. Factors (e.g.leadership, organizational culture, work environment, trust and nationality and regional differences) Influencing the Relationship Between Psychological Safety and Team Performance (RQ4)

Of 112 included studies, 74 (66.1%) contributed evidence on contextual factors influencing the relationship between psychological safety and team performance. The mapped factors span organizational, interpersonal, and individual conditions.

RQ4 overview

  • 74 studies (66.1%) address contextual influences, including leadership, organizational culture, work environment, trust, nationality and regional differences, personality, and gender- and power-related dynamics.The review describes these as conditions under which psychological safety is associated with team functioning and performance; some emerged inductively from thematic analysis.Source: E. Factors (e.g.leadership,… · p. 21

1) Leadership Factors Associated with Psychological Safety and Team Performance

The reviewed studies associate psychological safety and team performance with leadership behavior and organizational and team culture. Supportive conditions are linked to stronger safety and outcomes, while negative leadership and toxic or unsupportive cultures are linked to weaker outcomes.

1) Leadership Factors Associated with Psychological Safety and Team Performance

  • Supportive, inclusive, transformational, and empowering leadership are associated with stronger psychological safety, openness, participation, and team performance.Clear supportive communication, leaders’ emotional signals, and safety climate are also associated with openness, trust, and participation; hierarchical, controlling, or harmful leadership may weaken these conditions.Source: 1) Leadership Factors Associated with… · p. 21

2) Cultural Influences on Psychological Safety and Team Performance

  • Supportive, open, learning-oriented, and agile cultures are associated with stronger psychological safety and team outcomes, while toxic or unsupportive cultures are associated with reduced openness and participation.Shared and national cultural norms also shape psychological safety, collaboration, decision-making, and consistency of team performance.Source: 2) Cultural Influences on… · p. 22

3) “Work Environment” affecting the relationship between psychological safety and team performance

The review describes the relationship between psychological safety and team performance as context-dependent. Work environment, trust, and individual and sociocultural differences are among the mapped conditions, with less attention given to the latter differences.

3) “Work Environment” affecting the relationship between psychological safety and team performance

  • Work-environment evidence links psychological safety and team performance with supportive, trust-based, inclusive, and well-structured conditions, while workload and other pressures are associated with reduced openness and participation.The reviewed themes also connect psychologically safe environments with creativity, innovation, coordination, and team functioning.Source: 3) “Work Environment” affecting the… · pp. 22–23

4) “Trust” affecting the relationship between psychological safety and team performance

  • Trust is associated with psychological safety, open communication, collaboration, and team functioning in both co-located and virtual environments.The review connects trust with reduced interpersonal risk and fear, trust in leaders and teammates, and stronger coordination and effectiveness.Source: 4) “Trust” affecting the relationship… · pp. 23–24

5) “Nationality/ Region/Personalities” affecting the relationship between Human Factors / psychological safety and team performance

  • Nationality and regional context, personality, and gender- and power-related dynamics shape psychological safety and team outcomes, but receive less research attention than leadership, culture, work environment, and trust.The review identifies variation in communication, interaction, participation, and voice across these contexts; overall, it characterizes the relationship with performance as context-dependent rather than uniform.Source: 5) “Nationality/ Region/Personalities”… · pp. 24–25

F. Challenges or barriers to establishing psychological safety in software development teams (RQ 5):

Barriers to psychological safety span interpersonal, organizational, leadership, inclusion, and work-environment conditions; reported strategies range from leadership support to everyday practices, learning, trust-building, and well-being.

F. Challenges or barriers to establishing psychological safety in software development teams (RQ 5):

  • Barriers operate across communication, trust, organizational structures, leadership, inclusion, and workload, rather than arising only from individual behavior.Communication and information-flow problems are the most dominant reported barriers.Source: F. Challenges or barriers to… · p. 26

G. Strategies, Practices, and Interventions for Enhancing Psychological Safety in Software Teams (RQ6):

  • Supportive, open leadership and formal policies, HR systems, and fair recognition practices are reported as ways to strengthen team safety.This theme draws on 22 studies.Source: G. Strategies, Practices, and… · p. 27
  • Agile routines, clear roles, shared ownership, collaboration tools, and structured workflows embed communication and coordination in everyday teamwork.This theme draws on 18 studies.Source: G. Strategies, Practices, and… · p. 27
  • Open feedback, reflection, shared learning, training, and coaching are reported as practices that build confidence and support participation.This theme draws on 16 studies.Source: G. Strategies, Practices, and… · p. 27
  • Relationship-building, inclusive practices, and shared norms support trust, belonging, respectful communication, and broader participation.This theme draws on 19 studies.Source: G. Strategies, Practices, and… · p. 27
  • Stress management, resilience, and supportive technology are reported as approaches to sustaining psychological safety over time.This theme draws on 9 studies; the evidence describes practices but does not establish their long-term effectiveness.Source: G. Strategies, Practices, and… · pp. 27–28

5 Discussion

The discussion presents psychological safety as a multidimensional team construct and relates it to performance outcomes through team interaction and learning. It also identifies uneven evidence and contextual gaps.

A. Discussion of RQ1:

  • Psychological safety is conceptualized through interconnected dimensions, while communication receives more attention than individual or contextual dimensions.The discussion calls for more integrated models and notes limited attention to individual differences, organizational constraints, and the mechanisms linking safety to learning.Source: A. Discussion of RQ1 · pp. 28–29

B. Discussion of RQ2:

  • The discussion associates psychological safety with productivity, software quality, innovation, and team satisfaction, with uneven attention across outcomes.Productivity and learning-related mechanisms receive greater attention than innovation, satisfaction, and contextual influences.Source: B. Discussion of RQ2 · p. 29

5 Discussion

1) Psychological Safety and Team Productivity

  • Productivity-related evidence links psychological safety with collaboration, communication, learning, feedback, knowledge sharing, trust, and proactive behavior.The reviewed literature offers stronger evidence for the presence of these processes than for their direct, measurable productivity effects.Source: 1) Psychological Safety and Team… · pp. 29–30

2) Psychological Safety and Software Quality

  • Software-quality relationships are described as operating mainly through interaction, learning, error management, and knowledge sharing, rather than a direct technical mechanism.The discussion notes that studies provide limited evidence about how these processes translate into measurable quality outcomes.Source: 2) Psychological Safety and Software… · p. 30

3) Psychological Safety and Innovation

The discussion associates psychological safety with innovation and team satisfaction, then examines collaboration and communication as team processes. Across these areas, outcomes depend on process quality and contextual conditions.

3) Psychological Safety and Innovation

  • Psychological safety is associated with innovation through idea sharing, creativity, experimentation, learning, and knowledge sharing, alongside supportive and inclusive environments.The literature emphasizes team behaviors more than the conditions under which they produce implemented, measurable innovation.Source: 3) Psychological Safety and Innovation · pp. 30–31

4) Psychological Safety and Team Satisfaction

  • Psychological safety is associated with individual and team satisfaction through communication, trust, well-being, role clarity, team processes, and supportive organizational conditions.Workload, organizational pressure, and individual expectations may qualify satisfaction outcomes, while structural conditions receive less attention.Source: 4) Psychological Safety and Team… · p. 31

C. Discussion of RQ3

  • Psychological safety is associated with collaboration, communication, and decision-making through participation, knowledge exchange, interpersonal risk-taking, trust, and supportive conditions.The discussion identifies these as recurring mechanisms across the three team processes.Source: C. Discussion of RQ3 · p. 31

1) Psychological Safety and Team Collaboration

  • Collaboration is associated with open participation, constructive dialogue, shared learning, and problem-solving, but depends on conflict management, knowledge quality, trust, and organizational conditions.The discussion calls for research on when these interactions translate into effective collaborative outcomes.Source: 1) Psychological Safety and Team… · p. 32

2) Psychological Safety and Team Communication

  • Psychological safety is associated with open dialogue and information exchange, but communication effectiveness also depends on constructive dialogue and broader human and contextual conditions.Greater willingness to communicate does not by itself establish higher communication quality or useful information exchange.Source: 2) Psychological Safety and Team… · pp. 32–33

3) Psychological Safety and Team Decision-Making

Psychological safety is associated with inclusive, reflective decision-making, but decision processes receive less attention than collaboration and communication. The reviewed findings also link safety and team performance with leadership and cultural conditions.

3) Psychological Safety and Team Decision-Making

  • Decision-making findings associate psychological safety with inclusive participation, diverse perspectives, error discussion, and constructive questioning, but this process is comparatively underexplored.The reviewed literature does not establish that greater participation directly improves decision quality.Source: 3) Psychological Safety and Team… · p. 33

D. Discussion of RQ4:

  • Leadership style, organizational culture, work environment, and trust shape how psychological safety is expressed and associated with team performance.These contextual factors may strengthen or constrain the relationship across software-engineering settings.Source: D. Discussion of RQ4 · p. 34

1) Leadership Style, Psychological Safety, and Team Performance (RQ 4.1)

  • Supportive, inclusive, transformational, and empowering leadership are associated with favorable safety and team conditions, while restrictive hierarchies and negative behaviors are linked to less favorable outcomes.Leadership communication, emotional signaling, and power relations also shape these conditions; effects may vary across team and organizational contexts.Source: 1) Leadership Style, Psychological… · p. 34

2) Organizational and Team Culture, Psychological Safety, and Team Performance (RQ 4.2)

  • Psychological safety is associated with supportive, learning-oriented, agile, and innovation-oriented cultures, as well as shared norms and broader national-cultural contexts.Blame-oriented and unsupportive cultures are linked to reduced communication and participation; how cultures are implemented, change, or are transformed remains less studied.Source: 2) Organizational and Team Culture,… · p. 35

3) Work Environment, Psychological Safety, and Team Performance (RQ 4.3)

Psychological safety and performance are associated with work-environment conditions, trust, and sociocultural and individual differences. Barriers span interpersonal, organizational, structural, inclusion, and work-related conditions.

3) Work Environment, Psychological Safety, and Team Performance (RQ 4.3)

  • Work-environment conditions associated with psychological safety and performance include supportive climates, leadership and structure, autonomy, inclusion, value alignment, and workload pressures.Some studies also associate psychologically safe environments directly with team functioning and innovation, though interactions among conditions remain underexplored.Source: 3) Work Environment, Psychological… · pp. 35–36

4) Trust, Psychological Safety, and Team Performance (RQ 4.4)

  • Trust is associated with psychological safety and team functioning at interpersonal, leadership, and team levels, with its role varying across co-located and virtual settings.The evidence base offers limited understanding of how trust forms across virtual teams or how leadership and team-level trust interact.Source: 4) Trust, Psychological Safety, and… · p. 36

5) Sociocultural and Individual Factors, Psychological Safety, and Team Performance (RQ 4.5)

  • Cultural and regional context, personality, gender, and power dynamics are associated with psychological safety, but receive less attention than leadership, work environment, and trust.The findings indicate that safety is not experienced uniformly and call for more integrated, context-sensitive research.Source: 5) Sociocultural and Individual… · p. 37

E. Discussion of RQ5:

  • Barriers are interconnected across communication, trust, organizational structure, leadership, diversity and inclusion, and workload and resource conditions.Communication and trust barriers receive more research attention than bias, inclusion, workload, and resource constraints.Source: E. Discussion of RQ5 · pp. 37, 39

F. Discussion of RQ6:

The mapping identifies reported practices for supporting psychological safety across leadership, organizational, team, learning, process, well-being, and technology dimensions. It also integrates fragmented software-engineering evidence, while finding limited evaluation of practices’ effectiveness and sustainability.

F. Discussion of RQ6:

  • Reported strategies span leadership and organizational support, agile and process practices, learning and feedback, trust and belonging, and well-being and technology.The literature identifies these practices more often than it evaluates their implementation quality, effectiveness, scalability, or sustainability over time.Source: F. Discussion of RQ6 · pp. 39–40

6 Comparison with Existing Studies

  • The mapping integrates conceptualizations, performance outcomes, team processes, contextual factors, barriers, and improvement strategies that prior studies often examined separately or in narrower contexts.It complements rather than replaces focused studies, identifying recurring patterns and underexplored areas.Source: §6 · p. 41

7 Research Gaps

The mapping identifies uneven coverage across conceptual, contextual, and methodological dimensions of psychological-safety research in software teams. It highlights underexplored areas and limitations in how the evidence has been produced and assessed.

7 Research Gaps

  • Overall, research attention is uneven across dimensions and contexts, motivating a balanced, context-sensitive agenda with more diverse methods and rigorous empirical evaluation.Communication, collaboration, and positive outcomes receive comparatively greater attention than several contextual areas and methodological approaches.Source: §7 · p. 41, C. Methodological Gaps · p. 43

A. Conceptual Gaps

  • Decision-making and the integration of individual human factors with team-level psychological safety remain conceptual gaps, including how individual differences relate to shared safety perceptions and team performance.Decision quality, conflict resolution, and strategic outcomes receive less attention than communication and collaboration.Source: A. Conceptual Gaps · pp. 41–42

B. Contextual Gaps

  • Diversity, inclusion, gender, and power conditions receive limited attention, while workload and well-being also remain comparatively underexplored.The evidence on how diversity-related conditions relate to psychological safety across software-team contexts remains limited.Source: B. Contextual Gaps · p. 42, C. Methodological Gaps · p. 43
  • Virtual, distributed, and hybrid teams are not yet a sustained focus, leaving limited understanding of how safety develops across geographical, cultural, and technological boundaries.Relevant conditions include communication, coordination, and technology-mediated interaction.Source: B. Contextual Gaps · p. 42
  • AI-supported collaboration has a limited evidence base, insufficient to establish how these technologies relate to psychological safety across software-development contexts.Open questions include effects on communication, participation, trust, team relationships, and willingness to speak up.Source: B. Contextual Gaps · p. 42

C. Methodological Gaps

  • Qualitative, conceptual, and case-based work predominates, while longitudinal evidence is limited and cross-sectional associations offer little basis for establishing temporal order or relationship direction.The mapping calls for larger-scale empirical and mixed-method studies, alongside longitudinal and stronger causal designs where appropriate.Source: C. Methodological Gaps · pp. 42–43
  • Variation in definitions, metrics, instruments, and evaluation approaches makes direct comparison and synthesis across studies more difficult.The mapping recommends clearer, comparable measurement approaches and consideration of whether instruments need adaptation to software-engineering contexts.Source: C. Methodological Gaps · p. 43

A. Internal Validity

  • The study used procedural safeguards across search, selection, extraction, and thematic coding, but detailed per-study quality-score rationales are not provided.The omitted rationales may limit complete reproducibility of some quality-assessment decisions.Source: A. Internal Validity · pp. 43–44, §8 · p. 43

B. External Validity

The study maps psychological safety in software development teams, reporting recurring associations, contextual influences, barriers, and support practices. It qualifies these findings with limits in transferability, construct consistency, and causal interpretation.

B. External Validity

  • Transferability beyond software teams may be limited, and peer-reviewed-only coverage may omit relevant industry and unpublished evidence.The authors suggest adding industry studies and examining whether patterns also occur in other organizational and professional contexts.Source: B. External Validity · p. 44

C. Construct Validity

  • Variation in terminology, definitions, and operationalizations may cause missed studies and leave psychological safety represented inconsistently across the mapped evidence.The review used multiple keywords and distinguished psychological safety from related constructs, but variation across primary studies remains.Source: C. Construct Validity · p. 44

D. Conclusion Validity

  • Theme frequencies do not establish causal strength or effect size, and the number of studies supporting individual themes varies.The authors base conclusions on recurring patterns and frame them as associations, patterns, and reported practices.Source: D. Conclusion Validity · p. 44

9 Conclusion

  • The mapping analyzed 112 primary studies published from 2006 to June 2026 using descriptive and thematic analysis across six research questions.Publication activity increased in recent years, and studies appeared across IEEE, ACM, Springer, ScienceDirect, and Wiley.Source: §9 · pp. 44–45
  • Psychological safety is associated with productivity, software quality, innovation, satisfaction, collaboration, communication, and decision-making, with relationships shaped by context.Reported contextual factors include leadership, organizational culture, work environment, trust, and sociocultural and individual conditions; barriers include organizational constraints, leadership issues, inclusion challenges, and workload pressures.Source: §9 · p. 45
  • The synthesis organizes evidence across six dimensions and identifies gaps in decision-making, inclusion, workload, distributed teams, emerging technologies, longitudinal research, and measurement.The authors present the mapping as a structured evidence base for future empirical research and context-sensitive approaches.Source: §9 · p. 45
  • Organizations are advised to adapt and evaluate reported practices to their contexts because comparative effectiveness and long-term sustainability evidence is limited.Suggested approaches include inclusive leadership, open communication, feedback, role clarity, addressing structural barriers, and combining agile, learning, relational, and well-being practices.Source: §9 · p. 45
  • The authors call for larger-scale, longitudinal, context-sensitive studies and more consistent measurement and systematic evaluation of interventions.The paper highlights uneven evidence across decision-making, diversity and inclusion, workload and well-being, distributed and hybrid teams, and emerging technologies.Source: §9 · p. 45

Appendix A Inter-Rater Agreement (IRA)

The appendix describes Cohen’s Kappa as a measure of reviewer agreement during study screening and reports moderate-to-substantial agreement. It also explains how the study aligns its goal, research questions, and extracted data through GQM.

Appendix A Inter-Rater Agreement (IRA)

  • Cohen’s Kappa assessed agreement beyond chance across screening stages, with reported agreement ranging from moderate to substantial.Reviewers independently screened samples at each stage and resolved disagreements through discussion and consensus.Source: Appendix A · p. 50

Appendix B Goal–Question–Metric (GQM) Approach

  • The GQM approach links the study goal to six research questions and corresponding data-extraction items.The authors describe this alignment as supporting traceability, transparency, replicability, and consistent synthesis.Source: Appendix B · pp. 50–51
  • The appendix lists tables on influencing factors, barriers, practices, findings and implications, existing-study comparisons, and validity threats.The supplied table captions identify these topics but do not provide their contents.Source: Table XI · p. 52, Table XII · p. 53, Table XIII · p. 54
Loading 2610.08896v1…