Balancing Team Dynamics

Ever feel like constant supervision is holding you back instead of lifting you up? Progress thrives on trust, not micromanagement. But when trust is replaced by over-control, here’s what happens: - Innovation stalls When micromanaged, team members are hesitant to take risks or explore new ideas, stifling creativity. - Motivation drops Constant supervision undermines autonomy, leaving individuals feeling untrusted and disengaged. - Growth halts Over-control limits opportunities for team members to learn, grow, and develop their full potential. Micromanagement may seem like it ensures perfection, but in reality, it creates: ➜ Frustration Micromanagement creates a feeling of being suffocated, leading to dissatisfaction and disengagement. ➜ Burnout The pressure of constant oversight can drain energy and lead to exhaustion, affecting both productivity and well-being. ➜ Talent loss Talented team members may seek environments where their contributions are valued and trusted, leading to turnover. The truth? Progress requires a leader’s confidence in their team. Trust isn’t just a nice-to-have—it’s essential for: ✔️ Empowering creativity Trust allows team members to explore their ideas and solutions, fostering a culture of innovation. ✔️ Building accountability When leaders trust their teams, individuals take responsibility for their work, leading to better results. ✔️ Driving sustainable growth A confident, autonomous team can adapt, evolve, and grow, driving long-term success. So ask yourself: Are you empowering your team or just supervising them?

Working with people you find difficult is no joke. It can impact your well-being, your performance, and definitely your ability to enjoy your job. For Harvard Business Review, I shared 7 strategies to help you work more effectively with challenging coworkers, whether you're dealing with an insecure boss, a passive-aggressive peer, or someone whose behavior simply gets under your skin (we all know people like that!). Here’s a quick overview: 1️⃣ Remember your perspective is just one of many. We all see situations through our own lens. Try asking yourself: Could I be wrong? 2️⃣ Be aware of your biases. From confirmation bias to affinity bias, our brains take shortcuts that often distort how we perceive others, especially those who are different from us. 3️⃣ Don’t make it “me against them.” Reframe the conflict as a shared problem to solve, not a personal battle to win. 4️⃣ Know your goal. What are you actually trying to achieve - peace, productivity, recognition? Let that intention guide how you show up. 5️⃣ Be careful with venting and gossip. Some venting can be helpful, if done the right way. But negatively intended gossip can harden your view, damage your credibility, and reinforce negativity. 6️⃣ Experiment to find what works. Try small behavior shifts and observe the impact. If one approach doesn’t work, try another. Think of it as an experiment, not a fix. 7️⃣ Stay curious. Certainty keeps us stuck. Curiosity opens the door to empathy, creativity, and sometimes even resolution. These aren’t quick fixes - nothing worthwhile is - but they can help you feel more grounded and less reactive, even when someone else’s behavior doesn’t change. Link to the full article is in the comments 👇 Image alt text: How to Navigate Conflict with a Coworker

