Field Manual for Modern Corporate Sabotage
Fascomachy · Applied
The art of invisible friction.
Bottom line up front
- The mechanism. Digital work is engineered to remove friction. Every sync, ticket, and dashboard exists to shave resistance off the transfer of your attention into someone else’s margin. Friction is the last input a worker still controls.
- The method. Don’t break the machine — overfeed it. Follow every process exactly, consult every stakeholder, document every decision, until the organization is crushed under the weight of its own compliance.
- The constraint. It has to survive an audit. Refusal reads as insubordination and ends in termination. The identical output, delivered cheerfully and on process, reads as diligence and ends in a promotion. The difference is not in the work. It is in the paperwork.
On this page
- Bottom line up front
- A procedural note
- The premise
- 1 · Communication and alignment
- 2 · Project management and Agile workflows
- 3 · Leadership and middle management
- 4 · The individual contributor
- Before the system of record
- The limit of the method
- Field exercises
- A closing note on the list
- Sources and further reading
Evidence tier: Operational. Decision procedures and tactics for the reader. Its tests check the situation, not the doctrine. Evidence Protocol · Theme Explorer
A procedural note
Fiction. The list is invented; the migration rule is not.
At some point in the last eighteen months your name was added to a list.
The list has no owner. The owner field was made mandatory during the migration, and rows with a null owner were skipped, so the list was not migrated, which means it does not exist, which means it cannot be amended. It is still consulted at the end of every quarter.
You will not be told which list. Requesting the name of the list requires the name of the list. There is a process for this. The process is sound. It was designed by people acting in good faith, every one of whom has since moved into a different function, and the function itself was dissolved in a reorganization that is still, in a strictly technical sense, underway.
This is not a warning. Nothing is going to happen. Nothing will ever happen. All there is, all there ever is, is a buzzing between the eyes. That is the hum.
The premise
In 1944 the United States Office of Strategic Services issued the Simple Sabotage Field Manual to civilians in occupied Europe. Its most famous directives were not about explosives. They were about meetings: insist on channels, refer matters to committees, haggle over precise wordings. The directives survive because they describe a normal Tuesday.
The contemporary assembly line is not built from steel and steam. It is built from calendar invites, Slack channels, and Jira tickets, and it runs on a single principle: reduce the cost of moving your attention onto someone else’s balance sheet. Every tool sold into the modern workplace makes some part of that transfer cheaper.
Nobody built this. That is the first thing to understand about it. There is no office where the decision was taken to fill your week with syncs about syncs. There is no signature at the bottom of the memo. There is no memo. The apparatus assembled itself out of reasonable individual choices made by people who have since left the company, and it runs now without an author, which is why you cannot appeal to it. You can raise a concern. There is a process for this. Raising a concern is a process. It has an owner, and the owner is on leave, and their delegate is the person you wanted to raise the concern about. This is not a malfunction. The process is working. The process is sound. A process that produced a different result would be a different process, and there is no procedure for requesting one.
Direct refusal fails here, and it fails predictably. Capitalist realism, as Mark Fisher put it, makes it easier to imagine the end of the world than the end of capitalism; an organization has no vocabulary for a worker who simply says no, so it reaches for the vocabulary it does have — performance management, and then the door. The alternative is over-identification. The corporation craves order. Supply so much order that the system suffocates under its own procedural weight.
Form enacts meaning. The resistance is the bureaucracy.
What follows is a taxonomy of strategic entropy, sorted by where you sit. Four directives. Each ends the same way.
1 · Communication and alignment
Taken here: decision speed. Given back: consultation. Reads as: rigour.
The organization’s scarcest resource is a decision that sticks. Every directive below ensures a decision is reached only after every available party has been exhausted, and then reached again.
The “let’s sync” protocol
Never resolve asynchronously what can justify a meeting. When a colleague asks a simple question in writing, reply: “This feels a bit nuanced — let’s jump on a quick 30-minute sync so we’re fully aligned.” Ninety seconds of reading is now an hour of collective attention. You have done this while appearing to care about clarity, which is the only part that goes on the record.
Weaponized inclusion
Stall any initiative by observing that not all stakeholders have been consulted. Refuse to proceed until marketing, legal, HR, and the intern have weighed in. Frame the obstruction as a commitment to cross-functional democratization. The objection is unanswerable: nobody in a modern organization can argue on the record for consulting fewer people. Note also that the stakeholder list is maintained by a stakeholder. Removal from it requires a request to the group. The group must first be convened. Convening the group requires the list. The list can only be determined by the group.
The vocabulary of paralysis
Deploy management jargon to strip sentences of actionable verbs. Instead of “we should build this feature,” offer: “we need to holistically evaluate the bandwidth required to synergize this deliverable with our Q3 OKRs before we commit to an execution paradigm.” The sentence contains no instruction. It cannot be acted on. It also cannot be criticized, because it is indistinguishable from the language of the people who will assess you.
The sponsor loop
Cc the executive sponsor on every routine approval. Frame it as visibility. The cost lands squarely on the calendar of whoever set the target, and no one senior enough to object has a defensible reason to say they want less oversight of their own initiative.
None of this appears anywhere as obstruction. It appears as four people who wanted to get it right. The initiative is in its fifth week of alignment and has not yet been described. Nobody objected.
2 · Project management and Agile workflows
Taken here: throughput. Given back: precision. Reads as: quality.
Agile methodology is built to maximize output under uncertainty. Its rules are therefore its weakness: applied with absolute literalism, the ceremony consumes the work it was designed to schedule.
Story-point haggling
During sprint planning, dispute the estimate on every task. Argue — with visible good faith — that a two-point ticket is really a three, owing to unforeseen technical debt. A fifteen-minute planning session becomes a two-hour ordeal, and you have spent it demonstrating exactly the estimation discipline the framework asks for.
The acceptance-criteria trap
Refuse to start any task until the acceptance criteria are drafted with impossible rigour. The criteria cannot be finalized until the work is scoped. The work cannot be scoped until the criteria are finalized. Both statements are true. Both are now in the ticket. The ticket is assigned to you, which means you are blocked, which means the ticket is not yours, and a ticket that is not yours cannot be escalated by you.
Micro-ticketing
Break simple tasks into an absurd number of sub-tasks. Asked to write a report, raise separate tickets for outline report, draft introduction, select typeface, and review formatting. Update their status constantly. The board fills with motion, the notification volume climbs, and your throughput — measured in tickets closed — is the best on the team.
The velocity chart is up. The burndown is clean. The feature does not exist, and the reason it does not exist is documented across eleven tickets, every one of them closed. Nobody objected.
3 · Leadership and middle management
Taken here: your team’s surplus. Given back: process. Reads as: care.
If you hold a managerial role, you control the one variable an individual contributor cannot: how much of your team’s capacity ever reaches the work. Use proximity to power to shield the people below you from producing it.
Mandatory wellness
Schedule structured team-building and wellness check-ins during peak productivity hours, and make attendance non-negotiable. The destruction of deep work is thereby recorded as an investment in psychological safety. No one will decline, because declining looks like a symptom.
The committee void
Never make an executive decision. Refer every choice, however trivial, to a newly formed exploratory committee, and require a forty-page deck before any action is authorized. I recommend the Working Group on Working Group Effectiveness. It has met eleven times. Its terms of reference are being drafted by a subcommittee, which is waiting on the terms of reference. The Working Group meets on the second floor of a building the company stopped leasing in 2024. Entry requires a badge issued by the Working Group. The scanner is not the obstacle. The committee’s calendar is.
The vanished approval
The approval exists. It was granted in March. Nobody can produce it, because the person who granted it has moved to a different reporting line, and the new line does not recognize approvals issued under the old one. Ask, in writing, for confirmation that the approval still stands. The request will be routed to the person who needs the approval in order to answer it. It is routed there by a colleague in Enablement whose title has changed three times, whose reporting line nobody can draw, and whose sign-off is required regardless. Work stops. No one has stopped it.
Hyper-documentation
Require your team to document every process, interaction, and minor expense. When the documentation is complete, require it reformatted into a different platform to optimize future scalability. Documentation is the one demand that cannot be refused by an organization that has spent a decade complaining nothing is written down.
Your team has never been better looked after and has not shipped since April. The engagement scores are the highest in the division. Nobody objected.
4 · The individual contributor
Taken here: the hours nobody paid for. Given back: literalism. Reads as: conscientiousness.
The gap between what you are paid for and what you supply is the whole of the employer’s margin on your labour. Close it, slowly, and cultivate an air of earnest bewilderment toward corporate technology.
The perennial update
When called on to share your screen, look steadily at the webcam. Let a full seven seconds pass before offering: “Zoom is forcing an update.” Or the VPN. Or the intranet. Nobody has ever successfully disputed a VPN.
Siloed deference
Police your role boundaries strictly. When an issue sits adjacent to your responsibilities and would take four minutes to solve, decline it: “That’s DevOps architecture — I want to respect their ownership of that space.” Territorial refusal, phrased as respect, is unfalsifiable.
The perfectionist delay
Withhold deliverables on the grounds that they have not yet met your standard. Polish the insignificant — the hex codes in a chart, the alignment of a footer — while the deadline passes. Lateness recorded as a commitment to brand integrity is not lateness. It is judgment.
You are meeting expectations. You have always met expectations. Meeting expectations is both the ceiling and the floor, and you have located the one position in the organization where the two touch. Nobody objected.
Before the system of record
![]()
Fiction. After Kafka, “Before the Law” (1915). The system, the contractor and the gatekeeper are invented.
Before the system of record there stands a gatekeeper. To this gatekeeper comes a contractor carrying a laptop, a paper cup with his name misspelled upon it, and a request to see the maintenance history of the machine he has been hired to repair. The machine has stopped. The gatekeeper agrees that this is serious. Access, however, cannot be granted at this time.
The contractor asks whether it might be granted later. It is possible, says the gatekeeper, but not now. He says this with regret, and the contractor is reassured by the regret because it suggests that somewhere behind the gate there exists a person whose authority has caused it.
The contractor is given a form. The form requires the name of the system owner. The gatekeeper is not the system owner. He is the first of many gatekeepers, and even he cannot bear to look upon the third, whose calendar displays no openings and whose automatic reply has acquired the force of weather. The contractor writes unknown. The form rejects uncertainty in a required field.
He opens a ticket to learn the owner’s name. The ticket requires an owner before it can be routed. The gatekeeper advises him to request temporary access so he may consult the ownership directory. Temporary access requires proof that permanent access is pending. Permanent access requires the owner’s approval. The contractor writes these conditions in a notebook because the system does not permit notes until access has been granted.
At first he returns home each evening. Then the machine’s failure is declared operationally urgent, and he is asked to remain available near the gate. A chair is provided. The chair has one short leg and belongs to Facilities, which asks him not to modify it. He folds a copy of the access policy beneath the leg. This is the first useful thing the policy does.
Days pass. The contractor attends meetings about the delay. His presence is required because he is the requester, although he cannot answer questions about the system because he remains outside it. Minutes record that the requester supplied no new information. The absence of new information is entered as a dependency. The dependency is assigned to him.
He learns the gatekeeper’s children’s names and asks them to intercede. They do intercede, and it changes nothing. He learns the birthdays of analysts who have never opened the ticket, the dietary restrictions of a manager who has declined every invitation, and the preferred spelling of a program that no longer exists but retains approval authority because nobody has completed the form required to abolish it.
The machine remains stopped. Other contractors arrive to work around the stoppage. They build a temporary process with spreadsheets, private messages, and a shared drive called FINAL. The process becomes essential. Because it is essential, it cannot be altered without a change request. The original machine is reclassified as legacy infrastructure, which makes the contractor’s request both less urgent and more sensitive.
Years pass. The contractor’s security photograph is renewed several times, each image displaying a man less recognizable to the previous image. His badge continues to identify him as TEMPORARY. New gatekeepers arrive and ask him how the gate works. He explains the forms, the queues, the owner field, and the difference between a request being rejected and a request being returned for clarification. People begin sending newcomers to him. He is not granted access, but he is copied.
A review finds that his ticket has remained open longer than any other. This is praised as evidence of continuity. The gatekeeper proposes closing it and opening a new one under the current process. The contractor refuses. He has come to believe that the age of the ticket proves the justice of his request. The ticket is now the only record that he was ever asked to repair the machine.
In his final years he no longer knows whether he is speaking aloud or only drafting. His eyesight fails. The gatekeeper brings him a larger monitor, but the contractor cannot sign for it because equipment assigned outside the system of record has no recognized custodian. The monitor remains in its box beside the chair.
At the end, hearing that a quarterly review is approaching and fearing that his silence may be interpreted as consent, he asks one last question: In all these years no one else has come to request access. How can that be?
The gatekeeper, who can see that the man is dying and whose compassion is genuine within the authority available to him, bends close. No one else could be granted access here, he says, because this access was intended only for you.
I am going to close the ticket now.
The limit of the method
Four times now a directive has closed on the observation that nobody objected. That is the mechanism working exactly as described. It is also the bill.
The contractor at the door ran every directive in this manual. He ran them faithfully and without malice, and the outcome was identical. From the outside—and, given long enough, from the inside—deniable sabotage and patient defeat become the same behaviour. The constraint that makes the method survivable is the constraint that makes it unverifiable.
Somewhere in your building is a person who took this job because they wanted to be good at something. They are on the Working Group on Working Group Effectiveness. They are taking the minutes. They will circulate the minutes, and no one will read them, and next month there will be more of them, and this will continue until they are fifty-eight.
That person is not the enemy. That person is the casualty. So it goes. It does not have to.
Two constraints follow from that, and they are what keep this manual from becoming the thing it is mocking.
Friction must travel upward. A tactic that costs your peers their afternoon and costs the firm nothing is not resistance; it is a tax on the people with the least power to avoid it. David Graeber’s point in Bullshit Jobs is that the misery of pointless work is already distributed horizontally. A manual that shrugs at that inherits it. Every directive above was chosen because its cost lands on a calendar belonging to someone who set the target.
The saboteur pays too. Days spent generating entropy are still days spent. The method protects your energy from extraction. It does not convert those hours into anything you would want. What it buys is time, and time is only worth taking if you have decided in advance what it is for.
If you have not decided, you have not built a resistance. You have just been doing your miserable work slowly.
Field exercises
- Audit your calendar. Identify three tasks currently resolved asynchronously that could defensibly require a multi-stakeholder meeting. Convert one.
- Draft the phrasebook. Prepare a set of jargon-dense, non-committal responses for your next sprint planning or quarterly review, and rehearse them until they sound sincere. Sincerity is the entire delivery mechanism.
- Survey the tooling. Review your project management software for places where a mandatory compliance check, an approval gate, or a documentation requirement can be introduced under the banner of quality.
- Name the casualty. Identify the person in your organization who absorbs the friction you are about to generate. If you cannot name them, you have not finished planning.
A closing note on the list
You will not be told which list.
You were not told at the start of this document either. You have now verifiably read to the end of it, which has been recorded.
Nothing is going to happen. Nothing but the Hum.
Sources and further reading
- United States Office of Strategic Services (1944). Simple Sabotage Field Manual. Declassified; the founding text of the genre.
- Fisher, M. (2009). Capitalist Realism: Is There No Alternative? Zero Books.
- Graeber, D. (2018). Bullshit Jobs: A Theory. Simon & Schuster.
- Kafka, F. (1915). “Before the Law” (Vor dem Gesetz), later incorporated into The Trial (1925). Trans. Mitchell, 1998, Schocken. The parable above is a direct transposition.
- Scott, J. C. (1985). Weapons of the Weak: Everyday Forms of Peasant Resistance. Yale University Press.
- Braverman, H. (1974). Labor and Monopoly Capital: The Degradation of Work in the Twentieth Century. Monthly Review Press.
- Deleuze, G. (1992). “Postscript on the Societies of Control.” October, 59, 3–7.
- Zuboff, S. (2019). The Age of Surveillance Capitalism. PublicAffairs.