Building Trust To Enhance Knowledge Sharing

The lesson I take from so many dispersed teams I’ve worked with over the years is that great collaboration is not about shrinking the distance. It is about deepening the connection. Time zones, language barriers, and cultural nuances make working together across borders uniquely challenging. I see these dynamics regularly: smart, dedicated people who care deeply about their work but struggle to truly see and understand one another. One of the tools I often use in my work with global teams is the Harvard Business School case titled Greg James at Sun Microsystems. It tells the story of a manager leading a 45-person team spread across the U.S., France, India, and the UAE. When a major client system failed, the issue turned out not to be technical but human. Each location saw the problem differently. Misunderstandings built up across time zones. Tensions grew between teams that rarely met in person. What looked like a system failure was really a connection failure. What I find powerful about this story, and what I see mirrored in so many organizations today, is that the path forward is about rethinking how we create connection, trust, and fairness across distance. It is not where many leaders go naturally: new tools or tighter control. Here are three useful practices for dispersed teams to adopt. (1) Create shared context, not just shared goals. Misalignment often comes from not understanding how others work, not what they’re working on. Try brief “work tours,” where teams explain their daily realities and constraints. Context builds empathy, and empathy builds speed. (2) Build trust through reflection, not just reliability. Trust deepens when people feel seen and understood. After cross-site collaborations, ask: “What surprised you about how others see us?” That simple reflection can transform relationships. (3) Design fairness into the system. Uneven meeting times, visibility, or opportunities quickly erode respect. Rotate schedules, celebrate behind-the-scenes work, and make sure recognition travels across time zones. Fairness is a leadership design choice, not a nice-to-have. Distance will always be part of global work, but disconnection doesn’t have to be. When leaders intentionally design for shared understanding, reflected trust, and structural fairness, I've found, distributed teams flourish. #collaboration #global #learning #leadership #connection Case here: https://lnkd.in/eZfhxnGW

It might not look like it, but I’m actually quite approachable. Not when I’m grilling candidates on The Apprentice, perhaps, but definitely in work situations. I’m particularly mindful of creating a collegiate, non-threatening environment where colleagues feel safe sharing ideas, concerns, and especially mistakes. Here are four actionable ways you can enhance approachability and build trust with your team: 1. Be present and visible Approachability starts with visibility. If your team rarely sees you or feels they’re intruding when they do, they won’t speak up. Walk the floor, join informal conversations, and make time for spontaneous interactions. Your presence signals you’re open to hearing them, even outside formal meetings. 2. Think aloud and invite the input of others Explain your reasoning — and uncertainties — when making decisions. This creates space for others to contribute ideas or challenge assumptions. During meetings, outline options and explicitly ask for input. This builds trust and shows you value diverse perspectives. 3. Admit to your own mistakes Leaders who own their errors make it safer for others to do the same. Share a recent mistake in a team debrief and what you learned from it. This “models imperfection” and encourages a culture of learning from failure. 4. Use debriefs as learning moments After key projects or challenges, organise post-mortem meetings to review outcomes. Ask open-ended questions like, “What could we have done differently?” or “What should we carry forward next time?” These sessions will also repair tensions from stressful moments. Approachability is a leadership skill like any other. It takes effort and focus. But by fostering openness, you’ll build stronger relationships, improve performance and create a culture of trust. What techniques have you seen that bring out the best in people?

Are we realising the potential of our networks to make change happen? Most innovation emerges from collaborative projects where teams openly “borrow” & adapt each other’s (often small but powerful) ideas. Many networks & communities of practice could achieve so much more by experimenting together around collective priorities to generate & share new solutions. This is beyond spreading known “best” or “good” practices. It is about innovating to design new solutions collectively. So I appreciated this piece from Ed Morrison about three different kinds of networks: - Advocacy networks are communities that seek to mobilise people, creating pressure to shift policies, priorities or messages in a particular direction. Their aim is to connect & influence rather than to change how they themselves work. - Learning networks are communities of practice. They share knowledge, compare practice & build shared capability. Learning networks often excel at spread & improvement of existing practice, but only sometimes move into structured innovation work. - Innovating (or transforming) networks are communities that combine their assets - ideas, relationships, data, capabilities - to create new value that none could produce alone. They manage collaboration as a process of experimentation: agreeing a shared outcome, running multiple connected tests of change, learning by doing & amplifying what works across the network. https://lnkd.in/edbbexiG. Every learning network has the potential to become an innovating/transforming network. Some actions to enable this: 1. Build a foundation of strong, trusting relationships within the network, understanding each member’s starting point & motivation for change 2. Focus on helping each other to succeed; listen to each others’ stories & plans, co-coach, give advice to each other & build shared inquiry 3. Move from “sharing” or “raising awareness” to some concrete outcomes the network want to change together through collective experimentation 4. Agree some simple norms for the network so that members help each other to make progress, make it safe to try things, fail fast & share incomplete work 5. Encourage multiple, parallel tests of change around similar outcome so projects can “steal with pride” from one another & quickly refine promising ideas 6. Put simple routines in place for noticing patterns (what is shifting where & why), capturing these insights & amplifying them across the network 7. Add additional success metrics including innovations tested, adapted & adopted in multiple places Graphic by Ed Morrison. Content with added inspiration from June Holley.

