Collaboration Tools Tips

Remote work isn't broken. The rulebook is: Most companies wrote one set of remote rules and handed it to everyone. But managers and employees need to run it differently: 1. Set core hours ↳Manager: Pick 3-4 hours the whole team is online, then stop scheduling meetings outside that window ↳Employee: Block those hours on your calendar and protect the rest of your day for deep work 2. Overcommunicate context ↳Manager: Explain the why behind a task, not just the what, so no one has to guess ↳Employee: Add a quick note to every update so your manager never has to ask "where are we" 3. Ask before you assume ↳Manager: If a message sits unanswered for an hour, check in before you jump to conclusions ↳Employee: Ask before you guess, it saves both of you a redo 4. Default to written ↳Manager: Put decisions in a doc or channel, not just a call, so nothing gets lost ↳Employee: Recap verbal conversations in writing so there's a record everyone can check 5. Trust the work ↳Manager: Judge output, not hours online, and say that out loud to the team ↳Employee: Share progress often so trust builds without anyone having to ask for it 6. Show up on camera ↳Manager: Make camera use a norm for some meetings ↳Employee: Turn your camera on for priority calls 7. Build in real connection ↳Manager: Schedule time that isn't about work, even 15 minutes, so the team stays a team ↳Employee: Show up to that time, skipping it quietly adds up to feeling cut off 8. Document everything ↳Manager: Keep one source of truth for decisions so new hires can catch up fast ↳Employee: Write down what you did and why before you log off each day 9. Ask for feedback ↳Manager: Check in at least monthly on what's working and what feels isolating ↳Employee: Speak up early if something feels off, don't wait for the review 10. Guard the boundary ↳Manager: Don't message after hours unless it's urgent, model the behavior you want ↳Employee: Set a hard stop time and actually log off when you hit it A rulebook only works if both sides read it the same way.  Most don't. Which of these feels hardest to actually follow, as a manager or as an employee? --- ♻️ Repost to help remote teams work better together. And follow me George Stern for more remote work content.

I've facilitated 500+ workshops. These 5 closing techniques are the only ones that stick. Most facilitators spend hours designing the opening and the activities. Then the last 10 minutes arrive and they panic. → "Let's share a final thought." → "Any last reflections?" → "Thanks everyone, great session!" The closing is where behaviour change gets locked in or evaporates. Most facilitators treat it like an afterthought. Here are the 5 that actually work: 1. The One Commitment Round Every participant states one specific thing they'll do differently this week. Out loud. To the room. → Not: "I'll communicate better." → Instead: "I'll start every Monday standup asking my team what's blocking them before giving updates." Vague commitments die on the drive home. Specific ones survive. Public commitment creates social accountability. Say it out loud and it costs something to not follow through. 2. The Accountability Partner Every participant pairs up. They exchange commitments. They set a check-in within 14 days. Calendar invite sent before they leave. → Not: "Let's all keep each other accountable." → Instead: "You and your partner have a 15-minute call on March 31st. One question: did you do it?" Accountability without a name and a date is just a wish. 3. The Letter to Yourself Each participant writes a short message to their future self. What they committed to. Why it matters. The facilitator collects them and emails them back in 2 weeks. A delayed mirror. When the workshop energy has faded, you get a message from yourself reminding you what you promised when you were most motivated. 4. The Team Contract The group co-creates 3-5 agreements about how they'll work together. One page. Everyone signs. Photographed and shared in the team channel before they leave. → Not: "Let's agree to be more open." → Instead: "If you disagree with a decision, raise it in the meeting, not after. If you don't speak up, you've agreed." Invisible norms become a visible artefact. When someone breaks the agreement, anyone can point to it. The contract does the confrontation so individuals don't have to. 5. The Pre-Mortem Close Instead of "how was the session?" ask: "It's 30 days from now and nothing has changed. Why?" Participants write down every reason the commitments might fail. Then for each, one thing that would prevent it. → "It'll fail because I'll get pulled into daily fires." → Prevention: "I'll block 30 minutes every Friday to review my commitment." Instead of hoping for the best, you design against failure before it happens. The pattern across all 5? Every closing that sticks has three things: → A specific commitment, not a feeling → A named person responsible for follow-up → A date on the calendar Without all three, it was a nice ending to a nice day. Nothing more. ___ Save this for later (three dots, top right). Share with friends → ♻️ Repost. Get consultant-grade workshops every Sat → https://lnkd.in/eSfeUapJ

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.

