Business analysis
Why good ideas fail because of jargon
Technical precision is of little use if the people who matter do not understand what they are supposed to decide on

A specialist presents a solution. The architecture is well thought out, the concept technically coherent, the risks documented. After twenty minutes, someone from the executive board asks a simple question: "What will this improve for our customers?" The answer contains three more technical terms. The presentation continues. In the end, a lot was explained but little was understood.
The problem is not necessarily a lack of competence. Quite the opposite. The deeper people immerse themselves in a field, the more natural its language becomes to them. They recognise connections in terms that others would first have to work hard to understand.
Technical language is valuable. It can describe complex matters precisely and concisely. But when it becomes the only means of communication, a barrier arises between knowledge and decision.
A good idea does not become understandable simply because it has been explained in technically correct terms.
Expertise and making yourself understood are different achievements
Let us imagine a company that wants to improve its information security. The technical team proposes checking access more closely by identity, role and context. In the conversation, terms such as Zero Trust, Conditional Access, Policy Enforcement and Least Privilege come up.
For specialists, these terms describe different, important aspects. They should not simply disappear. But the decisive question for the client might initially be: which people will be able to access which information in future, which risks are we reducing, and how will day-to-day work change?
Only once this effect is understood can the technical details be discussed meaningfully. Conversely, anyone who starts with the full terminology is asking the other person to learn a new technical language first before being allowed to assess the actual decision.
Understandability thus becomes a question of participation. Anyone who does not master the language may be unable to formulate a well-founded objection. They must either trust, object without sufficient grounds, or remain silent.
The convenient power of terms
Technical terms can also fulfil social functions. Anyone who uses them confidently signals that they belong to a group. They demonstrate competence and set themselves apart from people who do not know the vocabulary. This need not happen consciously. Professional communities simply develop their own forms of expression.
It becomes problematic where language controls access to a decision. When follow-up questions are treated as a sign of a lack of intelligence, people stop asking. Perhaps they agree even though they have not understood the difference between two options. Perhaps they reject a good concept because it seems unfamiliar and confusing.
A consultant should not derive any sense of superiority from this. Their job is not to impress with technical language. They should make knowledge accessible in such a way that the client can make a well-founded decision themselves.
This does not mean translating every technical truth into a trivial image. It means offering the right depth at the right time.
The first question is not: what can we offer?
Many presentations start with one's own offering. A company shows its method, its technology, its references and its services. Only later is the question asked whether the client actually has the problem it is meant to solve.
I consider this sequence a fundamental mistake. Good communication starts with the other person's situation. What do they want to achieve? What is stopping them? What consequences does the problem have today? And how would they recognise that a solution makes sense?
An example: a service provider offers an SME an extensive process automation programme. They explain platforms, workflows, integrations and AI functions. The managing director, however, is thinking about the recurring customer complaints because quotes are prepared too late.
The technically correct answer might well include automation. But first it has to be clarified what is causing the delay. Is information missing? Are responsibilities unclear? Are approvals taking too long? Or is a manual step actually the bottleneck? Without this diagnosis, the technology presentation is an answer to a question nobody has asked yet.
Understandable does not mean superficial
A common objection is that complex topics cannot be explained without technical language. There is a legitimate core to this. Certain distinctions are essential. Leaving them out can create a false impression.
But it does not follow that everyone involved needs the same level of detail. A responsible decision can be prepared in layers: first the situation and the intended effect, then the options for action with their costs and risks, and finally the technical details that justify a particular option.
Anyone who asks receives the depth their role requires. Anyone implementing a security architecture needs precise technical information. Anyone making an investment decision has to understand the effects, commitments and risks. Anyone who will later work with the system needs different information.
These different perspectives are not a quality defect. They are the reason why communication has to be designed.
A method: from term to decision
For a concept that needs explaining, I suggest making three translations.
First into the language of the problem: what is not working well enough today? Which people are affected? What observable consequences does this have? Examples should be concrete, but not distorting.
Then into the language of the decision: what options do we have? What do we have to give up or invest for them? What risks are we taking? What happens if we change nothing?
Only then into the language of implementation: which technical terms, technologies, processes and standards are relevant to the chosen solution? Which assumptions do specialists need to check and document?
This sequence is not mandatory in every situation. In a purely expert committee, you can start directly with technical details. But even there it is worth not losing sight of the purpose.
The danger of attractive simplifications
There is an opposite problem: some presentations are so heavily simplified that the actual matter disappears. AI supposedly solves every information problem. A new platform eliminates all media breaks. A strategy programme provides complete clarity.
Such promises are easy to understand and often wrong. They do not reduce the complexity of the task; they conceal it.
Good communication must therefore not be confused with advertising. It also has to explain limits. What can a solution not do? What prerequisites must be in place? What risks remain? Who will later be responsible for maintenance and operation?
Anyone who presents only the advantages in plain language and hides the risks in the technical appendix is not creating understandability. They are steering the decision.
An example from business analysis
In a project to harmonise customer data, IT talks about a "single source of truth". The term sounds convincing. But it can mean very different things. Should there be exactly one database? One leading record per customer? A shared definition of key figures? Or merely reliable access to information from several systems?
As long as these questions remain open, every group involved can agree to the term and understand something different by it. The project then appears to have a shared objective, but no shared requirement.
The task of good business analysis is not to ban technical terms. It has to make differences visible and prepare decisions. Anyone who talks about the "one truth" should be able to explain which data take precedence in the event of a contradiction, who approves changes and how errors are corrected.
Only then does the buzzword become a verifiable mandate.
Follow-up questions as part of quality assurance
Understandability cannot be measured solely by how the presenter feels. What matters is what has got through to the others. That is why we should not just ask whether anyone has any questions. It is often more helpful to have the planned decision summarised in their own words.
This can be done without making it feel like a test. "Which two risks do you see as decisive?" or "What would have to change in day-to-day work for this investment to pay off?" The answers show whether people have the same matter in mind.
A misunderstanding is then not an embarrassing incident but a valuable clue. It allows correction before an expensive project is built on a false shared assumption.
This also includes the willingness to revise one's own explanations. Anyone who declares the other person ignorant because they do not understand the presentation may be overlooking part of their own responsibility.
When technical language finds its way into contracts and decisions
Misunderstandings become particularly costly when unclear terms are carried over into a contract. A client orders a "complete integration". The provider takes this to mean a data interface. The client expects employees to be able to work in future without switching systems. Both sign in the conviction that they have agreed on the same result.
Such terms need a verifiable meaning. Which data are transferred? In which direction? How up to date? Who is responsible when errors occur? What happens in the event of an outage? How is acceptance carried out? Only with this information can it be determined whether both sides expect the same scope of services.
The same applies to larger strategic terms. An organisation can resolve on "digitalisation" and understand it to mean avoiding paper, changing processes or a new business model. As long as the difference has not been clarified, spending and expectations are aligned with different goals.
A significant decision should therefore have a short purpose that anyone can understand and a precise technical appendix. The two must refer to each other. Simplicity without precision leads to false expectations. Precision without understandability prevents a responsible decision.
Visualisations can help and deceive
A good drawing can make a complicated relationship accessible. It can show which systems talk to each other, where people make decisions or which steps follow one another. But a graphic also makes assumptions. What is not drawn in may appear insignificant.
An architecture overview, for example, shows a single arrow between two applications. In reality, behind it lie security checks, data cleansing, error routines and responsibilities. For initial orientation, the arrow makes sense. For a binding effort estimate, it is not enough.
That is why we should check visualisations with a simple question: which essential difficulty does this representation make invisible? Anyone who can answer this question uses visualisations as an aid to understanding and not as a substitute for technical review.
Good language does not only lead to agreement
An understandable explanation can lead to an idea being rejected. That is not a communication failure. Perhaps the client only now realises that the costs are too high or the prerequisites are missing. Perhaps a specialist finds an error that was hidden behind unclear terminology.
That is precisely where the value lies. The purpose of good communication is not to force agreement. It is to enable people to make a well-founded decision.
An organisation that takes this seriously will structure its texts, decision papers and presentations differently. It will not start with the names of methods, but with the problem. It will explain technical terms where they are needed. And it will make the limits of the proposed solution just as visible as its benefits.
Professional competence is shown not only in understanding something complex correctly. It is also shown in letting others share in it in such a way that they can decide responsibly.
If an idea fails because its language reaches no one, the idea itself may not be the real problem. Rather, it is the missing connection between the specialist's knowledge and the reality of the people for whom this knowledge is meant to make a difference.