How to Reduce Collaboration Waste

40-60% of your engineering delivery time is lost to handovers and coordination waste. Not to coding. Not to testing. Not to requirements. To waiting, asking, aligning, and passing work between people. The DevOps Handbook and Lean Software Development research make this painfully clear. Your biggest delivery bottleneck isn't technical complexity. It's the space between people. Here's what most organizations do: They add more process. More meetings. More documentation. More alignment rituals. And they wonder why things get slower instead of faster. What actually works? Eliminating the handovers entirely. Concurrent product development puts all the bright people working on the same thing, at the same time, in the same place. Requirements analysis, coding, testing, and documentation happen simultaneously, not sequentially. No waiting for specs. No waiting for code. No waiting for test results. No waiting for documentation. The Three Amigos approach (business analyst, developer, tester) working together in real-time on the same problem creates something you can't get any other way: shared understanding that doesn't need to be written down and handed off. The result? Teams that apply true concurrent development report what used to take 3 weeks being completed in a single day. Same people. Same skills. Radically different approach to how work flows between them. What percentage of your team's time is spent waiting for someone else? #ContinuousDelivery #TDD #ProductDevelopment

Your team is burning $1.48M a year on duplicate work. And you probably don't even know it. I analyzed productivity data from 500+ companies last month. Here's what I found: Your marketing team is recreating assets that already exist. Your developers are solving problems someone cracked months ago. Your sales team? They're rebuilding presentations from scratch. The numbers are shocking: • 2.5 hours per employee per week spent on duplicate work • $40.87 average hourly rate • $51,000 wasted every week • $1.48M burned annually But money isn't the worst part. It's killing your team's morale. It's missing deadlines. It's suffocating innovation. Here's how to fix it: 𝟭. 𝗕𝘂𝗶𝗹𝗱 𝗮 𝘀𝗶𝗻𝗴𝗹𝗲 𝘀𝗼𝘂𝗿𝗰𝗲 𝗼𝗳 𝘁𝗿𝘂𝘁𝗵 • Pick one tool (Confluence, Notion, Drive) • Create clear folder structures • Make it accessible to everyone 𝟮. 𝗧𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺 𝘆𝗼𝘂𝗿 𝗺𝗲𝗲𝘁𝗶𝗻𝗴𝘀 • Replace status updates with alignment checks • Ask "What should others know about?" • Share wins and roadblocks 𝟯. 𝗥𝘂𝗻 𝗮 𝘄𝗮𝘀𝘁𝗲 𝗮𝘂𝗱𝗶𝘁 • Track duplicate work for 1 week • Find the process gaps • Fix ownership issues 𝟰. 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲 𝘁𝗵𝗲 𝗯𝗮𝘀𝗶𝗰𝘀 • Template repeated tasks • Set up auto-reporting • Create shared dashboards Start here: Pick one department. Track duplicate work for 7 days. The results will shock you. What's the biggest time-waster in your team? Drop it below 👇

I've carefully observed hundreds of team meetings across industries, and one pattern emerges with striking consistency: the level of frustration team members feel leaving a meeting directly correlates with how clearly everyone understood why they were there in the first place. In one organization I worked with, weekly team meetings had become so unfocused that people openly admitted to bringing other work to complete while "listening." The meeting culture had deteriorated to the point where even the leader dreaded convening the team. Sound familiar? What transformed this team wasn't elaborate techniques or technology—it was implementing what I now call the "Purpose-Process-Outcome" framework. Before every meeting, this framework asks three deceptively simple questions: PURPOSE: Why are we meeting? What specific need requires us to gather synchronously rather than handling this asynchronously? PROCESS: How will we use our time together? What structures and activities will best serve our purpose? OUTCOME: What tangible result will we have produced by the end of this meeting? How will we know our time was well spent? When we implemented this framework with that struggling team, the transformation was remarkable: Meetings shortened from 90 minutes to 45. Participation increased dramatically. Most importantly, team members reported feeling that their time was respected. What made the difference? Each person walked in knowing exactly why they were there and what their role was in creating a specific outcome. One team member told me: "I used to leave meetings feeling like we'd just wasted an hour talking in circles. Now I leave with clear action items and decisions we've made together." Another unexpected benefit emerged: the team began to question whether meetings were always the right solution. They discovered that about 30% of their previous meeting time could be handled more efficiently through other channels. The framework forces clarity that many leaders avoid. When you can't clearly articulate why you're gathering people, what you'll do together, and what you'll produce, it's a signal to pause and reconsider. I've found that when team leaders commit to this framework, they stop being meeting facilitators and become architects of meaningful collaboration. The shift is subtle but profound—from "running" meetings to designing experiences that accomplish specific goals. What's your best tip for making meetings more productive? Share your wisdom in the comments. P.S. If you’re interested in developing as a leader, try out one of my Skill Sessions for free: https://lnkd.in/d38mm4KQ

