The 2025 State of Teams: Uncovering the Hidden Costs of Dysfunctional Teams

Nov 23, 2025
12 min read

Updated: Feb 22

Atlassian’s November release of the 2025 State of Teams report reveals a hard truth that many leaders sense but often avoid: we are overestimating our teams' performance. A staggering 76% of team time is wasted on work that does not drive results. Only one out of every four hours is spent on what truly matters. The rest is consumed by unclear goals, ambiguous roles, and meetings that drain energy instead of fostering momentum.

However, there is hope. The same data indicates what works. High-performing teams are not magical; they are intentional. They create psychological safety, allowing team members to speak up without fear. They make priorities visible and shared. They lead through coaching rather than control. The outcome? These teams are not only more productive but also more human, reporting 31% higher satisfaction and 37% greater adaptability.

This isn’t a call to work harder or longer. It’s an invitation to be braver: to confront the dysfunctions we have normalized and redesign how work is done. The data is clear. What happens next is a leadership choice.

The 76% Problem: Where Your Team's Energy + Productivity Really Goes

Let’s start with a number that should make every leader uncomfortable: only 24% of team time is spent on mission-critical goals.

Read that again. Three-quarters of your collective brainpower, energy, and talent are leaking out through a thousand small cuts: unclear priorities, redundant check-ins, territorial inbox wars, and the psychological burden of not knowing what truly matters.

Atlassian's 2025 State of Teams report, which analyzes thousands of knowledge-worker teams across various continents, industries, and company stages, does not hold back. Most teams are not failing due to a lack of talent or effort. They are drowning in structural dysfunction that has become so normalized it is now invisible.

We have all experienced this. You finish a week filled with back-to-back meetings, Slack marathons, and document updates, only to realize: What did we actually accomplish?

Statistically, the answer is not much.

High-performing teams—the top 20% in Atlassian's dataset—operate in a different reality. They have made a deliberate choice about what deserves focus and what should be eliminated. They revisit priorities monthly, not annually. They design collaboration rituals instead of inheriting them. They cultivate psychological safety not as a mere HR initiative but as the oxygen that makes everything else possible.

The gap between average and exceptional is not mysterious. It is measurable and closable.

What High-Performing Teams Actually Do Differently

They Make Priorities Brutally Explicit

Here’s the part that stings: most teams believe they have clear priorities. They do not.

Atlassian's data shows that teams that set explicit, transparent priorities—and revisit them at least monthly—deliver 43% more on core objectives than teams that set priorities once and assume they will remain relevant.

Consider your last quarter. Did your team's stated priorities shift as market conditions changed, customer needs evolved, or leadership pivoted strategy? Of course, they did. But did your team rituals, meeting agendas, and individual commitments shift with them?

Probably not.

High performers treat priority-setting as a living system, not a static document. They do not just announce goals in a kickoff deck. They embed them into every standup, every retrospective, and every decision framework. When someone proposes a new project, the first question is not "Can we do this?" It is "Does this serve our top three priorities?"

If the answer is no, it is not happening. This is how you reclaim the 76%.

They Practice Coaching, Not Command-and-Control

Leadership style is not a soft variable; it is a performance multiplier.

Research reveals a strong correlation between coaching-oriented leadership and both psychological safety and innovation outcomes. Teams with leaders who ask questions instead of giving orders, who facilitate instead of dictate, consistently outperform their directive-led peers.

Why? Because coaching unlocks collective intelligence. When team members feel safe to surface problems early, challenge assumptions, and propose unconventional solutions, the team's adaptive capacity skyrockets. These teams report 31% higher job satisfaction and 37% greater adaptability to change.

Contrast this with the command-and-control model most of us inherited. The leader knows best. The team executes. Problems get escalated, not solved. Innovation becomes the leader's job, not the team's habit.

That model worked when change was slow and information was scarce. In 2025, it is organizational suicide.

Coaching leadership does not mean being soft. It means demanding in a different way—demanding that people think, not just comply. Demanding accountability for outcomes, not just effort. Demanding that the team grows, not just produces.

They Design Hybrid Work Instead of Defaulting to Chaos

Remote work is not the problem. Ad-hoc, unintentional hybrid work is.

Atlassian's findings on hybrid teams dismantle the false binary between "return to office" and "fully remote." Hybrid teams that proactively design their collaboration rituals—structured check-ins, open feedback forums, explicit norms about synchronous vs. asynchronous work—outperform both fully co-located teams and ad-hoc hybrid teams in productivity and creativity.

