Over 30+ years in oil & gas operations, measurement, investigations, and regulatory compliance taught me something most people never learn:

Bad writing is rarely just bad writing.

It is often evidence of bad thinking.

Or worse —
an attempt to hide weak assumptions behind complexity, procedure, credentials, jargon, or institutional authority.

I see it constantly in:

• incident investigations
• measurement disputes
• expert reports
• regulatory filings
• root cause analyses
• royalty disputes
• internal company findings
• legal defenses

The people writing the weakest reports often believe:
more words = more authority.

In reality, the opposite is usually true.

Strong arguments are generally:
Clear.
Concrete.
Precise.
Defensible.

Weak arguments hide inside:
“Clearly…”
“Obviously…”
“Arguably…”
“Apparently…”
“Reasonably…”

Those words are often warning flares.

If something is truly obvious, evidence usually makes it obvious without announcement.

One of the biggest problems I encounter in forensic reviews and technical advisory work is what I call:

“Procedure compliance replacing ground truth.”

Everything appears compliant on paper.

The forms were filled out.
The calibrations passed.
The SOP was followed.
The investigation was “conducted.”

Yet the answer is still wrong.

I’ve seen “compliant” systems misstate gas value by millions because nobody stopped to ask:
“Are we measuring reality — or merely validating procedure?”

That difference matters in litigation.

It matters in insurance disputes.

It matters in royalty conflicts.

And it matters in safety investigations where incentives quietly shape conclusions before evidence is fully examined.

Another major problem:
Zombie nouns.

“Conducted an investigation.”
“Performed an evaluation.”
“Provided justification.”

No.

Investigated.
Evaluated.
Justified.

Strong writing moves.
Weak writing stalls.

One reason I built my consulting methodology around cross-examination principles, assumptions testing, incentive analysis, and exploratory thinking is because technical reports often collapse under one simple question:

“What assumptions must be true for this conclusion to survive?”

Most reports never ask that question.

They defend conclusions instead of testing them.

That is not analysis.
That is advocacy disguised as analysis.

The best technical communicators understand something critical:

The reader is no longer in the room with you.

An attorney, regulator, insurer, executive, or jury cannot stop and ask:
“What did you mean here?”

Your writing must guide them before confusion appears.

Short sentences create impact.

Longer sentences create pressure and nuance.

Rhythm matters.

Clarity matters.

But credibility matters most.

In my experience, the most dangerous reports are not always fraudulent.

They are often written by intelligent people operating inside flawed assumptions they never stopped to challenge.

Good writing exposes assumptions.

Bad writing protects them.