Establishing Communication Norms In Teams

As organizations strive for excellence, the challenge often lies not in making improvements, but in maintaining them. Once we achieve a certain level of quality or efficiency, how do we ensure these standards continue to be met, or even surpassed, over time? This is where the role of management systems needs to be understood. A robust management system is crucial for sustaining improvements. It's not just about the changes we implement, but how we embed them into our daily, weekly, and monthly routines. Annual reviews play a vital role, but the essence of sustaining improvements lies in the regular, smaller checks – those daily and weekly habits that keep us on track. 👉 Daily Gemba walks and check-ins or "huddles" can help teams stay aligned with their goals and quickly address any deviations. Adopting 2 Second Lean can help drive small everyday incremental improvements. (See previous posts on these topics and I also recommend Paul Akers book "2 Second Lean"). 👉 Weekly team meetings and cross-departmental process review meetings are key to increasing and sustaining improvements. These are most effective when they include a focus on not just planning but also performance metrics, reviews and lessons learned. Don't forget about 1:1's either- it's important to have regular individual check-ins. 👉 Monthly and bi-monthly evaluations provide opportunity for a comprehensive review of processes and a look at longer-term trends and effects. Regular Kaizen events ensure everyone is involved in CI discussions, process mapping, root- cause analysis and decision-making. In addition to this, it's important to offer ongoing training in your chosen quality management methodology. 👉 Annual reviews and audits are crucial for a deep dive into the year's performance, reassessing objectives, and setting new goals. I also recommend including an organizational health check at least once a year, and including succession planning in the strategic focus. Every organization has responsibility for setting up management systems. They are structured activities that everyone must be aware of and involved in. Each organization's management systems may look different, and that's ok! It is evident that leaders plays a pivotal role in this process. Managers and leaders need to be vigilant, proactive, and adaptable. They are responsible for fostering a culture of continuous improvement, where feedback is encouraged and acted upon. Maintaining high standards is a dynamic process. It requires a combination of robust management systems, consistent practices, strong leadership, and the integration of methodologies like Lean and Agile. By focusing on these elements, organizations can not only achieve excellence but sustain it in the long run. #continuousimprovement #lean #leanmanagement #agilemethodologies #managementsystem #leadership #management

When Teams Grow, Design Their Experience: An LXD Perspective. Rapid growth is often celebrated as a marker of success. Teams expand, business objectives increase, and new responsibilities are introduced. Yet growth often comes faster than the systems and processes that support it , leaving teams misaligned, overwhelmed, and disengaged. A sales team I worked with had grown from 10 to 25 members over six months. While expansion brought exciting opportunities , it also introduced a host of challenges: 📝 Increased administrative work and reporting requirements 📅 More frequent meetings for alignment across an expanded team 🎯 Higher performance expectations and KPIs ❓ Ambiguity in roles and responsibilities as new members joined Despite their enthusiasm and capability, the team began reporting stress, confusion, and a sense of constant pressure. From a Learning Experience Design perspective, processes that worked for a smaller team often do not scale without adjustment. The team’s capacity their available time, attention, and cognitive bandwidth did not expand in line with expectations. Role ambiguity and overlapping responsibilities created duplication of effort and accountability gaps. Here came an opportunity to redesign the team’s capacity and learning ecosystem rather than simply redistribute tasks. Key interventions included: 🔍 Conduct a Capacity Audit: Every task, meeting, and reporting requirement was analyzed to identify bottlenecks, duplication, and low-value activities. 📌 Prioritize Strategic Work: Non-essential tasks were delegated or removed. Core responsibilities aligned with business impact were clearly highlighted. ⚙️ Redesign Processes: Reporting templates were streamlined, recurring meetings reduced, and approvals standardized to reduce friction. 💡 Embed Reflection and Learning: Weekly “team retrospectives” were introduced, where team members shared wins, challenges, and lessons learned, enabling process improvement and knowledge transfer. 🧩 Clarify Roles and Responsibilities: Each team member’s tasks and ownership were mapped, eliminating overlap and increasing accountability. The results were striking. Performance stabilized as team members could focus on fewer, high-impact activities. Engagement increased 💪 because individuals felt their work mattered, and they had the space to contribute strategically rather than simply execute. Teams are more than output machines they are human systems. Rapid expansion can overwhelm these systems if we fail to consider capacity, clarity, and reflection. Designing growth with empathy and learning in mind ensures that teams remain motivated, skilled, and aligned. Ultimately, success comes not from doing more, but from doing better, together 🤝. #microlearning #learningeveryday #learningwithhiral #LearningExperienceDesign #EmployeeEngagement #Leadership #TeamDevelopment #ContinuousLearning #TeamCollaboration #LeadershipDevelopment

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

