What does it mean that capture must be frictionless?

If capturing a thought takes more than a few seconds, you will not do it consistently — and inconsistent capture means permanent information loss.

Example: You're walking back from a one-on-one when a solution to a cross-team dependency clicks into place. By the time you reach your desk, open a new document, and try to title it, the insight has degraded. You write something vague like 'talk to Platform team about shared API.' The original thought — which included a specific sequencing idea and a migration path — is gone. Not because you're forgetful. Because the capture path had too many steps.

Try this: Time your current capture workflow. Open a blank note on your phone or computer right now and start a stopwatch. Write a single sentence — any sentence. Stop the timer. If it took more than 5 seconds from intent to first keystroke, identify the friction: unlocking, finding the app, choosing a notebook, waiting for sync. Now try it with the fastest method available to you (voice memo, widget, keyboard shortcut). Record both times. The gap between them is the friction tax you're paying on every thought.