Before I codified this, one loud voice could hijack my whole session. Now? I handle resistance without losing the room (or my authority) I used to let “just one comment” slide. Until it derailed the agenda. What started as a “quick comment” turned into a 40-minute detour. I watched the energy drain from the group. And from the client’s face. I was bringing my personal baggage Back then, I believed being “tough” made you less likeable as a facilitator. But I wasn’t being kind, I was avoiding discomfort. And that made me unclear. And unclear loses the room. Here’s my 2M framework, I wish I had years ago to protect focus and relationships. 𝗠𝗶𝘁𝗶𝗴𝗮𝘁𝗲 (set yourself up for success): • Pre-session comms to set expectations • Co-create working agreements at the start • Introduce a ‘Parking lot’ early • Ask for permission to re-direct when needed 𝗠𝗮𝗻𝗮𝗴𝗲 (when things go off-track): • Notice and name the disruption, neutrally • Refer back to the group’s agreements • Add off-topic ideas to the Parking lot • Check: “Is this moving us closer to our outcome?” This approach earned me a long-term client who brings me back to facilitate strategy days with their global brand leaders. Why? Because I kept big personalities on track without making anyone wrong. And even had execs thank me for shutting them down. Turns out, clarity earns trust. Fast. And the tougher I’ve been as a facilitator, the more I’ve been respected. ♻️ Share if you’ve ever had to wrangle a room 👇 What’s your go-to move when a session goes off the rails?

I have made and saved a lot of money using remote teams across all of my companies.  Here’s how you do it: Almost every business could use at least some remote talent. It’s a great way to access a broader talent pool than your local area. You can also lower overhead costs — less office space, lower bills, and even hire talent from other countries. So how do you get the most out of a team that you don’t see face to face? Step 1: Define your objectives and needs Nail down your biggest reason for building a remote team. Broaden your hiring pool? More flexibility? Lower costs? Your main goal guides your future decisions. Then, assess which of your positions are suitable for remote or hybrid work. — Step 2: Develop a remote work policy A solid policy sets the tone and expectations for your team. Try to answer all questions ahead of time. Clarify Scope and Purpose: •  Who is eligible to work remotely? • For hybrid, how many days? • Is there a distance requirement? Set Communication Standards: • When should people be online and available? • What communication tools should they use? Security Protocols: Password manager?  VPN? Are you providing work equipment or expecting BYOD? — Step 3: Update your hiring process Build remote-specific job descriptions: Highlight skills like self-discipline and communication. Use diverse recruitment channels: Remote-specific job boards and communities. Tailor interviews for remote readiness: Include video calls and assess their home office setup. — Step 4: Find the right tools & technology Equip your team with tools that support collaboration and productivity. You’ll probably need: • An async communication hub (like Slack) • A video call platform (Google Meet) • A project management tool (Asana or Trello) • Hardware/software support Provide equipment or offer a stipend. — Step 5: Establish clear communication guidelines Effective communication is the backbone of remote work. Do you need people to: • Set online statuses? • Post daily updates? • Follow a response time rule? • When do you need people available for video calls? Make sure to set regular meetings and check-ins. Weekly stand-ups and monthly all-hands help keep everyone aligned. — Step 6: Build a strong team culture Strong remote teams thrive on culture and connection. Start with thorough virtual onboarding. Set up meet and greets and mentoring sessions. Add regular team activities: • Virtual coffee breaks • Game time • Casual Slack channels Celebrate everything: • Individual and team wins • Holidays • Company milestones — Step 7: Keep tabs on performance Address concerns head-on with clear goals and regular feedback. Set SMART goals: Specific, Measurable, Achievable, Relevant, and Time-bound. Schedule quarterly reviews. Focus on outcomes — not hours worked. — If you’re interested in remote staff for your teams. Comment below or message me and I’ll get you connected.

