Urgent.News

What's breaking now, across thousands of outlets.

Tech

It's official — new scientific report says your boss should talk less and listen more in meetings

Successful meetings have a balance of listening and speaking, and where the balance fails, participants and leaders have very different impressions on how successful it was.

It's official — new scientific report says your boss should talk less and listen more in meetings

A recent scientific report suggests that effective meetings should feature a balance of speaking and listening, with bosses encouraged to talk less and listen more. This conclusion comes from an in-depth review of over three decades of meeting research, which has been compiled in the 2026 Annual Review of Organizational Psychology and Organizational Behavior.

According to the review, meetings that lack structure or fail to achieve a goal are often considered failures, even if those in charge feel the meeting went well. The research also highlights the importance of warmup phases to encourage participation from quieter or more introverted participants. This can help make meetings feel more purposeful and productive, rather than aimless or redundant.

The report suggests that while bosses may not stop talking altogether, they might be able to make their meetings less self-centered and more focused on collective input. Experts agree that implementing the recommendations from this review could help improve the perception and effectiveness of team and departmental meetings.

Written by urgent.news from TechRadar's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at techradar.com →

More in Tech

Seeking Validation: Developer Requests Feedback on Go Compiler Codebase After Negative Review

Introduction: The Code Smell Dilemma A developer’s journey into compiler design took an unexpected turn when their Go-based project, krabbascript , faced harsh criticism. The feedback?

  • Excessive goroutine usage causes resource contention and latency spikes
  • Neglect of Go's error handling conventions leads to silent failures
  • Lack of comprehensive testing leaves codebase vulnerable to runtime failures

More from Saturday 24 October →