Clearing the Systemic Barriers to Authentic Agility Most so-called Agile “transformations” (oh, if ever there were a misnomer) don’t fail because of the framework, tooling, or training - they fail because of deeply embedded impediments that fall into four systemic categories: Culture, Structure, Process, and Technology. These factors form a complex ecosystem, and if you treat them like separate problems, you’ll get performative agility without real adaptability. Agility isn’t a checklist or a destination. It’s a continuous journey of adaptation. Ignore the interplay between these domains at your peril. Barrier #1: Culture - The Invisible Operating System That Resists Change Problem: Traditional organizational cultures prioritize control over creativity, rewarding compliance while punishing exploration. The result is risk-averse bureaucracy. Questions: Do people feel safe admitting mistakes? Are failures learning opportunities or liabilities? Can the status quo be challenged without retaliation? Strategies: Foster psychological safety with blameless retrospectives and candor-friendly spaces. Celebrate smart failures. Promote learning with cross-functional exposure, rotation programs, and curiosity-based metrics. Barrier #2: Structure - Your Org Chart Is Showing Problem: Hierarchical, siloed structures slow decisions and disconnect teams from value delivery. Questions: Are teams aligned to customer outcomes or department KPIs? Where do decisions get made? How often do handoffs or approvals delay progress? Strategies: Align teams to value streams. Push decision-making closer to the work. Use lightweight governance and clearly delegated authority to reduce drag. Barrier #3: Process - When Following Rules Becomes Valuable Problem: Agile rituals become performative when teams confuse ceremony with value. Questions: Are Agile events energizing or exhausting? Do metrics reflect outcomes or activity? Are teams allowed to evolve their way of working? Strategies: Design outcome-oriented processes. Audit meetings regularly. Enable process experimentation within safe bounds. Focus on feedback loops, not rituals. Barrier #4: Technology - Tools as Thrust or Drag Problem: Legacy systems and fragmented tools create cognitive friction, slow feedback, and kill momentum. Questions: Do your tools promote collaboration or reporting? Can teams release frequently without manual overhead? Does tech accelerate flow or block it? Strategies: Invest in CI/CD, test automation, and self-service platforms. Retire tools that reinforce control or don't add value. Prioritize fast feedback, simplicity, and team autonomy in tool selection. Agility Isn’t Implemented - It’s Cultivated True agility requires systemic change across all four domains. It’s messy, non-linear, and context-dependent. Focus on domain interactions. Create safe-to-learn environments. Measure progress by adaptability, not just delivery. Don't chase transformation; enable evolution.

Navigating Team Conflicts In team dynamics, some level of conflict is inevitable—even healthy. However, understanding the nature of the conflict can help leaders manage and resolve it more effectively. Here are four common conflict patterns and strategies for handling them: 1. The Solo Dissenter This conflict arises when one individual disagrees with the rest of the team. Whether due to personal differences or a challenge to the status quo, isolating or scapegoating this person is counterproductive. Instead, leaders should engage in one-on-one conversations to better understand their perspective and address any underlying concerns. Open communication can transform a dissenter into a valuable source of alternative viewpoints and broader system awareness. 2. The Boxing Match This frequent form of conflict involves a disagreement between two team members. If the issue stems from a personal relationship, external coaching may be helpful. However, if it’s task-related, the disagreement may benefit the team by introducing diverse ideas—provided the discussion remains civil. Leaders should avoid intervening prematurely, as genuine task-based disagreements often lead to more innovative solutions. 3. Warring Factions When two subgroups within the team oppose each other, an "us versus them" mentality can develop. This type of conflict is more complex, and solutions like voting or majority rule rarely resolve the issue. Leaders should introduce new options or third-way alternatives, encouraging both sides to broaden their thinking and find a compromise that addresses the core needs of both groups. 4. The Blame Game This challenging conflict involves the entire team, often triggered by poor performance. Assigning blame worsens the situation and creates more division. A more effective approach is to refocus the team on collective goals and explore strategies for improvement. Shifting the conversation from blame to team purpose and collective problem-solving can unite the group around a shared vision. By recognizing these conflict patterns and applying the right strategies, leaders can guide their teams through disagreements, fostering a more cohesive and productive environment.

Most teams confuse speed with chaos. Here are 7 steps to move fast with structure. True agility is speed with control. It sounds simple, but few teams ever get there. I’ve led teams that won fast. And I’ve led teams that broke faster. The difference was structure. We tried to race Jet Skis in a storm. It looked fun, but we failed. What we needed was a Destroyer with a plan. Here’s what helped us move fast without losing focus. 1. Choose your ship. Every problem needs a different one. Jet Skis explore. Destroyers execute. Carriers enable. 2. Find your rhythm. Decide how often you meet and review. Keep rhythm for speed, not noise. 3. Know who’s in charge. Give each goal one clear owner. Use shared rules where work overlaps. 4. Write it down. Use one-page plans and quick recaps. Keep a record after each win or loss. 5. Focus your bets. Three strong moves beat fifteen weak ones. Depth builds momentum. 6. Guard your focus. Say no to “urgent” work that adds no value. Save your energy for real impact. 7. Lead with calm. Teach others the same rules of order. A calm team is a fast team. We learned this lesson by slowing down. We stopped chasing every idea. We focused on what mattered most. The result was simple. Fewer projects. Better work. Stronger teams. That’s when real momentum came back. Speed isn’t the goal. Winning the right way is. Jet Skis win races. Destroyers win wars. Build for endurance. Lead with structure. Command your fleet. Save this post for your next storm. Share it with someone building theirs. ♻️ Repost if this resonates (and to help others).

