A systematic approach for managing project folder structures

There is an evil problem with all digital products design processes. Every company, design team or a designer itself sooner or later faces a challenge when it is impossible to quickly find an old-version source layout, understand a file’s relevance or find project-related resources.

It seems like a simple rule — to have a smart folder system. Moreover, it looks easy to think out something useful. But I faced many people who decided not to make a system at the first stages of work processes (startups or novice/junior designers usually).

I faced companies who build a system that was wrong because of their project specification. And it cost them several months to re-group and synchronize everything when it all gone too far.

I witnessed those who decided to use a very ill-conceived system even when they know how to do it correctly. Such people do their work fast at the first stages of a project’s life. But after several months, when the project grows, faced the same problems as I mentioned above.

Worst of all, I met those who prefer senseless, spontaneous workflow accessible only to their understanding.

Do not try this at home. Never ever.

In the future, when projects become frequent, their number grows, and the projects themselves grow, this leads to bad consequences — from the pure waste of time in a vain effort to find something to a colossal design department’s performance dropdown.

A good, structured catalog of projects and relevant resources proofs design-processes and teamwork, speed-ups designer’s work. It helps new employees to natively understand the catalog. It also allows separate accesses for security issues.

Author: Igor Kulemza

Collect by: uxfree.com