Team Collaboration Techniques

Just out in Harvard Business Review, summary of the Hybrid Experiment results and lessons on how to make hybrid succeed. Experiment: randomize 1600 graduate employees in marketing, finance, accounting and engineering at Trip.com into 5-days a week in office, or 3-days a week in office and 2-days a week WFH. Analyzed 2 years of data. Two key results A) Hybrid and fully-in-office showed no differences in productivity, performance review grade, promotion, learning or innovation. B) Hybrid had a higher satisfaction rate, and 35% lower attrition. Quit-rate reductions were largest for female employees. Four managerial lessons 1) Hybrid needs a strong performance management system so managers don’t need to hover over employees at their desks to check their progress. Trip.com had an extensive performance review process every six months. 2) Coordinate in-office days at the team or company level. Schedule clarity prevents the frustration of coming to an empty office only to participate in Zoom calls. Trip.com coordinated WFH on Wednesday and Friday. 3) Having leadership buy-in is critical (as with most management practices). Trip.com’s CEO and C-suite all support the hybrid policy. 4) A/B test new policies (as well as products) if possible. Often new policies turn out to be unexpectedly profitable. Trip.com made millions of dollars more profits from hybrid by cutting expensive turnover.

🌍 New Series: "Mind the Gap – PR & Communication Across Borders" Ever tried launching a PR campaign in another country and thought, “Wait… why did that land like a lead balloon?” You're not alone. As someone who's navigated international communication for a while, I’ve seen firsthand how cultural nuance can make—or break—a message. So I’m kicking off a new series exploring how PR and communication differ around the globe. 👉 First up: Germany vs. the USA U.S. Communication: Enthusiastic, emotional, and yes—peppered with exclamation marks!!! Storytelling is king. Personal anecdotes and a strong “why” lead the way. Positivity sells. Even problems get rebranded as “growth opportunities.” German Communication: Direct, precise, and suspicious of unnecessary fluff. Facts first. Then more facts. Then a few more, just to be safe. Understatement rules. If a German says something is “not bad,” it might be worthy of an award. Example: An American press release might open with: “We’re thrilled to announce our exciting new partnership that will revolutionize the industry!” A German version? “Company A and Company B have entered a partnership effective May 15. Objectives include market expansion and product development.” Both are correct. Neither is wrong. But the context is everything. Takeaway: If you're crafting messages across borders, remember—it’s not just about what you say, but how it’s heard. ✨ Stay tuned for more posts comparing global comms styles—from Japan’s silence-as-a-power-move to Brazil’s beautifully fluid approach to formality. Have you run into cultural communication quirks in your PR work? I’d love to hear them! Chris Prouty, tell us about your experience as a US PR pro, please. #PR #Communication #CrossCulturalCommunication #Germany #USA #GlobalMarketing #Storytelling #Localization #InternationalBusiness

Have you ever wondered how some organizations and leaders manage to conquer the constantly evolving world with ease, while others struggle to keep up? In the midst of the VUCA revolution - where Volatility, Uncertainty, Complexity, and Ambiguity reign – how can you transform challenges into triumphs and uncertainties into untapped potential? Brace yourself, because this new era not only tests our mettle but also opens the door to boundless opportunities for those daring enough to embrace change and ride the waves of innovation. Are you ready to seize the moment? Traditional strategic planning that focuses solely on predicting the future has become obsolete. What we need is a new approach that embraces uncertainty, actively seeks opportunities, and fosters agility. Here are some crucial points to consider: 1️⃣ Embrace the Unknown. In a VUCA world, the ability to embrace ambiguity is no longer a luxury but a necessity. By acknowledging and embracing the unknown, leaders can create an environment that encourages creative problem-solving, adaptability, and innovation. 2️⃣ Flexibility is Key. Instead of rigid long-term plans, develop a more adaptable framework that allows for strategic pivoting when needed. Prioritize agility over sticking to a predetermined roadmap and stay open to alternative paths and opportunities. 3️⃣ Collaboration is Non-Negotiable. In times of uncertainty, collective intelligence, and diverse perspectives become invaluable. Foster collaboration across departments and teams, leveraging the strengths and ideas of different individuals. The power of collaboration will help uncover innovative strategies that can propel your organization forward. 4️⃣ Continuous Learning. In a rapidly evolving world, leaders must prioritize continuous learning and encourage a growth mindset within their organizations. Invest in developing your own skills and those of your teams. Embrace new technologies, stay informed about industry trends, and remain adaptable in the face of change. The future of strategy lies in our ability to navigate the VUCA world with a sense of curiosity, agility, and collaboration. #Leadership #vuca #agileleadership #HumanResources ***************************** 👉 Follow Stuart Andrews for more leadership and practical insights on building high-performing teams. 👉 Ring the 🔔 for notifications.

