Techniques for Reviewing Team Collaboration Efficiency

I helped a COO cut delivery delays by 92% with one focused, 30 minute review a week. But it didn’t start that way. When I first met him, the teams were spending hours a week talking about priorities and alignment. They didn’t need that much time, They just didn’t know any different. Before I begin, a few terms I want you to be familiar with: Big Rocks - These are the most important goals of the week. We specify them, give a good definition of done, go over any questions, and then delegate them. Blockers - Anything that makes our big rocks impossible. These must be cleared ASAP. Openings - Optimizations that come up during our review, and are worth pursuing at this time. If they’re good ideas, but not worth pursuing now, we can still list them without an owner. With those out of the way, here is my condensed agenda for the most important meeting of the week: 1. Review last week Go over each Big Rock with the owner, as well as its status. If it’s still in progress, the owner should have an estimated completion date. If it’s too big to estimate, it’s too big of a rock. Chip it down. If it’s blocked, a fix needs to be identified and assigned with a deadline (more on that later). 2. Decide this week’s big rocks These are high leverage activities that will make everything else you do easier. They should be needle movers, not just busy work. As each is decided, discuss them in enough depth that everyone knows what the ideal outcome is, and how they can help deliver it. Clearly assign one owner to each rock. Confirm that they understand the outcome, and that all their questions have been answered. Document a clear first step so everyone knows how the ball is going to get rolling. 3. Blockers As you’re discussing past and future rocks, blockers will surface. These MUST be documented and assigned with clear deadlines. They should be assigned to the person who can clear them and 80% of the time that should NOT be you. If you’re having blockers assigned to you often, have someone shadow you on them a few times so you can eventually delegate to them. 4. Openings Throughout the discussions, opportunities for optimizations will also come up. These should only be pursued if 1) an attendee (not you) volunteers to take them on, and has the bandwidth to do so, or 2) they clearly tie back to a bigger objective that is already present. These are stretch goals unless they specifically become big rocks. Once they’re agreed on, assign an owner to them along with a clear next step so there’s a push to get the ball rolling. It may take a few times before ownership reviews like this become natural, but they are the single highest leverage activity you can do in only 30 minutes. I’ve even seen good reviews even start to replace the need for some of the other weekly meetings! 📌 Comment “Review” and I’ll send you my complete guide so you can start saving time too!

⚡ Employees with fewer than 2 hours of workday overlap with close collaborators take 3x longer to respond to messages. That’s not just an inconvenience...it’s a breakdown in collaboration efficiency. The shift to distributed and asynchronous work has fundamentally changed how teams operate, but the data reveals serious challenges: 📉 Low workday overlap = decision-making bottlenecks. When employees have limited shared working hours, response times lag, project cycles slow down, and real-time collaboration becomes near impossible. 💬 After-hours messaging isn’t a solution—it’s a problem. Employees who receive 15+ Slack messages after-hours report higher burnout and disengagement levels, showing that async work needs structure, not just flexibility. 🤝 Teams that fail to maintain strong cross-functional connections are 30% more likely to experience collaboration breakdowns. Lack of structured interactions leads to knowledge gaps, missed handoffs, and duplicated work. How do we optimize async collaboration without sacrificing speed and effectiveness? ✅ Set Clear Collaboration Hours 🔹 High-performing hybrid teams structure 2-3 hours of daily overlap for synchronous work. 🔹 This ensures essential decisions happen without forcing unnecessary meetings or 24/7 Slack availability. ✅ Leverage AI for Smarter Async Workflows 🔹 Automated note-taking & meeting recaps help reduce redundant calls. 🔹 Threaded Slack conversations (vs. direct messages) allow for flexible, non-disruptive collaboration. 🔹 Clear response expectations—not all messages need an instant reply. ✅ Monitor & Strengthen Network Health 🔹 Employees with fewer than 3 strong collaborations per week are at higher risk of disengagement. 🔹 Use ONA to identify disconnected teams and reinforce strategic connections. ✅ Rebalance Synchronous & Asynchronous Work 🔹 Target 30-60% async collaboration (document sharing, Slack threads, project boards) to protect focus time. 🔹 Cap meetings at 30 minutes and default to async updates when possible. 🔹 Monitor meeting-to-focus ratios—teams spending over 60% of their time in meetings struggle to execute effectively. Collaboration isn’t just about where we work...it’s about how we work. Want more collaboration insights? Make sure to check the comments for our full report. What strategies is your team using to optimize async collaboration? #PeopleAnalytics #HRAnalytics #Collaboration #HybridWork #FutureOfWork

