I wrote Unearthing Your Project’s Delays a couple of years ago. I told the story of Cliff, a manager who wanted to understand why the projects were so late. I gave several talks about that article. One eagle-eyed fellow asked me this question, “How long was the time from T0 to T1?” I said, “Managers
I encourage managers to delegate work. When managers insert themselves into the middle of the work, these problems occur: Managers slow the team down. Managers prevent people from learning. Managers don’t do their management work. That environment creates problems for everyone. Then I read Elisabeth Hendrickson’s original Delegation is Overrated. (She has removed the original
I’ve worked with several managers and team leaders over the past few weeks as everyone is suddenly remote. Every single person in a leadership position struggles with (agile) team transparency. These leaders think the team members work alone. (I think they’re correct.) The leaders worry that the team won’t finish the team’s work. (Correct again.)
I’m rewriting/reorganizing the Lead an Innovative Organization book. I realized I have 7 innovation principles: Clarify the organization’s purpose. Manage for effectiveness. Seek outcomes, not outputs. Flow efficiency at all levels. Encourage small-world networks of relationships. Organizational integrity. Encourage change and experiments. Anytime I’ve seen a successful innovation culture, I’ve seen these principles. (I’m trying
Are you a manager accustomed to Management by Walking Around and Listening (MBWAL)? You can use MBWAL with collocated teams. MBWAL doesn’t work for distributed or dispersed teams. Remember, working remote is Not Business as Usual. (And won’t be for a while.) And, you might still have this question: “If no one’s in the office,
If you’re like many of the teams I meet, you’ve sort of got a handle on things. You can release. Your product mostly works. And, then Something Happens. And, your team has trouble recovering. That’s brittleness in the system. You can build resilience as a team. In this post, I’ll summarize how your team can
When I started this series about team brittleness and resilience, I expected to discuss winter weather in the Boston area. Every year, we expect several large snowstorms. And, when it snows hard and long, we should stay off the roads so the plows can clear the snow. The organization and team I wrote about in
This series is about helping a team create a less brittle environment—more resilience. Part 1 was about individual work. This part is about shortening feedback loops. Brief description of the problem at a recent client: Person A checked in code that broke an “unrelated” part of the system. I’ll call this checking in code in
I’ve been working with clients who have brittle environments. Their brittleness doesn’t show up all the time. When everything is good, they’re able to finish work and deliver. But, someone checks in code that breaks something “over there.” Or, someone gets pulled off to work on production support issues and is no longer available to
Three New Year’s Tips to Ease Your Team’s Agility I hope you are all having a terrific holiday season. A reader asked me about tips I had to ease her project’s transition from waterfall to an agile approach. Woo! I have plenty, so I decided to select three tips I have seen work. Tip 1: