@leonardofreixas: The better you know a process, the worse you may explain it. "Put the peanut butter on the bread" sounds precise. Until someone follows it literally. Then everything you assumed becomes visible. The writer sees the workflow. The reader sees the words. That gap is where instructions fail. Every literal mistake exposes something the writer no longer notices they know. Literal interpretation is an assumption detector. You see the same failure in onboarding, handoffs, briefs, SOPs, and prompts. The more familiar you become with a process, the more of it becomes invisible. Good documentation doesn't explain everything. It predicts what this reader can safely infer. Clarity isn't maximum detail. It's minimum ambiguity for a specific reader. Documentation fails where assumed knowledge begins.