If you’re tired of team exercises that feel forced, try the Start / Stop / Continue ritual that actually builds team bonding. Here’s how to do it: Step 1: Pick a topic Choose one specific area you want to improve. You can do this as a team (like marketing strategy, branding, or workflow) or even as a couple or family (like health habits or household routines). When my team did this for our marketing strategy, we asked: “What’s working? What’s not? What should we try next?” Step 2: Sticky it up Give everyone a stack of sticky notes. Each person writes down every task they do related to that topic (one per note). Then, color-code: • Different colors for different people (for transparency) • Or all one color if you want to keep feedback anonymous This part alone often surprises people. We realize how many invisible tasks we’re doing, and how much effort goes unnoticed. Step 3: Place the tasks Draw three columns on the board: 🟢 Start – New ideas or things worth trying 🔴 Stop – Tasks that drain time or add no real value 🟡 Continue – What’s working and worth doubling down on Then, together, sort each sticky. When we did this at Science of People, we learned: • We wanted to start experimenting with Medium and LinkedIn posts • We needed to stop wasting time on low-return platforms (sorry, X) • And we should continue doing more of what was driving real results (YouTube, email newsletters, and blog writing) If you disagree on something (like we did about Medium), place it in between columns as a trial. Set a test period. For example, “Let’s try this for 2 months and then review.” Step 4: Create a safe space This is a critical step. Start / Stop / Continue only works when feedback feels safe. You’re talking about the task, not the person. We even use different colored stickies to separate ideas from ownership. That way, no one feels attacked. When people feel psychologically safe, they share the truth, and that’s when real improvement happens. Step 5: Assign and act Insight without action is just decoration. So before you finish, assign ownership: • Who’s starting the new tasks? • Who’s stopping or phasing out the old ones? And for the “Continue” column, ask: “Can we make this even better?” A bonus: It works outside of work, too I even do this exercise with my husband once a year, for our health and habits. We’ve listed things like: • Start: Morning protein shakes, evening routines • Stop: Buying soda, eating out too often •Continue: Yoga and weekend soccer We walk away feeling more connected and intentional. The takeaway: When you pause to ask, “What should we start, stop, and continue?” you give yourself (and your team) permission to refocus energy where it truly matters.

Most teams don’t have a talent problem. They have a challenge problem. It’s not that people aren’t smart, skilled, or hardworking. It’s that they play it too safe in conversations, avoid tough questions, and hesitate to push each other’s thinking. 👇 The result? Slow decisions, missed opportunities, and a team that feels collaborative but isn’t truly high-performing. A leadership team I worked with had all the right ingredients: experience, ambition, and expertise, but their discussions stayed surface-level. They weren’t failing, but they weren’t excelling either. So, we made some tweaks.  Not by forcing more meetings, but by shifting how they work together. Here are 6 practices you can also try: 1️⃣ Mental Model Mapping Instead of debating what to do, map out how each team member thinks about a challenge. Ask everyone to write down: - What assumptions they are making - What past experiences shape their views - What risks they foresee Comparing these “mental maps” exposes team blind spots and enhances collective intelligence. 2️⃣ Curiosity Round Before giving feedback, asking this question first: “What was your thought process behind this?”. It opens up constructive dialogue instead of triggering defensiveness. 3️⃣ "Energy Audit" Method Instead of assigning tasks based only on skills, tracking what energizes or drains each team member helps optimize workflows and prevent burnout. 4️⃣ "Mistake-Learning" Sprint Once a month, instead of analyzing success stories, pick a past team failure and collaboratively discuss: - What went right despite the failure? - What invisible factors played a role? - How would we approach it differently now? 5️⃣ Red Team vs. Blue Team For big decisions, split the team into: - The Red Team (critics) who try to poke holes in the idea - The Blue Team (defenders) who justify why it will work This forces teams to think through risks and opportunities instead of making rushed choices. 6️⃣ One Bold Experiment Encourage teams to propose and test one out-of-the-box idea every quarter, with permission to fail. - Frame it as a low-risk experiment rather than a big change - Assign a “learning lead” to document what works - Celebrate insights, not just outcomes This keeps teams innovative without fear of failure. P.S.: Which one would make the biggest difference in your team? --------------------------------- Hi, I’m Susanna. I help leaders and organizations build high-performing teams through psychological safety and inclusive leadership. 🚀 Visit my website to book a free discovery call!

