Most software teams spend a lot of time in meetings that should have been a short, clear note.
Someone asks for an “error” version of a banner. Design draws it and labels it one way. Engineering builds something that looks similar but names it another way. Testing writes a checklist in a third wording. Next week, everyone explains it again in standup. Nobody is failing at their job. They simply do not share a language. Each role translates the same idea into their own jargon. Every translation is a chance to drift. Work starts to feel like talking in circles.
Meanwhile is a bet that you can name things once, in a way design, engineering, and testing can all use, and then keep that meaning in a machine so you stop re-explaining it.