RunEvr
Agentic project management environment for creatives
Start new thread

Folders don’t store context. And that’s the problem.

by•

Where does your team keep project materials today?

Google Drive? Dropbox? Notion? Somewhere else?

We noticed something interesting while working on creative productions: finding a file is usually not the hardest part.

The hard part is remembering:

- Why was this version created?
- What feedback led to these changes?
- Which direction did the team agree on?
- Is this still the latest approved version?

A folder can store thousands of files, but it doesn’t always store the story behind them.

That’s something we’ve been thinking about while building RunEvr’s Materials module.

We wanted materials to stay connected to the workflow so context moves with the work.

Curious - how does your team handle this today?

Do you feel like you’re losing context around your files?

49 views

Add a comment

Replies

Best

Great point! Right now we solve this with strict naming convention and maintaining a living document in Notion that links to Drive files with status updates. It works but it requires a huge amount of manual upkeep and team discipline. The idea of contex moving with workflow automatically sounds like a game changer.

 Exactly - this is the challenge we kept seeing too.

Naming conventions and living documents can work, especially with a disciplined team, but over time they become another system that someone has to maintain.

Thanks for sharing your workflow details.

We’re collecting these approaches to better understand real production workflows and make RunEvr more useful.

I think the trend is actually moving toward keeping more and more of this stuff in git. Not just code, but docs, specs, skills, changelogs and etc. Expecially with ai agents becoming part of the workflow, having everything versioned in one place starts to make a lot of sense. Git already gives you history, authorship, branches and the context of why something was changed

 Interesting point. Git is definitely becoming more than a code repository - especially with AI workflows, version history and context are becoming increasingly valuable.

The challenge we see in creative teams is that not all work lives in Git: assets, reviews, visual iterations, client feedback, and approvals often happen across different tools. The bigger question is probably how to keep the history and reasoning connected to every type of work.