The #1 mistake I see companies make isn’t strategy. It’s collaboration. And it’s costing you more than you think. Here’s what’s happening: You’re treating performance like an individual sport. One “expert.” One “owner.” One “hero.” But here’s the problem with that approach… One study of 222 project teams found something remarkable: Groups outperformed their most proficient member 97% of the time. 97%. Let that sink in. So if your team is stuck, stop asking: “Who’s the expert?” Start asking: “How do we solve this together?” That shift changes everything. Here’s the simplest question I use with leadership teams: “What do you see that I don’t?” Then I do one thing most teams skip… I make it safe for the quiet people to speak first. Why? Because the first voices shape the whole room. If the loudest person goes first, everyone else just agrees or stays silent. Equal voice isn’t a “nice-to-have.” It’s how you get: • Better decisions • Faster alignment • Fewer blind spots And you have to measure it—not just outcomes, but collaboration behaviors. Try this for 30 days: Every meeting ends with: “What’s one risk we’re not naming?” “What’s one idea we didn’t hear yet?” Then assign the next step as a team— not a hero. Here’s the truth: If you fix collaboration, results follow. If you don’t, even great strategy collapses under friction. Stop building teams that depend on one genius. Build teams that compound intelligence. That’s how you turn good teams into unstoppable ones.

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

Kanban: We Should Be "Done" With "In-Progress" One of the best ways to use Kanban is by visualizing meaningful work states on your board. Thoughtfully designed boards can transform how teams deliver value, spot inefficiencies, and improve collaboration. Unfortunately, many teams miss these opportunities by relying on vague, catch-all columns like “In-Progress.” Let’s talk about why “In-Progress” is practically useless, and how breaking it into clearer work states is a smarter strategy. Why “In-Progress” Fails The term “In-Progress” might seem harmless, but it’s so broad that it adds little value. “In-Progress” doesn’t explain what’s actually happening. Is a task being coded, reviewed, or tested? Without specifics, delays and inefficiencies stay hidden. A generic column hides bottlenecks. For example, slow code reviews go unnoticed when everything sits under “In-Progress.” Vague statuses make it harder to know who should act next. Confusion leads to reduced accountability, delays, and misaligned expectations. Without data showing where tasks spend the most time, teams can’t identify trends or resolve inefficiencies. The Case for Clarity Replacing “In-Progress” with specific work states turns a Kanban board into a powerful tool for managing flow and driving improvement. For example, a software development team might use: Backlog: Items awaiting prioritization. Ready for Development: Work ready to start. In Development: Developers are actively working. Ready for Code Review: Development is complete, awaiting review. In Code Review: Review process underway. Ready for Testing: Code is ready for QA. In Testing: QA is actively testing. Ready for Deployment: Testing is complete, awaiting release. Done: Work is completed. Each state reflects a clear step in the workflow (not necessarily a handoff). This improves visibility, accountability, and makes bottlenecks easier to spot. Your team’s context might call for different states, but the goal stays the same: clarity. Spotting Bottlenecks Granular states make delays visible. If tasks sit too long in “Ready for Code Review,” reviewers may be overloaded or not prioritizing reviews. A backlog in “Ready for Deployment” could mean release processes need work. Tasks stuck “In Testing” might point to unclear requirements or a stretched QA team. Tracking time-in-state reveals where delays occur, helping teams reallocate resources or refine processes. Collaboration Benefits Meaningful work states improve collaboration. When a task moves to “Ready for Testing,” testers know it’s their turn to act. This reduces idle time and makes transitions smoother. Be Done With “In-Progress” Create columns for key steps in your workflow. Don’t overcomplicate things. Aim for enough granularity to reveal bottlenecks without overwhelming your team with administrivia. Set clear entry and exit criteria for each column. Kanban isn’t just about making work visible; it’s about making the right work visible.

How can 12 people consistently outperform a team of 200 engineers. We have all seen this David vs Goliath story play out time and time again. But something more interesting is happening. After optimizing engineering teams for 15+ years, I've discovered something counterintuitive: Team intelligence isn't about having the smartest people or the biggest budget. It's an emergent property that happens when you create the right conditions. Think of it like making popcorn. You can have the best kernels in the world, but without the right environment, you'll just end up with warm corn. Carnegie Mellon researchers found something fascinating: A team's collective intelligence predicts success better than individual IQ scores. Even better than the smartest person on the team. Here are two patterns I've seen transform good teams into great ones: ━━━━━━━━━━━━━━━━━━━━━━━━━━ 1️⃣ THE BURST METHOD High-performing teams don't communicate more, they communicate differently. They work in intense bursts of collaboration followed by deep focus time. Like intervals at the gym, but for your brain. Real example: A consumer products team was drowning in meetings. We flipped their schedule: → One focused 90-minute team session daily → 4-hour deep work blocks → "Check twice daily" async communication Result: 28% faster releases, 40% fewer meetings. More shipping, less Zooming. What's one workflow change that transformed your team's productivity? 👇 ━━━━━━━━━━━━━━━━━━━━━━━━━━ 2️⃣ THE KNOWLEDGE MAP Ever notice how frustrating it is when the one person who knows something critical is on vacation? One financial services team solved this with quarterly "expertise mapping", basically show-and-tell where everyone shares what they're secretly amazing at. The result? Solution time dropped 41% because people finally knew who to ask. Their best security breakthrough came from two people who had never talked before. Sometimes the best ideas are just two half-ideas that haven't met yet. ━━━━━━━━━━━━━━━━━━━━━━━━━━ Here's the really good news: Unlike technical skills that take months to build, you can improve team intelligence quickly. It's about changing how people work together, not teaching them new technical skills. As AI becomes central to what we build, the winners won't be teams with the most individual knowledge, they'll be the ones who are best at thinking together. Struggling with team dynamics or release velocity? I help tech teams unlock their collective intelligence. Drop me a message. 💬 ♻️ Repost and comment if you found this valuable ➕ Follow me (Phillip R. Kennedy) for more like this.

