work systems

🧭 what this is

a place for the systems that help work stay findable, survivable, and slightly less likely to become a haunted spreadsheet with teeth.

this is not about becoming perfectly organized.
it is about leaving myself enough breadcrumbs that future me does not have to become a detective in her own disaster museum.

🗂️ core rule

work needs:

• a place to land
• a clear current state
• a next action
• a way to return after interruption
• a “good enough” finish line

🧺 intake

new work goes into one of these buckets before it becomes a swarm:

• inbox / intake - not sorted yet
• active - currently being worked
• waiting - waiting on someone else
• review - done enough, needs confirmation
• complete - finished and confirmed
• holding - messy capture, not ready to process

🪜 task flow

1. capture the task
2. clarify the outcome
3. find or create the file/location
4. identify the next visible action
5. move it to active
6. work until either finished, blocked, or interrupted
7. leave a return anchor
8. move it to waiting, review, or complete

🧷 return anchors

when interrupted, leave one breadcrumb before switching away:

• save the file
• leave the tab open
• write the filename/path
• write the next step
• mark the status
• say the task name out loud
• leave a short “resume here” note

📁 file habits

• use lowercase / kebab-case when possible
• use clear descriptive filenames
• include dates like 20260505-that-slideshow
• increment by adding letter after date like 20260505b-ugly-postcard
• keep active files in a known place
• avoid mystery names like final-final-real-final-v7
• status folders are a must
• asset folder organization is important FROM THE START
• use status words only when they help:
  • working
  • draft
  • review
  • final

🧠 decision rules

when stuck, ask:

• what is the expected outcome?
• who is waiting on this?
• what happens if this is late?
• what is the smallest safe version?
• what information is missing?
• do i need to ask, decide, or just start?

📬 email rules

• urgent-looking email does not automatically become the whole day
• acknowledge first if needed
• execute later if it is not truly urgent
• turn vague emails into specific next actions
• if tone feels “off,” pause before responding
• if expectations are unclear, ask early
• do not mentally hold emails like cursed little pigeons

🖥️ tool-switching rules

switching tools costs brain coins.

before switching, write down:

• what i am doing
• where the file is
• what i need from the next tool
• where i should return afterward

🧯 when the system starts failing

signs:

• too many open tabs
• rereading the same email
• forgetting what i was doing
• everything feels equally urgent
• new “organization” suddenly seems irresistible
• active work has no next step
• files are open but untouched
• i am hunting for things instead of doing things

reset:

1. stop adding inputs
2. list the loose tasks
3. choose one active task
4. write the next action
5. close or park everything else
6. do one visible step

🔗 probably connected to

• overwhelm-patterns
• avoidance-loops
• focus-vs-interruption
• clarity-vs-ambiguity
• energy-vs-motivation
• ways-i-trick-myself-into-starting
• things-that-feel-productive-but-arent
• low-energy-defaults

🪴 note to self

a good system is not one i follow perfectly.

a good system is one that still works after sleep fog, interruptions, emotional weather, and the sudden appearance of a task shaped like a wet raccoon in a necktie.