As I read the article, I had the impression that what the author was describing was the kind of activities that they would batch, for example, reviewing pull requests.
That sounds more like part of the work involved in manufacturing software than what you refer to as problem solving / analysis.
What if the author decided to batch the processing of pull requests so that they processed all of their outstanding PRs once per week?
Would that be a good thing for the rest of the team? What if you're trying to deliver an important fix and your PR is stuck in queue waiting for Friday to roll around before the author gets around to review it?
The late Colonel John Boyd made important observations as to the competitive advantages that accrue to organizations that can move quickly and well-enough to accomplish the mission.
I certainly could be wrong, but batching everything, as the author seems to be suggesting, sounds like a recipe for an organization that is slow as molasses in January, but also populated with people who see themselves as being highly efficient.
That sounds more like part of the work involved in manufacturing software than what you refer to as problem solving / analysis.
What if the author decided to batch the processing of pull requests so that they processed all of their outstanding PRs once per week?
Would that be a good thing for the rest of the team? What if you're trying to deliver an important fix and your PR is stuck in queue waiting for Friday to roll around before the author gets around to review it?
The late Colonel John Boyd made important observations as to the competitive advantages that accrue to organizations that can move quickly and well-enough to accomplish the mission.
I certainly could be wrong, but batching everything, as the author seems to be suggesting, sounds like a recipe for an organization that is slow as molasses in January, but also populated with people who see themselves as being highly efficient.
What am I not seeing?