Communication Techniques For Virtual Teams

"Sorry for messaging." I see this phrase multiple times per day from Filipino team members. They are not apologizing for a mistake. They are apologizing for what they thought was a hassle they are bringing in. This is not about confidence. This is about culture. Filipino workplace communication emphasizes smooth relationships and deference to authority. The concept of "utang na loob" (debt of gratitude) runs deep. When someone helps you or employs you, maintaining that relationship through politeness becomes paramount. Foreign managers often misread this. They see frequent apologies and assume the person lacks confidence or feels anxious about their performance. That is not what is happening. Some examples I see constantly: "Sorry for the inconvenience" when asking a legitimate clarifying question. "Apologies for the delay" when the response came 2 hours later, not 2 days. Multiple apologies in a single message for what amounts to normal work communication. The challenge is this. Remote work requires directness. When someone hits a blocker, I need them to state it clearly and immediately. Not apologize three times before getting to the actual issue. This is what I think works: Model the behavior you want. When someone apologizes unnecessarily, respond with "No need to apologize. This is normal work communication." Reframe apologies into statements. If someone says "Sorry to bother you but I am blocked," teach them to say "I am blocked on X and need guidance on Y." Create explicit norms. Tell your team directly: "Asking questions is part of your job. You never need to apologize for doing your job." Acknowledge the cultural context. Explain that global business communication values directness and that this does not mean disrespect. The goal is not erasing cultural communication styles. The goal is helping your team understand that directness serves everyone better in remote work environments. Frequent apologies are not a performance issue. They are a cultural communication pattern that you can help reshape through clear expectations and consistent modeling.

A few years ago, I was in a high stakes meeting with colleagues from Japan. I presented my points confidently, thinking I was making a great impression. But as I scanned the room, I saw blank expressions. No nods. No engagement. Just silence. I panicked. Had I said something wrong? Was my idea unconvincing? After the meeting, one of my Japanese colleagues pulled me aside and said, “Sumit, we really want to understand you, but you speak too fast.” That was my light bulb moment. For years, I assumed that mastering English and business communication was enough to build strong global relationships. But the real challenge wasn’t just the language - it was the rate of speech! Most of us don’t realize that speaking speed varies drastically across cultures. Here’s an eye-opener: ·      In India, we typically speak at 120–150 words per minute. ·      The global standard for clear communication is around 60–80 words per minute. ·      In Japan, where English is not the first language, this rate drops even further. So, what happens when we, as fast speakers, communicate with someone who is used to a much slower pace? Our words blur together. The listener struggles to process. And instead of making an impact, we create confusion. We often assume that if people don’t understand us, we need to repeat ourselves. But the truth is, we don’t need to repeat - we need to slow down, simplify, and pause. If you work in a multicultural environment, here are three things that can dramatically improve your communication: a.   Control your pace: Consciously slow down when speaking to an international audience. What feels “normal” to you might be too fast for them. b.   Use simple language: Smaller sentences. Easier words (vocabulary). c.    Pause & check for understanding: Don’t assume silence means agreement. Ask, “Does that make sense?” or “Would you like me to clarify anything?” I’ve seen professionals struggle in global roles - not because they lack expertise, but because they fail to adjust their communication style to their audience. I’ve also seen leaders who thrive across cultures, simply because they master the art of respectful, clear, and paced communication. If you want to succeed in a global workplace, rate of speech is not just a skill - it’s a strategy. Have you ever faced challenges due to differences in speaking speed? Let’s discuss. #GlobalCommunication #CrossCulturalLeadership #EffectiveCommunication #SoftSkills #CareerGrowth #WorkplaceSuccess #HR

𝗣𝗥𝗢𝗙𝗜𝗡𝗘𝗧 𝗶𝘀 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 “𝗘𝘁𝗵𝗲𝗿𝗻𝗲𝘁 𝗶𝗻 𝗢𝗧”. It is one of the most widely used Industrial Ethernet protocols in automation — connecting PLCs, IO devices, drives, HMIs, and engineering systems. But one thing many people miss: PROFINET communication is not all the same. It mainly works through 3 communication channels: 1️⃣ NRT — Non Real Time Used for standard TCP/IP-based communication. Typical use cases: • Configuration • Diagnostics • Parameterization • Engineering access Timing: usually less time-critical, often around <100 ms. 2️⃣ RT — Real Time Used for cyclic IO communication between controller and field devices. Typical use cases: • PLC to remote IO • Standard automation control • Fast process data exchange Timing: commonly 1–10 ms, depending on controller, devices, and network design. 3️⃣ IRT — Isochronous Real Time Used when deterministic and synchronized communication is required. Typical use cases: • Motion control • Servo drives • High-speed synchronized machines Timing: typically <1 ms, with very low jitter in properly designed systems. 𝗪𝗵𝘆 𝘁𝗵𝗶𝘀 𝗺𝗮𝘁𝘁𝗲𝗿𝘀 𝗳𝗼𝗿 𝗢𝗧 𝘀𝗲𝗰𝘂𝗿𝗶𝘁𝘆 A PROFINET network is not just “another VLAN”. It carries engineering traffic, discovery traffic, diagnostics, cyclic IO, and sometimes highly deterministic motion-control traffic. So when we secure PROFINET environments, we need to think beyond basic firewall rules. Focus on: • Engineering workstation access • Device discovery and configuration paths • Switch and topology visibility • PLC-to-IO communication flows • Segmentation using zones and conduits • Change control for device names, IPs, and topology • Monitoring for abnormal discovery, scanning, or unauthorized engineering activity The key point: In OT, protocol understanding is security understanding. You cannot properly defend what you only know at the IP-and-port level. PROFINET needs visibility, context, and control — not assumptions. #PROFINET #OTSecurity #ICSSecurity #IndustrialCybersecurity #IEC62443 #AutomationSecurity #PLC #SCADA #CyberSecurity #OT