We recently overhauled how we collaborate at Stytch. Everyone canceled all their meetings and rebuilt their calendars. As a hybrid team, it's easy to default to death by a thousand 1-1s. While 1-1s certainly have their place, we found that people's days were overwhelmed with meetings and many of those were siloed conversations resulting in inefficient use of time. We wanted to create more time in everyone’s day for heads down time, impromptu meetings or huddles to get alignment in order to improve the efficiency and speed with which we’re making decisions. While we’ve always had a really strong culture of docs, we’ve been much weaker on async quick collaboration, namely our usage of Slack. For context, “Slack [the company] sends 70% [of messages] in public channels, 28% in private channels and just 2% in direct messages.” At Stytch our stats before this were: 17% in public channels, 6% in private channels, and a whopping 76% in direct messages!! Here's the tldr of what we're doing: • Default monthly for manager/direct report 1-1s, adjustable as needed • Managers should have 2-4 hours of unscheduled time per day for ad hoc conversations and async collaboration • If a meeting doesn’t have an agenda the night before, cancel it • Prefer group meetings over 1-1s to prevent having to play telephone or have the same conversation repeatedly • Move to more frequent, shorter meetings, like a biweekly stand up instead of a weekly hour long meeting to allow for more timely decision making • Move more conversations to Slack, especially public channels • Slack isn’t always the right tool, if your thread looks like a CVS receipt, either move to a 1 pager or ad hoc sync Instead of 8+ hours of back to back meetings everyday, now I have down time to post more on linkedin!!! JK I timed this and it took me 10 mins. But it is remarkable how much my days have changed, I can give much more timely feedback and dig into things more in depth. We’re just two weeks but excited to see how this experiment goes over the next couple months!

Stop Asking for Input You Don't Actually Want. I've seen this play out countless times in engineering teams: ➡️ A product manager "gathers requirements" but has already decided on the solution ➡️ A CTO asks for technical feedback on a decision they've already committed to ➡️ An executive seeks "team buy-in" on a roadmap that's already set in stone The damage is worse than wasted time. It erodes trust, kills innovation, and trains your team that their insights don't matter. I've been guilty of this myself. It's tempting to create the appearance of collaboration without the messy reality of actually considering different viewpoints. The most effective leaders I know do something different: ✅ They're transparent about what's already decided vs. what's open for input ✅ They genuinely consider perspectives that challenge their own ✅ They explain final decisions, especially when they go against team input Your team can smell fake collaboration a mile away. And once that trust is broken, good luck getting honest feedback when you actually need it. How are you ensuring the input you ask for actually matters?