This is how Anthropic decides what to build next—and it's brilliant. Instead of endless spec documents and roadmap debates, the Claude Code team has cracked the code on feature prioritization: prototype first, decide later. Here's their process (shared by Catherine Wu, Product Lead at Anthropic): Step 1: Idea → Prototype Got a feature idea? Skip the spec. Build a working prototype using Claude Code instead. Step 2: Internal Launch Ship that prototype to all Anthropic engineers immediately. No polish required—just functionality. Step 3: Watch & Listen Track usage religiously. Collect feedback actively. Let real behavior, not opinions, guide decisions. Step 4: Data-Driven Prioritization - High usage + positive feedback → roadmap priority - Low engagement or complaints → back to iteration This "prototype-first product shaping" flips traditional product development on its head. Instead of guessing what users want, they're measuring what users actually use. The beauty? They're dogfooding their own tool to build their own tool. The feedback loop is immediate, honest, and impossible to ignore. The takeaway: Your best product decisions come from real user behavior, not theoretical frameworks. Sometimes the fastest way to validate an idea isn't a survey or interview—it's a working prototype.

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.

This article in MIT Sloan Management Review on hybrid work by Nick Bloom, Prithwiraj Choudhury, and Brian Elliott confirms what we've been documenting for years: This isn't a location problem. It's a leadership capability gap. While too many executives still debate office attendance, their more forward-thinking, innovative competitors build the leadership AND operational capabilities that a high-performance flexible work model--not just "hybrid"--requires. The research and case studies that the article cites get critical points right: ✅ "To date, no peer-reviewed research shows a benefit to a rigid five-day office model." ✅ Synchrony's CEO focusing on measurable results over presence. ✅ Atlassian's teams creating working agreements. ✅ The reality that only 25% of managers of distributed teams get leadership training (and we wonder why they are reporting historically low levels of engagement and burnout!) But this alone doesn't close the capability gap. What I'm seeing in our work with organizations: 👉 Teams need more than permission to create norms. They need facilitation frameworks for making planning and coordination decisions within the context of broader organizational parameters that all levels of leadership have aligned behind. 👉 Managers need consistent protocols, tools and training to guide the conversations about how, when, and where their specific work gets done—not just implement generic policies. This includes defining: → How does work get prioritized and coordinated for your business? → When do teams need to be together in person, and not in person, to achieve specific outcomes? → In what spaces and places (in person and virtual) does different work happen most effectively given your constraints? The article does mention the importance of space redesign and technology but a high-performance flexible work model integrates technology capabilities, and workspace design into the defined parameters as one coordinated way of operating across places, spaces and time. This requires moving: ✅ From debating location to starting with the work and defining how, when and where that work happens best, and ✅ From treating flexibility as policy compliance to building it as strategic capability. The evidence is clear. The business case is proven. Organizations that build these operational and leadership capabilities have a competitive advantage and will outperform those still debating badge swipes. What's the biggest capability gap you're addressing to help your organization achieve high levels of sustainable performance working flexibly? #FutureOfWork #FlexibleWork #RTO #HybridWork #Leadership #WorkplaceStrategy #HighPerformanceFlexibility #ReimagineWork

Are you using Claude to autocomplete or to think in parallel with you? Many developers treat it like a faster tab key. The real power shows up when you use it as a second brain running alongside yours. Here’s what that looks like in practice. 1. Run Work in Parallel Spin up multiple sessions and worktrees so planning, refactoring, reviewing, and debugging happen simultaneously instead of sequentially. 2. Start Complex Tasks in Plan Mode Outline architecture and approach before writing code, so execution becomes clean and intentional instead of reactive. 3. Maintain a Living CLAUDE.md Document mistakes, patterns, and guardrails so Claude improves with your workflow and reduces repeated errors over time. 4. Turn Repetition into Skills Automate recurring tasks with reusable commands and structured prompts so you build once and reuse everywhere. 5. Delegate Debugging Provide logs, failing tests, or CI output and let Claude iterate toward solutions while you focus on higher-level thinking. 6. Challenge the Output Ask for edge cases, diff comparisons, cleaner abstractions, and alternative designs to push beyond “good enough.” 7. Optimize Your Environment Set up your terminal, tabs, and context structure so you reduce friction and maximize visibility while working. 8. Use Subagents for Heavy Lifting Offload complex or exploratory tasks to parallel agents so your main context stays clean and focused. 9. Query Data Directly Use Claude to interact with databases, metrics, and analytics tools so you reason about data instead of manually extracting it. 10. Turn It Into a Learning Engine Ask for diagrams, system explanations, and critique so every project improves your mental models. The difference is simple: Autocomplete makes you faster. Parallel thinking makes you better. The question is how you’re choosing to use it.

