The Document-Producing Motion in Large Firms
Exceptions to the document-producing default do exist within the Big Four, usually in specific practices within AI or applied technology groups.
Try it: try / except / else / finally
How an exception jumps out of a try block to the first matching except clause, when else runs, and why finally always runs.
How it works
- Statements in try run until one raises an exception; the rest of try is skipped.
- Python checks the except clauses in order and runs the first one whose type matches.
- If nothing was raised, the else block runs instead.
- finally runs in every case.
Default run (9 steps): Call safe_divide('4'). … Return 25.0. Output was: Worked: 25.0 / Done.
Simplified: One fixed function; int() and / are modelled exactly (including how Python prints floats), but nothing is executed as Python.
Loading the simulation…
Why an Exception Needs a Baseline
Most of this module describes the large consulting firms as they usually operate. Their delivery model tends to produce documents, reports, and recommendations rather than the working substance that the FDE approach is meant to deliver. A natural question follows: is that default the whole story, or can a group inside one of these firms break from it?
The source answers that exceptions do exist. Within the Big Four, certain practices have made real attempts to bring FDE-style substance into their work. The exceptions are real, but they are pockets rather than the rule. To judge a pocket fairly, you first need a clear picture of the pull it is swimming against. This article traces that pull, shows where the pockets tend to form, and then asks what an exception can and cannot prove.
What do you think happens?
Suppose one practice inside a Big Four firm produces real, working engagements. Does that mean the firm's default delivery model has changed?
Reveal answer
No, an existing exception does not by itself mean the default has changed.
The source states that a substantive practice can produce real engagements, but its existence does not mean the firm's default has changed. Whether the default shifts depends on partners willing to swim against the firm's current.
Three Forces Pulling Toward Documents
To see why an exception is hard to sustain, start with what surrounds it. The source names three forces inside the firm: default incentives, billing models, and partner-track structures. Each one, by its own logic, points toward the document-producing motion. Taken together they form a single pull, and that pull is the baseline against which any exception has to be measured.
Default incentives are the rewards the firm already gives for the work it already values. Because the firm rewards what it already does, an incentive system built around that work keeps pointing people back toward it.
Billing models determine what work gets paid for and how. The source says billing models shape what work gets paid for and how, which means the shape of billing feeds directly into the kind of output a team is inclined to produce.
Partner-track structures determine what kind of work advances a person's career. If the route to partner rewards document-producing work, then the people who reach senior roles are the ones who have already learned to produce documents.
The three forces are not separate rules that happen to agree. Each one supplies a reason for the same behavior, so an individual trying to do substantive work meets resistance from the incentives, from the billing structure, and from the career path at once.
How the Forces Reinforce the Default
The concept map below shows the three forces feeding into the document-producing motion, and a substantive practice pushing against it. Read the arrows as the direction of pull. A change in one element, such as how partners are billed or promoted, propagates through the others because each one is tied to the same pattern of rewarded output.
The diagram makes one point clear. The substantive practice is not drawn as a force that the other three elements support. It is drawn as something that has to push against all three at once. That is the source's own description of the difficulty: every structural force in the firm works in the opposite direction, so a substantive practice must keep choosing its own course against that background.
Where Exceptions Tend to Appear
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 FDE-style substance has its most natural home. 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 reason this detail matters is that a partner whose career was built around products tends to judge work by whether it produces something that functions. That is closer to the substantive standard than to the document standard. The source does not claim that a product background guarantees substantive work. It says only that such a background is characteristic of the partners who have pushed against the default.
Default Model Versus Substantive Approach
The contrast between the two approaches is easiest to see side by side. The source describes the default as producing documents, reports, and recommendations. It describes the FDE approach as aiming at working substance. The table below uses the source's own distinctions and marks where the source is silent rather than filling in detail.
| Dimension | Default delivery model | Substantive approach |
|---|---|---|
| What gets produced | Documents, reports, and recommendations | Working substance that functions |
| What the default rewards | Incentives, billing, and partner track all point toward it | Must be chosen against the current of incentives, billing, and career paths |
| Where it tends to sit | Core consulting delivery across the firm | Specific practices, usually in AI or applied technology groups |
| Who tends to lead it | Not characterized in the source | Often senior partners from product backgrounds |
| Whether it can produce real engagements | Not the focus of the source | The source says yes, it can |
Contrasts drawn from the source. Cells marked as not characterized indicate the source does not describe that dimension.
Reading One Exception Step by Step
Judging a single substantive practice
A practice inside an applied technology group of a Big Four firm delivers a working system for a client. A colleague argues this proves the firm's default delivery model has changed. Is that conclusion supported by the source?
- 1Identify the claim
The claim is that one working engagement proves the whole firm's default has shifted.
- 2Check what the source says the exception shows
The source says a substantive practice can produce real engagements, and that its existence does not mean the firm's default has changed.
- 3Locate the deciding factor
The source says whether the default changes depends on partners willing to swim against the firm's current. The existence of one practice is not that evidence by itself.
- 4Test against the three forces
Ask whether the incentives, billing models, and partner-track structures that surround the practice have themselves changed, or whether the practice is still working against them.
The exception is real and worth noting, but the source does not support the conclusion that the firm's default has changed. The working engagement shows the pocket exists, not that the pull has been removed.
Common Misreadings of the Exception Argument
The source is careful about what an exception shows. The errors below are the ones a reader most often makes when they move from the existence of a pocket to a claim about the whole firm.
Common mistake Treating the Big Four as uniformly document-producing
Why it failsThe source states that exceptions do exist within the Big Four, so a blanket claim erases the groups it identifies.
Do this insteadDescribe the default as the usual pattern, and name the specific practices where exceptions appear.
Common mistake Assuming an exception proves the default has changed
Why it failsThe source says a substantive practice's existence does not mean the firm's default has changed.
Do this insteadTreat the exception as evidence that a pocket exists, and keep the question of the default open.
Common mistake Assuming a product background guarantees substantive work
Why it failsThe source says only that product backgrounds are characteristic of partners who have pushed against the default.
Do this insteadUse the background as a tendency, not a guarantee.
Common mistake Describing substantive work as impossible inside the firm
Why it failsThe source says the difficulty is not that substantive work is impossible; these practices can produce real engagements.
Do this insteadDescribe the difficulty as the structural pull that every substantive practice must keep working against.
What Would Count as a Shift
The source gives a clear test of what an exception does not show, but it does not list the specific indicators that would distinguish a contained exception from a change in the default. The reasoning below is therefore our own, built from the source's three forces, and should be read as a way of organizing the question rather than as a finding the source reports.
A shift in the default would look different. The forces that surround the work would themselves begin to reward substantive output, so that a practice no longer had to swim against them. This is a reasoning test rather than something the source documents, so use it to frame evidence, not as proof that such a shift is happening anywhere.
Testing Your Reading of an Exception
A partner at a Big Four firm, who came from a product background, leads an applied technology practice that delivers working systems. A commentator says this shows the firm has abandoned its document-producing model. Using the three forces and the source's point about partners who swim against the current, explain what the practice does and does not establish.
Hints
- Ask whether the practice's existence shows the default has changed, according to the source.
- Name the three forces and consider whether the practice still has to work against them.
- Remember the source's point that a product background is characteristic of such partners, not a guarantee of substantive work.
Key Takeaways
- The document-producing default is pulled into place by default incentives, billing models, and partner-track structures, which together form a single pull toward documents, reports, and recommendations.
- Exceptions to that default do exist within the Big Four, usually in specific practices within AI or applied technology groups, and they are often led by senior partners from product backgrounds.
- A substantive practice can produce real engagements, but its existence does not by itself mean the firm's default has changed; that depends on partners willing to swim against the current.
- To evaluate an exception, measure it against the three forces that surround it rather than treating a single working practice as proof of a firm-wide shift.