AI Assisted Coding: Swimming in AI - Managing Tech Debt in the Age of AI-Assisted Coding | Lou Franco

AI Assisted Coding: Swimming in AI - Managing Tech Debt in the Age of AI-Assisted Coding | Lou Franco

AI Assisted Coding: Swimming in AI - Managing Tech Debt in the Age of AI-Assisted Coding

In this special episode, Lou Franco, veteran software engineer and author of "Swimming in Tech Debt," shares his practical approach to AI-assisted coding that produces the same amount of tech debt as traditional development—by reading every line of code. He explains the critical difference between vibecoding and AI-assisted coding, why commit-by-commit thinking matters, and how to reinvest productivity gains into code quality.

Vibecoding vs. AI-Assisted Coding: Reading Code Matters

"I read all the code that it outputs, so I need smaller steps of changes."

Lou draws a clear distinction between vibecoding and his approach to AI-assisted coding. Vibecoding, in his definition, means not reading the code at all—just prompting, checking outputs, and prompting again. His method is fundamentally different: he reads every line of generated code before committing it. This isn't just about catching bugs; it's about maintaining architectural control and accountability. As Lou emphasizes, "A computer can't be held accountable, so a computer can never make decisions. A human always has to make decisions." This philosophy shapes his entire workflow—AI generates code quickly, but humans make the final call on what enters the repository. The distinction matters because it determines whether you're managing tech debt proactively or discovering it later when changes become difficult.

The Moment of Shift: Staying in the Zone

"It kept me in the zone. It saved so much time! Never having to look up what a function's arguments were... it just saved so much time."

Lou's AI coding journey began in late 2022 with GitHub Copilot's free trial. He bought a subscription immediately after the trial ended because of one transformative benefit: staying in the flow state. The autocomplete functionality eliminated constant context switching to documentation, Stack Overflow searches, and function signature lookups. This wasn't about replacing thinking—it was about removing friction from implementation. Lou could maintain focus on the problem he was solving rather than getting derailed by syntax details. This experience shaped his understanding that AI's value lies in removing obstacles to productivity, not in replacing the developer's judgment about architecture and design.

Thinking in Commits: The Right Size for AI Work

"I think of prompts commit-by-commit. That's the size of the work I'm trying to do in a prompt."

Lou's workflow centers on a simple principle: size your prompts to match what should be a single commit. This constraint provides multiple benefits. First, it keeps changes small enough to review thoroughly—if a commit is too big to review properly, the prompt was too ambitious. Second, it creates a clear commit history that tells a story about how the code evolved. Third, it enables easy rollback if something goes wrong. This commit-sized thinking mirrors good development practices that existed long before AI—small, focused changes that each accomplish one clear purpose. Lou uses inline prompting in Cursor (Command-K) for these localized changes because it keeps context tight: "Right here, don't go look at the rest of my files... Everything you need is right here. The context is right here... And it's fast."

The Tech Debt Question: Same Code, Same Debt

"Based on the way I've defined how I did it, it's exactly the same amount of tech debt that I would have done on my own... I'm faster and can make more code, but I invest some of that savings back into cleaning things up."

As the author of "Swimming in Tech Debt," Lou brings unique perspective to whether AI coding creates more technical debt. His answer: not if you're reading and reviewing everything. When you maintain the same quality standards—code review, architectural oversight, refactoring—you generate the same amount of debt as manual coding. The difference is speed. Lou gets productivity gains from AI, and he consciously reinvests a portion of those gains back into code quality through refactoring. This creates a virtuous cycle: faster development enables more time for cleanup, which maintains a codebase that's easier for both humans and AI to work with. The key insight is that tech debt isn't caused by AI—it's caused by skipping quality practices regardless of how code is generated.

When Vibecoding Creates Debt: AI Resistance as a Symptom

"When you start asking the AI to do things, and it can't do them, or it undoes other things while it's doing them... you're experiencing the tech debt a different way. You're trying to make changes that are on your roadmap, and you're getting resistance from making those changes."

