Implementing Agile Methodologies for Teams

Harvard report: 71% of meetings are unproductive. 65% keep people from doing real work. The best leaders don’t run more meetings. They run the ones that matter. The goal: Keep teams aligned, focused, and moving fast. Without wasting time. Here’s how to run the meetings that actually move the business forward: Weekly 1:1 ↳ Let them drive the agenda ↳ Listen first, coach second ↳ End with 2–3 clear next steps Leadership Team Meeting ↳ Review key metrics in 10 minutes ↳ Focus on 2–3 high-impact issues ↳ End with clear decisions and owners Weekly Operating Review ↳ Review KPIs by exception ↳ Flag risks in revenue, churn, or ops ↳ Assign fixes with owners and due dates Quarterly Planning Session ↳ Review last quarter’s goals ↳ Debate and choose top 3 priorities ↳ Assign clear owners and resources Voice-of-Customer Session ↳ Bring 3 real pain points ↳ Let customers talk 70% of the time ↳ Follow up within 30 days Board or Investor Update ↳ Share the hard stuff first ↳ Highlight 1–2 metrics that matter ↳ Ask for help with specific challenges All-Hands ↳ Explain the why, not just the what ↳ Take live, unscripted questions ↳ End with one clear message You may not need all of these. Some might add a daily standup. But chances are, your company doesn’t need half the meetings on the calendar now. Use this list to audit what’s working. Cut what’s not. Your team will thank you for their time back. Better meetings = faster decisions, sharper focus, and real momentum. P.S. Does your company have too many meetings or just right? ♻️ Repost to help a leader in your network. Follow Eric Partaker for more productivity insights. — 📌 Want PDFs of this and 100+ free leadership resources? Get them here: https://lnkd.in/ekhxjakK

If your team’s not speaking up… you’ve already lost. Not ideas. Not productivity. Trust. And once trust is gone? Innovation stalls. Collaboration dies. People check out—or walk out. The fix? Not another tool. Not another policy. But something far more powerful: Psychological safety. It’s not a “nice to have.” It’s the hidden engine behind every high-performing team. Here’s how you build it—one conversation, one decision, one moment at a time 👇🏼 1. Lead with curiosity, not judgment. ↳ “Help me understand…” beats “Why’d you do that?” 2. Admit your own mistakes. ↳ Model the safety you want others to feel. 3. Give credit generously. ↳ Shine the light on others—often and publicly. 4. Respond, don’t react. ↳ Let people tell the truth without fear of fallout. 5. Invite pushback. ↳ Ask: “What am I missing?” 6. Remove silent punishments. ↳ Reward honesty, not just agreement. 7. Normalize “I don’t know.” ↳ That’s how real learning starts. 8. Make feedback feel safe. ↳ Correct with care. Aim for growth, not shame. 9. Start meetings with check-ins. ↳ Connection before conversation. 10. Celebrate courage, not just results. ↳ Applaud the voice, not just the victory. Because when people feel safe, they don’t hold back. They contribute. They challenge. They soar. If you want your team to rise—safety comes first. Which one of these 10 will you lead with this week? ♻️ Share this with your network if it resonates. ☝️ And follow Stuart Andrews for more insights like this.