Building High-Performance Remote Engineering Teams is not just about video calls.... I’ve worked with teams across the UK, Europe, and the US, and one thing is clear: remote work isn’t inherently slower. But a lot of engineering teams fail because they try to run distributed teams like co-located ones. Here’s what really makes a remote engineering team high-performing: 1️⃣ Communication by Design, Not by Chance Async-first: Chat isn’t enough. Document decisions, architectural diagrams, and API contracts in a place everyone can access. Structured updates: Daily standups are optional; status tracking through PR reviews, automated CI pipelines, and project boards is mandatory. 2️⃣ Ownership & Clear Boundaries Each engineer owns services, APIs, or modules end-to-end. Service contracts are explicit. Teams don’t block each other because ownership is clear and dependencies are well-documented. 3️⃣ CI/CD Is Non-Negotiable Remote teams must trust that pushing code won’t break production. Automated testing, linting, and deployment pipelines reduce friction and async bottlenecks. Feature flags and incremental rollouts are your best friend. 4️⃣ Knowledge Visibility Remote teams fail when knowledge lives in heads. Maintain internal wikis, architecture maps, and runbooks. Code reviews aren’t just for QA—they’re the primary async learning tool. 5️⃣ Metrics That Actually Matter Velocity in story points? Fine. But measure deploy frequency, mean time to recovery, bug escape rate, and codebase health metrics. These metrics highlight systemic issues instead of punishing individuals. 6️⃣ Tech Stack Choices Matter Prefer tools that support async collaboration: GitOps, Slack with integrated threads, Jira/Trello boards, distributed logging, observability dashboards. Avoid systems that require constant synchronous attention or centralised knowledge bottlenecks. 7️⃣ Culture Is Explicit, Not Implicit High-performing remote teams share principles in writing: “We merge only green builds,” “We document before we ship,” “We pair when ownership overlaps.” Bottom line: Remote engineering success is built on process, ownership, tooling, and visibility, not on heroic effort or long hours. If your team is still treating async work like a co-located office, you’re leaving productivity and sanity on the table.

Most leaders believe they communicate enough. Meetings are happening. Updates are shared. Reviews are scheduled. And still, things slip. Issues surface too late. Motivation fades quietly. Good people disengage without warning. That’s because most leadership conversations are mistimed. Annual reviews look backward. Quarterly check-ins skip what matters now. Weekly meetings track work, not humans. The strongest teams operate differently. They rely on intentional monthly conversations that focus on people, not just performance. Why monthly works: Over 30 days, a lot changes. • Priorities drift • Creativity gets buried by urgency • Minor friction turns into delay • Pressure builds without a signal • Progress goes unnoticed A monthly reset prevents all of that. Here’s how effective leaders structure those conversations: 1. Check in on the person first People open up when they feel seen, not evaluated. 2. Surface obstacles early Most problems are manageable before they compound. 3. Re-align on priorities Misunderstanding direction costs more than slow execution. 4. Call out what is working What gets recognized gets repeated. 5. Ask where support is needed High performers rarely volunteer this on their own. 6. Invite new thinking Those closest to the work spot opportunities leadership misses. 7. Reflect on challenges together Progress comes from learning, not just pushing harder. This isn’t about adding meetings. It’s about improving the quality of the conversations you already need. Timing matters. So do the questions. Monthly hits the balance: Frequent enough to maintain momentum. Spaced enough to see progress. Consistent enough to build trust. Your team sees things you don’t. They experience friction you never hear about. They often have answers before problems escalate. But only if you create the space. Stop assuming silence means alignment. Start asking questions that encourage honesty. Great teams are not built on flawless execution. They are built on consistent, meaningful dialogue. Make it monthly. Make it count. ♻️ If this was useful, share it with your network. Follow me for practical insights on building stronger teams faster.

