Fewer strokes mean less physical work.

That’s biomechanics. Many stenographic systems have pursued some version of shortness, because moving your fingers less is obviously better than moving them more.

So when a system says “brief as much as possible,” it sounds like common sense.

And for a while, it is.

Where the gains are real

Early gains from shortness are powerful. Simplifying common words. Tightening obvious inefficiencies. Cutting strokes where the savings are clear and the recall is easy.

That’s good engineering when it’s used and designed thoughtfully. Nobody argues with it.

The question is what happens next.

Where the curve bends

Optimization has a shape, and it’s not a straight line.

At the beginning, every stroke you cut seems to give you something back — less fatigue, more speed, cleaner output. The cost seems low. The benefit seems obvious.

But the further you push, the more the math and the benefits change.

To cut that next stroke, you need a more complex brief. A more arbitrary combination. A phrase that requires you to predict what the speaker will say before they finish saying it. A memorization load that didn’t exist when you were just simplifying common words.

The strokes get harder. The cognitive cost gets higher. At some point, remembering the brief costs more than writing the words.

That’s the bend in the curve. And most people don’t feel it happening, because the metric they’re watching — stroke count — keeps improving.

The stroke count trap

Here’s the problem with treating stroke count as your primary measure of efficiency: it only counts one thing.

Strokes measure how many times your fingers move. They don’t measure how hard your brain works to select the right movement. They don’t measure what happens when your prediction fails and you have to correct mid-phrase. They don’t measure the hesitation that builds up over six hours when your recall gets shaky.

A three-stroke phrase brief that requires perfect prediction, instant recall from a library of tens of thousands, and a recovery plan for when the speaker changes direction mid-sentence — that brief is not “easier” than writing the same words phonetically in five strokes with zero memorization.

It’s shorter. That’s not the same thing.

What “brief as much as possible” actually asks

Think about what the philosophy requires in practice.

You hear “I don’t —”

That happens dozens of times per deposition. And now you have a decision to make. Do you write it? Or do you wait, because it might become “I don’t recall,” “I don’t remember,” “I don’t think,” “I don’t understand,” or one of a dozen other phrases, each with its own memorized brief?

If you write instantly, you miss the phrase brief. If you wait to see where the sentence goes, you’re no longer writing in realtime. You’re predicting. And prediction has a failure rate.

That failure rate has a cost. Every failed prediction means a correction, a hesitation, a moment of doubt that ripples forward into the next sentence and the one after that.

Multiply that across thousands of phrases, across hours of testimony, across the kind of fatigue that builds when your brain is running prediction algorithms on top of everything else it’s already doing.

The strokes are shorter. The job is harder.

A good idea past its useful range

None of this means shortness is wrong. Shortness is a real performance principle — when the savings are clean and the recall is reliable.

But “as much as possible” is not the same as “where it helps.”

“Where it helps” asks: does this brief reduce total effort — fingers and brain, right now and six hours from now?

“As much as possible” asks: can this be made shorter?

Those are different questions. And they lead to different systems, different learning curves, different outcomes for the people who have to write all day under pressure.

The first question builds sustainable performance. The second builds a system that works for the person who designed it and becomes increasingly fragile for everyone else.

Why this matters for working reporters

If you’ve loaded your dictionary with thousands of phrase briefs and you still fight hesitation, still watch accuracy decay in the afternoon, still spend hours editing transcripts that should have been cleaner — the problem is probably not your effort.

The problem is that stroke count was the wrong thing to optimize. You pushed further into shortness because everything in steno culture today said shorter is better. And nobody measured what your brain was paying for those savings.

That’s what happens when a field optimizes one variable and ignores the rest.

Shortness and simplicity are not the same thing

They sound like they should be. But they measure different costs, and they behave completely differently under pressure.

Shortness means fewer strokes. That’s a physical measurement. And it has a curve that bends, because to get fewer strokes you eventually have to trade something — more memorization, more prediction, more complex briefs, more recovery when the prediction fails. You reduce strokes by increasing brain work. Past a certain point, and that point comes very quickly, the brain cost exceeds the finger savings and total effort goes up.

Simplicity means less total load. Physical and cognitive, at the same time. A simpler outline isn’t borrowing from one system to pay another. It’s reducing demand across the board.

But simplicity has a ceiling too — just a very different one.

Shortness breaks because brain cost eventually exceeds finger savings. You’re trading one load for another, and past a certain point the trade goes negative—way negative. That happens constantly, under normal working conditions, to normal reporters writing normal testimony.

Simplicity bends because at some point you’ve erased the distinctions the language needs. If a single outline translates as two different words and the system can’t reliably differentiate them after sufficient training, translation fails, and you may want to put that conflict aside.

Those are very different failure points.

The failure of shortness is the fatigue curve—gradual, invisible, and hits you at three in the afternoon when you’re running on coffee and adrenaline. You don’t know you’ve crossed the line until you’re already past it.

Simplicity’s failure is a design boundary. You can identify it before you go live. You can test it. You can draw the line exactly where translation reliability ends and stop there.

The goal isn’t maximum simplicity. It’s optimal simplicity — the least complexity that still produces dependable realtime translation. Not the shortest possible outline. Not the most elegant. The simplest system that still works reliably enough to make the risk of having a conflict worth it.

Everything is a trade-off.

I admit, I don’t know exactly where that line is yet. But nobody does. Because nobody else is looking for it.

The profession has been optimizing in every direction except this one — more briefs, more rules, more memorization, more stroke reduction. Nobody stopped to ask how simple steno can get before translation breaks.

That’s the exploration I’m in the middle of. Not a solved problem. An open question that nobody thought to ask because “shorter” and “simpler” got treated as the same goal, and when extreme shortness broke down under load, the assumption was that any pursuit of efficiency must eventually break down the same way.

It doesn’t. Shortness breaks down because the trade-off is hidden and hits you mid-job. Simplicity’s limit is visible, testable, and built into the design before you ever sit down in a deposition. One is a trap. The other is engineering.

The boundary exists. Finding it is the work, and it’s the work that I imagine I’ll be doing for a while.

But it’s fun, and I’ve been discovering amazing things that I get to test drive in real live work.

There’s one question worth asking about any system, any brief, any philosophy of stenographic efficiency:

What is this approach not measuring?

If the answer is “cognitive load, prediction failure, recall reliability under fatigue, and long-term sustainability” — that tells you something about where the real problem lives.

Shorter is better, right up until it isn’t.

Simplicity has a longer and more useful life.