Four people leave a meeting agreed about the risk of moving payroll to a new provider in January. The minute says so, and none of them has reason to doubt it. In the room, the payroll manager meant the chance that the first run would come out wrong. Finance meant what it would cost to put right. Legal meant who would answer for wages paid late. The programme lead meant the three months of roadmap a parallel run would eat. All four said risk, all four heard risk, and nothing in the hour gave any of them cause to check.
The four readings are not four points on one line. A botched payroll run is an event, the cost of putting it right is a quantity, answering for late wages is a relation between people, and giving up three months of roadmap is a decision. Two people using one word for a quantity and for a decision have nothing to disagree about until something forces both into the same sentence.
A disagreement about a number announces itself, because the two numbers sit on the same slide. A disagreement about a word can leave the room in four heads and carry on working. Weeks later a mitigation arrives: a contingency line in the budget, sized to cover corrections and a month of overtime. The payroll manager reads it and cannot say what is wrong with it, only that money set aside to repair a bad run is not the same as a run that comes out right. The agreement is minuted by then, the budget is allocated, and reopening it would look like obstruction.
Agreement of that kind is common, and not a failure of intelligence.
Words outlive the distinctions they were cut from
A word is durable. It gets repeated in meetings, printed on templates, written into job titles, and it survives without anyone attending to it. A distinction has no such life of its own. It exists while somebody is making it, and the making leaves no trace: nothing is minuted on the day a team stops separating a rule from the procedure that carries it out.
Rule and procedure tend to collapse first. A rule says what has to hold. A procedure says what somebody does about it. A credit limit that once sat in a policy ends up in step four of the onboarding script, and from then on it is whatever step four says. It moves when somebody edits step four, and nobody has to decide that it moved. A procedure, a step in a procedure, or an action is not a business rule, which Metier says at length and the onboarding script does not say at all.
Functioning and functionality go the same way, two words most organisations use interchangeably and Metier does not. A report saying the payroll system is functioning can mean that it ran, or that it paid people the right amount, and nothing in the report says which.
Buying some would solve the problem
Two weeks after the contingency line went into the budget, somebody proposed a reconciliation tool. It would run the old system’s output against the new one, line by line, and flag every difference. Nobody spoke against it. It would find every difference and settle none of them.
In Metier, business becomes functional, because business reads as a cost centre and the work in question is implementing the organisation’s goals. Technology becomes technical, because technology carries the suggestion that buying some would solve the problem. Information communication becomes compliancy, because the communication an organisation actually runs on, the expectations and the instructions, is not the communication its cables carry.
The glossary agreed with all four of them
Most organisations of any size already have a glossary. It is accurate. It was reviewed, circulated and signed off, and the entry for risk is broad enough that each of the four people in that meeting would have read it and found their own reading sitting inside it. That is why it was approved. An entry narrow enough to exclude three of them would not have survived the review.
A glossary records the words an organisation uses. What held the chance of a bad run apart from the cost of one was never a word. It was a habit of keeping two things separate, maintained by people who had some reason to keep them separate, and it went when the reason did. The entry stayed on the intranet, accurate and undisturbed, and by then it described a distinction nobody was making.
Something stricter would be a term, synonyms included, pointing at a single concept within a stated context. That needs a business vocabulary with a concept model underneath. A glossary can be written in an afternoon.
None of the four was working from a definition. They were working from a word, and the word was working perfectly.