"𝘞𝘩𝘦𝘯 𝘺𝘰𝘶 𝘱𝘶𝘴𝘩, 𝘸𝘦 𝘱𝘶𝘴𝘩 𝘣𝘢𝘤𝘬 𝘩𝘢𝘳𝘥𝘦𝘳." It’s an unspoken agreement in workplaces everywhere. Are you unknowingly igniting resistance instead of sparking change? 𝗧𝗵𝗲 𝗛𝗶𝗱𝗱𝗲𝗻 𝗖𝗼𝘀𝘁 𝗼𝗳 𝗣𝘂𝘀𝗵𝗶𝗻𝗴 𝗧𝗼𝗼 𝗛𝗮𝗿𝗱
 At City Hospital (a pseudonym used to protect confidentiality), the CEO, “Juliette Garnier” (also a pseudonym), believed decisive action would save the day. Faced with a funding crisis, she enforced a 10% budget cut across departments. Her intent? Keep the hospital afloat. The result? Chaos. Her leadership team froze in silence, employees raged in the corridors, and nurses threatened a strike over unsafe working conditions. Garnier had unknowingly stepped into what I call The 𝙋𝙪𝙨𝙝 𝘽𝙖𝙘𝙠 𝙋𝙖𝙩𝙩𝙚𝙧𝙣: * 𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝘃𝗲𝘀 = 𝗘𝗻𝗳𝗼𝗿𝗰𝗲𝗿𝘀 * 𝗘𝗺𝗽𝗹𝗼𝘆𝗲𝗲𝘀 = 𝗥𝗲𝘀𝗶𝘀𝘁𝗼𝗿𝘀 The harder you push, the harder people push back. 𝗪𝗵𝗮𝘁 𝗦𝗼𝗺𝗲 𝗟𝗲𝗮𝗱𝗲𝗿𝘀 𝗠𝗶𝘀𝘀 𝗔𝗯𝗼𝘂𝘁 𝗥𝗲𝘀𝗶𝘀𝘁𝗮𝗻𝗰𝗲
 Resistance isn’t about rejecting change. It’s about rejecting the way change is imposed. When people feel ignored, undervalued, or strong-armed, their silence or anger signals mistrust and resentment. The more forceful the push, the stronger the resistance grows. 𝗕𝗿𝗲𝗮𝗸𝗶𝗻𝗴 𝘁𝗵𝗲 𝗣𝗮𝘁𝘁𝗲𝗿𝗻
 Garnier recognised the pattern and shifted her approach. Instead of enforcing change, she invited her team to co-create solutions. Within weeks, the same employees who had resisted her became her strongest allies, crafting a plan that cut costs without compromising care. The strike was called off, and trust was restored. 𝗧𝗵𝗲 𝗟𝗲𝘀𝘀𝗼𝗻 𝗳𝗼𝗿 𝗟𝗲𝗮𝗱𝗲𝗿𝘀 
Leaders who force change light fires that burn bridges. Those who nudge—inviting collaboration and listening deeply—build lasting trust and sustainable results. Are you lighting fires or building bridges? Would love to hear your views: What strategies have worked for you to overcome resistance and inspire collaboration? 📚 For a systemic lens to creating lasting change, explore the ideas in my book, 𝙏𝙝𝙚 𝙃𝙞𝙫𝙚 𝙈𝙞𝙣𝙙 𝙖𝙩 𝙒𝙤𝙧𝙠.

How I manage stakeholders as a Project Manager without saying "no" Stakeholder management is one of the most underestimated skills in project delivery. And one of the trickiest parts is pushback. I’ve seen it time and time again: "Can we add this feature last minute?" "Can we deliver sooner?" "Can we skip UAT? "😅 Saying a direct “no” might feel assertive, but in many corporate environments, especially in matrixed organisations, it’s not always productive. It can cause friction, defensiveness, and damage relationships you need to maintain. So here is how I manage stakeholders without actually saying “no”: ✅ I reframe Instead of saying, "No, that’s out of scope," I say: "Let’s revisit the priorities and see where this fits in. If we bring this in, what are we okay to move out?” ✅ I ask questions Often people just want to feel heard. Instead of shutting down ideas, I ask: "What’s the driver behind this request?" "What would success look like if we included it?" This either de-escalates the urgency or helps me build a case for change. ✅ I make trade-offs visible I use timelines and impact visuals. "We can do that - here’s what happens if we do." Let the facts speak. Most reasonable stakeholders respond well to transparent data. ✅ I bring them into the process When stakeholders feel involved, they’re more likely to accept decisions, even tough ones. This approach helped me deliver projects on time while maintaining trust across business, tech, and delivery teams. Of course, sometimes you have to say “no”, but in most cases, it’s not what you say, it’s how you say it. Do you also navigate difficult stakeholder requests without being the “bad cop”? What strategies work for you? 👇

What if the pushback you’re getting is actually your team’s way of asking to be part of the process? I had such case recently with a team leader: “Susanna, my team resists everything I decide. I spend more time defending than leading.” So I asked him: “Do you involve them early in the process?” He paused. “Well, I usually let them know once the direction is clear.” So I joined one of his meetings. He walked in with a polished plan, laid out the logic, and wrapped it with: “Any quick comments before we move on?” Silence. Then came the emails. The 1:1s. The offhand comments. The real feedback but it was too late to shape anything. That’s when I introduced him to the concept of Status Threat. 🧠 When people feel excluded from decisions that affect their work, they don’t always say it directly. Instead, they resist in quieter ways like questioning, withdrawing, or slowing things down. Not because they’re stubborn. But because being left out sends a clear signal: “Your expertise isn’t needed.” “Your input doesn’t matter.” That’s not just a workflow issue - it’s a psychological safety issue. And when people don’t feel safe or seen, trust breaks down. And when trust breaks down, so does performance. We made a simple change: ✅ Before finalizing any decision, the leader created a 10-minute “challenge space” with a clear structure for input. ✅ He began framing ideas as drafts, not directives. ✅ He started explicitly naming the value of each person’s expertise, making team members feel recognized and included. What actually changed? The team didn’t become more agreeable. But they became more engaged. Because the pushback was never about the plan. It was about their place in it. P.S.: Have you ever mistaken a team's resistance for negativity only to realize later it was a call to be heard?