The pattern is clear: intentionality wins. Geography matters less than ritual design.

High-performing hybrid teams do not leave collaboration to chance. They map which activities benefit from real-time interaction (brainstorming, conflict resolution, relationship building) and which thrive asynchronously (deep work, documentation, cross-timezone coordination). They establish communication protocols everyone understands. They create space for serendipity without demanding constant presence.

The teams struggling with hybrid work are not failing due to Zoom fatigue. They are failing because they never designed for it.

The Hidden Tax of Psychological Safety Deficits

Here’s where data meets humanity.

Psychological safety—the shared belief that you can speak up, take risks, and make mistakes without punishment—is not just touchy-feely HR speak. It is the foundation of everything high-performing teams do.

Without it, people hoard information. They play politics instead of solving problems. They remain silent when they see disasters approaching. They optimize for looking good over being effective.

With it, teams unlock their collective intelligence. Problems surface early. Mistakes become learning opportunities. Innovation accelerates because people are not paralyzed by fear of failure.

Atlassian's data shows that teams in the top quartile for psychological safety consistently outperform peers on every metric that matters: delivery speed, innovation rate, adaptability, retention, and satisfaction.

However, here is the uncomfortable truth: most leaders believe their teams have psychological safety when they do not. They confuse politeness for candor. They mistake the absence of visible conflict for trust. They celebrate "we're all aligned" as a victory when it is actually a symptom of suppressed dissent.

You do not build psychological safety by merely declaring it exists. You build it through hundreds of small moments where vulnerability is met with respect, not punishment. Where challenges are encouraged, not silenced. Where saying "I don't know" or "I made a mistake" makes you stronger, not weaker.

This requires leaders who model it first. Leaders who admit uncertainty. Leaders who thank people for disagreeing. Leaders who treat failure as data, not sin.

It is uncomfortable. It is necessary. And it is the only way to unlock the 43% productivity gain hidden in your current team.

The Meeting Problem Isn't Meetings—It's Misalignment

We often complain about meetings. Too many. Too long. Too pointless.

But Atlassian's research suggests the problem is not meetings themselves—it is how we use them.

High-performing teams have fewer but more effective meetings. They use them for decision-making, alignment, and connection—things that genuinely need synchronous attention. Everything else gets pushed to asynchronous channels where people can contribute on their own time, think before responding, and eliminate the calendar chaos that makes knowledge work feel like air traffic control.

Teams stuck in meeting hell are not victims of their calendars. They are victims of misalignment.

When priorities are unclear, people schedule meetings to figure out what matters. When roles overlap, people schedule meetings to negotiate territory. When decisions lack clear owners, people schedule meetings to avoid accountability.

Fix the underlying dysfunction, and the calendar fixes itself.

Start by asking: What is this meeting actually for? Decision? Debate? Information sharing? Connection? If you cannot answer in one sentence, cancel it.

Then ask: Who actually needs to be here? If the answer is "the same 15 people who are in every meeting," you have found your problem. Most meetings should be small. Most decisions should have clear owners. Most information should flow asynchronously.

Your team's calendar is a diagnostic tool. If it is a disaster, your operating system is broken.

How to Diagnose Your Team's Hidden Dysfunctions

Recognition is the first step. Here’s how to see what you’ve been missing.

Run a Priority Audit

Gather your team. Ask everyone to list the top five things they believe are priorities right now. Then compare lists.

If you do not have 80% overlap, you have a priority problem. Even worse: if the activities consuming most of people's time do not map to those stated priorities, you have a priority execution problem.

High-performing teams have crystal-clear answers. Everyone can articulate the same two or three goals. When you examine their calendars, task lists, and Slack channels, those priorities are everywhere.

Measure Psychological Safety Honestly

Anonymous surveys are useful but insufficient. Real psychological safety shows up in observable behavior.

Ask yourself:

When was the last time someone on your team challenged your idea in a meeting?
When was the last time someone admitted they were stuck and asked for help before a deadline?
When was the last time someone said "I made a mistake" without qualifying or deflecting?

If you cannot remember recent examples, you do not have psychological safety. You have performance theater.

Map Your Collaboration Rituals

Write down every recurring team ritual: standups, planning sessions, retrospectives, one-on-ones, all-hands, and social gatherings.

