Entrepreneurship ยท 3 min read

Complex Language Kills Simple Systems

Jargon creates friction and slows execution. Why clear communication makes business systems work, and how to write instructions people actually follow.

A system is only as good as the instructions behind it.

You can design the smartest process in the world. If the people running it don't understand the words you used to describe it, it won't run. It'll get interpreted, guessed at, quietly changed, and eventually ignored.

That's why I believe complex language kills simple systems.

Jargon is friction

Every vague word in a process is a small decision someone has to make. What does "optimise the workflow" mean on a Tuesday afternoon? What exactly is "align with stakeholders"? Who does what, when, and how do you know it's done?

When the language is fuzzy, people fill the gaps with their own interpretation. Five people, five interpretations. And then you wonder why the same process produces five different results.

This costs more than most people think. A Grammarly and Harris Poll study estimated that poor communication costs US businesses up to $1.2 trillion a year, and one in five business leaders said they lost business or deals because of it. So this is an operations problem as much as a writing one.

Why do smart people write complicated things?

Usually for one of three reasons:

  1. To sound professional. Big words feel more serious, especially in a corporate setting.
  2. Because they haven't fully worked it out yet. Vague language hides vague thinking. If you can't explain it simply, you probably don't understand it well enough yet.
  3. Because nobody tested it. The writer knows what they meant. They never checked whether someone else does.

The fix for all three is actually not that difficult. It just takes a bit of discipline.

What clear system language looks like

When I write a process, I try to make every step pass a simple test: could someone new do this tomorrow without asking me a question?

In practice that means:

  • One action per step. "Send the invoice" is a step. "Handle billing" is a wish.
  • A verb first. Check, send, call, update, file. People act on verbs.
  • The trigger and the finish line. When does this step start, and how do you know it's done?
  • Plain words. If there's a shorter, simpler word, use it.
  • A name instead of a role, where possible. "Ask the team" goes nowhere. A named person gets it done.

It looks almost too simple on paper. That's the point. Simple language is what makes a system run without you standing next to it.

Clarity scales, complexity doesn't

A complicated process might work while the person who designed it is in the room to explain it. The moment it has to run without them, with new people, across languages, across time zones, it starts to break.

I've worked across several countries, with teams who didn't share a first language. In those settings you learn fast that clear, simple wording is the only thing that works. If it can be misread, it will be.

And the same goes for anything you write for clients, partners or your own future self. Six months from now, you won't remember what you meant either.

Start with one process

Pick the one process in your business that causes the most questions, mistakes or back-and-forth. Rewrite it with the rules above: one action per step, verb first, a clear trigger and finish line, plain words.

Then hand it to someone who's never done it, and watch where they get stuck. Every place they hesitate is a place your language failed, not them.

Fix those spots, and the system starts doing what it was designed to do.

Simple words build systems that run. Complex words build systems that need you.

Sources: Grammarly and The Harris Poll, "The State of Business Communication" (2022), via Business Wire, https://www.businesswire.com/news/home/20220125005525/en/Grammarly-and-Harris-Poll-Research-Estimates-U.S.-Businesses-Lose-1.2-Trillion-Annually-to-Poor-Communication

Related articles

All articles