When I work with teams, I don’t just ask “do you trust each other?” I look for three specific capabilities: 1. Psychological Safety 💬“I feel safe to speak up.” This is the most studied predictor of team performance. Teams with psychological safety voice concerns earlier, catch problems faster, and bring their full thinking into the room. It creates intellectual openness. 2. Vulnerability 💬“I can ask for help.” Trust isn’t built through independence, it’s built through interdependence. When team members admit uncertainty, say “I don’t know,” or ask for support, they create a signal loop that says: we grow together. This is where openness emerges as a habit. It humanizes the team and makes learning possible. 3. Shared Accountability 💬“We’re in this together.” Even the safest, kindest team fails without this. Shared accountability turns a group of individuals into a collective. It’s where courage kicks in to follow through, own outcomes, and hold each other to a shared standard. This is what transforms trust from a feeling into a performance structure. We often talk about trust like it’s a mood. Like it appears when people “click” or when culture is “nice.” But in high-performing teams, trust isn’t chemistry. It’s architecture. Built not on feelings, but on behaviors, signals, and systems.

If there's conflict in your team, how can you resolve it without aggression or escalation? And also without people-pleasing or giving away your power as a leader? The key here is: establish psychological safety. If your first response is to blame them, their guards will go up, and they will get defensive, because they will detect a threat i.e., lack of psychological safety. That's the end of the conversation and maybe even the relationship in extreme cases. Here are some examples: What NOT to Do: Dismiss or Ignore Concerns: Example: A team member raises an issue during a meeting, but it's brushed aside by the team leader without any further discussion. Instead: Acknowledge the concern and encourage open dialogue to understand its root cause and potential impact. What NOT to Do: Blame or Shame Individuals: Example: When a mistake is made, publicly assigning blame to a specific team member. Instead: Approach errors as learning opportunities for the entire team, focusing on solutions rather than assigning fault. Give constructive feedback in private. What NOT to Do: Dominate Discussions: Example: A few outspoken team members monopolize discussions, making it difficult for others to contribute their perspectives. Instead: Facilitate balanced participation by actively encouraging quieter team members to share their thoughts and ensuring everyone has an opportunity to speak. What TO Do Instead: Encourage Open Communication: Example: Create regular opportunities for team members to share their thoughts, concerns, and feedback in a safe and non-judgmental environment, such as through regular team meetings or anonymous suggestion boxes. Model Vulnerability: Example: Leaders openly admit their own mistakes or uncertainties, demonstrating that it's acceptable to be imperfect and fostering a culture of trust and authenticity. Provide Constructive Feedback: Example: When addressing performance issues, focus on specific behaviours or outcomes rather than attacking the individual's character. Offer guidance on how to improve and support them in their development. Celebrate Diversity of Thought: Example: Encourage team members to bring diverse perspectives to the table, recognizing that differing viewpoints can lead to more robust solutions. Celebrate successes that result from collaborative efforts. Establish Clear Norms: Example: Set explicit ground rules for communication and conflict resolution within the team, emphasizing the importance of respect, active listening, and maintaining confidentiality. Did this help? Then give this post a 👍🏼

