RDEL #122: How do daily stand-ups boost team performance?
Stand-ups don't directly improve satisfaction or performance—but they foster psychological safety, which drives both outcomes with high effect sizes.
Welcome back to Research-Driven Engineering Leadership. Each week, we pose an interesting topic in engineering leadership and apply the latest research in the field to drive to an answer.
Daily stand-ups have become ubiquitous in software teams, with 87% of agile teams holding these 15-minute check-ins every day. Yet despite their widespread adoption, we have surprisingly little quantitative evidence about whether they actually work—and if so, how. This week we ask: Do daily stand-up meetings improve team performance, and what psychological mechanisms make them effective?
The context
Daily stand-up meetings emerged from agile software development practices, particularly Scrum, but have since spread far beyond tech teams into manufacturing, healthcare, consulting, and other industries. The format is deceptively simple: teams gather for at most 15 minutes each day to each answer three questions: What did I work on yesterday? What will I work on today? Are there any obstacles blocking me?
The appeal is clear—regular synchronization, transparency about progress, and quick identification of blockers. However, the reality has been mixed. Some teams swear by them, while others report that the meetings feel like an inefficient use of time. This contradiction raises an important question: if stand-ups work, what makes them work? The answer may lie not in the meeting format itself, but in what these meetings create within the team—specifically, a sense of psychological safety where people feel comfortable taking interpersonal risks, sharing uncertainties, and asking for help without fear of judgment. This has previously been studied as one of the top social drivers of performance in software engineering teams.
The research
Researchers conducted two studies to test psychological safety - specifically, whether daily stand-ups (DSUs) foster psychological safety and if this explains their impact on satisfaction and performance. Study 1 surveyed 318 employees in agile software teams at two time points six weeks apart, while Study 2 used an experimental design with 108 university students randomly assigned to teams that either held DSUs for five days or met only at the beginning and end of the project.
Key findings include:
Daily stand-ups significantly increased psychological safety, meaning team members felt safer taking interpersonal risks and speaking up without fear of negative consequences.
The relationship between stand-ups and work satisfaction was fully mediated by psychological safety —stand-ups didn’t directly boost satisfaction, but they did so indirectly by creating psychologically safe environments.
Stand-ups improved perceived team performance through psychological safety, with significant indirect effects on performance perceptions, team efficacy, and team learning behavior.
The effect held across contexts: The positive impact of stand-ups on psychological safety was confirmed both in established agile software teams and in newly formed student teams working on short-term projects, suggesting the benefits aren’t limited to experienced agile environments.
Psychological safety had strong direct effects on outcomes, with standardized coefficients ranging from .46 to .61 for the relationships between psychological safety and various performance and satisfaction measures—indicating that when teams feel safe, they perform better and report higher satisfaction.
The application
Daily stand-ups work—but not simply because they improve coordination or transparency. They work because they create psychological safety, and psychological safety drives satisfaction, learning, and performance. The research shows that the structured, daily rhythm of these meetings provides a consistent forum where team members can share challenges, ask for help, and take interpersonal risks without fear.
Engineering leaders can leverage these findings by:
Model vulnerability in stand-ups: Share your own blockers and uncertainties first. When leaders admit they don’t have all the answers, it signals that others can do the same safely.
Focus on genuine obstacles, not just status: Encourage the team to use the “blockers” question for real problems where they need help. Celebrate when someone asks for assistance rather than treating stand-ups as progress reports.
Track whether people feel safe speaking up: Use brief anonymous pulse checks to monitor if team members genuinely feel comfortable sharing challenges. If psychological safety isn’t improving, the stand-ups won’t deliver results.
—
Have a happy research Tuesday!
Lizzie
Daily Stand-up, which originated in XP, and Daily Scrum are two distinct meetings that serve a different purpose. The three infamous questions are discouraged.
Studies like the one you are referring to are of limited value in general.
Your recommendations are valuable, but y'all got it backwards. Performance oriented teams that value collaboration will do those things without even thinking about them.
It's not the practises that make the difference, it's the difference that shapes the practices.