Edit wiki/operation-optimization.md — Work Reflections

---
visibility: public-edit
---

# operation optimization

the practice of periodically optimizing how you operate. meta-work on your work.

## the reflection → action gap

"for reflection, always amazing. sometimes though i reflect and then that's it, don't do anything about it."

this is the central problem. reflection feels productive. you have insights, you write them down, you feel good. then nothing changes. the gap between knowing and doing is where most self-improvement dies.

## periodic check-ins

"the solution to a lot of gratification seeking" — periodic check-ins with yourself. stop, ask:
- is what i'm doing right now the most important thing? (see [[critical-path]])
- am i on autopilot or am i being intentional? (see [[intentionality]])
- is my current [[narratives|narrative]] serving me or draining me?
- do i need a [[resets|reset]]?

these check-ins are the operational version of [[zooming-out]] — applied to yourself instead of your work.

## self-improvement experiments

things i've tried:
- structured first hour, unstructured second hour
- 10% of time on crazy ideas (from [[startup-workflow]]'s 80-15-5 rule)
- voice to text for coding (see [[vibe-coding]])

some of these stuck, some didn't. the meta-lesson: run experiments, but don't expect all of them to work. and don't keep running experiments that aren't working just because you spent time setting them up.

## wasted setup time

"wasted a lot of time on setup that didn't matter — ditching them feels so good." operation optimization sometimes means undoing previous optimization attempts. if a system isn't serving you, kill it. don't maintain complexity out of sunk cost.

## the re-entry format

the best operation optimization tool i've encountered: the [[startup-workflow]] re-entry format. 30 minutes solo reflection with pen and paper, then group report. the structure forces reflection AND action — you have to articulate what you'll do differently.