Energy management for meeting-heavy roles

Time management optimizes a quantity that is fixed and identical for everyone: there are 40-odd working hours in a week, and the discipline is about allocating them. Energy management optimizes a quantity that varies by hours of the day, by person, and by what you just did. The two produce different schedules from the same calendar, and on a meeting-heavy calendar the second one produces better meetings.

The argument, made repeatedly in the management literature and summarized well in Forbes' coverage of energy-based scheduling, is that capacity is renewable in a way time is not. You cannot make more hours. You can, within limits, decide when your best hours land and what you spend them on. A strategy discussion at your peak and a status sync at your trough is the same calendar as the reverse, and a materially different week.

Two pieces of biology do most of the explaining.

• Chronotype — the individual timing of your circadian rhythm. Early types peak mid-morning; late types genuinely do not, and a 9:00 AM design review costs them their worst hour and their colleagues' best one. Chronotype is largely not a habit you can talk yourself out of.
• Ultradian rhythms — inside the day, attention runs in cycles of roughly 90 minutes followed by a trough where sustained focus degrades. This is why the third consecutive hour of meetings feels categorically worse than the first, and why a break at minute 95 is worth more than the same break at minute 30.

Generic advice about morning people is worth less than two weeks of your own data. The tracking that works is deliberately crude, because anything more elaborate gets abandoned by Thursday.

• Three times a day — late morning, after lunch, late afternoon — rate your mental energy 1 to 5. One line in a note, five seconds.
• Next to it, write what you had just been doing. The point is not the score, it is what preceded it.
• After ten working days, look for the two blocks that are reliably 4s and 5s, and the one that is reliably a 2. Most people have exactly one dependable peak and one dependable trough, and are wrong about where they are.

The output is a two-line rule: your peak block, and your trough block. Everything below is applying those two facts to a calendar.

Meetings are not one kind of work. Some require generating new thinking under uncertainty; others require presence and little else. Sorting your recurring meetings by cognitive load, then placing them against your curve, is most of the practice.

The trough row is the one people resist and the one that pays. A post-lunch hour is a bad hour for solving something and a perfectly adequate hour for hearing a demo. Putting low-load meetings there is not wasting the slot, it is spending it at the price it is worth.

Two constraints make this real rather than aspirational. You control roughly the meetings you schedule, which is fewer than half of them, so start with recurring meetings you own — a weekly 1:1 moved once stays moved. And when someone else owns the invite, the lever is not the time but the preparation: arriving at a high-load meeting in your trough with the thinking already done converts it from generation to presentation.

The ultradian pattern implies something uncomfortable about back-to-back days: capacity does not reset because a new meeting started. Microsoft's Human Factors Lab measured this with EEG in 2021 and found stress-associated brain activity accumulating across consecutive video meetings, while short breaks between them let it reset instead. Recovery inserted between two cognitively demanding meetings is not a gap in the work, it is what makes the second meeting comparable to the first.

What actually restores capacity is narrower than it sounds:

• Ten minutes away from a screen beats ten minutes of email, which is a fourth meeting with worse ergonomics.
• Movement, even trivially — standing, walking to another room, going outside. The reset is physiological rather than motivational.
• Closing the previous meeting first. Sophie Leroy's attention-residue work shows that an unfinished task keeps consuming attention after you leave it. Writing down the decision and the owner ends it; carrying it in your head does not.
• Not stacking two high-load meetings. If both must happen today, put a low-load one between them rather than a gap you will fill with Slack.

The tactics for defending those gaps once they exist are in protecting focus between meetings, and the day-of version in surviving a day of back-to-back meetings.

Parkinson's Law — work expands to fill the time available — is usually quoted about projects. Its sharpest application in a meeting-heavy role is preparation, because prep is the one part of a meeting whose duration nobody bounds. An open evening before a board update will absorb an entire evening, and the version produced in the last 45 minutes is frequently the one presented.

The correction is to give preparation a container sized to the meeting's stakes rather than to your anxiety about it: 15 minutes for a status meeting, 45 for a decision meeting, a bounded 90 for something genuinely consequential. Then place that container in a shoulder hour rather than a peak one, because prep is medium-load work and your peak is worth more than that. The trap this avoids is the common one where the preparation consumes the energy that the meeting itself needed.

Energy also has a weekly period, and most people's is similar enough to plan against: a slow Monday, a strong Tuesday and Wednesday, a Thursday that holds if the week has been sane, and a Friday better suited to closing loops than opening them. Three moves follow.

• Put the week's hardest meeting on Tuesday or Wednesday. Monday pays a start-up cost, Friday pays an accumulated one.
• Batch meetings onto two or three days. Meeting days and thinking days each get to be what they are, and the rhythm stops fragmenting every day equally.
• Make Friday afternoon the review, not the deadline. It is the lowest-energy slot of the week and the best possible use of it is looking back at what was decided.

One drain sits outside all of this scheduling, because it is not on the calendar. After each meeting there is the work of remembering: what was decided, who owns it, what you promised. On a six-meeting day, ten minutes of reconstruction each is an hour spent re-deriving something you already heard, and it is drawn from the same account as the meetings themselves. Reconstruction from memory is genuinely expensive cognitive work, which is why a day of meetings leaves you tired in a way the hours alone do not explain.

This is the one part that responds to better capture rather than better scheduling. Earkeep records mic and system audio continuously while it runs and transcribes locally on your device, so the record exists before you decide you need it — no bot to invite, no start/stop to remember. Meetings are defined afterwards by selecting a span on a timeline, or automatically from a connected calendar. Audio is processed only in memory and never written to disk, and the transcript is a plain file you can search or hand to an agent. The post-meeting task becomes looking something up in your trough instead of reconstructing it at your peak.

Energy management is one layer of a system that also includes batching, buffers, and defended blocks. The pillar guide on time management for meeting-heavy roles covers the whole of it; this page is the part that decides which hour a given meeting deserves.

Download Earkeep free for macOS and let the transcript hold what you would otherwise be carrying between meetings.