How to Improve Collaboration in the Workplace
Inefficient collaboration was estimated to cost organizations up to $16,491 annually per manager in wasted productivity, based on a global survey commissioned by Zoom and conducted by Morning Consult, according to Zoom's 2024 workplace collaboration report. That's a reason to question the next status meeting, not buy another messaging tool.
If you're deciding how to improve collaboration in the workplace, treat coordination as a cost that must earn its place. People need access to the right colleagues, clear authority, and room to disagree. They don't need another place to post the same update.
Table of Contents
- Where Workplace Collaboration Time Actually Goes
- Run a Two-Week Collaboration Reset
- Match Each Conversation to the Lightest Channel
- Roles, Workflows, and Tools That Set the Rules
- Scripts That Make Psychological Safety Real
- Rituals, Metrics, and Fixes When Collaboration Breaks
- Start With One Hard Conversation This Week
Where Workplace Collaboration Time Actually Goes
In Microsoft's 2023 Work Trend Index, aggregated Microsoft 365 activity during a rolling 28-day period ending in March 2023 showed employees spent 57% of their time communicating through meetings, email, and chat, leaving 43% for creating documents, spreadsheets, and presentations; since February 2020, the average employee's weekly Teams meetings and calls had increased by 192%.
That split doesn't mean communication is wasted time. A difficult customer handoff or a well-run design review can prevent expensive mistakes. But managers need to distinguish those interactions from updates that require everyone to stop working without helping anyone move forward.
Better collaboration means clearer purpose and fewer low-value interactions, not a fuller calendar.
Where collaboration time breaks down
Microsoft's activity measures and respondent-reported meeting difficulties point to different management fixes. Treat the costs below as diagnostic possibilities, not additional measured findings.
| Signal | Finding | What it costs | First lever |
|---|---|---|---|
| Time split | 57% communicating through meetings, email, and chat | 43% left for creating documents, spreadsheets, and presentations | Move status off the live calendar |
| Meeting growth since February 2020 | 192% increase in the average employee's weekly Teams meetings and calls | Nearly threefold meeting-and-call activity | Cancel or convert recurring series |
| Virtual brainstorming | 58% of respondents said it was difficult | Ideas get rushed or dominated by whoever speaks first | Pre-read plus a short decision meeting |
| Joining late | 57% found catching up difficult | People repeat context | Agenda and a written brief |
| After the meeting | 56% struggled to summarize what happened | Decisions get lost | Named note-taker |
| Next steps | 55% said they were unclear | Rework and follow-up messages | Owner and deadline before hang-up |
Start with status updates because they rarely require simultaneous attendance. Ask the owner to publish progress, blockers, and the request for help before you decide whether a conversation is necessary.
For brainstorming, collect ideas independently before discussing them. For late arrivals, keep the decision question and current options visible in the meeting document rather than restarting the conversation.
A note-taker should capture conclusions, not transcribe every sentence. End with responsibilities and deadlines, then send a short summary to people who couldn't attend.
Diagnose before you delete
Repeatedly reconstructing context adds work even when the meeting itself is short. Use cognitive load management to examine how much remembering, searching, and switching you're asking people to do.
Before changing the calendar, label a recurring meeting as decision-making, information-sharing, coordination, or relationship-building. If the organizer can't name its primary purpose, don't renew the invitation unchanged.
Run a Two-Week Collaboration Reset
Don't begin by deleting every recurring invitation. First establish what people are doing, which interactions help, and whose participation everyone else relies on.
Tell the team that the reset evaluates working practices, not individual responsiveness. Otherwise, employees may protect themselves by sending more updates, which produces the opposite of what you need.
Make the changes in order
Log the baseline. During the two-week reset, record meeting hours, recurring series, email or chat volume, stated response expectations, and protected focus time per person. Outlook or Google Calendar plus a shared spreadsheet is enough. Record patterns, not private message contents.
Tag each collaborative activity. Use decision-making, information-sharing, coordination, or relationship-building. For an invitation that seems to cover everything, ask what participants must accomplish before leaving. Split unrelated purposes rather than preserving a catch-all meeting.
Remove duplication. Compare forums by subject, attendees, and output. If a project review and a department update repeat the same status, retain the forum that resolves issues and replace the other with a written update. Don't remove a cross-functional discussion merely because it's inconvenient.
Assign decision rights. For each open decision, name the person authorized to close it and the date they'll do so. List who supplies input separately. Consultation isn't a veto, and attendance doesn't make everyone an approver.
Protect focus and publish response norms. Put recurring focus blocks on calendars. A workable starting rule is same-day acknowledgment for genuine blockers and next-business-day responses for routine requests, adjusted for time zones and customer commitments. Define the escalation route so urgent issues don't disappear inside muted chat.
Compare and adjust at the end. Review meeting hours, canceled or converted series, decision cycle time, rework, and who appears in the most threads. If meetings fell but decisions slowed, investigate the missing handoff before restoring the old calendar.
The point is to recover capacity, not merely relocate conversations: Harvard Business Review's Collaborative Overload describes research spanning more than 300 organizations in which 3%–5% of employees generated 20%–35% of value-added collaborations, alongside related findings that targeted changes to four or five collaboration practices recovered 18%–24% of collaborative time.
Keep the cuts from becoming someone else's burden
Watch the employee who knows every exception, approves every edge case, and gets copied into every rescue thread. Removing their meetings won't help if colleagues replace those invitations with direct messages.
Give that employee a deputy, document repeatable answers, and clarify which requests don't need their involvement. Schedule a lightweight quarterly review of dependency load, with the employee's knowledge rather than covert monitoring.
Don't reward fast replies as a substitute for good work. Don't convert every canceled meeting into a permanent chat channel. And never remove a forum while leaving its responsibilities unassigned.
Finish with a reset note the manager can send:
- Stopped: Name the forums that ended and where necessary work now goes.
- Moved async: Specify the update location, author, and publishing expectation.
- Decision ownership: List each decision category, its owner, and the escalation route.
- Protected: Confirm the cross-functional discussions and focus blocks that remain.
Match Each Conversation to the Lightest Channel
A written update and a live conversation solve different problems. The useful question isn't whether your team prefers Slack, Teams, or meetings. It's what participants need to accomplish and whether they need to be present together.
Choose the least demanding channel that still lets people understand, contribute, and act. Async work isn't automatically efficient if employees must write elaborate documents to settle a simple misunderstanding.
Lightest channel by collaboration purpose
| Purpose | Default channel | Meet live only if | Required artifact |
|---|---|---|---|
| Information-sharing | Async brief or document | A decision is blocked by missing context | Written summary |
| Decision-making | Written proposal with an explicit approval request | Real options and trade-offs need debate | Named owner and deadline |
| Coordination | Shared tracker | Dependencies conflict | Updated owners |
| Relationship-building | One-to-one or in person | Trust or conflict needs a person | Follow-up note on agreed actions |
Information-sharing needs a readable brief, not a slide deck that requires narration. Include what changed, why it matters, and what the reader needs to do. If nobody needs to act, say so.
For decisions, circulate the options and recommendation before gathering people. A written vote can reveal preferences, but it doesn't replace an accountable decision-maker. When trade-offs need debate, use a bounded live discussion rather than an open-ended review.
Coordination belongs in a tracker until dependencies conflict. Say marketing needs final copy before legal can finish reviewing the claim: bring the relevant owners together to negotiate the sequence, not the entire department.
Relationship-building deserves actual attention. Don't disguise a status interrogation as a check-in, and don't require employees to record personal disclosures in a shared document. A private note about an agreed follow-up is enough.
Make hybrid expectations explicit
The tension is real: McLean & Company's 2025 workplace-collaboration report describes nearly one in three respondents believing their organizations didn't collaborate enough, while the accompanying evidence includes Gallup's finding that teams with a formal hybrid-collaboration plan were 66% more likely to be engaged and 29% less likely to experience burnout than teams without one.
Those associations don't prove that writing a plan causes better outcomes. The practical value of a plan is more direct: employees shouldn't have to guess whether missing a call means losing their opportunity to contribute.
Publish who must attend, who receives notes, when written input closes, and how quickly responses are expected. Don't compensate remote colleagues with extra calls when what they need is access to the decision.
Use a simple entry test before sending an invitation: if the owner can decide from the document after receiving relevant input, don't schedule a meeting.
Audit recurring invites by seat, not just by meeting. Replace low-value attendance with the written update, an asynchronous decision request, or a short private conversation.
Roles, Workflows, and Tools That Set the Rules
A recurring workstream needs a decision owner, a rotating note-taker, and someone responsible for keeping the tracker current. These are responsibilities, not necessarily separate jobs. Keep them visible so people don't assume the organizer owns everything.
The decision owner signs off. The note-taker records conclusions and unresolved questions. The tracker owner checks that assignments, dependencies, and dates reflect what people agreed.
Fill in a working agreement
Use this compact template in the team's existing document space:
| Agreement | Fill in |
|---|---|
| Decision authority | Our decision owner is [name]; escalation goes to [name] |
| Channel rules | Briefs live in [location]; coordination lives in [tracker] |
| Response expectations | Blockers use [route]; routine requests receive a reply by [expectation] |
| Attendance | Required participants are [roles]; everyone else receives [record] |
| Meeting entry | The organizer provides [question, context, and requested outcome] |
For work crossing departmental boundaries, MakeAutomation's guide can help managers build stronger cross-functional teams without confusing participation with authority. Use decision-making frameworks when the disagreement is about how to decide, rather than who should attend.
Make tools obey the workflow
Keep the stack to what the team already uses where possible. Jira, Asana, or Microsoft Planner can hold coordination; SharePoint or Google Drive can hold briefs and decisions. Choose a designated home rather than copying records across them.
Chat is for quick questions. When someone makes a decision there, the owner copies it into the permanent record that day.
Before adding software, assign an administrator, define which existing channel it replaces, and set a trial end date. If it creates another inbox without retiring an old one, stop the trial.
Recheck responsibilities quarterly and whenever someone joins, leaves, or changes projects. A current agreement beats an impressive diagram nobody maintains.
Scripts That Make Psychological Safety Real
Psychological safety isn't comfort or constant agreement. It's a repeatable way to raise a risk, disagree, admit uncertainty, and recover after a mistake without being punished for speaking.
A 2025 Workplace Options and IIRSM psychological-safety survey of 370 leaders and managers reported broad agreement that psychological safety supports wellbeing, productivity, innovation, and business performance. Managers make that principle credible through their response when someone brings an inconvenient concern.
Give dissent a usable form
When challenging a senior decision, connect the concern to the work rather than the person's competence.
I see a risk to the date if we skip the review. Can we test that before we lock it?
This makes the concern specific and offers a way to examine it. The manager's job is to engage with the risk, not demand that the employee prove loyalty before being heard.
When someone brings bad news, resist the immediate cross-examination.
Thanks for saying it early. What do you need from me this week?
You can investigate causes and accountability after stabilizing the situation. If your first response is irritation, people learn to delay the next warning until they have a solution they think you'll accept.
Separate listening from deciding
Before giving advice, clarify what the person needs from the conversation.
Do you want a decision, a reaction, or just a witness?
A colleague describing a difficult interaction may need acknowledgment before problem-solving. Someone blocked on approval needs a decision, not an extended reflection. If the manager must act regardless, explain that boundary rather than pretending the conversation is entirely open-ended.
After someone raises a concern, set a follow-up date and return with a clear response.
Here is what changed. Here is what we're keeping, and why.
Closing the loop doesn't require accepting every suggestion. It requires showing that someone considered the concern and explaining the outcome. Silence after disclosure makes the invitation to speak up feel hollow.
Account for power, not just participation
An employee can contribute confidently to a project discussion and still hide excessive workload or unfair assignments. Ask about capacity privately: what will slip if this request stays, and what should come off the list?
Don't make the employee solve an impossible workload alone. The manager owns the priority trade-off, including telling another stakeholder that their request must wait.
Rehearse conversations where the power gap is especially sharp, such as a layoff update, promotion discussion, performance review, or return from leave. Separate what's decided, what remains open, and what you genuinely want input on.
At the next staff meeting, invite dissent before closing a decision. Thank the person who offers it, examine the substance, and explain what you'll do with it.
Rituals, Metrics, and Fixes When Collaboration Breaks
Google's Project Aristotle found psychological safety was the strongest factor associated with team effectiveness across more than 180 Google teams; in a follow-on internal application, teams adopting at least one new working norm reported a 6% improvement in psychological-safety ratings and a 10% improvement in structure-and-clarity ratings, according to this account of Project Aristotle's findings.
Treat those results as organizational evidence, not universal causal estimates. The work was an internal management study, not a peer-reviewed experiment. Its useful lesson is to change observable team behaviors rather than assume a different personality mix or star hire will repair coordination.
Keep the rituals small
Adopt a limited set of behaviors that people can recognize:
- Rotate facilitation: Let different team members manage the discussion, not merely present their updates.
- Read back commitments: Before ending a decision forum, confirm the written owners and dates aloud.
- Pause for dissent: Reserve a brief round before closure so the fastest agreement doesn't become the final answer.
Measure outcomes rather than online presence. Lauren Baptiste publicly states that productivity is about outcomes, not activity. Green-status time and message volume won't tell you whether people made a sound decision or avoided rework.
Use a small monthly scorecard during the initial reset period:
| Measure | What the manager should examine |
|---|---|
| Meeting hours per employee | Whether necessary work still gets done |
| Meetings canceled or converted | Whether written alternatives remain useful |
| Decision cycle time | Where approval or missing input causes delay |
| Rework | Whether unclear decisions cause repeated effort |
| Dependency concentration | Whether the same people remain unavoidable |
Collaboration symptoms, causes, and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Hybrid call goes quiet | Unclear decision rights or fear of fallout | Pre-read the question and invite dissent |
| Same three people on every thread | Dependency load concentrated | Cap optional meetings and name a deputy |
| Chat replaced meetings and nothing closes | No owner after the channel change | Add an owner and deadline on the thread |
| Status meeting comes back | No trusted written update | Require a five-line note before reopening it |
| Remote people hear decisions late | The live meeting is the only record | Publish owners and deadlines the same day |
| Agreement in the room, debate in side chats | Input and decisions are mixed | Ask whether they want a decision, a reaction, or a witness |
A missing owner can often be resolved in a conversation. Redistributing specialist knowledge takes sustained delegation and documentation. Rebuilding confidence after a layoff or reorganization takes consistent behavior, not a newly branded meeting.
Pebb's practical solutions to workplace collaboration challenges offer additional troubleshooting prompts. When the problem is fear rather than logistics, focus on building workplace trust instead of changing channels again.
Our coaching method follows a similar discipline: get clear on what's going on, separate what matters from what's loud, pick a realistic next step, follow through without shame, and build change that lasts. A thoughtful question beats a pile of generic tips when it exposes the actual obstacle.
Pick the row that matches this week's problem. Assign its fix, then check whether the behavior changed before introducing another ritual.
Start With One Hard Conversation This Week
Choose a conversation already on the calendar: a decision the group keeps reopening, a capacity pushback, a performance review, or a difficult update after a reorganization. Don't schedule a separate collaboration workshop to prepare for it.
Prepare the conversation, not another meeting series
Write a short preparation note:
- Decision or concern: State what needs to be resolved without burying it in background.
- Dissent needed: Name the assumption or risk you want someone to challenge.
- Commitment at the end: Identify the owner and date you intend to leave with.
Include the channel rule and response expectation in that note. Give people a way to raise a follow-up without automatically creating another standing invitation.
For people who freeze before the conversation, we offer Text Lauren from Acheloa Wellness as a private rehearsal. Lauren for Teams provides on-demand coaching for the whole team, not just executives: the company sends employees a number, and they start texting, with no new app or SSO project. Conversations stay between Lauren and the employee and are never shared with HR, which matters when the concern involves workload, promotion, or speaking up.
Use the support before and after the conversation. Clarify the point, walk in, then debrief what happened rather than judging yourself only on how confident you felt.
Keep the standard practical: fewer unnecessary recurring meetings, a written owner for each decision, and dissent invited on purpose.
Acheloa Wellness, Inc. offers AI-powered coaching by SMS to help people prepare for difficult conversations, set boundaries, and follow through. Visit Acheloa Wellness, Inc. to explore private, in-the-moment support for the conversations that make workplace collaboration work.