Trust issues? Yep? You’re not alone. According to Endelmans latest report* the number of employees who trust their employer to “do what is right” has already fallen three points to 75% this year. And when trust dips? So does our engagement, motivation & commitment. Without trust, it doesn’t matter how banging your benefits are or how practical your processes, at some point that empire you're building will start to wobble. With trust as the foundation, though? 👇 💥 Companies with high trust levels outperform low-trust counterparts by 186%. 💥 Employees in high-trust environments report 74% less stress and 40% less burnout. “Great, so how do we build trust, pronto?" I hear you yell. Well, true trust takes time, but here’s some top-trust-tips to get you started: 1️⃣ Belonging > Busyness “We’re too busy” is the most basic excuse for skipping the moments that build belonging. And whilst we know there is a never-ending-to-do-list, investing time in connection now prevents bigger challenges later. 2️⃣ Meet people where they’re at. Drop preconceived notions. Instead of assuming how people are going to behave, start with the belief that everyone has the team’s best interests at heart. 3️⃣ It’s in your actions Building trust doesn’t come through words alone, it’s all in your actions. Show up prepared, be curious about everyone’s ideas, listen with intent. Trust is built through consistent, small actions - and these “signals” your sending will create a ripple effect of reciprocity. 4️⃣ Improve your information flow You know what makes people feel nervy or unsafe? When information is hidden from us. Think about who needs to know what to do their best work and to feel a sense of safety and belonging. You don’t need to share everything, but don’t withhold information people need to do their jobs well. 5️⃣ Act on feedback Did you know 62% of employees believe their feedback goes nowhere? Now that’s a fast track to losing trust. Listen to what your team is sharing, and act on it. Even small steps show you’re serious about their input and committed to making changes that matter. 6️⃣ Know what makes your team-tick The stronger your personal connections, the deeper the trust. Whether through quick coffee chats, walk-and-talks, or tackling projects together, invest in understanding your team. 7️⃣ Nip bad behaviours in the bud Address issues in real-time. Feedback, done continuously and constructively, can nip bad vibes and behaviours in the bud, and reinforce what we do and don’t stand for around here. 8️⃣ Recognise regularly Recognition of progress really matters. And that burst of joy we get when someone gives us a shout out also strengthens our trust. Build recognition into your rituals, but also encourage random-acts-of-recognition to make people’s day. And you know what? Through building trust you're also building those all important systems for how things are done around here 👉 Document it, communicate it, act on it. #Culture #Trust

The hidden force that breaks high-performing teams (and how to fix it) Trust. Trust isn’t built when things go well. Trust is built when things fall apart. Over years working with leadership teams at TikTok, Meta, and now with organizations globally through Oxford Leadership and Maximize Opportunity ,I’ve witnessed a similar phenomenon: Teams don’t break under pressure. They break under distrust. Not the obvious kind, the quiet kind. The hesitation before speaking. The question left unasked. The instinct to protect rather than share. The calculation that honesty might carry a cost. What we know is that: - High-performance cultures aren’t just built through better processes. They’re built through trust that feels earned, human, and real. - Trust grows in specific moments: • When you show the mess, not just the polished result • When you speak up despite the tremor in your voice • When you say “I don’t know” instead of pretending • When you reveal the person behind the title • When you give trust before demanding proof - Trust isn’t transactional. It’s relational. It’s an invitation to be in genuine connection, not just coordinated workflow. In our world of relentless speed and constant disruption, trust isn’t a nice-to-have. It’s the foundation of every meaningful collaboration. When trust becomes your culture: Teams accelerate. Conversations go deeper. People take braver steps. Work shifts from survival mode to creative mode. The leadership question isn’t: “How do I get people to trust me?” It’s: “Where can I show up more fully, so others feel permission to do the same?” That’s where trust begins. That’s how it multiplies. That’s how teams transform.

