/or-THOG-uh-nul/
Independent and non-overlapping. Two things are orthogonal when changing one has zero effect on the other.
Orthogonal literally means 'at right angles,' but in technical and strategic contexts it means completely independent. Two features are orthogonal if you can change one without affecting the other. Authentication and payment processing should be orthogonal — fixing a login bug shouldn't break checkout.
This word is incredibly useful when talking to AI because it precisely communicates scope boundaries. When you say 'these concerns are orthogonal,' you're telling the AI not to tangle them together. When you say 'is this orthogonal to the existing system?', you're asking whether a new feature can be built independently. It's the antidote to spaghetti code and muddled thinking.
When discussing system architecture, feature independence, or ensuring changes in one area don't cascade into another.
Orthogonal thinking produces modular systems. Modular systems are the only ones that survive contact with real users.
Picture two lines crossing at 90° — they share a point but go in completely different directions. That's orthogonal.
A Mac app that coaches your AI vocabulary daily