inbox processing
To have a strong capture flow, you need strong inbox processing.
It's all about confidence in your future self empowering the present you to get it all out of your head.
Then, once you've captured just way too much, trust that a process can squeeze the value out of the gibberish without taking you down with it.
Tools are great, but they have to be maintainable (as in, very little code).
inbox processing thoughts
from today's ideas.org review:
targets:
- prompts
SPC m r r 'promp...' RET - icebox
SPC m r r 'ice...' RET - archive
SPC m A
thought process is roughly:
- still relevant or inspire any excitement?
- any urgency? -> icebox.org
- enough detail to be executed? -> icebox.org
- stuff to explore/flesh out? -> prompts.org
- not relevant? -> archive!
- not sure? -> prompts.org
prompts.org is really my garden's inbox
it could be better as notes/inbox.org
for some questionable relevance things, the thought is that fleshing it out as a note will help surface the value - should this even be done? what would it be like?
for others, it's thought of as a quick add to a list of some kind - examples of annoying errors, influential movies/books i'd recommend...
other are ideas to share that i'll never actually get to - don't let it die with me
others are just content used to describe features of the workflow, routines,
processes that i run from memory - just trying to get explicit
inbox-processing, eh?
it's expected that prompts will brutally flesh out/write something or archive it. no hesitation. get it outta here. it'll come back if it's relevant.
Backlinks
To have a strong capture flow, you need strong inbox processing.
It's all about confidence in your future self empowering the present you to get it all out of your head.
Then, once you've captured just way too much, trust that a process can squeeze the value out of the gibberish without taking you down with it.
Tools are great, but they have to be maintainable (as in, very little code).