Alfred Hitchcock was, by the middle of his career, one of the most recognisable directors alive. He still had to fight for control of every picture, and Greene is specific that it was every picture:
In almost every film Alfred Hitchcock made, he had to go through the same wars, gradually wresting control of the film from the producer, the actors, and the rest of the team.1
That is worth sitting with, because it says something about how authority actually works in collaborative production. A film has a producer who has money, actors who have leverage, a studio that has final cut, and a director. The formal structure does not deliver control to the person whose vision the thing is supposed to express, and no amount of reputation changes the structure.
Greene picks the writer relationship as the miniature:
His struggles with screenwriters were a microcosm of the larger war.1
The problem is stated exactly, and it is a constraint rather than a preference:
Hitchcock always wanted his vision for a film to be exactly reflected in the script, but too firm a hand on his writer's neck would get him nothing except resentment and mediocre work.1
This is the specific difficulty of controlling creative labour, and it does not arise in most command situations. You can order a soldier to hold a position and the position gets held. You cannot order a writer to produce good work, because the thing you want requires their investment, and coercion removes the investment while leaving the compliance.
So the direct route is not merely unpleasant. It is self-defeating — you would win the argument and receive worse pages.
So instead he moved slowly, starting out by giving the writer room to work loosely off his notes, then asking for revisions that shaped the script his way.1
Two moves, and the order is the whole method.
Room first. The writer works loosely off notes. Not to a specification — off notes, with latitude. The result is genuinely theirs in a way that matters for how they will behave later.
Revisions second. Each request is small, local, defensible, and about this scene rather than about the direction of the whole. No individual revision is a claim on authorship. The aggregate is.
And then the trap closes, in the sentence that makes this a fait accompli rather than good collaboration:
His control became obvious only gradually, and by that time the writer was emotionally tied to the project and, however frustrated, was working for his approval.1
Emotionally tied to the project. The latitude at the start was not generosity; it was what produced the investment that made leaving unthinkable by the middle. And working for his approval is the endpoint — the writer is not merely complying, they now want Hitchcock to be pleased.
A very patient man, Hitchcock let his power plays unfold over time, so that producer, writer, and stars understood the completeness of his domination only when the film was finished.1
Only when the film was finished. There is no moment at which anyone could have objected, because at every point the accumulated position was a little more than it had been and the current increment was trivial.
Greene's general statement of the principle:
To gain control of any project, you must be willing to make time your ally. If you start out with complete control, you sap people's spirit and stir up envy and resentment.1
So begin by generating the illusion that you're all working together on a team effort; then slowly nibble away.1
The illusion. Greene's word, and he does not soften it. The collaborative opening is presented as a device rather than a phase.
And then the chapter's coldest line, which arrives without warning:
If in the process you make people angry, do not worry. That's just a sign that their emotions are engaged, which means they can be manipulated.1
There is a real problem sitting in the middle of this case, and it is worth naming because the technique is otherwise so usable.
Everything described — give collaborators latitude early, respond to what they produce, shape through iterative revision rather than up-front specification, be patient — is also an accurate description of good creative direction. It is what a competent editor, showrunner or design lead does, and it works for the reason Greene identifies: people invest more in work they had room in, and shaping is cheaper than commanding.
Greene's framing converts that into a manipulation by adding two things: the word illusion, and the claim that anger is useful because engaged emotions are exploitable.
But nothing in the observable behaviour changes between the two readings. The same sequence of notes, latitude and revisions describes a director who wants the best film and a director who wants undisputed authorship. Which suggests the distinction is not in the method at all — it is in whether the collaborators' contribution survives into the finished thing. That is checkable afterwards and invisible during, and it is the only test this case supports.
One more feature separates this from ordinary impatience, and it is the reason Greene calls him a very patient man.
The technique needs a long enough container that no single increment can be compared to the one before it. Over three days, a series of revision requests is visibly a series. Over four months, each one arrives in its own context — a new scene, a new problem, a conversation about something else entirely — and the comparison never gets made.
Which means the strategy has a minimum duration below which it simply does not work, and the duration is set by the collaborator's memory rather than by the amount of control being acquired.
That gives a defensive tell worth having: if you cannot remember what the original brief was, you are far enough into one of these that the answer has stopped being retrievable. Hitchcock's writers understood the completeness of the domination only when the film was finished — not because it was concealed at the end, but because by then there was nothing left to compare it against.
You need control of something that requires other people's genuine investment, and you cannot get it by asking.
Start by giving real latitude, and mean it. The room at the beginning is not a feint you can fake — it has to produce work that is actually theirs, because everything downstream depends on their being invested. A brief so tight that nothing of theirs survives produces exactly the resentment and mediocrity Greene warns about, and it produces it immediately.
Then shape by revision rather than by specification. Each request local, concrete, about this scene or section, and defensible on its own terms. Nobody argues about the direction of the whole project until someone frames a request as being about the direction of the whole project.
Then be slower than feels comfortable. Hitchcock's method takes an entire production. The reason it works is not subtlety — it is that at no point is the increment large enough to be worth a fight, which is Strategy 29 operating inside a collaboration.
And then the part Greene does not include, which the case needs. Decide in advance whether their contribution is going to survive. If it is, everything above is ordinary good direction and the investment you generated is real. If it is not, you are running a method whose entire mechanism is producing an emotional commitment you intend to spend — and it works once per collaborator, because the finished film is the disclosure.
And from the other chair: if you are the writer, the tell is not the volume of notes. It is whether anything you originated is still recognisable at the end. That question is answerable at the midpoint if you ask it, and almost nobody does, because by then the investment is doing its work.
Hitchcock's meticulous pre-planning, his conflicts with producers and studios, and his method of working with writers through iterative drafts are well documented across his career. [POPULAR SOURCE]
Greene's causal framing is stronger than the behaviour supports. The illusion that you're all working together is asserted, not evidenced. Hitchcock's actual working relationships with writers were long and repeated — several worked with him more than once, which is not the pattern you would expect from a method that spends collaborators. The observable facts fit "an exacting director who shaped work iteratively" at least as well as they fit "a manipulator running a fait accompli", and the chapter needs the second reading. 🚩 SINGLE SOURCE on the intent.
The anger line is the case's real problem and it is unqualified. If in the process you make people angry, do not worry. That's just a sign that their emotions are engaged, which means they can be manipulated. That is a general licence, offered without limit, in a passage otherwise about craft. It also does not follow from anything in the Hitchcock material — nothing in the described method requires making anyone angry, and the sentence reads as the chapter's thesis being pushed onto a case that did not generate it.
And the strategy's ethics turn entirely on a variable the chapter never mentions: attribution. A director who shapes a script through revisions and credits the writer is doing one thing; a director who does the same and takes the authorship is doing another. Greene's account is indifferent between them, which is the same indifference the whole book shows toward whether anyone else ends up better or worse off — and it is especially conspicuous here, because unlike a battlefield, a film set has a formal mechanism for recording who contributed.
Against Strategy 29: The Fait Accompli Strategy this is the chapter's only case at the scale most readers actually operate at. De Gaulle and Frederick take countries; Hitchcock takes control of a project, over a few months, from people he has to keep working with afterwards. That last constraint is the interesting one and the chapter does not register it — neither de Gaulle nor Frederick had to collaborate with the party they were nibbling from once the nibbling was done.
Against Hitchcock and the Detached Buddha this is the fourth Hitchcock treatment of the build, and the two are the same fact from opposite ends. That page holds Strategy 3's reading — total pre-production control as the source of on-set calm, the Vertigo shooting-script discipline. This page holds how that control was acquired. Together they close a loop neither closes alone: the famous serenity was downstream of a months-long acquisition of authority that nobody was in a position to contest, and Greene presents the calm as temperament in one chapter and the seizure as technique in another.
Against Divide and Rule and the Central Position this is the fifth Hitchcock appearance, holding "all roads led to Hitchcock" as a structural position. Read across all three: he acquired authority incrementally, arranged the production so that everything routed through him, and was therefore calm. One integrated operating method, distributed by Greene across three chapters on self-mastery, divide-and-conquer and piecemeal conquest.
Against Strategy 5: The Command-and-Control Strategy there is a direct convergence Greene half-makes: he introduces this case by noting the fait accompli is often the best way to take control of a project that would be ruined by divided leadership. That is Strategy 5's thesis, arriving twenty-four chapters later as the justification for a technique.
Psychology → Latitude manufactures the commitment that later prevents leaving. The writer works loosely off notes, becomes emotionally tied to the project, and ends up working for Hitchcock's approval even while frustrated. The vault's Cognitive Dissonance holds the mechanism: effort invested in something reorganises your evaluation of it.
The insight the pairing produces: the freedom given at the start is not a concession that is later withdrawn — it is the instrument that makes withdrawal survivable, because the investment it generated is what keeps the collaborator in the room once the control becomes visible. This is why the sequence cannot be reversed: a director who specifies tightly and then loosens gets compliance followed by indifference, while one who loosens and then tightens gets ownership followed by frustrated loyalty. And it identifies the defensive question precisely, which is not "how much freedom do I have?" but "how much of what I made is still here?" — the first is highest exactly when it matters least.
Behavioral mechanics → Increments below the objection threshold, inside a relationship. Each revision request is local and defensible; the aggregate is authorship. Set that beside Conservatism as the Exploited Constant — people accept small losses because contesting them costs more than absorbing them.
Together they produce a claim about collaboration that neither gives alone: in an ongoing working relationship the objection threshold is higher than in an adversarial one, because raising a small point costs you relational capital as well as time — which makes collaborators easier to nibble than opponents, not harder. An adversary contests early and cheaply. A colleague absorbs, because each individual objection would make them the difficult one. Which means the fait accompli is most effective precisely where trust is highest, and the practical defence is unglamorous: raise the pattern rather than the instance, once, early, framed as a question about direction — because that is the one framing the method has no small-increment answer to.
The latitude at the beginning is not generosity and not a feint — it is the mechanism, because the investment it produces is what keeps the collaborator working for your approval once the control becomes visible. Which means the sequence cannot be run in the other order, and the only real test of what was happening is whether anything they made is still in the finished thing.