Before you book another 30-min slot ask yourself this: Does this convo really need a meeting? That 30-min sync just stole 5 hours from your team. (10 people x 30 mins = wasted afternoon) Most meetings are time thieves disguised as collaboration. Here's your cheat sheet to decide faster: 1. Status updates ⇢ Async Post a short Loom or Slack note. No one needs 10 people sitting through what they could read in 2 minutes. 2. Brainstorming sessions ⇢ Meeting Ideas bounce faster when people react in real time. Keep it short and appoint someone to summarize. 3. Project reviews ⇢ Mostly async Share a Notion doc or deck. Only meet if there's real debate or a decision to make. Still reading? Good. These next ones surprise people: 4. Performance feedback ⇢ Meeting Feedback lands better when it's human. Eye contact > emojis. 5. Weekly team syncs ⇢ Depends If it's just updates, move it async. If it's for planning or alignment, keep it... but add structure and action steps. 6. Task clarification ⇢ Async Record a Loom walking through what you need. Saves everyone from another "Can you explain that again?" call. 7. Sharing new ideas or proposals ⇢ Async Drop a Notion doc or deck. Let people comment and react on their own time... better feedback that way. 8. Team celebrations or wins ⇢ Async (with a twist) Post in Slack, tag folks, or share a quick video shoutout. Doesn't always need a call... a public thank-you goes a long way. The goal isn't to cancel everything. It's to protect your team's focus. Every unnecessary call drains energy from the work that actually moves the needle. So next time your calendar fills up... pause and ask: Am I about to waste people's time? 👊 How do you decide when a meeting is actually worth it? 💬👇 --- ♻️ Repost to help someone reclaim their team's focus ✚ Follow Cory Blumenfeld for more entrepreneurial insights and motivation. I'm on a mission to inspire 1M everyday people to start their own business and find their voice in the process.

Most teams say collaboration drives performance. Our data shows collaboration often destroys it when unmanaged. 1. Network Size Healthy networks sit around 60 to 150 weekly collaborators. The typical employee has 72. Yet 20% sit in isolation risk. Isolation feels like low visibility and zero support even when busy. 2. Core Working Group High performers work with 5 to 12 close collaborators a week. The typical employee has 11. But 35% interact with 15 or more. That is not collaboration. That is context switching at scale. 3. Cross Team Contact Some partner teams spend only 12 minutes together a week. 12 minutes. That is not partnership. That is friction disguised as alignment. 4. Distributed Overlap Teams need roughly 4 to 6 hours of overlap per day to move fast. Too little overlap slows decisions. Too much real time communication kills focus. Balance wins. 5. Meeting Load Employees sit in about 11 hours of meetings weekly. Healthy range is about 4.5 to 8. Beyond that, productivity falls and decision cycles stretch. High performing teams do not collaborate more. They collaborate correctly. Small trusted groups. Meaningful cross team touch points. Enough sync to align. Enough async to think. If you could change one collaboration rule inside your company tomorrow, what would it be?

I've spent a decade learning about Scrum, Kanban, SAFe, Nexus, Lean etc etc. And honestly, 80 percent of the value of these tools comes from 5 main principles that you can achieve without a framework. 1. Work in small batches Every change and value add should be as small as you can make it. Yes, even when that seems like it's MORE work. This doesn't mean breaking every outcome into infinitely small tasks, it means breaking down the OUTCOME into the smallest parcels of recognizable value that is possible. 2. Focus on Value Things that seem obvious but are missed 90 percent of the time. Goals are more important than work items or elaborate plans. What 'value' means in your context is the first thing you need to pin down, but once you do, focus on it relentlessly, and make sure everything you do is in service to a valuable goal. 3. Pull, Don't Push Teams working on complex products need time to think, analyse and learn. The fastest way to make them unable to deliver value is to constantly push work onto them to fill their capacity. When Principle 2 is respected, principle 3 is easy. Let teams pull work as needed to deliver that value we care about it. 4. Eliminate waste Waste takes many forms, and a lot of them look like productivity. You should always assume that most of what you're doing is wasteful. Identify the most valuable things you're doing, and eject almost everything else. Keep it simple, from the product you're building to the way you build it. 5. Align on goals, not plans Working at scale is tough, and it can be easy to try to solve problems by aligning teams to fixed plans with clear dates so they can have certainty of what is needed, when. Instead, align on goals. Make sure that every team that might have a reason to care what you're doing knows exactly what you're trying to achieve right now. Keep the communication lines open, and make sure that if a goal is at risk, it's made transparent quickly. Detailed plans rarely make a difference so long as you understand *why* we're making the decisions we're making.