Lou identifies a fascinating pattern: tech debt from vibecoding (without code review) manifests as "AI resistance"—difficulty getting AI to make the changes you want. Instead of compile errors or brittle tests signaling problems, you experience AI struggling to understand your codebase, undoing changes while making new ones, or producing code with repetition and tight coupling. These are classic tech debt symptoms, just detected differently. The debt accumulates through architecture violations, lack of separation of concerns, and code that's hard to modify. Lou's point is profound: whether you notice debt through test failures or through AI confusion, the underlying problem is the same—code that's difficult to change. The solution remains consistent: maintain quality practices including code review, even when AI makes generation fast.

Can AI Fix Tech Debt? Yes, With Guidance

"You should have some acceptance criteria on the code... guide the LLM as to the level of code quality you want."

Lou is optimistic but realistic about AI's ability to address existing tech debt. AI can definitely help with refactoring and adding tests—but only with human guidance on quality standards. You must specify what "good code" looks like: acceptance criteria, architectural patterns, quality thresholds. Sometimes copy/paste is faster than having AI regenerate code. Very convoluted codebases challenge both humans and AI, so some remediation should happen before bringing AI into the picture. The key is recognizing that AI amplifies your approach—if you have strong quality standards and communicate them clearly, AI accelerates improvement. If you lack quality standards, AI will generate code just as problematic as what already exists.

Reinvesting Productivity Gains in Quality

"I'm getting so much productivity out of it, that investing a little bit of that productivity back into refactoring is extremely good for another kind of productivity."

Lou describes a critical strategy: don't consume all productivity gains as increased feature velocity. Reinvest some acceleration back into code quality through refactoring. This mirrors the refactor step in test-driven development—after getting code working, clean it up before moving on. AI makes this more attractive because the productivity gains are substantial. If AI makes you 30% faster at implementation, using 10% of that gain on refactoring still leaves you 20% ahead while maintaining quality. Lou explicitly budgets this reinvestment, treating quality maintenance as a first-class activity rather than something that happens "when there's time." This discipline prevents the debt accumulation that makes future work progressively harder.

The 100x Code Concern: Accountability Remains Human

"Directionally, I think you're probably right... this thing is moving fast, we don't know. But I'm gonna always want to read it and approve it."

When discussing concerns about AI generating 100x more code (and potentially 100x more tech debt), Lou acknowledges the risk while maintaining his position: he'll always read and approve code before it enters the repository. This isn't about slowing down unnecessarily—it's about maintaining accountability. Humans must make the decisions because only humans can be held accountable for those decisions. Lou sees potential for AI to improve by training on repository evolution rather than just end-state code, learning from commit history how codebases develop. But regardless of AI improvements, the human review step remains essential. The goal isn't to eliminate human involvement; it's to shift human focus from typing to thinking, reviewing, and making architectural decisions.

Practical Workflow: Inline Prompting and Small Changes

"Right here, don't go look at the rest of my files... Everything you need is right here. The context is right here... And it's fast."

Lou's preferred tool is Cursor with inline prompting (Command-K), which allows him to work on specific code sections with tight context. This approach is fast because it limits what AI considers, reducing both latency and irrelevant changes. The workflow resembles pair programming: Lou knows what he wants, points AI at the specific location, AI generates the implementation, and Lou reviews before accepting. He also uses Claude Code for full codebase awareness when needed, but the inline approach dominates his daily work. The key principle is matching tool choice to context needs—use inline prompting for localized changes, full codebase tools when you need broader understanding. This thoughtful tool selection keeps development efficient while maintaining control.

Resources and Community

Lou recommends Steve Yegge's upcoming book on vibecoding. His website, LouFranco.com, provides additional resources.

About Lou Franco

Lou Franco is a veteran software engineer and author of Swimming in Tech Debt. With decades of experience at startups, as well as Trello, and Atlassian, he's seen both sides of debt—as coder and leader. Today, he advises teams on engineering practices, helping them turn messy codebases into momentum.

You can link with Lou Franco on LinkedIn and visit his website at LouFranco.com.