Across many facilitated discussions, one pattern keeps showing up: Questions are too vague Example: Aligning on priorities A common question sounds like: Example: "How do people feel about this direction in general?" A better one is already directional: Example: "What feels most important to resolve before we move on?" Sometimes the room is taking something for granted, with Socratic Questioning, you probe what that is: → "This was already our priority last quarter and it didn't happen. What makes us think this time will be different?" With the ORID Method, you'd move through four levels: → Objective: "What did we commit to last time?" → Reflective: "What was the collective mood?" → Interpretive: "What have we learned from last time?" → Decisional: "If we could only do three things differently, which three?" One thing I've learned: don't skip the Reflective step. If people jump from facts to decisions, the unspoken reactions come back later. With Chunking Questions, you'd shift altitude: → Up: "How do these connect to company direction?" → Down: "What would the first two weeks look like?" → Sideways: "What would our biggest client say?" Same conversation, three lenses. You don't need to be the most talkative person in the room. In fact, please don't. Be the one who asks the question that saves time. These are from the Facilitation Guide at Facilitator School — link in my profile.

Excellent tips here illustrating how a subtle change in tone can have a massive influence upon how your message is received. 1) Acknowledge Delays with Gratitude "Sorry for the late reply…" "Thank you for your patience." 2) Respond Thoughtfully, Not Reactively "This is wrong." "I see your point. Have you considered [trying alternative]?" "Thank you for sharing this—I appreciate your insights." 3) Use Subject Lines That Get to the Point "Update" "Project X: Status Update & Next Steps" 4) Set the Tone with Your First Line "Hey, quick question…" "Hi [Name], I appreciate you. I wanted to ask about…" 5) Show Appreciation, Not Acknowledgment "Noted." "Thank you for sharing this—I appreciate your insights." 6) Frame Feedback Positively "This isn’t good enough." "This is a great start. Let’s refine [specific area] further." 7) Lead with Confidence "Maybe you could take a look…" "We need [specific task] completed by [specific date]." 8) Clarify Priorities Instead of Overloading "We need to do this ASAP!" "Let’s prioritize [specific task] first to meet our deadline." 9) Make Requests Easy to Process "Can you take a look at this?" "Can you review this and share your feedback by [date]?" 10) Be Clear About Next Steps "Let’s figure it out later." "Next steps: I’ll handle X, and you confirm Y by [deadline]." 11) Follow Up with Purpose, Not Pressure "Just checking in again!" "I wanted to follow up on this. Do you need any additional details from me?" 12) Avoid Passive-Aggressive Language "As I mentioned before…" "Just bringing this back in case it got missed."

Do you work remotely some or all of the time? Then you're probably not doing this well enough 👇 ✨ Being visible ✨ Learning how to be visible is one of the most valuable skills for people working in distributed teams, whether that's fully remotely or hybrid. I'm not talking about being physically visible. I mean making your work and your ability visible no matter where you're working from. It matters because: 🤝 Trust is built on evidence, not assumptions. In an office, effort is visible through presence. Online, absence of visibility can be mistaken for absence of effort. 🏆 Opportunities flow to the visible. Research shows people who are top-of-mind are more likely to be tapped for exciting projects, mentorship, and promotions. In a distributed team, surfacing your work isn’t showing off, it’s levelling the playing field. 👻 Invisibility can lead to isolation. Checking in, contributing in Slack, or speaking up in virtual meetings reminds others (and yourself) that you’re part of a shared endeavour, and want to progress. 🔍 Distributed teams need transparency across the board: narrating progress, celebrating wins, and acknowledging effort, so that no one’s work gets lost in the digital noise. So, how can you do this? Here are a few suggestions I have based on leading a remote-first team for the past five years: 🎯 Hit target? Share it when you have and as you're working towards it. 🙌 Someone senior asked you to do something? Jump on it and share widely. 🙋♀️ A volunteer needed for something small? Offer, it'll be remembered. 📣 Working on a big project? Update as you go and don't let it disappear. 😞 Something didn't go as planned? Share why, and what needs to change. 🥇 Manage a team? Update on their wins too. Managers can make their teams visible too. For many distributed teams, Slack and instant messaging services are offices, and we need to learn how to adapt to these new ways of working. It's not about creating a new sense of presenteeism, it's about creating a working environment that is efficient, effective, and fairer for all. What do you think about the concept of being visible online? #DistributedTeams #Culture

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?