High-quality code makes your work short-lived. Poorly written code ensures the company will always need your help. 😜 Funny — yet many people still follow this mindset. Here’s the hard truth: Across my career, from freshers to senior leaders, I’ve seen professionals who deliberately complicate work, avoid documentation, refuse to share knowledge, and quietly build a dependency around themselves. It’s not incompetence — it’s strategy. A strategy that slows teams down, breeds silos, and creates a dangerous single point of failure. And while it may offer short-term “job security,” it kills long-term team health, innovation, and trust. For leaders, these situations are the most challenging because the person often looks productive on the surface. But behind the scenes, the team becomes fragile, and delivery risks multiply. In engineering, we avoid single points of failure in systems. We should avoid them in people too. 💡 Hard-Hitting Tips for Leaders to Fix This 1️⃣ Make knowledge sharing non-negotiable Mandate documentation, code reviews, and walkthroughs. If knowledge lives only in someone’s head, that’s a risk — not a strength. 2️⃣ Remove dependency incentives Reward collaboration, not silo-building. Make team outcomes matter more than individual heroics. 3️⃣ Rotate responsibilities Let others touch the “critical” areas. If someone resists, that’s a red flag — not loyalty. 4️⃣ Build a culture where transparency is expected Open communication, shared ownership, and regular alignments reduce the power of hidden information. 5️⃣ Address the behaviour early Silence is approval. The longer you let it grow, the harder it becomes to fix. 6️⃣ Make it safe for others to speak Often the team knows who the blocker is — but they need psychological safety to raise concerns. 7️⃣ Lead by example Leaders who share knowledge freely create teams that do the same. Healthy teams grow when knowledge flows. Strong leaders rise when they dismantle silos. And real progress happens only when success is shared — not hoarded. #Leadership #TeamWork #EngineeringCulture #TechLeadership #TeamDynamics #OrgCulture #KnowledgeSharing #GrowthMindset #PeopleManagement #LeadershipTips #CriticalResource #SoftwareEngineering #MunnaPrawin #BUMI #SmartLife

𝗢𝗻 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘁𝗿𝘂𝘀𝘁 𝘄𝗶𝘁𝗵 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗽𝗮𝗿𝘁𝗻𝗲𝗿𝘀 Early in my career, I thought being a great researcher meant delivering perfect insights. I spent hours polishing slides, crafting the clearest recommendations, thinking that’s how I would gain influence and drive impact. But over the years, I’ve learned: 𝗧𝗿𝘂𝘀𝘁 𝗶𝘀𝗻’𝘁 𝗯𝘂𝗶𝗹𝘁 𝗶𝗻 𝗳𝗶𝗻𝗱𝗶𝗻𝗴𝘀 𝗮𝗹𝗼𝗻𝗲. 𝗜𝘁’𝘀 𝗯𝘂𝗶𝗹𝘁 𝗶𝗻 𝗵𝗼𝘄 𝘆𝗼𝘂 𝘀𝗵𝗼𝘄 𝘂𝗽. Looking back, some of the most trust-building moments weren’t in research readouts, but in smaller and ongoing interactions like chats, 1:1s, tech reviews and roadmap meetings. At first, these deeply technical discussions about model architectures, system tradeoffs, and backend constraints felt daunting. But I leaned in with deep curiosity to learn their world – their language, their constraints, how they define success. I began asking questions that brought a different lens – questions about user experience implications, hidden assumptions in metrics, and whether definitions of success truly aligned with user value. Over time, I noticed a shift. Partners began pulling me into more of these conversations. They valued not only the different perspective I brought but also that I was designing research grounded in their reality. The closer I got to their world, the more they trusted me to help them navigate complexity with users in mind. Here are a few lessons that have guided me: 💡 𝗟𝗲𝗮𝗱 𝘄𝗶𝘁𝗵 𝗰𝘂𝗿𝗶𝗼𝘀𝗶𝘁𝘆, 𝗻𝗼𝘁 𝗰𝗿𝗶𝘁𝗶𝗾𝘂𝗲. It’s easy to point out flaws. It’s harder – and far more powerful – to ask questions that unlock better thinking. 💡 𝗚𝗲𝘁 𝗰𝗹𝗼𝘀𝗲 𝘁𝗼 𝘁𝗵𝗲𝗶𝗿 𝘄𝗼𝗿𝗹𝗱. Sit in their reviews and participate in their discussions. Learn the tradeoffs they’re wrestling with. Empathy is the foundation of trust. 💡 𝗦𝗵𝗮𝗿𝗲 𝘆𝗼𝘂𝗿 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗰𝗼𝗻𝗰𝗹𝘂𝘀𝗶𝗼𝗻𝘀. When partners see how you approach a problem, they begin to trust your intuition and judgment, not just your final results. 💡 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝘂𝗽𝗹𝗲𝘃𝗲𝗹𝗶𝗻𝗴 𝘁𝗵𝗲𝗶𝗿 𝘄𝗼𝗿𝗸. Research isn’t just about answering questions; it’s about reframing them to drive better decisions. When partners see that your involvement helps them achieve goals faster, better, and with greater user impact, trust accelerates. 💡 𝗖𝗲𝗹𝗲𝗯𝗿𝗮𝘁𝗲 𝘁𝗵𝗲𝗶𝗿 𝘄𝗶𝗻𝘀. Research insights are powerful, but it’s the engineers, PMs, and designers who build and ship. Recognizing their contributions creates shared ownership and success. At the end of the day partnership is built in 𝘀𝗺𝗮𝗹𝗹 𝗺𝗼𝗺𝗲𝗻𝘁𝘀 – asking a clarifying question that reframes priorities, acknowledging a tough tradeoff, or staying a bit longer to align on next steps. Trust grows when partners see you’re not just doing your job, but actively working to strengthen their efforts and amplify their impact.

