Walk through any data team today and you'll trip over the word. Concept models. Semantic layers full of concepts. Knowledge graphs whose nodes are, you guessed it, concepts. Catalogs that promise to govern your concepts. The word has become the universal solvent of IT conversation — pour it on anything and the awkward silence dissolves. It's a concept. Everyone nods. Nobody is any wiser.
Here's the problem hiding in plain sight: everything is a concept. A customer is a concept. An invoice is a concept. "Delivered on time" is a concept. So is "delivered," "on," and "time." When you point at something and announce it's a concept, you have said precisely nothing — you've labelled the box, not what's inside it. It's like answering "what's that animal?" with "it's a thing." Technically flawless. Completely useless.
And yet naming it a concept feels like progress. That's the trap. We mistake the act of attaching a noun for the act of understanding. We give the thing a word and walk away satisfied, as if a word were a definition rather than a promissory note we now have to honour.
The question we skipped
The interesting question was never what concept is this? It was the one we walked past on the way in: what are we actually talking about?
Not in the abstract. Concretely. Who says what, to whom, about what? What are the real sentences in which this thing turns up? Because a concept doesn't arrive first, hovering in the ether, waiting to be named. It's the residue of communication. It's what's left over once you've looked at all the things people actually say and noticed they keep talking about the same kind of thing. The sentences come first. The concept is downstream.
So a thing that has no sentences behind it isn't a concept that needs a name. It's a question that needs its examples. Which utterances put this here? What did someone need to say that made it necessary at all? Until you can produce a few concrete cases — "Customer Smith ordered three units of product X on the fifth" — you don't have a concept. You have a shape and a fancy word taped to it.
This is the old lesson from the philosophy of language, the one Wittgenstein kept hammering: don't go hunting for the meaning, look at the use. Meaning lives in the sentence, in the doing, in the exchange between people who need to get something done together. It does not live in the label. Reaching for the word concept is the picture-theory mistake in miniature — assuming the word points at an object, when really the use came first and the object is something we reconstructed afterwards.
Why this gets worse, not better
You might think all this hair-splitting matters less now that machines do the reading. The opposite is true. We are now stuffing models, catalogs, and ontologies full of confidently named "concepts" that no human can ground in a single sentence of real business communication. The label looks authoritative. The grounding is missing. And a language model handed a beautifully named concept with no verbalization behind it will do what we taught it to do: fill the gap with something plausible. The same emptiness, but now eloquent.
Grounding isn't a nice-to-have you add later. It is the meaning. Strip away the sentences and "concept" is just a shape with good PR.
The honest answer
So when someone offers you a concept that hasn't been named, the right response isn't hurry up and name it. It's back up — what were we talking about in the first place?
Show me the sentences. Tell me who says them and why. Get those right, and you'll find the concept doesn't need you to name it. It names itself.
Download 
Use Online