For each one, ask:

What is its explicit purpose?
How does it serve our priorities?
What would break if we stopped doing it?

If you cannot answer these questions, you are maintaining rituals by inertia, not intention. High-performing teams design their cadence deliberately. They add friction where it prevents mistakes and remove it where it slows progress.

A Step-by-Step Approach to Team Transformation

Ready to move from diagnosis to action? Here’s how.

Month 1: Clarity

Define your top three priorities as a team. Not five. Not ten. Three.

Get everyone in a room (physical or virtual). Debate until you reach consensus. Write them down. Make them visible everywhere: Slack headers, wiki homepages, meeting agendas, email signatures.

Then audit every active project and meeting against these priorities. If it does not serve one of the three, kill it or pause it. This will be uncomfortable. Do it anyway.

Month 2: Cadence

Design your collaboration rituals for the next quarter.

What needs synchronous time? What can be asynchronous? How often should you realign on priorities? How will you surface blockers early?

Build in space for:

Weekly priority check-ins (15 minutes, standing agenda)
Bi-weekly feedback loops (what's working, what's not)
Monthly priority retrospectives (are we still focused on the right things?)

High-performing teams do not leave this to chance. They engineer their operating rhythm.

Month 3: Safety

Start building psychological safety through deliberate leadership behavior.

Model vulnerability. Say "I don't know" when you do not know. Share a mistake you made and what you learned. Ask for critical feedback in front of the team—and receive it gracefully.

Reward people who surface problems early, even if the news is bad. Publicly thank those who thoughtfully disagree with you. Celebrate "productive failures" where teams tried something bold, learned quickly, and pivoted.

This is not a one-month project. It is a shift in leadership identity. But you must start somewhere.

Ongoing: Measurement

What gets measured gets managed. Pick your metrics:

Percentage of time on mission-critical work (aim to move from 24% toward 50%+)
Team confidence in priorities (monthly pulse check)
Psychological safety score (quarterly anonymous survey)
Meeting hours per person per week (track and reduce)

Review these metrics monthly with your team. Make them visible. Discuss them. Treat them like you treat revenue or customer metrics—because they predict those outcomes.

The bottom line: Your team isn't broken. It's designed—usually by default, not intention—for the outcomes you're currently getting. That 24% efficiency rate isn't fate. It's feedback. Atlassian's research provides the blueprint: clarity kills confusion, coaching unlocks collective intelligence, and psychological safety transforms dysfunction into high performance. You do not need permission to start. You need conviction. Because in 2025, mediocre teamwork is not a minor handicap—it is an existential threat. High-performing teams are not working harder. They are working deliberately. Join them.

Frequently Asked Questions

How do I know if my team has a dysfunction problem or just a workload problem?

Workload problems show up as temporary spikes with clear causes—a product launch, a seasonal rush, a crisis response. Dysfunction problems are chronic. They do not resolve when you hire more people or finish the current project. The pattern Atlassian's research exposes is persistent: even when teams have capacity, they spend it on low-value activities because they haven't clarified priorities or designed their operating system. If adding resources does not improve outcomes, you do not have a capacity problem. You have a clarity problem.

What if my leadership style is naturally directive, not coaching?

Leadership is not personality—it is skill. You can learn coaching behaviors even if they do not come naturally. Start small: replace one directive statement per day with a question. Instead of "Here's what we should do," try "What options do you see?" Instead of solving every problem brought to you, ask "What have you tried?" and "What would you recommend?" The goal is not to stop leading. It is to distribute intelligence across the team instead of bottlenecking it in you. This makes everyone stronger, including you.

How long does it take to see results from prioritizing psychological safety?

You will see early signals within weeks—people speaking up more, surfacing problems earlier, experimenting without permission. But deep cultural change takes quarters, not weeks. The key is consistency. Every time you respond to vulnerability with respect instead of punishment, you build trust. Every time you reward someone for admitting a mistake, you shift norms. Atlassian's high-performing teams did not build psychological safety overnight. They built it through hundreds of small, repeated leadership moments. Start now. Measure in six months.

Our team is fully remote. Do these principles still apply?

Absolutely. In fact, remote teams may benefit most from intentional ritual design and explicit priority-setting because you cannot rely on proximity to create alignment. Atlassian's data shows that hybrid and remote teams with proactive collaboration design outperform co-located teams that rely on osmosis and hallway conversations. The forcing function of distance makes you clarify what matters and how to coordinate. That discipline scales. Just do not default to synchronous meetings for everything—asynchronous tools are your superpower if you use them strategically.