Jaksot(200)

How Upper Management Can Destroy a High-Performing Team in Minutes | Somya Mehra

How Upper Management Can Destroy a High-Performing Team in Minutes | Somya Mehra

Somya Mehra: How Upper Management Can Destroy a High-Performing Team in Minutes Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. While working as a business analyst at a startup building an exam evaluation product for universities, Somya witnessed a well-functioning team with good collaboration and timely delivery. However, upper management began challenging the team lead and Scrum Master, accusing the team of padding story points. When leadership confronted the team, the tech lead threw the entire team under the bus, breaking all trust. The CEO's declaration that he could detect padding in estimates shattered the relationship between developers and leadership, leading team members to want to leave. Featured Book of the Week: Agile Retrospectives by Larsen and Derby Somya recommends "Agile Retrospectives" by Larsen and Derby because doing Scrum right means doing retrospectives right. As someone who wanted to excel as a retro facilitator, she found this book invaluable due to its excellent reviews and practical examples. The book provides several examples of how to facilitate retrospectives effectively, making it her go-to recommendation for Scrum Masters wanting to improve their retrospective facilitation skills. Self-reflection Question: How do you maintain trust between your team and leadership when management questions the team's estimates or performance? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Somya Mehra Somya is a Scrum Master at u-blox with nearly 7 years of IT experience across India and Finland. With experience in Waterfall and Agile models, she leads with empathy and a people-first approach. Somya is deeply interested in human behavior and understanding the motivations behind people's actions. You can link with Somya Mehra on LinkedIn.

12 Elo 16min

Learning to Spot Team Performance Warning Signs Early As A Scrum Master | Somya Mehra

Learning to Spot Team Performance Warning Signs Early As A Scrum Master | Somya Mehra

Somya Mehra: Learning to Spot Team Performance Warning Signs Early Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. At the start of Somya's Scrum Master journey, she joined a well-organized and balanced team. However, after two senior developers left the company, the team faced unexpected challenges. Despite hiring new people, velocity didn't improve. Somya discovered that a remaining senior developer had been stepping back and wasn't contributing actively to the team. Through conversations and giving specific tickets to the senior developer, Somya learned valuable lessons about early intervention and communication. Self-reflection Question: How quickly do you address performance concerns with team members, and what signals do you watch for to identify when someone might be disengaging? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Somya Mehra Somya is a Scrum Master at u-blox with nearly 7 years of IT experience across India and Finland. With experience in Waterfall and Agile models, she leads with empathy and a people-first approach. Somya is deeply interested in human behavior and understanding the motivations behind people's actions. You can link with Somya Mehra on LinkedIn.

11 Elo 14min

BONUS: Why Large Organizations Struggle to Innovate With Elliott Parker

BONUS: Why Large Organizations Struggle to Innovate With Elliott Parker

