Implementing Agile Methodologies for Teams

During one of my projects, we noticed that the daily client standup meetings were not very effective. They would drag on for longer than needed, and some would not pay attention. We brainstormed on complicated ways to make the meetings effective. And that is when someone had a brainwave. All stand-up meetings had to be, as the name suggests, literally held standing up. 30 mins. There was no chair in the room (unless somebody had a medical issue). No tea. No snacks. And overnight, the meetings became a lot more effective. Nobody deviated from the agenda. Everyone paid attention so that the meeting could get done on time, because nobody wanted to stand for longer than needed. No side conversations. No multi-tasking. Just focused discussion. Sometimes, the simplest solutions end up being the most effective.

Scrum as a Service: When Agile Teams Become Ticket Processors Scrum as a Service is when Agile teams are execution units, taking orders instead of owning value delivery. They don’t solve problems; or shaping the product, they just code and close Jira issues. It’s what happens when companies adopt Scrum mechanically but keep traditional thinking and control structures intact. Symptoms of Scrum as a Service 1) No Product Ownership The PO is a backlog manager, not a decision-maker. Teams can’t challenge priorities. The backlog is a job assignment queue. Sprint Planning is a scheduling exercise, not a conversation about functional or technical trade-offs. 2) No Cross-Discipline Collaboration UX, DevOps, and Security exist outside the team, creating slow handoffs. Developers get fully fleshed-out requirements, not problems to solve. Agile teams are ticket processors, not value creators. 3) Nothing Changes Daily Scrums become status meetings for managers. Retros don’t lead to improvements, just performance reviews. Teams are judged by team outputs like velocity, not business outcomes. How This Happens 1) No Organizational Change Leadership keeps command and control, just renaming old roles. 2) Waterfall Thinking Teams have fixed scope and deadlines, no room for continuous discovery or progressive elaboration. 3) POs as Middlemen, Not Leaders POs relay stakeholder demands instead of shaping product strategy. 4) SMs are Managers. Not Coaches SMs push teams to move faster rather than helping them achieve a sustainable pace. How to Fix It 1) Give Teams Ownership Let teams define and prioritize their backlog. Facilitate direct feedback loops with users, not just stakeholder requests. Make POs strategic leaders, not order-takers. 2) Tear Down Silos Embed UX, DevOps, QA, and Security into the Scrum team. Stop treating devs as coders for hire. Make them coequal partners in product thinking. 3) Shift to Outcome Metrics Stop measuring success by velocity, throughput, or tickets. Track customer impact, retention, usability, and product adoption. Ask: Are we solving problems or just releasing code? 4) Decentralize Decision-Making Replace top-down roadmaps with team-driven prioritization. Let teams influence scope, trade-offs, and release planning. Encourage teams to experiment and innovate. 5) Foster Continuous Improvement Make retros actionable. Give teams time for technical excellence, like refactoring, automation, and innovation. Shift from feature delivery to sustainable, high-quality product development. From Execution Teams to Product Teams Scrum teams should be value creators, not feature factories. Agile is meant to empower teams, not turn them into Jira clerks. If teams can’t challenge priorities, shape solutions, adjust processes, or innovate, then you don’t have Agile. You have Scrum as a Service. Does your organization trust teams to own the product? If not, Scrum isn’t the problem. Your structure is.

In 2021, I proposed an initiative I thought was brilliant—it would help my team make faster progress and better leverage each member's unique skills. Brilliant, right? Yet, it didn’t take off. Many ideas or initiatives fail because we struggle to gain buy-in. The reasons for resistance are many, but Rick Maurer simplifies them into three core categories: (1) "I don’t get it" Resistance here is about lack of understanding or information. People may not fully grasp the reasons behind the change, its benefits, or the implementation plan. This often leaves them feeling confused or unsure about the impact. (2) "I don’t like it" This is rooted in a dislike for the change itself. People might feel it disrupts their comfort zones, poses a negative impact, or clashes with personal values or interests. (3) "I don’t like YOU." This is about the messenger, not the message. Distrust or lack of respect for the person initiating the change can create a barrier. It might stem from past experiences, perceived incompetence, or lack of credibility. When I work with leaders to identify which category resistance falls into, the clarity that follows helps us take targeted, practical steps to overcome it. - To address the "I don't get it" challenge, focus on clear, accessible communication. Share the vision, benefits, and roadmap in a way that resonates. Use stories, real-life examples, or data to make the case relatable and tangible. Give people space to ask questions and clarify concerns—often, understanding alone can build alignment. - To address the "I don't like it" challenge, emphasize empathy. Acknowledge potential impacts on routines, comfort zones, or values, and seek input on adjustments that could reduce disruption. If possible, give people a sense of control over aspects of the change; this builds buy-in by involving them directly in shaping the solution. - And to address the "I don't like you" challenge, solving for the other two challenges will help. You can also openly address past issues, if relevant, and demonstrate genuine commitment to transparency and collaboration Effective change isn’t just about the idea—it’s about knowing how to bring people along with you. #change #ideas #initiatives #collaboration #innovation #movingForward #progress #humanBehavior

