All organizations use cost accounting to report on their revenue, including profit and loss. We are so accustomed to using cost accounting that we don’t realize how it hides the truth about our progress. Worse, cost accounting creates and reinforces a culture of resource efficiency thinking. (In resource efficiency, the person is the unit of […]
I started this series discussing where AI use might create bottlenecks. The more people work solo on anything, the more likely they become bottlenecks for the team. When each person works solo with AI, they reinforce resource efficiency, where everyone is busy, but the team can’t seem to finish anything when anyone wants it. Instead,
This is Johanna Rothman’s June 2026 Pragmatic Manager Newsletter. The Unsubscribe link is at the bottom of this newsletter. Most of us have worked with managers who guided our careers. But managers aren’t the only ones who can support other people’s growth. Sometimes, technical leaders who are not “people managers” can have just as much
So many people (and some teams) work under mandates to “use AI.” While I am a fan of these two functions for the current LLMs: The ability to create fast prototypes for human assessment and judgment. And the ability to gain new insights into you, your team’s, or your organization’s data. (This often requires a
I’ve been thinking and experimenting a lot about how to use the various LLMs, both in my work and with my clients. I keep seeing a familiar trap: that managers think the gating factor in product development is the speed of coding. But that’s not true. The gating factor is the speed of understanding the
Many of my management clients tell me, “time is money.” That is only partially correct. Once you decide to invest a dollar, that dollar has the same value as any other dollar. Instead of focusing on the expense of a dollar, look for the value that dollar can return. (Because no one ever knows how
I said earlier in this series that no one cares about how “agile” your team is. Or the kind of “agile” your team professess to be. Managers do care about agility: the ability to respond quickly to a changing or changed environment. And that depends on where your team has delays. That’s why value stream
In Part 1, I wrote about what the value stream map looked like for expert-focused “cross-functional” teams. In Part 2, I discussed cooperative teams that have working agreements on when to do code review or make other decisions as a team. While those teams exhibit somewhat more agility, cooperative teams are still not collaborative. So
In Part 1, I wrote about what the value stream map looked like for expert-focused “cross-functional” teams. While those teams are cross-functional, they are not collaborative. However, these expertise-focused “teams” are not the only type of non-collaborative agile teams. There are also cooperative teams. Cooperative teams still tend to work sequentially, focused on each person’s
We talk about cross-functional agile “teams” as if they are the norm. That’s what I show in this image: some responsible person creates a ranked backlog that the cross-functional, collaborative team works on. That team delivers increments of value on a regular basis. At some point, the team will demo their work and retrospect on