💬 Most leaders think they’re having enough conversations with their teams. They’re not. Annual reviews catch issues too late. Quarterly check-ins miss critical moments. Weekly meetings focus on tasks—not people. The teams that perform and stay have leaders who ask the right questions every month. Because in just 30 days: • Priorities shift without clear communication • Innovation gets buried under busy work • Small blockers turn into major delays • Stress builds quietly • Wins get forgotten Monthly conversations change that dynamic. Here’s how to make them count 👇 1. Start with genuine wellbeing checks. Show your team you care about them as people, not just about their output. 2. Identify what’s blocking progress. Most obstacles are easy to solve—when they’re caught early. 3. Reconfirm priorities. Misalignment wastes more time than any other factor. 4. Recognize what’s working well. Reinforce success patterns to make them repeatable. 5. Ask where support is needed. Top performers often struggle to ask for help. 6. Create space for new ideas. Those closest to the work often see opportunities leaders miss. 7. Turn challenges into learning moments. Growth requires reflection, not just action. This isn’t about adding more meetings—it’s about having better conversations. Monthly is the sweet spot: ✅ Frequent enough to maintain momentum ✅ Spaced enough to see progress ✅ Consistent enough to build trust Your team has insights you need, challenges you don’t see, and solutions you haven’t considered— but they need you to create the space for those conversations. Stop assuming everything is fine because no one’s complaining. Start asking questions that invite real answers. The best teams aren’t built on perfect execution— they’re built on consistent, meaningful dialogue. #LeadershipDevelopment #PeopleFirst #TeamCulture #Communication #LeadershipMatters

Remote work isn't just about where you work—it's about how you work. You can be 10x more effective on a remote team if you master a few key habits: ✅ Over-communicate, but be concise Clarity matters more than frequency. Say what’s needed, and say it clearly. ✅ Align before you act Check for shared understanding before diving into big tasks. Nothing wastes time like misaligned assumptions. ✅ Make your work visible Use docs, updates, or async tools to show progress—even when no one’s asking. ✅ Respect time zones (and your own time) Be flexible, but not a doormat. Set boundaries and honor others’ schedules, too. ✅ Own the outcome, not just the task Remote teams thrive when people think beyond checklists and focus on impact. ✅ Build trust through reliability Be the teammate who always follows through. Remote or not, trust is everything. ✅ Don’t forget to be human Drop a gif. Ask how someone's weekend was. Show up with personality. Culture still matters—maybe more than ever. Remote work isn't an excuse to fade into the background. It’s your opportunity to shine without ever stepping into a meeting room. What’s helped you be more effective remotely? #RemoteWork #AsyncWork #TeamCulture #WorkFromAnywhere #Productivity #LeadershipTips

Remote teams don't fail because people don't communicate. They fail because they communicate badly. After years of working in remote software teams, I've learned this the hard way. Here are 8 lessons I wish I'd learned earlier. And yes, a few of these will annoy people. 1️⃣ Over-communicate, then assume it still wasn't enough. ↳ Silence creates friction. People fill gaps with the worst story 2️⃣ Jargon saves time for the writer, not the reader. ↳ If someone has to decode your message, you've already lost. 3️⃣ More messages !== better communication. ↳ Noise kills the signal. Be deliberate, not sloppy. 4️⃣ Writing clearly is real work. ↳ If it feels slow, you're doing it right. 5️⃣ Celebrate publicly. Critize privately. ↳ Create space for celebrations and share them. 6️⃣ Never assume shared context. ↳ If it lives in your head, it doesn't exist yet. 7️⃣ Say exactly what response you want. ↳ And when you want it by. Ambiguity is procrastination in disguise. 8️⃣ Distance isn't just geography. ↳ There's physical distance, operational distance, and emotional distance. Ignore any of them, and trust erodes. Most remote teams don't need more tools. They need higher standards for their communication. What else would you add? —— 💾 Save this for future reference. ♻ Repost to help others level up their communication skills.  ➕ Follow Petar Ivanov + turn on notifications.