We've mediated over 200 workplace conflicts in the last decade. Most managers handle them completely wrong. The default approach is to sit both people down, let them air grievances, and try to find middle ground. This almost never works. Here's why: by the time a conflict reaches you, both sides have already constructed narratives where they're the reasonable one and the other person is the problem. Letting them "share perspectives" just hardens those positions. The approach that actually resolves things: 1. Talk to each person separately first. Not to hear their side of the story. To understand what they actually need to do their job. Strip away the personality complaints and get to the operational friction. 2. Identify the structural issue. 90% of "personality conflicts" are actually role confusion, competing priorities, or broken processes. Two people fighting over resources aren't having a relationship problem. They're having an allocation problem. 3. Fix the system, not the people. Change the workflow. Clarify the decision rights. Adjust the reporting structure. When you remove the structural friction, the interpersonal stuff usually evaporates. 4. Only then address behavior if needed. Sometimes someone genuinely acted poorly. But address it as a behavioral correction, not as part of the "conflict resolution." Keep it separate. The manager who tries to get two people to "understand each other" is solving the wrong problem. The manager who figures out why their jobs keep colliding and fixes that is solving the right one. Most workplace conflict isn't actually about personalities. It's about poorly designed systems forcing good people into competition.

Most designers mess up their first 90 days in a new role. They join the company, open Figma, and immediately start designing. While highlighting: "This navigation is terrible." "Why would anyone design the checkout flow like this?" "The design system is a mess." But here's the smarter move: Start small. Build trust. Then go big. Because everything that exists today- good or bad- got the company to a point where they could afford to hire you. Someone went back and forth with product managers & developers. Someone worked with half the budget. Someone shipped under impossible deadlines. Someone kept the product alive when things got messy. When you start by criticising, you question the people who built it. When you start by understanding, you earn their trust. Here's what the best designers do in their first 90 days: 🔹 Days 1-30: Listen & Learn 👉🏼 Talk to the customers (not just stakeholders) 👉🏼 Understand why current designs exist 👉🏼 Find ONE small problem you can solve quickly 🔹 Days 31-60: Ship & Show Impact 👉🏼 Fix that small problem 👉🏼 Document the results 👉🏼 Share the win with the team 🔹 Days 61-90: Build Authority & Scale 👉🏼 Now tackle a bigger challenge 👉🏼 People trust your judgment 👉🏼 Your ideas get approvals faster The designer who fixes a confusing button label in week 2 earns more respect than the one who proposes a complete redesign in week 1. Small wins build authority. Authority unlocks bigger opportunities. Bigger opportunities create real impact. The harsh truth? Your brilliant redesign ideas mean nothing if nobody trusts you yet. Start small. Prove value. Then scale. What was the first thing you designed when you joined your current company? Follow Rohan Mishra for more such content.

The Leadership Paradox: Embracing Absence to Achieve Presence The conventional image of a leader is often someone always at the helm, steering the team with a firm hand. But I've come to believe that the true mark of leadership lies not in constant presence, but in the ability to step back and trust the team you've built. This paradox – the idea that leading effectively sometimes means not leading at all – might seem counterintuitive. Yet, in my experience at Merino Group, it's been the key to unlocking our team's full potential. To strive for and foster a culture of ownership and accountability we need to start: ➡ Hiring for potential, not just experience: We look for individuals who are eager to learn, take initiative, and challenge the status quo. ➡ Setting clear expectations and goals: We ensure everyone understands their role and how it contributes to the bigger picture. ➡ Providing resources and support: We offer training, mentorship, and the tools necessary for success. ➡ Creating a safe space for failure: We encourage experimentation and risk-taking, recognising that mistakes are opportunities for growth. When we trust our team to make decisions, we empower them to become leaders in their own right. And when we step back, we create space for new ideas and fresh perspectives to emerge. Of course, this approach requires a shift in mindset – for both leaders and team members. It takes courage to let go of control and trust in the collective wisdom of the group. But the rewards are immeasurable. #leadership #empowerment #trust #teamwork #delegation #MerinoGroup