Energy Audits: A Two-Week Experiment

There's no shortage of opinions on this topic, but most of them stay at the surface, recycling the same advice that's been around for decades without questioning whether it still applies. Mapping your real energy patterns. The goal of this piece is to go a level deeper — concrete, defensible, and grounded in how this work actually shows up in modern teams. You'll see some advice that contradicts what you've heard before. Where I disagree with conventional wisdom, I'll explain why, with examples from real settings. The intent isn't to be contrarian for its own sake; it's to give you a framework that holds up under the messy, high-stakes conditions where this skill matters most.

The simple tracking method

There's a cultural element to the simple tracking method that doesn't get discussed enough. The expectations around it vary significantly across companies, geographies, and industries. What looks rigorous in one context looks bureaucratic in another. What feels lightweight and pragmatic in one team feels reckless somewhere else. Calibrate to the room you're actually in, not the one you've read about online. Read the cues from how senior people around you handle the same moments — that's usually a more reliable signal than any published advice.

A useful test for the simple tracking method: imagine explaining your reasoning to someone whose judgment you respect, three months from now, after the outcome is known. Would your reasoning hold up? Would they nod, or would they politely ask why you chose that path? Most shortcuts feel defensible in the moment but fall apart under that retrospective gaze. Calibrating to that imagined critic is one of the cleanest ways I know to stay honest with yourself about whether you're actually doing the work or just performing it.

There's a version of the simple tracking method that looks impressive but doesn't move the needle, and a version that looks ordinary but compounds over time. The first is performative — it signals that you've done the work without actually doing it. The second is invisible to outsiders but visible in the outcomes. The trick is recognizing the difference in your own work, which is harder than it sounds because the performative version often feels more productive. Boring, repeated, applied consistently is what you're aiming for.

Patterns to look for

When teams skip patterns to look for, it almost never blows up immediately. It blows up four months later, when the cost of fixing it has multiplied and the cause has been buried under layers of subsequent work. By the time the failure shows up, nobody connects it to the original shortcut. The investment now is small — minutes, sometimes — and the avoided cost later is significant. This is one of the structural reasons why senior operators front-load this kind of discipline; they've paid the long-tail cost too many times.

What I've found useful is to separate the visible part of patterns to look for from the invisible part. The visible part is what other people see — the email, the meeting, the deliverable. The invisible part is the thinking that produced it: the alternatives you considered, the frames you rejected, the assumptions you tested. Most career feedback focuses on the visible part, but the invisible part is where the actual quality lives. Investing time there pays back many times over, even though almost nobody will see you doing it.

Be honest with yourself about how much of patterns to look for you're doing for the audience versus for the outcome. There's nothing wrong with optimizing for both — it's how careers get built — but mistaking one for the other leads to systematic blind spots. If you're writing the document mostly to be seen as someone who writes documents, the document will read that way to anyone paying attention. The cleanest output happens when the underlying intent is to actually solve the problem, with the credit being a side effect.

The smallest version of this you can run this week is the right size. Anything bigger is theory; anything smaller misses the lesson.

Designing your week around the data

There's a tendency to over-systematize designing your week around the data, treating it as a checklist to grind through rather than a judgment call to make. The frameworks help — they give you a vocabulary and a starting point — but they're not a substitute for taste. The best practitioners use frameworks to set up the question, then trust their judgment to answer it. If you find yourself mechanically applying steps without stopping to ask whether they apply, the framework has become a crutch rather than a tool. Step out of it periodically to stay sharp.

Designing your week around the data is one of the few skills that genuinely separates senior operators from everyone else. It's not innate; it's practiced, in low-stakes settings first, until you can do it without thinking when the stakes go up. That's the deceptive thing about it — it looks easy from the outside because the people who do it well make it look effortless. They've simply done the reps. If you watch closely, you'll notice they make small choices early that prevent the big problems others end up scrambling to solve.

One small reframe that helps: think of designing your week around the data as a public artifact, not a private one. Even if only one person ends up reading it, write it as if it might be reviewed by a larger audience six months later. That mental shift — from disposable to durable — changes the level of care you bring. It also turns out to be a useful self-check. If you wouldn't want to be quoted on the wording, that's information about whether the thinking behind it is sharp enough to act on.

• Keep the scope tight — broad goals quietly fail in ways that are hard to recover from.
• Choose people you'll actually listen to, not just the loudest voices in the room.
• Measure something concrete, even if imperfect — partial signal beats no signal.
• Review monthly; iterate quarterly; never let a year pass without a serious audit.
• Reset the system rather than patch it once you've outgrown the original frame.

Re-running the audit annually

This is the part most people get wrong on autopilot. Re-running the audit annually sounds straightforward, but it requires deliberate attention every time the moment comes up. The shortcut is to treat it as a habit rather than a heroic effort. Build a small ritual around it — a checklist on your desk, a recurring calendar reminder, a phrase you ask yourself before you act — and the quality starts to compound without conscious effort. The teams that do this well don't rely on individual willpower; they bake the practice into the workflow itself.

In practice, re-running the audit annually is rarely a single decision; it's a sequence of small ones, each of which seems trivial in isolation. The teams that do this well are deliberate about each step — they don't treat any part of the sequence as automatic. The teams that get it wrong often handle the obvious parts well and then drop the ball on the boring middle steps, which is exactly where the value compounds. Pay attention to the parts that feel rote. That's where the gap between adequate and excellent usually lives.

The mechanic most people miss is the connection between re-running the audit annually and trust. When you handle this part of the work consistently, you build a reputation that opens doors you didn't know existed — invitations to harder problems, more interesting projects, the benefit of the doubt during ambiguous moments. The reverse is also true: doing it badly is one of the fastest ways to lose standing, often without any single dramatic moment to point to. The damage accumulates quietly until one day you notice you're not in the rooms you used to be in.

Putting It All Together

This is the part most people get wrong on autopilot. Designing your week around the data sounds straightforward, but it requires deliberate attention every time the moment comes up. The shortcut is to treat it as a habit rather than a heroic effort. Build a small ritual around it — a checklist on your desk, a recurring calendar reminder, a phrase you ask yourself before you act — and the quality starts to compound without conscious effort. The teams that do this well don't rely on individual willpower; they bake the practice into the workflow itself.

In practice, designing your week around the data is rarely a single decision; it's a sequence of small ones, each of which seems trivial in isolation. The teams that do this well are deliberate about each step — they don't treat any part of the sequence as automatic. The teams that get it wrong often handle the obvious parts well and then drop the ball on the boring middle steps, which is exactly where the value compounds. Pay attention to the parts that feel rote. That's where the gap between adequate and excellent usually lives.

The mechanic most people miss is the connection between designing your week around the data and trust. When you handle this part of the work consistently, you build a reputation that opens doors you didn't know existed — invitations to harder problems, more interesting projects, the benefit of the doubt during ambiguous moments. The reverse is also true: doing it badly is one of the fastest ways to lose standing, often without any single dramatic moment to point to. The damage accumulates quietly until one day you notice you're not in the rooms you used to be in.

None of this is exotic — most of it is just deliberate practice applied to ordinary moments. The reason it doesn't feel that way is because the moments are recurring; you see them every week, often without recognizing them as instances of the same underlying skill. Pick one idea from this article, set a small reminder for yourself next week, and see what changes when you apply it intentionally. Then do it again the week after. The compounding here isn't dramatic week to week, but the difference between someone who does this for two years and someone who doesn't is enormous, and almost entirely invisible until it shows up in their outcomes.