Exodus
Navigate the bureaucracy
Decompose the process, find the bottleneck document, and build the checklist before the queue builds it for you.
A bureaucracy is a pipeline with undocumented dependencies: forms that need forms, offices that need appointments, one document with a lead time that silently gates everything behind it. The machine's job is to decompose the process end to end, surface that bottleneck document early, and produce the checklist you actually execute: what, where, in which order, with which papers in hand.
The catch is that procedures drift and the machine's memory of them ages. Requirements change by office, by country, by month; the confident recollection of a process is the most dangerous artifact in this domain. For every gating step, verify against the current official source, in whatever language it lives in, before you stand in the queue it governs.
How to practice it
Decompose to a checklist.
Steps, offices, documents, order, lead times. The process you can see is the process you can schedule.
Find the long pole first.
One document usually gates the rest. Identify it on day one and start it first.
Verify the gating steps live.
For anything with a queue or a deadline, check the current official rules, not the remembered ones.
Carry the folder.
Build the paper manifest per visit: originals, copies, translations. The trip that fails on a missing photocopy was preventable.