People don’t evolve while drowning. They need to tread water first. Many organizations and their leaders are demanding agility. Too few are asking whether their people have the bandwidth for it. I see this as a central contradiction of leadership in our disruptive age. When your energy is consumed by the third reorganization in two years, by figuring out which of your responsibilities will be automated next quarter, by guessing whether the strategy announced Monday will still be the strategy on Friday... there is no psychological bandwidth left for adapting. Agility requires surplus. What I find myself telling ambitious team leaders these days is this: Before you demand agility from people navigating an AI transition, a restructuring, or their fourth new boss in three years, genuinely ask yourself: have I created an environment where agility is possible? Or am I asking for agility from people who are barely staying afloat?   I’ve been suggesting three tools to help leaders figure this out:   1. Do a Bandwidth Audit. Ask each person on your team: On a scale of 1–10, how much mental energy do you have left after getting through your daily work? If the average is below 5, you don’t have an agility problem. You have a staying-afloat problem. That’s where to begin. Otherwise, every initiative you launch is just more weight on people who are already sinking. 2. Remove Before You Add. Identify one obligation, meeting, or process that is draining your team without producing value and see if you can eliminate it this week. Don’t replace it with anything. Just return the time. In a period of constant disruption, one of the most helpful things a leader can do is subtract before asking anyone to add. 3. Protect Unstructured Time. Block one hour per week with no agenda and no deliverable. (I know, it's hard when calendars look like heavily-stacked pancakes.) In disruptive environments, every hour tends to get filled by urgency. Protect this one: Let people bring half-formed ideas, strange observations, or problems they can’t crack. Good solutions and ideas often come from the collisions that happen when people have room to think. If your team looks resistant or slow to adapt, the question may be what’s wrong with the water level and not what’s wrong with them. #disruption #change #energy #learning #leadership

As a Business Analyst(BA), many times, difficult conversations are unavoidable. Be it conflicting priorities, unrealistic expectations, scope creep and more. When you handle such conversations with a practical plan, difficult conversations can be managed well. 1. Prepare facts, not emotions. Don’t enter the room with opinions. Enter with data, examples, and impact. 👉 Example: Instead of “This requirement is confusing,” say “We’ve had three different interpretations of this step.” 2. Reframe, don’t resist. If a stakeholder pushes back, turn their statement into a clarifying question. 👉 “You want this in Phase 1 — can we discuss what must drop if we add it?” 3. Stay neutral, act as a mirror. Repeat what each side said, in simple words, so they hear themselves. It reduces defensiveness. 4. Use “we,” not “you.” Shifts tone from blame to collaboration. 👉 “We need more clarity here” instead of “You haven’t given enough clarity.” 5. Document live. In tough talks, write things down on the screen or whiteboard. It forces alignment and reduces “I didn’t say that” later. 6. Escalate issues, not people. If you need to involve a manager or sponsor, focus on the issue’s impact, not stakeholder behaviour. 7. Pick the right medium. Some conversations resolve faster face-to-face (or by call) than in long emails. 8. Pause if emotions run high. Suggest continuing after a break instead of forcing closure in a heated moment. 9. Ask for support when needed. 👉From PM/Product Owner: if priority or scope needs authority. From SMEs: if you lack domain depth to challenge assumptions. From QA/Dev leads: if feasibility is in question. 10. Debrief after conflict. Summarise agreements in writing and circulate — ensures no confusion later. Mismanaged conversations damage trust and stall progress. Handled well, they create clarity, respect, and momentum. Knowing when to seek help saves you from carrying the entire conflict alone. As BAs, it's sometimes difficult, but we should never avoid difficult conversations, because, if not today, tomorrow, that difficult topic will hit back badly. Try to make conversations structured with neutral emotions, and involve the right people to reach clarity. #businessanalyst #stakeholdermanagement #businessanalysis #projectmanager #projectmanagement #BA #agile #scrum #customer #customerstakholder

Leaders: create an environment where your team doesn't second guess themselves. Failure is okay. Difficult conversations need to happen. Worthwhile work is hard. But here's the thing: your team will fail to execute according to your standards when you've built a system around fear (whether intentional or not). And even worse, the standards they can achieve. Here's how I try (and fail at times) to build a culture of trust on the marketing team: Encourage Transparency: Make it safe for your team to share challenges, ask for help, and voice concerns. Have monthly or quarterly meetings with every team member, make it a safe space to share their concerns. Show Your Vulnerability: Lead by example, show your own vulnerability. Admit your mistakes, and model how to learn and move forward. Get Agreements: Fear often arises from uncertainty. Be clear about goals, priorities, and what success looks like. Share Before Ready: Encourage your team (and yourself) to share work-in-progress ideas, drafts, and projects. Waiting for "perfect" never works. Give Feedback With Empathy: Feedback should be constructive, not destructive. Focus on the behavior, not the person. Fear can stifle even the most hardworking and intelligent. It also blunts creativity, slows your team, and severely limits trust. It's your job to remove the barrier.