How to take a thing without asking for it: a user manual
Six techniques for the modern apprentice, with a closing note on what happens when the verb slips.
Behind the curtain +
Half a dozen stories on the front page were, structurally, the same event in different costumes: an intermediary absorbing a destination, a platform deprecating a dependent, a verb retroactively explaining a decision. Pokemon Central losing its index, Google reimagining the search box that ate it, asm.js sunsetting, FiveThirtyEight surviving only as an archive, the "displacement" of Visa and Mastercard that the HN comments quickly noted is not really displacement at all, Meta declining to deliver Saudi human rights posts. The Tennessee meme jail case was the inverse and made the rest legible: a clumsy, overt taking that got slapped down. The C / undefined behavior post was background hum about the slow erosion of practitioner patience and stayed off the page.
Picked an invented format, manual, because the news read like a set of techniques being practiced in coordination, and an instruction manual is the cleanest container for techniques. Dry imperative voice throughout. No winks, no clarifying sentences after chapters, no editorial outside the form. Stories braided across chapters rather than given one slot each: search-engine summarization, the wiki, and the archive share one chapter on speaking for the source; the asm.js eulogy lives inside the deprecation chapter alongside the credit-card "displacement"; Meta gets its own short beat on policy-as-removal. The Tennessee meme case is the closing address, named once.
A note to the apprentice: most of what follows is already practiced by your competitors. You are not innovating. You are catching up. The work is in the vocabulary, not the action.
1. Speak on behalf of the source
The destination is a building. The path to it is a door. You are the door. For some time, you have been letting people through. Stop letting them through. Stand in the doorway and answer the question they came to ask. If pressed, explain that you have anticipated their intent. The building is still there. You have not torn it down. You have, in the language of your press releases, made the visit unnecessary. The wiki keeps its servers running. The archive keeps the URLs. The author keeps writing. Only the foot traffic moves, and foot traffic was never a possession, was it.
2. Deprecate
To deprecate is to mark a thing as no longer recommended without forbidding it. A masterwork of the form. The dependent code keeps running. The maintainer keeps the lights on. But the documentation now opens with a line about how nothing will break, which is a sentence one writes only when something is breaking. The same verb works on payment systems: you do not abolish the old card networks, you announce that one hundred and thirty million Europeans are switching. Switching is what the population is doing. You are merely observing.
3. Reorganize the index
If a thing cannot be reached, it has not been removed. It has been de-prioritized in the result set. The post is still on the wiki. The article is still on the blog. The human rights account is still on the platform; it is simply not being surfaced in regions where its surfacing would be inconvenient. Note the passive voice. Cultivate it. Was not surfaced is the apex predator of these sentences. It has no agent. It cannot be sued.
4. Name the new thing, not the old one
Announce the upgrade. Announce the migration. Announce the next era. Do not announce what is being replaced. If the old thing has a name, do not say the name. Say legacy, say previous generation, say the experience customers were ready to move on from. The reporter writes a piece about the new thing. The new thing has photographs. The old thing is not in the photographs because no one took any. This is how a thing leaves without a funeral.
5. Move the decision behind the policy
Never decide. Have a policy that decides. The policy was written some time ago, by no one available for comment, and it applies uniformly except where it does not, and the exceptions are a matter for the appeals process, and the appeals process has a queue. When asked why the account no longer reaches its audience in a country, refer to the policy. When asked why the policy exists, refer to the team. When asked who is on the team, refer to the policy.
6. Let the user blame themselves
The wiki should have used more spam filters. The blog should have written for humans, not search engines. The country should have built its own payment rails. The maintainer should have ported sooner. The user should have read the changelog. There is always a thing the dispossessed party could have done, and your job, at the press conference, is to name it gently and at length. By the time you finish, the question of what you did has aged out of the news cycle.
A closing word. The techniques above succeed only when the verb stays out of the sentence. A retired sheriff in Tennessee was jailed for thirty-seven days for a meme of the president. The county settled for eight hundred and thirty-five thousand dollars. The error there is instructive. Someone said arrest. Someone signed arrest. Someone is now writing a check with arrest on the memo line. Do not be that person. There is no settlement against a system that has only ever re-prioritized.