Knowledge & Communication Defects
Defects that emerge from gaps between what people know and what the code expresses - the hardest to detect with automated tools and the easiest to prevent with team practices.
less than a minute
These defects emerge from gaps between what people know and what the code expresses. They are the hardest to detect with automated tools and the easiest to prevent with team practices.
| Issue | Earliest Detection (Automation) | Automated Detection | Earlier Detection with AI | Systemic Prevention |
|---|---|---|---|---|
| Implicit domain knowledge not in code | Coding | Magic number detection, code ownership analytics | ▲ Identify undocumented business rules and knowledge gaps from code and test analysis | Domain-Driven Design with ubiquitous language; embed rules in code |
| Ambiguous requirements | Requirements | Flag stories without acceptance criteria, BDD spec coverage tracking | ▲ Review requirements for ambiguity, missing edge cases, and contradictions; generate test scenarios | Three Amigos before work; example mapping; executable specs |
| Tribal knowledge loss | Coding | Bus factor analysis from commit history, single-author concentration alerts | ▲ Generate documentation from code and tests; flag documentation drift from implementation | Pair/mob programming as default; rotate on-call; living docs |
| Divergent mental models across teams | Design | Divergent naming detection, contract test failures | ▲ Compare terminology and domain models across codebases to detect semantic mismatches | Shared domain models; explicit bounded contexts |
Related Content
- Defect Sources - full catalog overview and how to use it
- Anti-Patterns - patterns that undermine delivery performance