Johanna Rothman, Management Consultant
Expert in Managing Product Development
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 Delegation is Overrated. I realized two things: Some managers …
Continue reading “Delegate Problems and Outcomes, Not Tasks”
We’ve all heard of big organizations where the top management said, “No need to ever be back in the office. Work from home, as long as you want.” And, the Wall Street Journal has this article, Business Travel Won’t Be Taking Off Soon Amid Coronavirus (you might need to subscribe to see the article). (I …
In the agile and lean communities, we talk a lot about transparency. This image is the transparency principle we used in From Chaos to Distributed Agile Teams. I see the most product and program success when the various teams create transparency between them, the middle of the continuum. That’s the full-product transparency. I see many …
I’ve had the pleasure—and displeasure—of many remote meetings over the past few weeks. The difficult meetings had a common root cause: the meeting leaders attempted to do a direct transfer of how they lead an in-person meeting to remote/WFH meetings. When that occurs, they miss the ability to optimize on our separation by choosing how …
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 …
Continue reading “Want Business Agility? Use These Seven Innovation Principles”
Back when I was a manager, my senior management wanted to separate the “new” work from the “maintenance” work. I suggested that every new line after the first line of code was maintenance. The managers poo-poohed me. My concern: How would the “new” developers learn from their mistakes? I lost that discussion and I managed …
Continue reading “Effects of Separating “New” Work vs “Maintenance” Work”
I keep encountering managers and consultants who want to make work “fun” for people. As a goal, “fun” is a bunch of hooey. Before I was a consultant, I held various Director-level positions at local companies. Each organization had mandatory fun days. In one organization, we played softball. Yes, everyone—especially the managers—had to play softball …
Does your team have to keep two sets of “books”? You have an agile roadmap to see where you’re headed. You have a smallish backlog of the near/upcoming work. You’re delivering on a frequent basis. And, someone on your team keeps a Gantt chart because a manager wants to see the team’s progress in a …
Continue reading “What Decision Will You Make Based on This Data?”
It’s time to wrap this series. I started asking if you actually need an agile approach in Part 1 and noted the 4 big problems I see. Part 2 was why we need managers in an agile transformation. Part 3 was about how people want a recipe. Part 4 was about how “Agile” is meaningless …
Continue reading “Where I Think “Agile” is Headed, Part 5: Summary”
I started this series asking where “Agile” was headed. (I didn’t like what I saw at the Agile 2019 conference.) Part 1 was about the 4 big problems I see. Part 2 was why we need managers. Part 3 was about how people want a recipe. This part is about what “Agile” or “agile” means. …
Continue reading “Where I Think “Agile” is Headed, Part 4: What Does “Agile” Mean?”