Summary

This book made one argument, repeated from several angles: reengineering starts at the top, with what a company is actually for and what it’s genuinely good at, and only afterward, several steps downstream, does it produce a headcount number. Skip the first steps and go straight to the number, and you get restructuring wearing reengineering’s name — the same work, thinner staffing, and a slow rebuilding of the capacity you just cut.

The five questions in the second chapter are the whole method, in miniature: what are the firm’s goals, what are its real advantages, what processes and outputs follow from those, what would the ideal version of those processes look like, and how do you get from here to there. Meridian Bank was one small, honest answer to all five, applied to one process instead of an entire company, because a company’s worth of process redesign doesn’t fit inside one worked example and shouldn’t have to, to make the point.

What Meridian’s story doesn’t show on its own is the part covered in the chapter after it: that none of this is free of cost to the people living through it, and that the cost isn’t only moral. It’s operational. The best people leave first, whether or not their own job was ever at risk. The people who could tell you honestly what their work is worth have a reason not to. The managers who could eliminate work that no longer matters often won’t, because the person doing it is someone they know. And the old process still has to run, staffed adequately, until the new one actually replaces it. A reengineering effort that only gets the analysis right and ignores all of that isn’t finished. It’s just started.

What Tends to Go Wrong

Most of the failures I’ve watched share a short list of causes, and none of them are exotic:

• Mistaking restructuring for reengineering — cutting headcount against an unchanged process and calling it done.
• Letting the CEO delegate the diagnostic instead of owning it, the way Thorndike’s capital allocators never delegated the decision of what businesses to be in.
• Leaving the elimination decision with the manager closest to the person affected, instead of someone with the authority and the distance to make the harder call — maybe the outside consultant I watched do exactly that, decades ago.
• Underestimating the transition itself — treating the human and operational risk as a footnote to the plan rather than a part of it.
• Running out of patience or attention before the ideal state is actually reached, and settling for whatever the org chart looks like partway through.

None of this is a reason to avoid the work. Companies that are genuinely worth saving, and companies in genuinely good shape looking to widen their lead, both eventually run into a process that’s outlived its usefulness. The question was never whether to reengineer it. It’s whether you’re willing to do the first-principles version — the harder one — or the easier one that just cuts the number and calls it a strategy.