Search
Browse Categories
Final-Final-V4
UX

The Day 'final-final-v4' Finally Died

Why the file naming problem was never about the files.

• Updated • Return to all posts

At some point in every design career, you end up staring at a folder that looks like this:

  • final.psd
  • final_v2.psd
  • final_final.psd
  • final_FINAL_v4_USE_THIS_ONE.psd

Everyone laughs. Nobody fixes it.

Raven Note
“Final” has never meant final. It means “I’m tired and I know we're not done.

Those files weren’t bad organization. They were emotional armor, so you didn’t lose what you did when you knew your boss was going to change their mind again. Every decision needed a backup plan. Every tweak became a new universe.

Anxiety with puncutation, if you will.

Then the Application Changed

I just… stopped opening Photoshop. I opened Figma instead.

And quietly, the entire tone of the work changed.

The file stayed alive. The canvas stayed active. History stopped being something you had to protect.

Raven OMD
Undo exists. Version history exists. The world did not end.

Suddenly, duplicating a file felt unnecessary. Weird, even. Why fork reality when you could just… keep working?

The Weirdest Part: We Didn’t Plan This

Nobody sat down and said:

“Okay team, from now on we will stop naming things final_final_v4.”

It just… stopped happening.

Because the tool stopped rewarding that behavior.

Raven Spicy
Turns out a lot of “process problems” are just tool side effects.

We Didn’t Rename Files. We Renamed States.

This is where it actually shifted.

Instead of naming things after confidence levels, we named them after where they were.

  • 🟡 In progress
  • 🔵 For review
  • 🟢 Ready for dev
  • 🗄️ Archive

Dates instead of version numbers. Status instead of promises.

Nothing was “final.” It was just ready for the next design phase.

Raven Note
“Ready for dev” is a way better commitment than “final.”

And suddenly, the pressure disappeared.

The Tool Changed the Workflow (Without Asking)

What changed wasn’t discipline. It wasn’t maturity. It wasn’t a better team.

It was the environment. The software made some habits pointless. So we stopped doing them.

Raven Note
You don't become better designers from tools alone, but you can become a calmer, more organized one.

What I Learned (So You Don’t Have to “Final-v5” Again)

  • Tools can shape behavior more than process docs ever will.
  • If everyone is clinging to “final”, something upstream is broken.
  • Good tools don’t force better habits - the can make bad ones unnecessary.