Bad news is like fish. The longer it sits, the worse the whole situation smells. The Dilemma: A high-stakes launch is on the roadmap. Your team has brilliantly de-risked the plan, securing the most critical milestone ahead of schedule. Rock-solid work. But... they also know the full scope won't make the original date. And leadership? They haven't been told yet. The temptation to stay silent is powerful. The logic is seductive: "Let's not raise a flag until we have the perfect solution," or "Let's wait for a 'better time' to deliver this news." Here’s the counterintuitive truth: Waiting is the riskiest move you can make. Transparency without all the answers isn't weakness; it's a strategic advantage. A Better Way: Proactive Transparency Escalation isn't failure; it's a tool for alignment and trust-building. You don't need a perfect solution. You just need to own the narrative. My playbook for this conversation: 💪 Lead with the Win: Start with the good news. "We've secured the most impactful part of the launch and will deliver it early." 💪 State the Reality, Simply: Be direct. "This smart pivot means the subsequent phases will be delayed." 💪 Show Proactivity: Demonstrate control. "We are actively re-planning the remaining milestones." 💪 Own the Next Step: Provide certainty on communication. "We will share a full, revised plan with you by next week." When you do this, you're no longer delivering "bad news." You're delivering a reality-checked, responsibly managed plan. You're treating your leaders like partners. Surprising your leadership is a risk you can't afford. Building their trust is an asset you can't put a price on. Don't wait until the house is on fire. Be the leader who points to the smoke and says, "I've got this, and here's the plan." – 👉 Follow me, Rony Rozen, for more real-world insights on tech leadership. 

Sharing an approach I’ll be using to kick off the facilitation of an HSE Leaders Forum tomorrow that I hope others might find valuable. Instead of starting with the usual introductions (name, job role etc), I want to focus on the reason we are there: discussing innovative ways to solve the challenges participants are facing in their workplaces or industries. Each participant will introduce themselves by sharing a challenge framed as a "How Might We?" (HMW) statement. This simple method encourages participants to: 1️⃣ Clarify the Challenge: Turning a health and safety challenge into an opportunity helps focus the conversation on possibility. 2️⃣ Spark Collaboration: Open-ended, opportunity-focused challenges invite diverse perspectives and ideas. 3️⃣ Create Immediate Value: Sharing key challenges helps everyone see where they can contribute and connect meaningfully - on the things that matter. "How might we better communicate critical risk management expectations with subcontractors?" "How might we reduce working at height activities in our business?" "How might we assure critical risk controls in real-time?" I’ve found this approach aligns discussions with what really matters, and leaves participants with actionable insights. If you’re planning a collaborative session, this could be a great way to shift from introductions to impactful conversations right from the start. Feel free to adapt this for your own forums or workshops; I’d love to hear how it works for you and if you have any other facilitation tips. #SafetyTech #SafetyInnovation #Facilitation #Learning

The quickest way to lose a decision in a global team is to speak the right language in the wrong culture. I’ve sat in too many “same page” meetings where everyone walked out convinced the other side didn’t get it. After 13 years in Europe and now in the US, I see the pattern repeat in global FMCG. With the UK, tone carries as much weight as content. “Interesting” often means “not convinced.” “Let’s park this” usually means “no.” Humor is a tool to lower the temperature before a tough point lands. You win the room by bringing a balanced case, letting stakeholders react, then following up quietly with crisp next steps. Corridor consensus matters as much as the meeting itself. With France, ideas come first. Leaders want a coherent narrative, the strategic why, and the principles that will hold under pressure. Debate is respect, not resistance. If the story is strong, the resources follow. Bring options framed as choices with consequences, show the thinking, and expect smart pushback. If you are allergic to intellectual challenge, you will misread the room. With Switzerland, preparation is the love language. A clear pre-read sent on time. Risks and mitigations listed. Owners named. If the governance is tight, speed is possible. Pilots are welcomed when guardrails are explicit, service levels protected, and the impact on partners is thought through. Precision builds trust, and trust unlocks tempo. The American instinct is to move. Ship a pilot, learn in market, fix in public. That energy is valuable, but it lands better when paired with the UK’s stakeholder rhythm, France’s clarity of thought, and Switzerland’s discipline on process. What I coach cross-border teams to do: agree the “decision dialect” before the meeting, are we greenlighting a concept or a finished plan. Share a one-page pre-read 48 hours ahead, problem, options, risks, owner, go or no go. Translate feedback into action, “interesting” equals add proof, “we need alignment” equals map the stakeholders, “gut feel” equals bring a data cut. Split speed from safety, pilot with tight guardrails while the bigger build earns its evidence. Mirror first, then lead. Speak the local operating code well enough to earn trust. Bring your own strengths once the room believes you understand theirs. Curious where this shows up for you right now, which habit would fix half your misfires this quarter? #FMCG #CPG #Leadership #GlobalTeams #Communication #ExecutiveSearch #ConsumerGoods #UK #France #Switzerland #US #Culture #StakeholderManagement