Cycle frequency matters more than step quality. The more…

April 2, 2026

Continues Nobody knows the right answer upfront. So reduce everything to cycles:…

Cycle frequency matters more than step quality. The more iterations you run, the higher the chance one of them hits the mark.

Backlinks

Today you need to re-strategize every few hours. A weekly retrospective is already too slow. →

This principle is why management has been shortening cycles for decades — from annual reviews to quarterly OKR to weekly sprints to continuous flow. Each step buys more attempts per unit of time. →

Feedback Loops

2039604195364647207 — reduce everything to cycles: hypothesis → action → feedback → adjust

2039604487682486628 — cycle frequency matters more than step quality

2039604691202662534 — re-strategize every few hours; weekly is already too slow

2039604827538550874 — the cycle applies to agents, products, companies, and life

2039603982247870958 — Taleb: tinkering beats planning in complex systems

2039606964775444504 — convex tinkering: small errors, large potential gains

2039607159978328172 — hypothesis → action → feedback = Scrum's empirical process control

2039607374038880401 — shortening cycles buys more attempts per unit of time

→

PID Control Most management frameworks operate P-only or at best PI. The derivative component requires frequent, reliable measurement — which is why shorter feedback cycles (xettel) enable better control. →

Stability in Feedback Systems

A team that over-corrects after a bad sprint (hiring spree, process overhaul) may oscillate between extremes

Quarterly OKR reviews (xettel) have high latency — by the time the error is detected, the correction may already be stale, producing overshoot

Shortening the feedback cycle (xettel) reduces lag, which improves stability — but only if the measurement is reliable

→