Tips for Iteration and Improvement Strategies

Obsess over the feedback loop. All the learning you need is in the feedback loop. Most people don’t fail because they lack talent. They fail because they lack a system for learning from failure. Every success story rests on a foundation of failures that were properly ↳ Analyzed ↳ Iterated On ↳ And Improved Most of us don’t hit these important marks. We move move past failure too quickly, avoiding the embarrassing discomfort of reflection. We take failures personally instead of treating them scientifically. We assume trying harder is the answer when we need to try harder to design a better approach. I focus on one core truth: Learning more from failure is how we ultimately win. Failure is a feedback loop, and if yours is broken, you won’t just fail, you’ll repeat your failures over and over. Here’s how to fix that. 👇🏼 1️⃣ Pause & Reflect ↳ Before you move forward, stop. ↳ What went wrong? ↳ What did you assume? ↳ What was unexpected? 2️⃣Capture Data ↳ Write everything down. Future-you needs this information. 3️⃣ Remove Your Ego ↳ This isn’t about you, it’s about the process. ↳ Failures are feedback, not character judgments. 4️⃣ Get External Input ↳ Find people ahead of you who will tell you the truth. ↳ No sugarcoating. ↳ No yes-people allowed. 5️⃣ Identify the Root Cause ↳ Surface-level problems aren’t the real issue. Dig deeper. ↳ What’s the pattern behind your failures? 6️⃣ Make One Small Change ↳ Not everything needs an overhaul. ↳ Start with one adjustment and test the impact. 7️⃣ Test & Observe ↳ Don’t make assumptions. Run your new approach. ↳ Measure the results, and see what actually works. 8️⃣ Iterate with Consistency ↳ One correction doesn’t fix everything. ↳ Keep adjusting, keep improving, keep refining. 9️⃣ Build a Culture of Learning ↳ Winners review their losses more than they celebrate their wins. Every failure contains data. Every mistake contains insight. Are you learning? If you’re not, you’re setting yourself up to fail the same way again. DO. FAIL. LEARN. GROW. WIN. REPEAT. FOREVER. What do your feedback loops like? Which of these ideas might be most helpful to your work? Drop a comment below to share your experience. 👇🏼 _____ 🔗 Subscribe to The Failure Blog via the link in my profile (💯🙏🏼) ➕ Follow me, John Brewton, for content that Helps (💯🙏🏼) ♻️ Repost to your networks, colleagues, and friends if you think this would help them (💯🙏🏼)

Most leadership advice is too big, too slow, or too vague. What’s actually worked for me? Tiny intentional experiments. When I first became a manager, I felt like I ended every day buried in follow-up tasks. I was trying to be helpful by taking on little things but I was actually slowing my team down and draining my energy. So I ran a one-week experiment: I stopped taking on any follow-up items in meetings. None. I drew a hard line. My job was to clarify direction—not do any tasks myself. It was a simple shift, but it changed how I saw my role. Later, as the teams I led grew, I hit a new stuck point. My calendar was so full of weekly one-on-ones it didn’t give me the flexibility I needed to spend time on what mattered most each week. We tested a new rhythm: less frequent 1:1s, longer small-group working sessions. It worked—but it also surfaced new needs: async check-ins, better visibility into blockers, and more space for last-minute coaching. One experiment led to several helpful changes. Then there was AI. I wanted to use AI more, so I committed to one week of asking our AI platform, Rovo, every single question I had before asking a teammate. It helped me build a new habit—and stop pulling people out of focus for info I could find myself. These aren’t PhD style randomized controlled trials or big overhauls. They’re small shifts to break patterns and get new information. They work best when you: 1️⃣ Start small and time-bound 2️⃣ Get clear on what you are trying to learn 3️⃣ Focus on iteration, not perfection And they’ve helped me grow as a leader in real, lasting ways. Today, in Glue Club we all designed a self-experiment, which got me thinking about how key experimentation is for growth. What’s one small experiment you could run next week?

I'm often asked which ceremony I think is most important when running Agile. While all of the ceremonies play a key role in success of delivering outcomes, I feel that the retrospective is what makes the Agile team a team! NFL teams dedicate hours to reviewing game film after each game. This practice helps coaches and players break down their performance to identify strengths, weaknesses, and areas for improvement. Some key elements of NFL film analysis include: 1. Reviewing successful plays and strategies to reinforce positive behaviors. 2. Pinpointing errors in execution and decision-making. 3. Strategizing ways to counteract opponents and improve for the next game. Watching film allows players to visualize their actions and receive direct feedback from coaches, much like Agile retrospectives foster open discussions and learning. In Agile software development, the retrospective ceremony is a cornerstone of continuous improvement. It's a time for teams to reflect on what went well, what didn’t, and how they can improve. The main goals of a retrospective include: 1. Recognizing what went well and building on those strengths. 2. Acknowledging obstacles and areas that need improvement. 3. Collaborating on action items to enhance productivity. Teams often follow frameworks like Start-Stop-Continue or the Five Whys technique to dig deeper and create actionable takeaways. The similarities between Agile retrospectives and NFL film study demonstrate a universal truth: consistent reflection and adaptation are key to success, whether you're coding software or running plays. Here are a few ways these practices align: - Both require honest feedback, communication, and alignment on goals. - Just as developers own their contributions, players must take responsibility for their performance. - Success hinges on iterative progress—making small, consistent improvements over time. By following the below, we can have more effective Agile teams. 1. Be Honest and Open: Like NFL players facing their game tape, Agile teams should embrace transparency and feedback. 2. Focus on Actionable Change: Improvement is valuable only if followed by concrete steps. 3. Celebrate the Wins: Recognizing achievements helps maintain morale and reinforces good practices. Whether you're part of an Agile team delivering software or an NFL team chasing a championship, the retrospective process is crucial for growth and success. By embracing lessons learned and continuously striving for improvement, both Agile practitioners and athletes can achieve peak performance.