What does it mean that output batching?

Produce multiple outputs in one focused session rather than one at a time.

Example: You have been publishing one lesson per day, writing each one from scratch in its own session — open the skeleton, research, draft, edit, publish. Each session takes ninety minutes. Forty of those minutes are pure startup friction: re-reading the phase arc, loading the style into your head, configuring your writing environment, finding the right tone. You are paying a forty-minute cognitive changeover cost for every single output. One Saturday, you try something different. You block four hours and write three lessons in sequence. The first lesson takes the usual ninety minutes. The second takes fifty-five. The third takes forty-five. You produced three outputs in three hours and ten minutes instead of four hours and thirty minutes. The startup friction was paid once. The style was loaded once. The tone was found once. And the quality of the second and third lessons was higher, not lower — because by the time you started them, your pattern-recognition for the phase arc was sharp and your editorial judgment was warmed up. You did not work harder. You batched.

Try this: Identify one output type you produce regularly — lessons, emails, social posts, reports, meeting agendas, code reviews, anything that recurs. This week, instead of producing each instance individually as it comes due, batch three or more instances into a single focused session. Before the session, prepare all inputs (briefs, templates, reference material) so that once you start producing, you do not stop to gather materials. Time the session. After completing the batch, record three numbers: total session time, average time per output, and your subjective quality rating (1-5) for the batch versus your typical one-at-a-time output. Compare the per-unit time to your normal production time. If batching saved at least 20% per unit and maintained or improved quality, schedule a recurring batch session on your calendar for this output type. If it did not, examine whether the bottleneck was preparation (you stopped mid-session to gather inputs) or fatigue (the session was too long). Adjust and try again next week.