What does it mean that values as a compass, not a map?

Values tell you which direction to walk but not which specific path to take. They are a compass, not a map — and confusing the two leads to rigidity or paralysis.

Example: A software engineer values craft and quality. That value doesn't tell her whether to refactor the legacy codebase or build the new feature first. It tells her that whichever she chooses, she should do it with care and thoroughness. When her manager pushes for speed, she doesn't abandon the value — she negotiates how craft shows up in a compressed timeline. The value survived the constraint because it was a direction, not a prescription.

Try this: Pick one of your core values. Write it down. Now list three decisions you're currently facing. For each decision, write how that value gives you direction — not a specific answer, but a bearing. Notice the difference between 'my value tells me what to choose' (map thinking) and 'my value tells me what kind of choice to make' (compass thinking). If you catch yourself deriving exact answers from a value, you've switched from compass to map.