mediumConceptScenarioBehaviouralMidSeniorStaff
Everyone in the business calls it the fax queue, and nothing has been faxed since 2014. Do you keep that name in the code?
5 min readUpdated 2026-08-15
Answer
Short answer
Usually yes for the label and no for the concept.A fossil name is still the word that lets you and the business point at the same thing, so keep it as the shared term, but model what the queue is for today rather than the channel it was named after.
Domain vocabulary matters here because the business term that no longer describes answer has to show the boundary, not just the happy path.
Was this answer helpful?
Likely follow-ups
- The fossil name has become a superset of two different things. How do you split it without losing the word?
- A regulator uses the same word with a narrower defined meaning. Which one wins in your model?
- How would you introduce a new term into a business's vocabulary without simply decreeing it?
- When is a badly named column worth a migration, and when do you leave it and document it?
Related questions
- A stakeholder keeps using a term you have never heard. What do you do in the meeting?easyAlso on domain-vocabulary and ubiquitous-language5 min
- How do you turn what the business tells you into a domain model that holds up once the exceptions arrive?hardAlso on domain-modelling7 min
- The operations team says there is no rule for this, they just use judgement. How do you model that?hardAlso on domain-modelling7 min
- Your test lifts conversion, but something else moved the wrong way. What are guardrail metrics, and when do they stop a launch?hardSame kind of round: concept5 min