BONUS: Elliott Parker on Breaking The Illusion of Innovation and Why Large Organizations Struggle to Innovate In this BONUS episode, we dive deep into the paradox of modern corporate innovation with Elliott Parker, CEO of Alloy Partners. Elliott shares his insights on why well-managed organizations often struggle with innovation, the critical difference between execution and learning challenges, and how venture studios can bridge the gap between corporate resources and startup agility. In this episode, we explore Elliott's book The Illusion of Innovation. The Golden Gate Bridge Paradox "It took 7 years to add a safety net to a bridge that took 3 years to build." Elliott opens with a striking example that illustrates the central thesis of his work. Large organizations today are paradoxically less capable of handling opportunities and challenges despite being better managed than ever before. The irony lies in their very efficiency—modern corporations have become so optimized for capital efficiency and short-term profits that they've inadvertently sacrificed their capacity for future innovation. This focus on Return on Invested Capital (ROIC) creates organizations that excel at managing existing assets but struggle with the uncertainty required for breakthrough innovation. The Corporate Innovation Anti-Pattern "The more the innovation team borrows from the business, the more the innovation team starts to look like the original organization." Elliott reflects on a belief he once held and now completely disagrees with—that corporate innovation teams could successfully drive disruptive innovation from within. Having worked in corporate innovation focused on IP licensing and later in venture capital, he discovered that these internal teams, while excellent at expanding existing business models, inevitably become constrained by the very organization they're meant to transform. The solution he advocates is funding startups outside larger organizations, where there's nothing to preserve or perpetuate, allowing for true disruptive thinking. In this segment, we talk about Clayton Christensen's Disruption Theory which he explored in the now famous book: The Innovator's Dilemma. Execution vs. Learning Challenges "Moving slow is a feature of corporations, not a bug." One of Elliott's key frameworks distinguishes between execution challenges and learning challenges. Corporations are brilliantly designed for execution—when the problem and solution are known, they excel. However, learning problems, where the problem is clear but the solution unknown, require a fundamentally different approach. Elliott suggests marrying the best of both worlds: leveraging the funding and market research capabilities of large organizations with the disruptive ideas and solution-seeking agility of startups. He provocatively suggests treating communication around innovation as something to be avoided until solutions are proven, advocating for working in silos until innovation actually works. The Controlled Burn Philosophy "The only way to get data about the future is to collect data by running experiments." Elliott introduces the concept of "controlled burn" using forest fire management as a metaphor for corporate innovation. Just as western US forests have become dangerously dense from aggressive fire suppression, corporations have become fragile by avoiding all risk and experimentation. We can't predict the future, and there's no existing data about what's coming—the only way to generate future insights is through deliberate experimentation. However, managers are typically incentivized to avoid experiments and minimize risk, creating the organizational equivalent of dense forests prone to devastating fires when disruption eventually arrives. Creating Safe-to-Fail Environments "In corporates we focus on frequency of correctness. In startups we focus on magnitude of correctness." After initially believing he could change organizations from within, Elliott learned that creating truly safe-to-fail environments within established companies is nearly impossible. This realization led him to focus on creating startups as the perfect vehicle for business model experimentation. The fundamental difference in mindset is crucial: corporations optimize for being right most of the time, while startups optimize for the size of their wins when they are right, embracing a venture capital-like approach to innovation where occasional big wins compensate for frequent small failures. Shifting from Wealth to Knowledge Generation "Civilizations fail because they don't innovate fast enough." Drawing on insights from David Deutsch's work on learning and innovation, Elliott argues that long-term resilience comes from learning, not just wealth generation. He advocates for shifting corporate conversations from immediate wealth generation to knowledge and learning, positioning companies as explorers of innovation and business models. This requires different funding mechanisms—moving away from operational budgets managed through traditional Excel-based metrics toward "patient capital" that can sustain the uncertainty inherent in true innovation. Traditional management approaches lack the passion needed for breakthrough innovation. In this segment, we refer to David Deutsch's book The Beginning of Infinity: Explanations that Transform The World. About Elliott Parker Elliott Parker is CEO of Alloy Partners, where he helps corporations and universities launch startups through a venture studio model. A former Innosight consultant and entrepreneur, he's passionate about bridging big companies with startup ecosystems to unlock real innovation and long-term growth in an increasingly distributed world. You can link with Elliott Parker on LinkedIn.

9 Elo 44min

How Decision Journals Can Transform Product Owner Behavior | Florian Georgescu

How Decision Journals Can Transform Product Owner Behavior | Florian Georgescu