Engineering will never be the same again. For months, everyone talked about Vibe Coding. Now Vibe Engineering is becoming real. Last weekend, I decided to test something. Instead of opening CAD and clicking through sketches, I built a workflow where I simply described a component and let AI construct it for me. No manual modeling. No GUI-driven feature creation. Just a prompt. I wrote the technical specifications of a CAD part. Seconds later, the geometry appeared in Onshape by PTC, fully parametrized and built step by step. This wasn’t a demo from a big tech lab. It was my weekend project. And it made one thing very clear: We’re shifting from GUI-driven construction to prompt-driven construction. AI is becoming the mediator between engineer and CAD system. Core thesis: The future of CAD is not clicking features, it’s describing intent. Here’s the workflow I built: 1. I write a structured prompt with the technical specifications of the part. 2. Claude Code (embedded in an IDE, in my case Google's Antigravity) calls Claude's Opus 4.6. 3. Opus 4.6 generates parametrized Python code that constructs the part sequentially. 4. Claude Code executes that Python code. 5. The code activates an MCP server and sends REST API calls for every construction step. 6. Onshape by PTC builds the geometry automatically, feature by feature. Intent → code → API → geometry. The consequences are hard to ignore: • Massive acceleration of construction tasks • Near-instant design iterations • Lower barrier to entry for CAD tools • Engineers shift from “modeling operators” to “design architects” Yes, you still need engineering expertise. You still need to understand tolerances, constraints, manufacturability. But execution is no longer limited by tool fluency. The bottleneck is moving. From mouse skills to clarity of thought. From feature clicking to technical articulation. CAD is becoming democratized. If you can clearly formulate what should exist and give technically clean instructions, you can construct. Vibe Engineering isn’t hype. It’s already possible. The question is: Are we ready to train engineers for a world where describing intent matters more than mastering the interface? Vlad Larichev | Timmo Sturm | Dr. Pascalis Trentsios | Rick Bouter | Holger Wienecke

I just taught Claude to directly query my CRM. Complex workflows became single prompts: A month ago my network kept talking about something called Model Context Protocol (MCP). Initially abstract, I understood it simply as: MCP lets AI models directly access your existing tools and databases. Think of it like the invention of USB: → Before USB: Multiple incompatible ports → After USB: One universal connection → Before MCP: Custom data integrations → After MCP: Universal plug-and-play AI connectivity Then a week ago I got an email from my personal CRM provider Clay that they had support for MCP. Historically, CRMs have acted as passive databases, requiring manual interactions to deliver insights. Here is what I used to do when I wanted to know who within my network had changed roles recently: OLD PROCESS: → Log into Clay CRM, export contacts as CSV → Clean and format data in a spreadsheet → Copy-paste formatted data into Claude → Manually instruct Claude to analyze job changes → Copy Claude’s insights back to Clay → Update contact records individually → Manually set follow-up tasks for each contact NEW PROCESS: → Simply instruct Claude: “Identify contacts in my network who recently changed jobs, showing their old and new positions and when I last interacted with them.” → Claude directly accesses Clay via MCP → Finds contacts who’ve recently changed jobs → Instantly provides a detailed, actionable list The results aren't perfect, but they turned a previously tedious process into an effortless query. The technical setup took 5 minutes: → Generated a Clay API key → Connected through Clay’s Smithery page → Installed Node.js locally → Ran one terminal command → Restarted Claude, confirming integration MCP's power comes from three shifts: → From isolated silos to interconnected intelligence → From sequential tasks to seamless orchestration → From human middleware to direct and automated interactions While it is early days, I believe we are scratching the surface with what is possible. I'm now working with several of our portfolio companies to explore how we can do deeper AI integrations. In an age where everyone has access to similar AI tools, the real competitive advantage isn't the tool itself. It's how deeply you embed it into your workflows.