Everyone has their role. But they have to stay in sync. Communication is the difference between cross-functional alignment and costly confusion. Finance, Ops, and RevOps all care about performance, but they often define and track it differently. And if your team spends more time interpreting each other than acting, growth stalls fast and value-creation is impossible. So what does effective communication actually look like in a scaling agency? 1. Create shared language around core concepts How: Agree on standard definitions for key metrics like “forecast,” “margin,” “utilization,” and even “booked vs. billable.” Put these into a shared knowledge base or glossary and refer back regularly in dashboards, meetings, and reporting. Example: You say “utilization is low.” Ops hears “we need to fire someone.” Finance hears “margins are tanking.” Instead, everyone agrees: utilization = total billable hours ÷ total available hours. Now you’re debating numbers, not definitions. 2. Use asynchronous updates for tactical reporting How: Move recurring tactical updates (like forecast roll-ups, budget tracking, pipeline status) into asynchronous formats like Loom videos, Slack threads, or shared dashboards so meetings are reserved for strategy and decisions, not reporting. Example: Instead of spending 30 minutes reviewing pipeline and delivery metrics in your weekly sync, each function posts a Loom walk-through in a shared channel every Monday. Your Tuesday meeting now focuses on what the data means and what to do about it. 3. Make project and pipeline transparency a default, not a request How: Give all three teams access to real-time delivery and pipeline data via shared tools (e.g., HubSpot, ClickUp, Float, Mosaic). Remove permission bottlenecks. Build dashboards that auto-pull from shared sources. Example: RevOps updates a proposal scope. Ops sees it immediately in ClickUp. Finance sees the expected hours in their margin model. No email. No Slack ping. No lag. Everyone acts faster because they’re already in the loop. Great collaboration doesn’t require more meetings. It requires better visibility and shared understanding. Get your communication architecture right, and everything else - forecasting, hiring, pricing, client delivery - gets easier. Clarity Scales. Misalignment Costs.

If your team is missing deadlines or you feel like you’re constantly putting out fires, it’s time to fix your systems. Scaling a business is tough, but without solid systems, it’s almost impossible.  This is a straightforward guide to developing systems that can help your team scale efficiently. First, document everything. Start by writing down every process and procedure in your business. Use tools like Notion or Confluence to create a comprehensive knowledge base. This makes sure everyone on your team has access to the information they need and keeps everyone on the same page. Next, use advanced project management tools. Platforms like Monday or ClickUp can be customized to fit your specific needs, keeping projects on track and your team coordinated. Connect these tools with your CRM systems to streamline workflows and keep communication smooth across departments. Automation is your friend. Identify tasks that are repetitive and can be automated. Use platforms like UiPath or Blue Prism to handle these tasks, freeing up your team to focus on higher-value activities. Clear communication is critical. Set up a unified strategy that includes both asynchronous and real-time tools. Use Slack for immediate communication and Loom for updates that can be watched at any time. Regular check-ins and clear communication reduce misunderstandings and keep everyone aligned. Creating a culture that is always improving. Regular retrospectives and feedback loops with frameworks like Kaizen or Six Sigma can significantly improve your processes. Encourage your team to provide feedback and suggest improvements. This boosts efficiency and encourages a sense of ownership and engagement among team members. Role definitions need to be crystal clear. Develop a competency matrix to define roles and responsibilities clearly. This helps identify skill gaps and create targeted training programs, making sure everyone knows their part and performs it effectively. Training and development should be a priority. Create a learning and development plan using platforms like LinkedIn Learning or Coursera. Encourage cross-functional training to build a team capable of adapting to new challenges. Data-driven decision-making is key. Regularly review KPIs and adjust strategies based on data insights to stay on the right path. Streamline your onboarding process. Develop a comprehensive program that includes interactive modules, mentorship, and milestone-based assessments. This way, new hires integrate smoothly and contribute effectively from day one. Finally, promote collaboration. Use platforms like Miro or MURAL for brainstorming and project planning sessions. You need an environment where ideas can be freely exchanged and innovation thrives. You don’t need to change everything overnight. Start with one or two key areas and build from there.