🔄𝐒𝐩𝐫𝐢𝐧𝐭 𝐑𝐞𝐭𝐫𝐨𝐬𝐩𝐞𝐜𝐭𝐢𝐯𝐞𝐬 𝐚𝐫𝐞 𝐧𝐨𝐭 𝐣𝐮𝐬𝐭 𝐦𝐞𝐞𝐭𝐢𝐧𝐠𝐬—they’re the heartbeat of continuous improvement in Agile teams. Yet many teams struggle because retrospectives become repetitive, unfocused, or just a box-ticking exercise. To make them truly effective, focus on these key elements: ✅ 𝐒𝐞𝐭 𝐭𝐡𝐞 𝐒𝐭𝐚𝐠𝐞 – Create a safe space where everyone feels comfortable sharing. ✅ 𝐒𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞𝐝 𝐀𝐠𝐞𝐧𝐝𝐚 – Use formats like Start–Stop–Continue or Mad–Sad–Glad to keep discussions focused. ✅𝐄𝐧𝐜𝐨𝐮𝐫𝐚𝐠𝐞 𝐏𝐚𝐫𝐭𝐢𝐜𝐢𝐩𝐚𝐭𝐢𝐨𝐧 – Involve quieter voices and balance the conversation. ✅ 𝐀𝐜𝐭𝐢𝐨𝐧𝐚𝐛𝐥𝐞 𝐈𝐧𝐬𝐢𝐠𝐡𝐭𝐬 – Turn conversations into meaningful improvements. ✅ 𝐓𝐫𝐚𝐜𝐤 𝐏𝐚𝐬𝐭 𝐀𝐜𝐭𝐢𝐨𝐧𝐬 – Review commitments and celebrate progress. ✅ 𝐓𝐢𝐦𝐞𝐛𝐨𝐱 𝐭𝐡𝐞 𝐌𝐞𝐞𝐭𝐢𝐧𝐠 – Respect time, stay concise and productive. ✅ 𝐆𝐚𝐭𝐡𝐞𝐫 𝐅𝐞𝐞𝐝𝐛𝐚𝐜𝐤 – Continuously improve retrospectives themselves. When facilitated well, retrospectives build trust, strengthen collaboration, and drive better delivery outcomes. 🚀 How do you make your retrospectives engaging and valuable? 👇 #ScrumMaster #Agile #Scrum #SprintRetrospective #AgileCoach #ContinuousImprovement #Teamwork #Leadership #AgileMindset

I’ve been managing high-performing teams for 10+ years. Tried dozens of “weekly meetings” templates. Stop overthinking it and steal this one. Weekly meetings can easily become a waste of time. To avoid that, a good framework is always a solid start. With our amazing CMO Domitille de Saint-Exupéry, we use this one, and it works just perfectly: Mood Let’s stay human and start with a quick mood check. But it can easily get boring or just end up with a plain “I’m good” every week. So we use a meme to reflect our mood. It’s a fun way to practice creativity and better express emotions. 1. Weekly Progress This section is for reporting the team’s progress on projects. We use a simple spreadsheet: 1 row = 1 project 1 column = 1 week Color coding: Green = all good / Orange = so-so / Red = issues I think it’s important to monitor the week-over-week evolution, not just a snapshot of the current week. 2. Problems Here we talk about problems.  Two sections: → Problems she can manage on her own (just for my information) → Problems she needs help with 3. People Always good to have a quick team update: how are people feeling? 4. Weekly Priorities This part is about stepping back: What do you want to have achieved by the end of the week? 5. Next Steps Defining the next steps following our meeting --- Hope you’ll like it. Any other format you like?