I managed teams for 10 years before I learned this important truth: Empathy isn't a "soft skill." It's your most powerful leadership tool. I once had a top performer who was missing deadlines. Instead of asking "Why isn't this done?" I asked "How can I support you?" Turns out, she was dealing with family health issues but was afraid to speak up. That one conversation changed everything. 8 ways I learned to show empathy at work: — Listen without jumping to fix things — Be flexible when life throws curveballs — Make time for non-work conversations — Give praise in public, feedback in private — Create space where no question feels stupid — Support mental health days, not just sick days — Ask how you can help, not why things aren't done — Treat your team like people first, employees second When you lead with empathy, productivity and loyalty naturally follow. You don't have to choose between being human and being successful. The most effective leaders are both. Because at the end of the day, people don't leave bad jobs. They leave environments where they don't feel understood or appreciated. Want to transform your team? Start with empathy. It's the investment that pays the highest returns. ♻️ Agree? Repost to spread the message. Thanks! 📌 Follow Justin Wright for more on emotional intelligence. Want my 99 best cheat sheets? Get them free: BrillianceBrief.com

If your feedback isn't changing behavior, you're not giving feedback—you're just complaining. After 25 years of coaching leaders through difficult conversations, I've learned that most feedback fails because it focuses on making the giver feel better rather than making the receiver better. Why most feedback doesn't work: ↳ It's delivered months after the fact ↳ It attacks personality instead of addressing behavior ↳ It assumes the person knows what to do differently ↳ It's given when emotions are high ↳ It lacks specific examples or clear direction The feedback framework that actually changes behavior: TIMING: Soon, not eventually. Give feedback within 48 hours when possible Don't save it all for annual reviews. Address issues while they're still relevant. INTENT: Lead with purpose and use statements like - "I'm sharing this because I want to see you succeed" or "This feedback comes from a place of support." Make your positive intent explicit. STRUCTURE: Use the SBI Model. ↳Situation: When and where it happened ↳Behavior: What you observed (facts, not interpretations) ↳Impact: The effect on results, relationships, or culture COLLABORATION: Solve together by using statements such as - ↳"What's your perspective on this?" ↳"What would help you succeed in this area?" ↳"How can I better support you moving forward?" Great feedback is a gift that keeps giving. When people trust your feedback, they seek it out. When they implement it successfully, they become advocates for your leadership. Your feedback skills significantly impact your leadership effectiveness. Coaching can help; let's chat. | Joshua Miller What's the best feedback tip/advice, and what made it effective? #executivecoaching #communication #leadership #performance

Early in my career, I worked with two very different leaders within the same company. Under the first, team meetings were silent affairs where new ideas were often met with criticism. We stopped contributing. When I moved teams, my new manager actively encouraged input and acknowledged every suggestion, even the imperfect ones. Our productivity and innovation skyrocketed. This experience taught me the power of psychological safety. That feeling that you won't be punished or humiliated for speaking up with ideas, questions, or concerns. Here are three concrete ways leaders can foster psychological safety in meetings: 1. Practice "Yes, and..." thinking. Replace "That won't work because..." with "Yes, and we could address that challenge by..." This simple language shift acknowledges contributions while building on ideas rather than shutting them down. 2. Create equal airtime. Actively notice who's speaking and who isn't. Try techniques like round-robin input or asking quieter team members directly: "Alyzah, we haven't heard your perspective yet. What are your thoughts?" 3. Normalize vulnerability by modeling it. Share your own mistakes and what you learned. When leaders say "I was wrong" or "I don't know, let's figure it out together," it gives everyone permission to be imperfect. AA✨ #PsychologicalSafety #InclusiveLeadership #WorkplaceBelonging

There is a silent killer of execution on too many teams. It's not what you think. I've seen it too much over 25+ years of helping teams from startups to Fortune 500s: Lack of trust destroys results faster than anything else. I could tell stories, but there are decades of research on the costs: - 74% higher stress levels - 40% increase in burnout - 50% drop in productivity - $6,450 less earnings per employee - 2X higher turnover rates Here's what doesn't work: 😯 Extravagant offsites (fun, but a one-time event) 😯 Team building events (well-intentioned, but again, one-time event) 😯 Micromanaging (can work in tiny chunks; otherwise, unravels trust and productivity) 😥 "Trust fall" exercises (at best, an ice-breaker) Why don't these work? Because they ignore the simple math of trust: Trust = Time + Consistency Put another way, Trust comes from consistency over time. 3 proven ways to build trust through consistency: 1/ Make priorities crystal clear - and explain why when they need to change.   2/Create regular rhythms for updates that never, ever get skipped 3/Address issues immediately, even if solutions take time 🤺 Bonus method for max impact: celebrate wins (even small ones) every week. (You aren't being "tough" or having "high expectations" by ignoring this.) The research on the benefits of these practices is clear: teams with high trust show 106% more energy at work and consistently outperform their peers. The formula is simple, but it requires discipline to implement. What's powerful: These practices cost NOTHING but attention and commitment. Like and share so more people hear this. Then go out with your team and crush Q4.

