I’ve learned a ton about software projects. One thing I know is that any project that uses continuous integration (agile or not) has a better chance of succeeding. Not a guarantee, but a much better chance.
I’ve learned other things I find necessary for successful software projects. Two of my favorites are the need for a team-based purpose or focus, and the need to collaborate as a team.
That means that I stopped learning about continuous integration, purpose, or collaboration. I know these things work. I use them. I continue learning about ways to practice these ideas better. That often means I need to challenge my mental models about how projects work.
When I challenge my mental models and use double-loop learning as in the image above, I learn more in-depth. That in-depth learning helps me learn how to change how I use CI, purpose, and collaboration.
I use double-loop learning to extend my practices to apply these (and other) ideas to projects (and management).
I don’t just learn from reading other people’s words. I learn via my coaching and the workshops I offer. I learn through my work, my projects. As I live and work, I continue to reflect and refine my knowledge.
And, I know people who claim they are too busy to learn more. When I ask them why they stopped learning, I hear these reasons.
- I learned everything I needed to succeed in my projects a year ago. (Or, 2, 5, 10 years ago.) Besides, I’m too busy to take the time to learn something new.
- There’s nothing new in the field. Besides, I’m too busy to take the time to learn something new.
- I’m certified. Why would I need to learn anything else? Besides, I’m too busy to take the time to learn something new.
Those people achieved some status quo and stopped learning. They no longer verify their mental models or adjust what they do know to experiment or be more effective.
Here’s why the idea of “too busy” doesn’t make sense to me. Very often, they could help their busy-ness by taking some time to learn. Even if they don’t learn from outside their project, they could use double-loop learning inside the project.
I recently met project leaders who were stuck on one approach for estimation. (Story points in an agile project.) When I suggested two alternatives (counting stories or using cycle time), all I got were blank looks. They hadn’t heard of these ideas? No, they were too heads-down in the projects, too busy to realize they had alternatives.
Why were they so busy? The projects were late. Why were the projects late? Because the estimation was wrong. For every single project.
And, the leaders, the people who might have been able to see the system and realize something was wrong? They were all too busy to learn. They didn’t know how to learn about their projects’ system of work. They were so busy, they couldn’t learn about alternatives to story point estimation.
I have found that when I stuck in a loop of “this doesn’t work so I must try harder to make it work,” I should examine my mental models instead. And, when I use double-loop learning and challenge everything I know, I often discover it’s time for me to learn something new.
As soon as I think I’m too busy to learn, that’s the time I need to spend a little time and learn. Does this ever happen to you? I bet it does!
That’s the question this week: Are you too busy to continue learning?
- Do You Choose to Mistake-Proof or Future-Proof?
- When Are You Willing to Practice in Public?