Some company is buying your company (or vice versa). Why? They claim it’s “Economies of scale,” and the combined organization will save money by centralizing “overhead” and flattening management. You know who that “overhead” is: the people who support the business, such as finance and HR. And, the managers. Worse, the new management asks managers […]
Many of my middle-management and senior leadership clients want certainty about future work. That’s one of the reasons they create huge backlogs and long roadmaps. Yet, even those backlogs and roadmaps don’t offer certainty. One of these managers said, “I have so much uncertainty and ambiguity. I feel as if I can’t make a good,
Several of my trusted advisor clients have asked this question, “Why do I need to choose between effectiveness and efficiency? Why can’t I have both?” A great question. I recommend they start with effectiveness. That occurs when they say yes to just the work they need now, to reduce the organizational WIP. Start with managing
For years, we’ve used several metaphors to describe software product development: People-based metaphors, such as: Man-weeks for all the humans working on a project or a product. FTE for full-time Equivalent (as in human beings!) “Resources” instead of the words: people, or human beings Construction metaphors, such as: build, which describes how we organize and
Several people on LinkedIn commented on my post, Want Better and Faster Results? Increase Team Size and Reduce WIP. They wondered if adding more people to a small team would violate Brooks’ Law. As with all good questions, the answer is “It depends.” It depends on how your lifecycle manages feedback loops and learning, how
For years, I’ve advocated relatively small teams. Why? Small teams can more easily learn—faster and together. All because they have fewer communication paths. I was only partially right. Smaller teams tend to have lower WIP (Work in Progress). Even if a 5 to 7-person team falls into the Everyone Starts Their Own Story trap (see
If you’re trying to use an agile approach, what do you care about in terms of finishing: That the team finish the work, regardless of the personal or team cost? That you know who did what, so you can reward them? Or that the team completed the work, without undue stress and strain? (also called
Tim, a C-Level leader, loves his skip-level meetings. He feels the meetings offer him a chance to connect with people he doesn’t normally see. They get to talk about whatever the other person wants. Sharon, a different C-Level leader, never conducts skip-level meetings. She feels that those meetings might cause her managers to feel unsafe,
In preparation for a recent consulting engagement, the client, Tim, said, “I want you to track meeting attendance. If people don’t come to your meetings, I want to know why.” Tim was worried about the cultural changes we needed to discuss for the client’s ability to be more effective. Tim had good reasons to worry
Too many managers don’t know how to manage remote people. Worse, those managers, or their organizations, don’t trust people to do a good job. The organization installs spyware to see if people are working. That’s classic Theory X behavior. However, people are smarter than the spyware. Many of these spied-upon people have installed mouse (and