By Matt Harrington, BCBA · Behaviorist Book Club · April 2026 · 12 min read

Agile Methodology and Psychological Safety: What Behavior Analysts Can Learn from Software Development

Overview & Clinical Significance

Kristyn Peterson's workshop draws an unexpected but analytically rigorous connection: the metacontingency structures embedded in Agile software development teams inadvertently create conditions for psychological safety in ways that most ABA organizations have not deliberately designed. For behavior analysts, who are trained to analyze contingency structures, this connection is both intellectually compelling and practically useful — if Agile creates psychological safety through specific metacontingencies, those contingencies can be identified, analyzed, and generalized to any team environment.

Psychological safety, as defined in the organizational research literature, is a shared belief among team members that the team is safe for interpersonal risk-taking — that mistakes can be acknowledged, ideas can be proposed, and concerns can be raised without fear of punishment, rejection, or humiliation. Amy Edmondson's foundational research demonstrates that psychological safety is among the strongest predictors of team learning and performance, particularly in complex, uncertain task environments. Behavior analysis, like software development, is a complex professional domain where team learning is essential to quality.

The clinical significance for BCBAs and clinical teams is direct. ABA teams that operate with high psychological safety are more likely to: identify clinical errors before they affect clients, share honest assessment of client progress including stagnation, raise ethical concerns about organizational practices, generate creative clinical solutions, and seek consultation rather than managing uncertainty independently. Teams with low psychological safety do the opposite — they manage information strategically, conceal difficulties, and avoid the interpersonal risks that clinical transparency requires.

For supervising BCBAs who are responsible for creating the team conditions in which BTs and other supervisees work, this course provides both a theoretical framework for understanding what creates psychological safety and practical tools — Agile retrospective analysis — for implementing it. The workshop format means participants leave with skills that can be applied immediately, not just conceptual understanding.

Background & Context

Metacontingency, as a behavior analytic concept developed in the interlocking behavioral contingencies and cultural practices literature, refers to contingency relationships between cultural practices (interlocking behavioral contingencies among individuals) and outcomes at the aggregate level. The concept provides a framework for analyzing how group-level behavioral patterns are shaped by their collective consequences — which is precisely the analysis needed to understand how Agile practices create team-level outcomes like psychological safety.

Agile methodology, developed primarily in software engineering contexts, organizes work into iterative cycles (sprints), with defined ceremonies for planning, daily coordination, review, and retrospective. The retrospective is the most directly relevant to psychological safety: it is a structured team reflection on what went well, what went poorly, and what should change, held at the end of each sprint. When implemented with fidelity, the retrospective creates recurring opportunities for team members to raise concerns, acknowledge errors, and propose process changes without career risk — because the format creates explicit permission and expectation for this kind of disclosure.

The behavior analytic analysis of why retrospectives create psychological safety points to several metacontingency mechanisms. The formal structure provides permission and precedent for raising concerns — it is expected behavior, not deviant behavior. The regularly scheduled occurrence means concerns are raised when fresh rather than accumulating until they reach a crisis threshold. The team-level focus shifts attribution from individual failure to process failure, reducing the threat value of disclosing problems. And the explicit action-orientation — every retrospective ends with specific changes — reinforces disclosure with the experience of actual change, building the history of consequences that makes future disclosure more likely.

Psychological safety research in organizational settings consistently identifies leader behavior as the primary determinant of team psychological safety. Leaders who model intellectual humility, who respond to raised concerns with genuine problem-solving rather than defensiveness, who acknowledge their own errors and uncertainties, and who explicitly invite dissent create the antecedent and consequence conditions for psychological safety. Leaders who respond to concerns with dismissal, who attribute problems to individual failure rather than systems, and who punish deviation from expressed views create the conditions for its absence.

For ABA teams specifically, the clinical context creates additional complexity. BTs often occupy significant positional power differentials relative to their supervising BCBAs, and the clinical stakes of raising concerns — about client welfare, about a colleague's performance, about an organizational practice — are high. The Agile retrospective structure provides a format that makes concern-raising lower-stakes by normalizing it, regularizing it, and connecting it to organizational response.

Clinical Implications

The most direct clinical implication of psychological safety for ABA teams is improved error detection and reporting. Clinical errors in ABA — missed data collection, misimplemented procedures, overlooked behavioral signals — are most likely to be caught and corrected when team members feel safe reporting what they observe. Teams with low psychological safety develop workarounds and information management strategies that keep clinical errors from reaching the supervisor level, where they could be corrected. High-psychological-safety teams surface errors early, enabling rapid correction before they affect client outcomes significantly.

For BCBA supervisors, the Agile retrospective model provides a structural format for creating regular, low-stakes opportunities for team reflection and concern-raising. Adapting retrospective practices to clinical supervision contexts — holding regular structured team reflections on what is working in current programming, what is not, and what should change — creates the recurring permission and expectation that psychological safety requires. The key adaptation is maintaining the non-punitive, process-focused orientation of the retrospective even when the concerns raised involve individual performance.

Team learning velocity — how quickly a clinical team incorporates new information into improved practice — is directly affected by psychological safety. Teams that discuss clinical challenges, share observations about client behavior, raise questions about program design, and debate treatment options learn faster than teams where this kind of open discussion is not safe. For BCBAs managing complex caseloads, the team learning that high psychological safety enables is a clinical quality multiplier: each team member's observations and insights can improve the clinical decisions that affect all clients on the team.

The Agile practice of working in defined iterative cycles — sprints — has a clinical analog in the behavior analytic concept of regular program review. ABA programs should be reviewed at defined intervals with explicit criteria for whether to continue, modify, or abandon current approaches. This iterative review structure, when implemented with team-level transparency rather than solo BCBA review, creates the conditions for collective clinical intelligence to influence programming rather than only the supervising BCBA's individual judgment.