Florian Georgescu: How Decision Journals Can Transform Product Owner Behavior Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The Humble Learner Florian describes a Product Owner who started from scratch with business knowledge but no PO experience. This exemplary PO demonstrated transparency and engagement in their communication style, showed humility in recognizing knowledge gaps, and actively built strong relationships with the team. They used practical tools like a Product Canvas shared with the team, implemented "Story Time Tuesdays" for informal refinement sessions, and introduced feature learning cards to assess impact and learn from completed work. This PO's success came from embracing the learning journey openly and creating collaborative environments where both they and the team could grow together. The Bad Product Owner: The Command-and-Control Controller Florian encountered a Product Owner who transitioned from 20 years in project management, bringing a command-and-control style that frustrated the development team. Despite having good business and technical knowledge, this PO made technical decisions for the team without allowing input, particularly challenging since they were in a different location. Florian addressed this through a "decision journal" experiment over three sprints, documenting every product decision and analyzing their impact during retrospectives. This approach served as a powerful mirror, clearly showing that technical decisions made without team input produced poor results, ultimately helping both the PO and team recognize the importance of collaborative decision-making. Self-reflection Question: How does your Product Owner balance their expertise with the team's input, and what tools could help improve this collaboration? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Florian Georgescu Florian is a seasoned Agile Coach with 10+ years of experience guiding teams across startups to large enterprises. He specializes in tailoring workflows, mentoring Scrum Masters, and fostering collaboration. Passionate about continuous improvement, Florian helps organizations boost agility and align delivery with strategic goals for lasting impact. You can link with Florian Georgescu on LinkedIn.

8 Elo 17min

When Teams Embody Agility Without Having To Thinking About It | Florian Georgescu

When Teams Embody Agility Without Having To Thinking About It | Florian Georgescu

Florian Georgescu: When Teams Embody Agility Without Having To Thinking About It Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Florian defines success for Scrum Masters as achieving teams that embody agility naturally, without conscious effort. He identifies key behaviors that indicate true team maturity: team members openly discuss their needs and how to fulfill them, they embrace constructive conflict as productive and necessary, and developers can communicate with business stakeholders in accessible language rather than technical jargon. This level of success represents the ultimate goal for Scrum Masters – creating self-organizing teams that have internalized agile principles so deeply that they become second nature, enabling authentic collaboration and effective business communication. Featured Retrospective Format for the Week: Naikan Retrospective The Naikan Retrospective, based on a Japanese self-reflection practice, proved invaluable when Florian's team faced a catastrophic release failure during a Champions League game at a sports betting company. This format addresses three key questions: "What have I done successfully for my team?", "What did I get back from my team?", and "How did I support my team in these hard moments?" Despite initial concerns about team acceptance, this retrospective format provided structured relief during high-tension situations, allowed team members to express missing support needs, and created lasting positive impact. The human-centered approach helped the team process failure constructively and build stronger relationships through structured self-reflection. self-reflection Question: What behaviors in your team indicate they're truly embodying agility, and how might you recognize when they no longer need your guidance? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Florian Georgescu Florian is a seasoned Agile Coach with 10+ years of experience guiding teams across startups to large enterprises. He specializes in tailoring workflows, mentoring Scrum Masters, and fostering collaboration. Passionate about continuous improvement, Florian helps organizations boost agility and align delivery with strategic goals for lasting impact. You can link with Florian Georgescu on LinkedIn.

7 Elo 13min

From Resistance to Effective Change Leadership in Agile Adoption | Florian Georgescu

From Resistance to Effective Change Leadership in Agile Adoption | Florian Georgescu

Florian Georgescu: From Resistance to Effective Change Leadership in Agile Adoption Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Florian shares his transformation from resisting organizational standardization to becoming a champion of strategic alignment. Initially fearing that standardization would stifle innovation and turn agile practices into rigid frameworks, he discovered the bigger picture when he became scrum master chapter lead for 12 scrum masters across multiple locations and cultures. The breakthrough came from implementing a three-level standardization approach: level 1 for non-negotiables, level 2 for encouraged patterns, and level 3 for team-specific innovations. Using the 80/20 principle, they focused on the 20% of standards that would create 80% of alignment. The scrum master chapter became a learning hub where teams could share their level 3 innovations, creating a balance between consistency and creativity that enabled effective cross-tribe collaboration. Self-reflection Question: How might you balance the need for organizational alignment with preserving team autonomy and innovation in your current context? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Florian Georgescu Florian is a seasoned Agile Coach with 10+ years of experience guiding teams across startups to large enterprises. He specializes in tailoring workflows, mentoring Scrum Masters, and fostering collaboration. Passionate about continuous improvement, Florian helps organizations boost agility and align delivery with strategic goals for lasting impact. You can link with Florian Georgescu on LinkedIn.

