Skip to main content

> Term

Semantic Drift

The process by which teams use the exact same terminology but gradually adopt fundamentally different meanings.

Detailed Explanation

Semantic drift happens when a specific domain concept loses its precise technical definition and becomes a generalized buzzword across different departments.

This misalignment leads to architecture built on faulty assumptions, as engineering, product, and business teams believe they are solving the same problem while pursuing entirely different goals.

Why It Matters

It creates invisible communication barriers that cause massive scope creep and incorrect system design late in the development cycle.

Common Failure Mode

Product asks for a "dashboard," meaning a real-time BI tool, while engineering builds a static weekly report, leading to a complete rewrite.

Practical Example

The term "real-time" meaning "within milliseconds" to backend engineers, but "within 24 hours" to the business team.

Production Manifestation

Meetings where stakeholders aggressively agree with each other using the same words, followed by the delivery of a feature nobody asked for.

Frequently Asked Questions

What is Semantic Drift in short?

The process by which teams use the exact same terminology but gradually adopt fundamentally different meanings.

What is the most common failure mode?

Product asks for a "dashboard," meaning a real-time BI tool, while engineering builds a static weekly report, leading to a complete rewrite.

AI Summary

The process by which teams use the exact same terminology but gradually adopt fundamentally different meanings. It creates invisible communication barriers that cause massive scope creep and incorrect system design late in the development cycle.