Why Plain Language Matters When Businesses Adopt New Technology

When a business introduces new software, most of the attention goes on choosing the product and setting it up. In our view, far too little goes on explaining it to the people who will rely on it every day. This opinion piece argues that plain language is not a nice extra but one of the most important parts of any technology change.

The gap between buying and using

Technology decisions are often made by a small group who have read the documentation, sat through demonstrations and absorbed the vocabulary. By the time a tool reaches the wider team, those decision-makers can forget how unfamiliar it all sounds to everyone else.

The result is a gap. Staff are told a new system is "live" and that they should "migrate their workflows", but not what that means for the task in front of them on Monday morning. People then fill the gap with guesswork, workarounds or quiet avoidance.

Jargon creates hidden costs

Unclear explanations rarely cause dramatic failures. Instead, they create small, steady costs that are easy to overlook. Someone spends twenty minutes searching for a button. Someone else keeps a private spreadsheet because they do not trust the new system. A manager answers the same question repeatedly.

None of this appears in a project plan, but it adds up. It can also lead to security problems, because people who do not understand why a step matters are more likely to skip it or find a way around it.

What plain language looks like in practice

Plain language does not mean oversimplifying or talking down to people. It means explaining things in the words your colleagues already use, focusing on what they need to do and why.

In practice, that tends to involve:

• Describing tasks, not features: "how to send a quote", rather than "using the document module"

• Explaining the reason behind a change, especially when it adds a step

• Defining unavoidable technical terms once, in a sentence, the first time they appear

• Keeping instructions short, ordered and specific to real situations

• Saying clearly what has not changed, so people know what they can stop worrying about

These habits apply equally to training sessions, internal guides, emails announcing a change and the labels used inside the software itself where those can be customised.

Clarity builds trust

People are more willing to change how they work when they understand what is happening and believe it will help. Clear explanations signal respect. They show that the organisation has thought about the people affected, not only about the technology.

Clarity also makes it easier for staff to give useful feedback. If someone understands what a tool is meant to do, they can say precisely where it falls short. If they are confused from the start, their feedback is likely to be a general sense that "the new system is difficult", which is much harder to act on.

Responsibility sits with the people introducing the change

It is tempting to treat difficulty with new tools as a training problem on the user's side. We think that framing is usually wrong. If a reasonable person cannot follow the explanation they were given, the explanation needs work.

That responsibility applies to vendors as well as to internal teams. Product interfaces, help pages and onboarding material that rely heavily on jargon make adoption harder for everyone. Businesses choosing between tools could reasonably treat clear documentation as a genuine point in a product's favour.

Writing clearly takes effort. It means testing instructions on someone unfamiliar with the tool, rewriting the parts that cause confusion and resisting the urge to sound technical. That effort is modest compared with the time lost when a whole team struggles in silence.

A simple test

One practical check is to ask whether a new colleague, on their first week, could follow your guidance without help. If the answer is no, the language probably needs simplifying. Another is to read instructions aloud: sentences that sound awkward when spoken are often hard to follow on screen as well.

The bottom line

New technology succeeds or fails in daily use, not on the day it is purchased. Explaining tools in plain, practical language helps people adopt them with confidence, reduces hidden costs and builds the trust that any change depends on. It is one of the least expensive improvements a business can make, and, in our opinion, one of the most overlooked.