A self-reflective process on tools, backups, and the underrated art of letting go.

There are two kinds of people:

1. People who archive their projects.
2. People who insist they will “sort it later” and then die surrounded by folders named “Final_FINAL_ReallyFinal.”

If your life is dominated by projects – client work, bird outings, rescue calls, content drafts – your “archive” isn’t just storage. It’s your second brain. And if you don’t build it intentionally, it becomes a landfill with a search bar.

I’ve learned this the hard way and also the oddly beautiful way, because one of the most important things I’ve built in the last few years (my personal brand name) came from an old client folder I would’ve lost if I didn’t archive properly.

More on that in a bit.

1) The goal isn’t saving everything. It’s finding the right thing quickly.

Most people think archiving is about hoarding files responsibly.

It’s not.

It’s about being able to answer future questions like:

• “Where’s that client deck from 2021 that had the good framing slide?”
• “Did I already shoot this bird in that exact light or am I hallucinating?”
• “What was that rescue where the snake was stuck behind the drain cover and the torchlight made it look like a horror film?”
• “What the hell was I thinking when I named this folder ‘new’?”

A good archive should give you:

• Retrieval (find it fast)
• Context (remember why it exists)
• Resilience (survives laptops, phones, accidents, and bad decisions)

2) Your three project types need three different archiving styles

Here’s the mistake people make: they treat all projects the same.

But client work, bird photography, and snake rescue videos behave differently. So they should be archived differently too.

A) Client work: “proof + process + portability”

Client projects are about:

• deliverables (final decks, docs, videos)
• supporting material (research, notes, drafts)
• the ability to reuse thinking later (frameworks, slides, language)

What to keep

• Final deliverables
• 2-3 key drafts (not every micro-version)
• Supporting research if it’s reusable
• A “best slides” folder if you tend to borrow from yourself (you should)

What to kill

• Endless duplicate exports
• Old fonts/asset dumps that are irrelevant
• “Version soup”

B) Bird photography: “searchability beats sentimentality”

Bird photography creates volume. Archive success here is less about folders and more about metadata and selection discipline.

You need:

• date and location in the folder name
• consistent “selects” vs “all raws”
• tags/keywords for later search (species, habitat, behaviour)

If you can’t search “Barbet + backlight + 2024” and get results, you don’t have an archive. You have a darkroom without labels.

C) Snake rescue videos: “story packaging”

Rescue footage is neither client work nor wildlife art. It’s a third thing: documentation with stakes.

Here the archive isn’t just media, it’s narrative material.

You want to preserve:

• the raw footage (for future edits)
• the final edit (for social/YouTube)
• the “story spine” (what happened, where, why it matters)
• any learning notes (what you’d do differently next time)

This category benefits massively from a simple README note (more on that below).

3) Choose a structure that respects time (because memory does)

The simplest archive that stays usable is:

Archive /

2025 /

• Client_Work
• Bird_Photography
• Snake_Rescues
• Personal_Brand (optional, for Shifting Radius / Nanusense / experiments)

Inside each category, use the same logic:

Client_Work

2025-08 ClientName_ProjectName

Bird_Photography

2025-12-02 Location_OutingName
(then subfolders: RAW / Selects / Exports)

Snake_Rescues

2025-11-06 Location_Species_QuickNote
(then subfolders: Footage / Audio / Exports / Thumbnails)

The date prefix is not a nerd flex. It’s how folders auto-sort into a timeline without you doing any work later.

4) The one habit that upgrades everything: a 2-minute README

Every “archived” project gets a tiny note called README.txt.

Two minutes. No more.

It answers:

• What was this project?
• What is the final output?
• Any links (YouTube, blog, client delivery, Instagram)
• Any key context you’ll forget
• Any “next time do this” lessons

This is how you stop your archive from being a pile of mute files that look familiar but refuse to explain themselves.

5) Backups: boring, essential, and deeply unforgiving

You don’t need an elaborate setup. You need a setup that survives reality.

A clean rule:

• Working copy (laptop / active drive)
• Local backup (external SSD)
• Offsite backup (cloud)

That’s it.

Because the truth is: you don’t back up because you expect disaster.
You back up because disaster doesn’t ask permission.

6) Letting go: the actual hard part

Every project archive has a graveyard: abandoned ideas, half-edits, experiments, drafts that were “promising.”

The reason we keep them isn’t utility.

It’s identity.

Deleting old project files can feel like deleting proof that you were once the kind of person who started that thing.

So here’s the compromise I use:

Keep three things:

1. Proof: finals and published outputs
2. Pieces: reusable assets (templates, select footage, best stills)
3. Personal meaning: a few files that matter emotionally, not professionally

Everything else moves to:

• Graveyard/
  And gets one rule:
  If untouched for 18 months, delete it or compress it into a single vault zip and exile it.

You’re not erasing your past. You’re reducing noise so the future can be built.

7) The Shifting Radius story: why archiving pays you back

Here’s why I take this seriously.

Years ago, back when we used to help clients name their companies, we created a list of name options for a property management company in the US. And one name stayed in my head for no practical reason: Shifting Radius.

It had that rare combination: sharp recall, clean sound, and an explanation you could build a brand around.

Fast forward to when I took birding seriously and wanted a single umbrella name for all my hobbies – photography, wildlife, storytelling, all of it.

I didn’t try to “invent” a name.

I went back into my own archive.

I remembered the year, the client, the naming files. I dug it out, reread the list, and there it was still good, still mine in spirit.

One simple Google search showed it wasn’t being used. I registered the domain immediately.

That’s the difference between a messy hard drive and a real archive.

A real archive lets you reclaim your own ideas.

It’s not nostalgia. It’s retrieval.

8) The monthly ritual that prevents chaos

If you don’t do this lightly and regularly, archiving turns into a once-a-year existential crisis.

Once a month (30 minutes)

• Move finished client work into Archive
• Cull bird photos: keep RAW + Selects, ditch junk duplicates
• Label rescue footage and write a quick README
• Run backup

Once a quarter (2 hours)

• Consolidate phone dumps + WhatsApp media
• Clean the graveyard
• Update your “Project Index” (optional but powerful)

Your archive is your memory, but better behaved

Memory is unreliable. It rewrites the past. It forgets details. It confidently lies.

An archive doesn’t.

And sometimes, it hands you a gift, like a name you planted years ago for someone else, only to realise it was quietly waiting for you.