What if only 24% of our time on mission-critical work is actually industry-standard?

It is average, not acceptable. Averages do not win markets. If everyone else is operating at 24% effectiveness, that is your competitive opportunity—not your excuse to stay mediocre. High-performing teams in Atlassian's research hit 40-50%+ time on mission-critical work by ruthlessly eliminating low-value activities and realigning constantly. The gap between you and them is not talent. It is operating discipline. That is entirely fixable.

How do I convince my team to revisit priorities monthly when we already have quarterly goals?

Make it about precision, not instability. Quarterly goals set direction. Monthly reviews ensure you are still on course. Markets shift. Customer needs evolve. Technologies change. The teams that win are not the ones with perfect plans—they are the ones that adapt fastest. Frame monthly priority check-ins as increasing your odds of hitting quarterly targets, not abandoning them. Show the data: 43% better delivery on core objectives. That is not chaos. That is strategic agility.

What's the difference between psychological safety and just being nice?

Psychological safety is about candor, not comfort. Nice teams avoid conflict and hard truths to preserve feelings. Psychologically safe teams embrace conflict and hard truths because they trust the process and each other. You can have brutal honesty with psychological safety if that honesty is directed at problems, not people—and if everyone knows mistakes will not be weaponized later. The opposite of psychological safety is not rudeness. It is fear. And fear kills performance faster than any honest conversation ever could.

How do I implement these changes if I'm not the senior leader?

Start with what you control. If you lead a sub-team, apply these principles there. Model the behaviors: set explicit priorities, design rituals, build safety through vulnerability. Show results. Then share what worked with peer leaders and up the chain. Change does not always cascade from the top—sometimes it percolates from pockets of excellence. Atlassian's research focused on team-level dynamics precisely because that is where transformation happens. You do not need C-suite permission to stop having pointless meetings or clarify priorities with your direct reports. Lead where you stand.

Can these principles scale to large organizations, or are they only for small teams?

The principles scale; the execution adapts. Large organizations need the same fundamentals—clarity, coaching, safety, ritual design—but implemented at multiple layers. High-performing enterprises have clear priorities at the organizational level that cascade (not dictate) to divisions, departments, and teams. Each layer translates strategy to their context while maintaining alignment. The mistake large organizations make is thinking scale requires command-and-control. Atlassian's data suggests the opposite: as complexity increases, you need more psychological safety and distributed decision-making, not less. Centralized control does not scale. Trust and clarity do.

What's the fastest way to improve our team performance starting tomorrow?

Run a 30-minute priority alignment session. Ask everyone: "What are the top three things we should be focused on right now?" Compare answers. If you do not have 80% overlap, spend the rest of the session debating until you do. Write down the agreed priorities. Cancel any meeting or project that does not serve them. This single intervention—painful as it may be—will immediately redirect energy from diffusion to focus. Atlassian's 43% improvement statistic for teams with explicit priorities is not magic. It is the compounding effect of everyone rowing in the same direction. Start there. Everything else builds on that foundation.

References and Citations

Atlassian. (2025). State of Teams 2025: Global Research Report. Retrieved from https://www.atlassian.com/state-of-teams-2025
Atlassian Team Playbook. Team Health Monitor and Diagnostic Tools. Available at https://www.atlassian.com/team-playbook/health-monitor
Duhigg, C. (2016). What Google Learned From Its Quest to Build the Perfect Team. The New York Times Magazine. Available at https://www.nytimes.com/2016/02/28/magazine/what-google-learned-from-its-quest-to-build-the-perfect-team.html
Edmondson, A. C. (2018). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley. Available at https://www.wiley.com/en-us/The+Fearless+Organization-p-9781119477242
Project Aristotle (Google re:Work). Guide: Understand Team Effectiveness. Retrieved from https://rework.withgoogle.com/guides/understanding-team-effectiveness/steps/introduction/
Atlassian Work Life blog. The Science of High-Performing Teams. Available at https://www.atlassian.com/blog/teamwork
Harvard Business Review. (2023). The Leader as Coach. Available at https://hbr.org/2019/11/the-leader-as-coach
Atlassian. (2025). Hybrid Work Research: What Actually Works. Retrieved from https://www.atlassian.com/blog/hybrid-work-research