Back to the Journal

Consistency beats efficiency

The efficient way is the wrong first question. Nothing compounds until you've proven you'll still be doing it in November.

The efficient way to run this journal would be to batch it. Block off one caffeinated weekend, write three months of posts, schedule everything, touch it never. We know this because we’ve planned that weekend at least four times. It has never once happened, and the journal keeps publishing anyway, which eventually taught us something the productivity industry doesn’t like to say out loud.

Efficiency is the wrong first question.

Everyone optimizes for the efficient way. It’s the respectable obsession, the one with dashboards and frameworks and conference talks. But consistency beats efficiency ten times out of ten on a long enough timeline, for a reason that isn’t motivational, just arithmetic: nothing compounds without it. Not an audience, not trust, not skill, not search rankings, not the strange gravitational pull a studio develops when it’s been visibly making things for years.

Compounding has exactly one non-negotiable input, and it’s the next installment.

Run the comparison honestly. An exquisitely efficient process you abandon in March produces less by December than a clumsy one you’re still running in November. That’s the whole proof. The elegant system that died is worth zero, and zero compounds into zero, and no amount of process design changes the multiplication.

The order only works one way

What’s strange is how backwards most teams sequence it. They want the efficient system first, as a precondition, before they’ll commit to the schedule. Get the workflow right, then we’ll publish weekly. Get the release pipeline pristine, then we’ll ship monthly. And the system never quite gets right, because systems designed in advance are designed against imaginary friction. You don’t know where the real drag lives until you’ve shipped the thing enough times to feel it in your hands. Which means the order only works one way: start consistent, even when it’s inefficient, even when it’s embarrassing how manual it is. Efficiency isn’t a prerequisite for showing up.

It’s a byproduct of it. The rough edges announce themselves through repetition, and you sand the ones that actually cost you something, which are almost never the ones you would have guessed from the whiteboard.

The same arithmetic everywhere

The pattern holds anywhere compounding lives.

  • Publishing, obviously.
  • Shipping product, where the team that releases something modest every month laps the team perfecting a launch that keeps sliding.
  • Training, where every gym veteran will tell you a mediocre program done for three years beats a perfect program done for three weeks, and the perfect program is usually abandoned by week three precisely because its perfection made it fragile.
  • Client relationships too, honestly. The agency that sends the plain Tuesday status email every Tuesday builds more trust in a year than the one that surfaces quarterly with a beautiful deck.

Will Durant, compressing Aristotle’s ethics into a line so good everyone now attributes it to Aristotle directly, wrote that we are what we repeatedly do, and that excellence is therefore not an act but a habit.

Note what the line doesn’t say. Nothing about the acts being optimized. The entire weight sits on repeatedly, and Durant put it there on purpose, because Aristotle’s actual argument was that virtue is trained into a person through practice, the way a craft is. You don’t think your way into it. You rep your way into it.


There’s a version of this piece that ends with a system, five steps for building your cadence, and writing it would feel efficient.

Instead we’ll just tell you what’s true from the inside: some of these posts were drafted in the gaps of brutal weeks, and the batching weekend still hasn’t happened, and the schedule has held anyway. Not because we’re disciplined people. Because the schedule stopped being a decision a long time ago, and things that aren’t decisions don’t need willpower.

The efficient way is a fine second step.