Substance Versus Cargo Cult in Consulting Delivery

Consulting work often ends with a polished artifact: a report, a set of recommendations, a slide deck. The artifact can look like the completion of the job. This article is about a distinction that the course module draws between two ways of delivering consulting work. The first is the document-producing default, which the module says is how the large consulting firms usually operate. Its output tends to be documents, reports, and recommendations. The second is substance, the working output that the forward deployed engineer (FDE) approach discussed in this module is meant to deliver.

A natural question follows from that description. Is the default the whole story, or can a group inside one of these firms break from it? The source answers that exceptions do exist. Certain practices inside the Big Four have made real attempts to bring the substance into their work. The rest of this article follows one thread: why those exceptions are real, why they remain pockets rather than the rule, and what that means for how we judge them.

To understand why an exception is hard to sustain, start with what surrounds it. The source names three forces inside the firm. Default incentives reward what the firm already rewards. Billing models shape what work gets paid for and how it is paid for. Partner-track structures determine what kind of work advances a person's career. Each of these forces, by its own logic, points toward the document-producing motion.

The important point is that the three forces are not independent. Together they form a single pull, and that combined pull is the baseline against which any exception has to be measured. Follow the trace in the diagram below. Each lever feeds into the document-producing motion, and that motion in turn is what the firm's structures reward. A substantive practice therefore has to work against all three at once, not against one isolated rule.

The source locates the exceptions in specific practices, usually within AI or applied technology groups. These are the parts of a large firm where the work sits closest to building and deploying technology, which is where the substance of the FDE approach has its most natural home. The source is careful on this point: the exceptions are not described as the firm's core consulting units. They are the groups that have made genuine attempts to import the substance.

The source also makes a point about people. These practices are often led by senior partners who came from product backgrounds rather than consulting backgrounds. The hierarchy below shows how a single exception sits inside the firm: the firm operates a default delivery model, and within it, specific practices in technology groups are where the exceptions tend to appear and where product-background partners are often found leading them.

Set the two approaches side by side. The default produces documents, reports, and recommendations. The substantive approach aims at working substance, which the source describes as the output the FDE approach is meant to deliver. The source also gives a sense of the standard each approach implies. A partner with a product background tends to judge work by whether it produces something that functions, which the source describes as closer to the substantive standard than the document standard.

The distinction between a contained exception and a shift in the firm-wide default turns on the same pull described earlier. A contained exception is a practice that succeeds while the three forces still point toward documents for the rest of the firm. A shift in the default would mean those forces themselves were changing. The source does not give a checklist of evidence for telling the two apart, so keep the claim at the level it supports: the exceptions are real, they are pockets, and their survival depends on individual partners who keep choosing their own course against the surrounding pull.