What does it mean that unique identifiers prevent confusion?

Every distinct idea needs a unique, stable address — without one, you cannot reference it, link to it, or build on it reliably.

Example: Your team has three Confluence pages titled 'Architecture Decision.' One is about migrating to microservices (2023), one is about the event-driven rewrite (2024), and one is about the AI integration layer (2025). Someone links to 'Architecture Decision' in a Slack thread. Which one? Nobody knows. The conversation derails into ten minutes of 'which doc do you mean?' If each had a unique identifier — ADR-001, ADR-002, ADR-003 — the link is unambiguous, the reference is instant, and the conversation stays on substance.

Try this: Open your note system. Search for any term that returns 3+ results with similar titles — 'meeting notes,' 'project plan,' 'ideas,' 'architecture.' For each collision, assign a unique identifier: a date prefix (2026-02-22), a sequential ID (IDEA-047), or a descriptive slug (architecture-decision-event-driven-rewrite). Rename the note so the identifier is part of the title. Time: 10-15 minutes. Artifact: 3-5 renamed notes with unique, unambiguous identifiers.