For clinical organizations undergoing change — new program implementations, policy changes, caseload restructuring — the Agile retrospective model provides a practical mechanism for managing change-related anxiety and maintaining psychological safety during periods of uncertainty. Regular structured reflection during change processes prevents the accumulation of unaddressed concerns that erodes psychological safety under stress.

Ethical Considerations

Code 2.01 on beneficence is directly implicated in team psychological safety. Clinical teams with low psychological safety produce worse client outcomes because clinical errors go undetected and unaddressed. The structural interventions that create psychological safety — regular retrospective formats, leader modeling of intellectual humility, non-punitive responses to concern disclosure — are therefore clinical quality interventions with direct implications for whether clients receive competent services.

Code 1.04 on integrity requires BCBAs to behave with honesty and transparency in professional relationships. Organizational cultures with low psychological safety create conditions in which honest professional communication carries personal risk — which creates pressure on individual practitioners to behave with less than full transparency. BCBAs who create high-psychological-safety environments are removing a structural barrier to the honest professional communication that Code 1.04 requires.

Code 4.04 on maintaining supervisory relationships requires BCBAs to create supervisory environments that support supervisee development without exploitation. Teams with low psychological safety are experienced as psychologically unsafe by supervisees, who learn to manage information strategically to protect themselves. This is the opposite of the open professional relationship that Code 4.04 envisions. Supervisors who invest in creating psychological safety through Agile-inspired structures are meeting this ethical requirement more fully.

The power differential between BCBAs and BTs is relevant to the ethics of psychological safety. BTs are in positions of relative organizational vulnerability — they depend on their supervising BCBAs for performance evaluations, schedule assignments, and professional references. This vulnerability means that the BCBA's behavior has disproportionate influence on the psychological safety of the team environment. BCBAs who use their positional authority to suppress dissent or punish concern-raising are exploiting this power differential in ways that are ethically problematic under Code 4.04 and Code 1.04.

Assessment & Decision-Making

Assessing team psychological safety requires behavioral observation and self-report measures. Observationally, signs of high psychological safety include: team members raising concerns in group settings without appearing anxious about the response, spontaneous sharing of errors and near-misses, genuine debate about clinical approaches rather than deference to the supervisor's stated preference, and BTs seeking consultation proactively rather than only when directly asked. Signs of low psychological safety include: team meetings characterized by agreement rather than discussion, concerns raised only in private one-on-one settings, errors discovered by supervisors rather than disclosed by the BTs who made them, and a general pattern of communication that manages information rather than sharing it.

Peterson's workshop specifically addresses analyzing examples and non-examples of metacontingencies — the ability to identify which team practices are creating psychological safety and which are undermining it. This analysis is the behavior analyst's contribution to the organizational literature: moving from phenomenological description of psychological safety to behavioral analysis of its contingency determinants. Practicing this analysis in a workshop context develops the skill that translates directly to organizational assessment.

For BCBAs considering implementing Agile retrospective practices in their teams, a pilot design should specify: the retrospective format (structured questions, time allocation, facilitation approach), the frequency of retrospectives (biweekly is common in Agile teams), the follow-up mechanism that ensures retrospective outputs produce actual change, and the criteria for evaluating whether the retrospective is producing the intended effects (increased disclosure, increased team learning velocity, improved psychological safety self-report).

Agile data analysis — the second assessment component Peterson addresses — involves examining team-level performance data through the same behavioral lens that individual client data receive: looking for patterns, generating hypotheses about function, and making data-driven decisions about what to change. This practice, applied to ABA clinical teams, means reviewing collective performance data (case completion rates, data collection consistency, program progress rates) for team-level patterns that point to systemic issues rather than only individual performance problems.

Decision-making about which Agile practices to adopt requires analysis of which metacontingencies are missing from or poorly designed in the current team structure. Teams that lack regular structured reflection need retrospective practices. Teams that lack clear visibility into collective performance data need Agile-style data radiators — visual displays of team performance that create shared awareness of how the team is functioning. Teams that lack structured iteration cycles need sprint-like program review practices. The analysis starts from where the team's psychological safety gaps are.

What This Means for Your Practice

Implement a team retrospective. Start with monthly if biweekly feels too frequent — the key is regularity and non-punitive framing. Typical retrospective questions: What has been going well in our current work? What has been difficult or frustrating? What should we try changing next period? Facilitate with genuine curiosity, not evaluation. The changes that emerge from retrospectives should be implemented, not discussed and forgotten — nothing erodes psychological safety faster than disclosure without response.

Examine your own behavior as a team leader for the metacontingency signals you are sending. When a BT raises a concern, do you respond with genuine problem-solving or with defensiveness? When a mistake is disclosed, do you treat it as information or as a performance problem? When a supervisee disagrees with your clinical reasoning, do you engage the disagreement as clinical discussion or dismiss it? Your responses to these moments are the primary determinants of your team's psychological safety, far more than any structural initiative.

Learn to analyze team data through a metacontingency lens. When your team is underperforming on a clinical metric — data collection consistency, session attendance, family communication frequency — ask whether the problem is in individual behavior or in the contingency structure. If multiple team members show the same problem, the contingency structure is the more likely culprit. Retrospective analysis of team data with the team creates both a diagnostic and a psychological safety intervention simultaneously.

For BCBAs interested in the Agile-behavior analysis connection specifically, the workshop format of Peterson's course means the analysis skills developed are directly transferable. Practice analyzing the metacontingency structure of team interactions you observe in your own organization: which practices are creating psychological safety, which are undermining it, and which Agile-inspired modifications might improve the structure.