All blogs / Engineering management / careers
Pawel Brodzinski on Leadership in Technology
Whatever it takes to lead a team, build a product, and run a business
Engineering management / careersSoftware / engineering practiceAI / ML
- Posts
- 280 from 2 Nov 2006 to 14 Jul 2026
- Posting
- monthly (8 in the last year)
- Kind
- personal blog
- Feed
- https://brodzinski.com/feed
2026 6
- We 3.5x’d Our Pull Requests with AI: Now We Catch Fewer Bugs
- Check Your F**cking Sources, People!
- Conway’s Law Teaches a Grim Lesson About AI in Product Development
- The Ultimate Question: What Does the Endgame Look Like?
- What LEGO Can Teach Us about Autonomy and Engagement
- Limited Autonomy Is the Main Reason for Low Engagement Levels
2025 26
- Would You Pay to Have Your Resume Read?
- A Non-Obvious Answer to Why the AI Bubble Will Burst
- Trust Networks as Antidote to AI Slop
- We Will Not Trust Autonomous AI Agents Anytime Soon
- Care-Driven Development: The Art of Giving a Shit
- AI Has Broken Hiring
- Radical Candor Is an Unreliable Feedback Model
- Fundamental Flaw of Hustle Culture
- The Most Underestimated Factor in Estimation
- The Renaissance of Full-Stack Developers
- Flailing Around with Intent
- A Love Letter to Physical Whiteboards
- Care Matters, or How To Distribute Autonomy and Not Break Things in the Process
- The Role of Alignment
- Pivotal Role of Distributed Autonomy
- Reinvent Your Daily Meetings
- Wholeness Is a Lie
- Is Growth Necessary for Survival?
- Why Wouldn’t an Intern Fire a CEO?
- Levels of Slack Time
- Respect (and How It Makes or Breaks Culture)
- Milk Kanban
- Lateral Skills Are Core Skills
- The Case for Subjective Assessment System
- (Non-)Challenges of Distributed Decision-Making
- Choosing Partners: Make or Break
2019 3
2018 6
2017 2
2016 3
2015 15
- Don’t Limit Work in Progress
- Don’t Mess with Culture
- Context Switching: The Good and the Bad
- Hierarchy Is Bad For Motivation
- Value of MVP and Knowledge Discovery Process
- Why We Want Women in Teams
- Culture Pockets
- Portfolio Kanban Board
- The Fallacy of Shu-Ha-Ri
- The Cost of Too Many Projects in Portfolio
- Why We Fail to Change
- Story Points and Velocity: The Good Bits
- Decision Making Process
- Economic Value of Slack Time
- On Feedback (Again)
2014 22
- Minimal Indispensable Feature Set
- Happiness Index as Team Sustainability Metric
- Two Rules of Autonomy
- Portfolio Kanban and Doing the Right Thing
- Lean Kanban Central Europe Leadership Track
- Practices, Principles, Values
- There Is No Shortage of Leaders
- Scaling Up Is Not the Only Option
- Kanban: The Culture Challenge
- Portfolio Management: Stop Starting, Start Finishing
- Recipes Are (Almost) Useless
- Evolutionary Change of Portfolio Management
- A Fool With a Tool Is Still a Fool
- Hyperproductivity Myth
- Personal Ritual Dissent
- Unscaling Agile
- Why Your Change Program Will Fail
- (Don’t) Change Your Job
- Why Kaizen Boards (Typically) Don’t Work
- No Management Mindset
- The Fallacy of the Ideal Team Size
- Closing Leadership Gap
2013 37
- What Value Is Exactly
- Portfolio Management: The Search for Value
- Why People Don’t Learn
- Why Bonus Systems Don’t Work
- Multitasking Teams
- Estimation Quality
- 5-Minute Board Test
- What Does Project Management Mean to Me
- Options, Options, Options
- Hiring for Cultural Fit
- Teams
- Portfolio Visualization
- What Makes Project Attractive
- Limit Work in Progress Early
- No Estimates Middle Ground
- Cumulative Flow Diagram
- Kanban Landscape and Portfolio Kanban
- All Sorts of Kanban
- Kanban Leadership Retreat: Portfolio Kanban
- Manager-Free Organization
- MVP Thinking
- Hire the Best
- What Makes Teams Better
- It’s the People, Not the System
- Better Standups
- Maturity of Kanban Implementation and Kanban Kata
- WIP Limits by Conversation
- Happiness Chart
- Portfolio Kanban: Why Should I Care?
- Brickell Key Award Nomination
- Why I Don’t Limit WIP (On Occasions)
- Making Use of Estimates
- No Authenticity, No Leadership
- Retrospectives Reloaded
- Emergent Explicit Policies
- Flying Office
- Gemba Walk Is Not Enough
2012 48
- Price versus Quality
- Against Rightshifting
- (Sub)Optimizing Cycle Time
- On Transparency
- Kitchen Kanban, or WIP Limits, Pull, Slack and Bottlenecks Explained
- Why Organizational Transformations Fail
- WIP Limits Revisited
- Leadership, Fellowship, Citizenship
- Why Burn-up Chart Is Better Than Burn-down Chart
- Refactoring: Value or Waste?
- Code Better or Code Less?
- Kanban Coaching Professional
- Is a ScrumMaster of Any Value?
- Don’t Ask For Permission
- Local Optimizations Aren’t (Always) Evil
- Splitting Huge Tasks
- Radar Charts and Maturity of Kanban Implementations
- Feedback Culture
- Pitfalls of Kanban Series: Stalled Board
- Scott Berkun on Consultants and Practitioners
- Practitioner versus Consultant
- Cadences and Iterations
- Trap of Estimation
- Visualization Should Be Alive
- On Feedback
- Pitfalls of Kanban Series: Wishful Thinking
- Kanban and Behavioral Change
- Slacker Manifesto
- Ball Flow Game
- What Do You Want To Do In Two Years From Now?
- Slack Time
- Pitfalls of Kanban Series: Abusing WIP Limits
- The Project Portfolio Kanban Story: Better Board
- Pitfalls of Kanban Series: Kanban Board Not Up To Date
- Pitfalls of Kanban Series
- You Can Deliver Late
- The Project Portfolio Kanban Story: Why Standard Board Design Is Not a Good Choice
- How Much Work In Progress Do You Have?
- Instant Feedback Culture
- What Is Slack Time For?
- Better Conferences or Better Learning?
- Learn. Adapt. Experiment. Repeat.
- A Myth of 100% Utilization
- Naming Issue
- On Agile Once Again
- The Project Portfolio Kanban Story: First Changes
- In Defense of Difficult Decisions
- Why You Should Ask: “Why?”
2011 46
- Effective Standups around Kanban Board
- Product Owner versus Product Ownership
- The Project Portfolio Kanban Story: A Basic Approach
- The Purpose of Retrospectives
- Get Rid of Estimation
- Hand-Offs Are Bad (But Unavoidable)
- The Project Portfolio Kanban Story: Project Portfolio Kanban? Why?
- The Project Portfolio Kanban Story
- Collaborative Spirit of Kanban
- What Makes a Good Retrospective
- Alternative Kanban Board Design
- Don’t Stick to Standard Kanban Board Designs
- When Kanban Fails
- Team Retreat
- Learn! Or How to Get a Better Job
- Visual Management
- Be Passionate!
- Kanban Story: Kanban Board Should Reflect the Reality
- What Kanban Really Is
- Pull and Push in Kanban
- The Worst Management Task Ever
- Kanban: When It Is Hard to Map a Process to a Kanban Board
- On Making Difficult Decisions
- Trainers, SMART Goals and Context
- The Kanban Story: Skipping Part of Process
- Communication: Quality versus Quantity
- Visualization: Don’t Get Attached to a Specific Tool
- Give Honesty a Try
- Kanban Leadership Retreat
- Challenge your Rules
- Visualize Everything
- Procedure Is Not an Answer
- Experiment!
- Surprising Truth about Kanban Improvements
- The Kanban Story: Standard-Sized Features
- Project Management in One-Man Project
- Limiting WIP Is a Buzzword
- Taught Helplessness
- Visualization Stupid!
- People Are Not Our Most Valuable Resource
- Scrum versus Kanban
- Mechanics of Kanban Improvements
- Project Management Styles: The Good, the Bad and the Ugly
- Good Waterfall Is Better Than Bad Agile
- Kanban Board: Keep It Simple Stupid
- Why Money Doesn’t Motivate
2010 36
- Definition of Done
- The Kanban Story: Retrospectives
- Money and Motivation
- We Are Unique Syndrome
- Kanban Basics
- The Beauty of Kanban
- The Value of Certification
- Being a Leader
- The Kanban Story: Moving Cards Back
- Embrace Failure
- So You Promoted Wrong People to Management, What Now?
- How to maintain backlog?
- Implementing Change
- One Measure to Appraise Them All
- The Kanban Story: Small Tricks Do the Job
- The Role of Manager
- Performance Reviews Are Dead, Long Live Performance Reviews
- The Kanban Story: When and Why We Abuse Limits
- Why I Prefer to Hire Women
- Don’t Promote Best Engineers to Management Positions
- Choose Your Battles
- You Can Manage Your Boss
- We Know Nothing about Our Teams
- When Kanban is the Best Choice
- The Kanban Story: Swarming
- The Kanban Story: Coarse-Grained Estimation
- The Kanban Story: Measuring Lead Time
- The Kanban Story: Kanban Boosters
- Why We Don’t Write User Stories Anymore
- Manual Testing Is a Must
- Managers Are Clueless
- The Kanban Story: Kanban Board Revisited
- Fighting with Status Quo
- Big Companies Are The Best… In Maintaining Status Quo
- The Kanban Story: Pseudo Iterations
- The Kanban Story: Throwing Sticky Notes Out
2009 22
- The Kanban Story: I Don’t Know, Experiment!
- The Kanban Story: Kanban Alone Is Not Enough
- The Kanban Story: Kanban Board Evolution
- The Kanban Story: What We Do and What We Don’t Do
- The Kanban Story: Kanban Board
- The Kanban Story: Implementation of Kanban
- No Meeting Culture
- The Kanban Story: A Discovery of Kanban
- Co-location Rules!
- The Kanban Story: First Issues
- The Kanban Story: Initial Methodology
- The Kanban Story: The Beginning
- The Kanban Story
- Technical Leadership and People Management
- Random Thoughts on Estimation
- A Company Which Didn’t Know How to Fire People
- Is It Possible to Over-Communicate In Project?
- Sure Shot Method to Improve Quality of Your Estimates
- Evidence Based Scheduling – One More Way to Improve Your Estimates
- Role of Leaders in Startups
- Lessons Learned: Startup Failure Part 2
- Lessons Learned: Startup Failure Part 1