6 Elo 13min

When Knowledge Hoarding Destroys Team Dynamics | Florian Georgescu

When Knowledge Hoarding Destroys Team Dynamics | Florian Georgescu

Florian Georgescu: When Knowledge Hoarding Destroys Team Dynamics Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Florian describes a payment system development team where an experienced tech lead unknowingly created a dangerous dependency. This senior developer, while well-intentioned, became the single point of knowledge and decision-making for the entire team. Other developers began copying his behavior, creating a culture where team members were afraid to ask questions for fear of appearing incompetent. When this key developer left, the team fell apart - planning sessions became confusing, technical discussions stalled, and two junior developers quit citing lack of learning opportunities. The story demonstrates how knowledge hoarding, even when unintentional, can destroy team resilience and create toxic dynamics that stifle growth and collaboration. In this segment, we refer to the Monday episode with Florian as context for the story he shares on this episode. Self-reflection Question: How might knowledge hoarding be happening in your team, and what steps could you take to encourage more distributed learning and decision-making? Featured Book of the Week: The Responsibility Process by Christopher Avery Florian The Responsibility Process by Christopher Avery particularly valuable for understanding the stages people go through when taking responsibility. The book's framework helped him process his own burnout experience and provides crucial insights for helping teams accept responsibility for their outcomes. Florian emphasizes how the responsibility process is essential for understanding what you can influence when you want to take ownership, making it a powerful tool for both personal growth and team development. In this segment, we refer to the Responsibility Process, by Christopher Avery, who was a previous guest on our Audiobook project: Tips From the Trenches, Scrum Master Edition. [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Florian Georgescu Florian is a seasoned Agile Coach with 10+ years of experience guiding teams across startups to large enterprises. He specializes in tailoring workflows, mentoring Scrum Masters, and fostering collaboration. Passionate about continuous improvement, Florian helps organizations boost agility and align delivery with strategic goals for lasting impact. You can link with Florian Georgescu on LinkedIn.

5 Elo 14min

From Burnout to Balance: A Scrum Master's Reality Check | Florian Georgescu

From Burnout to Balance: A Scrum Master's Reality Check | Florian Georgescu

Florian Georgescu: From Burnout to Balance: A Scrum Master's Reality Check Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Florian shares his experience of trying to single-handedly transform an entire IT service company, leading to what he calls the "superman scrum master syndrome." His story highlights the dangers of trying to be everywhere for everyone and create perfect change from the beginning. Working with a coach, Florian recognized the warning signs of burnout - exhaustion, frustration, and the unhealthy need to control everything. His journey teaches us that sustainable change takes time, and it's perfectly acceptable for things not to be perfect from the start. The key insight is learning to pace yourself and accept that meaningful transformation is a gradual process, not a solo mission. Self-reflection Question: When have you found yourself trying to be the "superman" in your role, and what signs helped you recognize it was unsustainable? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Florian Georgescu Florian is a seasoned Agile Coach with 10+ years of experience guiding teams across startups to large enterprises. He specializes in tailoring workflows, mentoring Scrum Masters, and fostering collaboration. Passionate about continuous improvement, Florian helps organizations boost agility and align delivery with strategic goals for lasting impact. You can link with Florian Georgescu on LinkedIn.

4 Elo 15min

Suosittua kategoriassa Politiikka ja uutiset

rss-ootsa-kuullut-tasta
aikalisa
tervo-halme
ootsa-kuullut-tasta-2
politiikan-puskaradio
viisupodi
et-sa-noin-voi-sanoo-esittaa
rss-vaalirankkurit-podcast
rss-podme-livebox
aihe
otetaan-yhdet
linda-maria
rss-polikulaari-humanisti-vastaa-ja-muut-ts-podcastit
rss-hyvaa-huomenta-bryssel
the-ulkopolitist
radio-antro
rss-valiokunta
rss-kaikki-paskaksi-ystavat
rss-terevisio
rss-tasta-on-kyse-ivan-puopolo-verkkouutiset