A meeting can produce a fine sentence without producing an action.

There is an old story about four people: Everybody, Somebody, Anybody and Nobody.

An important job needed doing. Everybody assumed Somebody would handle it. Anybody could have stepped in. Nobody did.

In the end, Everybody blamed Somebody.

The story is old. Its author is uncertain. The problem has survived very well.

I have heard Nobody receive many actions

I have sat in meetings where people discussed a problem for an hour. The group reached “general agreement”. The action note then said:

“The matter should be reviewed.”

Nobody had been asked to review it. No date had been set. The meeting had produced a sentence, not an action.

A month later, the problem returned. Everybody remembered that Somebody was going to do something.

Nobody could remember who.

This is not rare. It happens in projects and daily management. Volunteer groups know it too. It happens at home as well.

“The garage needs cleaning” is an observation. It is not an agreement about who will clean it.

The passive voice can remove the person

Orwell warned against using the passive voice when the active voice will do.

The passive voice has a proper place. Sometimes the act matters more than the actor. Sometimes we do not know who acted.

It also gives us an easy way to leave the actor out.

“Mistakes were made.”

Who made them?

“The customer was not informed.”

Who should have informed the customer?

“The new process was poorly explained.”

Who explained it, and to whom?

The grammar may be correct. Responsibility has still gone missing.

A named person can still have an unclear job

Writing “John owns this” does not settle everything.

What must John do? When? What result shows that the work is finished? Does John have the right information and authority?

I have seen managers give someone an action that depends on another department, then call the delay a lack of ownership. Naming a person is useful. Giving that person an impossible job is not.

Responsibility must fit the work.

If several people need to act, say what each one will do. Do not give the whole group one large verb and hope the details arrange themselves.

Soft language can hide an order

People with authority sometimes avoid plain words because they do not want to sound harsh.

“It might be useful to have another look at the report” may mean “Correct the report and send it back today.”

The manager hears an instruction. The employee hears a suggestion.

Later, the manager says the message was clear.

It was clear inside the manager’s own head.

If something is required, say so. Give the reason where it helps. Listen if the person sees a problem with the request.

Plain does not need to mean rude.

Personal promises need the same care

Responsibility does not begin at the office door.

“We should call them sometime” usually gives the telephone to Nobody.

“I will call on Sunday” gives the job to me.

That small change matters. I have made a promise that can be kept or broken.

First-person language can feel exposed for exactly this reason. “I decided” is harder than “it was decided”. “I forgot” is harder than “it slipped through”.

The plain version leaves less room to escape.

Ask the question before the meeting ends

When a discussion reaches an apparent decision, ask:

Who will do what? By when? How will we know it is done?

These questions are not clever. They work.

The old story remains funny because Everybody, Somebody, Anybody and Nobody sound like people we know.

Sometimes I am one of them.

Orwell’s point about active language helps me see the choice. Name the act. Name the person when the person matters.

Otherwise Nobody may have another busy week.

George Orwell, *Politics and the English Language*: https://www.orwellfoundation.com/the-orwell-foundation/orwell/essays-and-other-works/politics-and-the-english-language/

Return to the Orwell and Plain Language series