This might surprise you… Most leaders think trust is built through big speeches. That’s only half true. The fastest way to build trust is through small, repeatable moments that stack over time. Here are 3 daily habits that create trust on your team: 1/ Keep tiny promises → Say what you’ll do today. Do it. → Reply by end of day. Send the recap. Share the doc. Trust grows when you keep commitments no one else notices. 2/ Give specific recognition → Generic praise is forgettable. → Specific praise proves you noticed. “During the presentation, you paused to check for understanding. That small step kept everyone aligned.” 3/ Ask one honest question → Curiosity signals respect. → “What’s one thing I could do this week to make your work easier?” Then listen. Summarize what you heard. Close the loop. Do this for a week and the room feels different. Do it for a month and people speak up sooner. Do it for a quarter and your team moves faster with less friction. Trust isn’t built overnight. It’s built in minutes. 👉 Which one will you start practicing today? --- ♻️ Repost to help more leaders build trust. 👋 I’m Will — here to help you lead better, grow people, and build real trust at work. Follow for more.

“How do I enhance trust with my team?” - It’s a question I’ve been asked many times as a Trainer and a consultant. In truth, trust isn’t built through a single inspiring speech or an annual offsite. It’s built through daily choices, consistency, and creating the right environment. Here are a few principles that I use in my trainings: 1️⃣ Consistency builds credibility Our teams don’t need us to be perfect — they need us to be predictable. Small follow-throughs matter more than lofty promises. 2️⃣ Psychological safety matters Harvard research shows teams perform best when people feel safe to speak up without fear of blame. In practice, this means inviting opinions before giving your own, and rewarding candor instead of punishing it. 3️⃣ Transparency creates alignment People trust decisions they understand, even when they disagree. Explaining the “why” behind a choice reduces resistance and builds confidence in leadership. 4️⃣ Vulnerability earns respect Admitting mistakes or saying “I don’t know” doesn’t erode authority — it strengthens human connection. Trust grows when leaders are real, not flawless. 5️⃣ Recognition strengthens belonging Acknowledging effort and progress (not just outcomes) reinforces that people are valued, not just their KPIs. "Trust is a two way street. Other can trust you as much as you can trust them" 👉 I’d love to hear from you: What’s one thing you do that helped you build trust with your team? #trust #learninganddevelopment #corporatetraining #organisationalpsychology

People often ask me for quick ways to build trust on a team. I have a dozen solid go-to moves, but one stands out because it’s dead simple and nearly always works. You’ve probably heard of the “connection before content” idea—starting meetings with a personal check-in to warm up the room. But let’s be honest: questions like “What’s your favorite color?” or “What five things would you bring on a deserted island?” don’t build trust. They just waste time. If you want a real trust-builder, here’s the question I use: “𝗪𝗵𝗮𝘁’𝘀 𝘆𝗼𝘂𝗿 𝗯𝗶𝗴𝗴𝗲𝘀𝘁 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 𝗿𝗶𝗴𝗵𝘁 𝗻𝗼𝘄?” That’s it. One question. And here’s why it works: 𝟭. It creates vulnerability without forcing it. You can’t answer this question without being a little real. And when someone’s real with you, it’s hard not to trust them more. You see the human behind the role. 𝟮. It unlocks practical support. Once I hear your challenge, I can picture how to help. I feel drawn to back you up. That’s the foundation of real partnership at work. 𝟯. It increases mutual understanding. Sometimes we feel disconnected from teammates because we don’t know what they actually do all day. When someone shares a challenge, it opens a window into their work and the complexity they’re navigating. If you’re short on time, allergic to fluff, and want something that actually bonds your team—this is your move. Ten minutes, and you’ll feel the shift."

One of the most important currencies a BA has isn’t requirements, templates, or processes. It’s trust. When stakeholders trust you, they’ll share the real issues, let you guide tough conversations, and be more open to change. Here are four ways to start building that trust: 1. Follow through on what you promise 2. Ask questions with curiosity, not judgment 3. Share insights clearly and simply 4. Admit when you don’t know and then go find out Requirements and processes will always change. Trust is what makes people listen, collaborate, and move forward together. 👉 What’s one way you’ve built trust with your stakeholders?