Most failed projects never lacked a plan — they lacked agreement. A project charter isn’t paperwork. It’s the invisible contract that aligns every stakeholder before chaos starts. It defines: - Why this project exists (purpose) - Who owns what (accountability) - How success will be measured (outcomes) I’ve seen teams skip this step because “we need to start fast. ” They end up starting twice — once to build, once to fix. But too often, teams skip this step because “ we need to start fast. ” The truth? They end up starting twice — once to build, once to fix. If you want to lead with clarity, start with alignment. Your first deliverable isn’t the Gantt chart — it’s shared understanding. Here are 3 ways to make your project charter actually work: ✅ 1. Make it outcome-driven, not output-driven. Most charters focus on what will be delivered — timelines, budgets, tasks. Shift to why it matters. Define the problem it solves and what success looks like in behavior or adoption. - Instead of “Deliver new CRM,” say “Increase user adoption by 25% within 3 months.” ✅ 2. Co-create, don’t delegate. A charter written for stakeholders dies fast. A charter written with stakeholders lives. Run a short alignment session before writing — get your sponsor, users, and leads to co-own the “why” and the “how.” - The goal: fewer sign-offs, more buy-in. ✅ 3. Keep it human-readable. If people can’t skim it, they won’t follow it. Use one page, plain language, and visuals (timeline, ownership chart, success metrics). A charter is not a report — it’s a roadmap for humans. - Ask yourself: “Could my team summarize this in 30 seconds?” If not, simplify. Because in the end — a good charter isn’t about process. It’s about clarity, ownership, and trust. 📈 Start with alignment. Delivery gets easier from there. #ProjectManagement #WGU #PMP #Leadership #ProjectCharter #Delivery

𝗛𝗼𝘄 𝘁𝗼 𝗕𝗿𝗲𝗮𝗸 𝗗𝗼𝘄𝗻 𝗦𝗶𝗹𝗼𝘀 𝗶𝗻 𝗠𝗲𝗱𝗧𝗲𝗰𝗵 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: (𝗖𝗿𝗲𝗮𝘁𝗶𝗻𝗴 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗵𝗮𝗿𝗺𝗼𝗻𝘆 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝘁𝗵𝗲 𝗵𝗲𝗮𝗱𝗮𝗰𝗵𝗲𝘀) Ever notice how Quality, R&D, Regulatory and Marketing teams seem to speak completely different languages? This disconnect isn't just frustrating, it's costing your medical device company time, money, and potentially regulatory approval In my personal experience, I've seen how departmental friction can derail even the most promising innovations 𝗧𝗵𝗲 𝗥𝗲𝗮𝗹 𝗖𝗼𝘀𝘁 𝗼𝗳 𝗦𝗶𝗹𝗼𝘀 👉 Delayed submissions and market entry 👉 Regulatory surprises late in development 👉 Documentation rework and compliance gaps 👉 Increased development costs 👉 Team frustration and burnout Here's how to create seamless collaboration across your MedTech organization: 𝗦𝘁𝗲𝗽 𝟭: 𝗘𝘀𝘁𝗮𝗯𝗹𝗶𝘀𝗵 𝗖𝗿𝗼𝘀𝘀-𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗚𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲 Create a development council with representatives from Quality, Regulatory, R&D, Manufacturing, Marketing and Clinical. Meet bi-weekly with a structured agenda (top tip keep the minutes to use towards management reviews). 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: A Class II device manufacturer implemented this model and reduced their development timeline by 30%, if not more, by identifying regulatory concerns during concept phase rather than pre-submission. 𝗦𝘁𝗲𝗽 𝟮: 𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁 𝗦𝘁𝗮𝗴𝗲-𝗚𝗮𝘁𝗲 𝗥𝗲𝘃𝗶𝗲𝘄𝘀 𝘄𝗶𝘁𝗵 𝗔𝗹𝗹 𝗦𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿𝘀 Don't move to the next development phase without formal sign-off from every department. This prevents costly backtracking 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: During a stage-gate review (Design Review), a clinical specialist identified that the intended claims presented by the regulatory team would require further clinical data. By catching this early, the company adjusted their development plan rather than facing a surprise 6-month+ delay come submission time 𝗦𝘁𝗲𝗽 𝟯: 𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗦𝗵𝗮𝗿𝗲𝗱 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗟𝗮𝗻𝗴𝘂𝗮𝗴𝗲 Develop a glossary of terms that bridges departmental jargon. This prevents miscommunication that leads to rework. 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: One client I worked with created a “MedTech Translation Guide” with input from each department. Not only did it reduce confusion, but it also built mutual respect engineers finally understood what the regulatory team meant by “intended use” and marketers stopped using terms that could trigger a knock on the door by Competent Authorities 𝗧𝗵𝗲 𝗕𝗼𝘁𝘁𝗼𝗺 𝗟𝗶𝗻𝗲? When this is done right, it accelerates development, strengthens compliance, and builds a more engaged team ✅ Faster to market ✅ Fewer compliance surprises ✅ Less internal friction If you're building your next-gen device and struggling with internal disconnects, it’s time to rethink how your teams work 𝘵𝘰𝘨𝘦𝘵𝘩𝘦𝘳 💬 I'd love to hear: How does your team keep cross-functional collaboration on track? #MedTech  #MedicalDevice #ProductDevelopment

