Principlesof Impact

Easy-to-count activity can quietly replace the outcome that mattered in the first place.

• Name the human or system-level change first.
• Choose the smallest signal that would show movement.
• Retire metrics that reward motion without meaning.

A perfectly optimized week can still produce very little that matters.

• Judge a week by mission advancement, not task completion.
• Protect capacity for consequential work before filling the gaps.
• Use productivity tools to serve judgment—not replace it.

Beautiful plans often depend on conditions that disappear the moment real work begins.

• Design around constraints before adding ambition.
• Make the next action obvious under pressure.
• Prefer a small system people use to a complete system they avoid.

Stories inspire action, but unbounded stories can hide uncertainty and make weak lessons look universal.

• State what the evidence does and does not show.
• Separate observation from interpretation.
• Invite disconfirming evidence before declaring a lesson.

Polished success stories travel farther than the messy instructions that would make them useful.

• Publish the method alongside the outcome.
• Name the conditions and resources the work depended on.
• Make adaptation easier than imitation.

Perfectionism delays learning; endless iteration without a standard can become motion without progress.

• Start with what is already working.
• Choose one improvement with a clear reason.
• Run another cycle before adding more complexity.