Most people assume collaboration happens naturally. It rarely does. Not because people are difficult. But because they are overwhelmed, distracted, and unsure if working with you will actually make their life easier. Meanwhile, your best ideas stall. Projects lose momentum. Opportunities slip by simply because the right people never said yes. Here are 6 reasons collaboration falls apart (and what to do to turn it around): 👉 People do not understand the value They cannot see the benefit clearly. Explain the win for them, not just for you. 👉 You have not built enough trust Collaboration requires confidence in your reliability. Show small proofs first so they can see your follow-through. 👉 The ask feels too big Most people decline because the commitment looks overwhelming. Break the request into smaller steps and lower the barrier to entry. 👉 They do not see where they fit If roles feel vague, people hesitate. Clarify what you need and why you chose them. 👉 Timing is unclear Busy people default to no unless urgency is obvious. Explain the timeline and why now matters. 👉 You have not tapped into mutual benefit People are most motivated when interests align. Look for outcomes that support their goals as much as yours. Collaboration is not luck. It is a skill. When you make it easier for others to say yes, your ideas move farther and faster than you ever could on your own. Which one of these resonates most with you? Repost to help someone else (or spark a conversation about collaborating!) ⊕ Follow Dorie Clark for more

The meeting is not the work. The work is the work. Why over-scheduling is killing your execution engine. Let’s get something straight: If your team needs 14 meetings to finalize a two-slide update… You don’t have a performance problem. You have a calendar addiction. Everyone’s talking about execution. But no one’s actually doing the work. Because here's the truth nobody wants to hear: 👉 You’re not executing—you’re over-scheduling. 📅 Welcome to the meeting apocalypse At some point, leaders stopped leading and started hosting. You’ve got kickoffs, sync-ups, alignment sessions, retrospectives, and “quick touch-bases” that last 43 minutes. And then you wonder why nothing gets done. 📊 According to Microsoft’s 2023 Work Trend Index: The average employee spends 252 hours a year in unnecessary meetings. That’s over 6 weeks of full-time work lost—per person. Multiply that by your team size. Now imagine what your quarterly numbers could look like with that time actually spent executing. 🧠 Meetings aren’t evil. Misused meetings are. Let’s be clear—some meetings matter. But most? • Could’ve been a Slack. • Could’ve been an email. • Should’ve been cancelled before it even hit the calendar. We use meetings to feel busy. To avoid decisions. To delay accountability. To perform the illusion of progress instead of actually making progress. That’s not collaboration. That’s organizational theater. ⚙️ Execution Is what you deliver—not what you discuss If you walk out of a meeting with: • No clear owner • No deadlines • No decision • Or worse, another meeting scheduled... You didn’t work. You just rehearsed. Execution happens in motion, not in a Zoom room. It lives in deliverables, shipped code, closed deals, launched campaigns, tough calls made—not slides about how nice it’ll all look later. 💣 So, what should you do? 1. Kill half your meetings. No ceremony. Just do it. If you’re not sure which ones? Start with the ones no one wants to attend. 2. Default to async. Write, record, document. Your future self (and team) will thank you. 3. Enforce ruthless clarity. Every meeting must answer: What’s the decision? Who owns it? When’s it due? 4. Create time for deep work like its revenue-generating—because it is. Block the calendar. Guard it like your bonus depends on it. (It does.) 🧨 Make no mistake You don’t get paid to meet. You get paid to move. And if you’re drowning in meetings, chances are your execution is gasping for air. Because the meeting is not the work. The work is the work. #Leadership #Management #Meeting #Execution #Strategy #Productivity #TimeManagement #MeetingFatigue #Meetings