I’ve had to protect my team in the past, particularly when their time or focus was at risk. I’ve seen this happen at companies like Microsoft, Google, and Amazon, where mandates and initiatives would stack during the same timeframe. While each initiative alone might have been reasonable, together they overburdened the teams. Those compiled costs may be invisible to the folks driving the individual mandates. You may have seen teams get overwhelmed by a major release, a review cycle, and bi-annual business planning all at once. This type of time management stress is usually manageable, but there are times when teams can be stretched too thin and compromise morale and quality. When you witness this, I believe it’s crucial to step in. You will hear from your team and you need to be close enough to the issues to decide how to respond. This can be tricky for a leader: on one hand, you want to ensure your team can succeed; on the other, you’re part of the broader leadership and need to support the decisions being made. Sometimes, you have very little room to maneuver. In those cases, I find it most effective to have a private conversation with key decision-makers. Meeting behind closed doors allows you to present the reality of your team’s capacity without putting anyone on the spot. Armed with clear data or project plans, you can often negotiate more realistic timelines or priorities. Another common pressure is when stakeholders create frequent direction changes. Repeated shifts in goals or features will thrash your team and waste energy. This often reflects deeper issues with strategy, alignment, and communication. However, you may not have time for a complete overhaul of your planning processes, and you still need a way to prevent thrash. A short-term fix is to set firm near-term milestones or “freeze” dates, after which any changes must go through a formal triage process. This ensures that if changes are necessary, they follow a transparent, deliberate sequence rather than blindsiding. After the freeze, broader project changes can be considered. Ultimately, I see my responsibility as a leader as fostering an environment where my team can perform at a high level, stay motivated, and avoid burnout. Part of a leader's role is to protect their team’s capability and long-term health. There will always be sprints and times when you need to push, but you also need to consider the long view and put on the brakes when required. People who feel supported are more productive, more creative, and likely to stay engaged.

Agility isn’t a phase. It’s a leadership mindset. Lately, I’ve been thinking about what that really means. Because in my experience, the most agile orgs aren’t just chasing speed. They’re the ones where clarity, trust, and adaptability are baked into the culture. Not just in frameworks or sprint cycles, but in how we show up, make decisions, and create space for our teams to move faster than we ever could on our own. A few ways I’ve seen that come to life: Empower small, cross-functional teams: Some of the most meaningful work I’ve seen has come from lean teams with a shared mission and the freedom to move. When people are trusted, they move with purpose. Make feedback continuous and lightweight: Agility doesn’t mean changing direction every week. It means building habits around listening, iterating, and staying close to the signals that matter. Use AI to reduce drag, not just cut costs: The right tools go beyond automation. They unlock autonomy, helping teams make smarter decisions faster and clearing the path for momentum. Agility starts with how we lead, not just how fast we can go. Curious to hear: what has helped you build a more responsive, resilient organization? #Leadership #EnterpriseAgility #FutureOfWork

Have you ever felt the need to bite your tongue at work, fearing that what you say could lead to punishment or humiliation? It’s a common scenario but one we need to change urgently for greater and healthier workplaces.  En español diríamos: te muerdes la lengua y te envenenas... de todo lo que tienes guardado y no has podido contar. #1:Understand What Psychological Safety Is Psychological safety, a concept introduced by Harvard Business School professor Amy Edmondson, is the belief that team members can take risks, express ideas and concerns, speak up with questions, and admit mistakes without fear of negative consequences. I became obsessed with it while working at Google and being a spokesperson about creating high performing teams. Remember, it’s not about being overly nice (I talked about toxic positivity last week) ; it’s about fostering authenticity and trust within the team. #2: Recognize Its Importance Psychological safety is crucial for sound decision-making, innovation, and operational efficiency. Why? Because when people feel safe, they engage more, share their creative ideas, and contribute to the team’s collective intelligence. Examples: - Imagine a team where members feel empowered to point out potential risks in a project. This openness can prevent costly errors and lead to better outcomes. - Think about a brainstorming session where no idea is too wild or far-fetched. This creates a breeding ground for groundbreaking innovations. #3: Implement Practical Steps to Foster Psychological Safety Creating a psychologically safe environment isn't a one-off task; it's an ongoing commitment. Some best practices I can recommend: - Encourage Open Communication: Make it clear that every voice matters. Regular feedback sessions and open-door policies can help. - Lead by Example: Show vulnerability as a leader. Admit your own mistakes and ask for feedback. It signals to your team that it’s okay to be human. This is the most difficult, I know. You might need your therapist to help you out. 😂 - Prioritize Employee Input: Actively seek and value your team’s input and suggestions. It demonstrates that their perspectives are essential for the company’s success. Now it’s your turn. Take these steps and start creating a safe space for your team to thrive. Let’s make it happen. What strategies have you used to foster psychological safety in your team? Share your experiences in the comments below! If you found this article helpful, don’t forget to like and share it with your network. #Leadership #TeamBuilding #PsychologicalSafety #WorkplaceCulture #Innovation