Having remote teams across continents bring both opportunities and challenges. How do you get it right? Working with global teams, especially when spread across drastically different time zones, is a reality many product managers face today. It can stretch your collaboration skills and test your patience. But, done right, it can be a powerful way to blend diverse talents and perspectives. Here's how to make it work: 1. Creating Overlaps: Aim for at least an hour or two of overlapping work hours. India's time difference with the US means you'll need to adjust schedules for essential face-to-face time. Some teams in India choose to shift their hours later. This is crucial for addressing any pressing questions. 2. Context is Key: Have regular kickoff meetings and deep dives where all team members can understand the big picture—the customer needs, project goals, and product vision. This enables your engineers to make informed decisions even if you're not available to clarify on-the-spot. 3. Document, Document, Document: While Agile champions minimal documentation, it's unavoidable when teams can't meet frequently. Keep clear records of decisions, questions answered, and the day’s progress. This provides continuity and reduces paralysis when immediate answers aren't possible. 4. Strategic Visits and Camaraderie: If possible, send team members to different locations periodically. This builds relationships and trust, which are invaluable when working remotely. If travel isn't possible, consistent video calls and personal updates help. 5. Local Leadership: Consider having local engineering leads in the same region as your development team. This can bridge gaps and streamline communication, ensuring that strategic and operational alignment occurs naturally. Ultimately, while remote setups have their hurdles, they are not impossible to overcome. With thoughtful planning and open communication, your team can turn these challenges into strengths, fostering innovation and resilience that transcends borders. 🌎

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

The 'Out of Sight, Out of Mind' Trap: How to Conquer the Distance Google is a global company with offices all over the world, and while this diversity is a strength, it also presents unique challenges for communication and collaboration. Especially when your key stakeholders and decision-makers are continents away! Those hallway conversations, spontaneous coffee chats, and quick desk drop-bys that teams at HQ take for granted? Yeah, those aren't happening when you're separated by oceans and time zones. And that can lead to a disconnect. Your team's amazing work might get overlooked, your challenges might go unnoticed, and your stakeholders might feel out of the loop. But fear not, fellow remote leads! Here are a few strategies I've learned along the way: ‣ Tailor your communication approach: Every leader has their preferred communication style. Some love detailed reports, others prefer concise bullet points, and some just want the TL;DR. It's your job to adapt and deliver information in the way they'll best receive it. ‣ Embrace Radical Transparency: The worst thing that can happen is your leadership feeling blindsided by a problem or a missed deadline. Over-communicate! Share updates regularly, highlight both wins and challenges, and don't be afraid to ask for help when needed. ‣ Educate Your Leads: Help them understand the unique challenges of leading a remote team in a different location. Explain why you might need more proactive communication or different approaches to stay connected and aligned. ‣ Build Relationships Beyond Email: Travel when possible. Occasional visits to the main office can be invaluable for building relationships and understanding the nuances of the company culture. ‣ Celebrate Wins: Make sure your stakeholders are aware of your team's accomplishments, both big and small. This reinforces the value of your team and keeps them top-of-mind. ‣ Iterate and Improve: What works for one lead might not work for another. Experiment with different communication styles, ask for feedback, and continuously refine your approach. Leading a local team in a remote site requires extra effort and intention. By mastering the art of communication and building strong relationships with your stakeholders, you can ensure your team's success, no matter where you are in the world! What are your favorite tips for leading remote teams across continents? Share your insights in the comments! 👇 #RemoteLeadership #Communication #TechLeadership #lifeAtGoogle