Johanna Rothman, Management Consultant
Expert in Managing Product Development
As I complete the Modern Management Made Easy books, I realize I need to explain how much tolerance an organization has for experiments. The more clients I have, the more I realize most organizations have a sweet spot for how much they can tolerate experiments or bets. Each person has an affinity for more or …
Continue reading “What’s Your Organization’s Tolerance for Experiments?”
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’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”
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 …
Continue reading “Build Team Resilience: Work “Anywhere” and “Anytime” (Part 3)”
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 …
Continue reading “Build Team Resilience: Shorten Feedback Loops (Part 2)”
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 …
Continue reading “Build Team Resilience: Work Together (Part 1)”
Collecting data isn’t free. There’s a cost to every piece of data. There’s also value. How do we balance the cost and value of data? As with all juicy questions, it depends. And, in general, the easier the data is to collect, the less value there is in the data. Examples of Useless and Cheap …
A client wants to know how best to calculate their software capitalization. They had a “standard” approach when they used waterfall. They no longer have all waterfall projects. They’ve started to use agile approaches. And, the projects don’t all look the same. Being somewhere in the middle means they’re having trouble reasoning about capitalization. Why …
Continue reading “Capitalizing Software During an Agile Transformation”
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”