When designers can’t find the right file, they may remake it, delay a handoff, or use an outdated version. Before blaming untidy folders or individual habits, look at how your team stores, approves, and retrieves images. These seven signs can help you decide where that workflow needs attention.
Sign 1: designers rebuild assets they know exist
“It’ll be faster to just remake it” is a warning worth listening for. A designer knows the hero banner or product icon exists somewhere. They can’t pull it up in search, the thumbnails look alike, and file names say IMG_4829 or banner-new. So they open Figma or Illustrator and start over.
That’s search failure, not speed.
Rebuilding feels productive in the moment, but it rarely is. The new version drifts a little: the corner radius shifts or color values move a few points, and spacing tightens. No one means to break brand rules. They just don’t have the editable masters in front of them. And when deadlines press, “close enough” ships.
A useful first check is to ask how often this happens in a month. If you hear the story often, your library isn’t searchable. Create one shelf for approved work where final files live with clear dimensions and usage notes, and keep working drafts elsewhere. If designers still can’t find that shelf in seconds, the retrieval problem needs attention before you ask people to be more disciplined.
Not every rebuild is a retrieval failure, though. Sometimes a designer genuinely needs a new supporting photo or illustration rather than something already in the library, and the search spills across old folders, saved attachments, and open browser tabs. When that happens, a searchable image database can shorten the hunt for usable starting points, with license and permission records still needing review before use. Keep that sourcing step separate from your internal approved files, which need their own governed home with names, tags, and version notes your team controls.
Sign 2: file names try to do version control
File names tell the story. When you see logo_final_v2_approved_FINAL3.png next to logo_final_v2_USE_THIS_ONE.png, no one knows what’s current. The suffixes were meant to help. They’ve become a private code that only made sense on the day someone typed them.
The mess usually starts with good intent. A designer saves a variant for review and a teammate renames it for a deck. Weeks later, both copies look official. The handoff breaks down at this point because product and web teams pull whatever ranks first in results. Wrong dimensions ship, or a low-res PNG lands where an SVG belonged.
Consistent naming helps, but names alone cannot explain approval decisions or preserve a change history. A useful reset is to choose one authoritative export per use and move the rest into an archive folder with dates. Keep approved exports apart from working files. If your team still argues about which file won approval, you need version history that lives with the asset rather than inside its name.
Sign 3: only one person knows where things are
Ask where the launch imagery lives and everyone points to the same person. She’s been here longest. She remembers that the homepage carousel sits three folders deep under Campaigns 2023, except the video stills, which are on her desktop because the drive ran out of space.
That arrangement is fragile. When she takes time off, changes roles, or leaves, no one can browse with confidence because the structure lived in her head. A folder structure can feel obvious to its creator while leaving colleagues unsure where to start.
Search versus browse is the split to watch. Browse asks people to remember paths. Search lets them describe what they need and get a match. If your team can’t find core assets without asking a guide, tribal knowledge is your system. A first move is to write down the ten assets people ask for most and put them where anyone can search by name or campaign, with file type as another way in. If that list keeps growing, you need metadata and tagging rather than deeper folders.
Sign 4: new hires can’t find their footing
New hires show the cracks fast. They join with fresh eyes and good habits. Then they spend their first days pinging the channel to find the logo pack, learn which product shots are cleared for the site, and work out whether a Figma file is current or just a concept.
It’s awkward for them and draining for the team. A senior designer stops real work to play tour guide through a maze of shared drives and email threads. Brand guidelines don’t help much when they aren’t linked to the actual files. People read the PDF, then still grab the wrong shade because the swatch file is buried.
A DesignOps lens helps here. Treat slow ramp as a signal about access quality rather than a normal part of joining. Give every newcomer a starter kit on day one with logos, fonts, templates, and go-to photography, each labeled with dimensions and approved uses. Time how long it takes them to ship their first work without help. If they still need constant rescue, your storage may be tidy for veterans and opaque for everyone else.
Sign 5: assets live in too many places at once
Desktops hold quick exports, while email holds “final attached” threads and chat holds links that expire. One drive holds marketing decks and another holds product shots. No one planned it this way. It grew file by file.
Scattered storage creates quiet risk. Two versions of the same banner circulate and no one knows which one passed review. A designer pulls a print-ready master and shrinks it for web without noting the change. A contractor grabs an old folder and reuses imagery that was meant to be retired.
Cloud storage such as Drive or Dropbox can work well for general docs and simple sharing. Many teams find image work needs tighter handling around visual preview, dimensions, and status. You can browse a doc by title. You can’t judge a crop or color grade without seeing it. A first cleanup is to map where approved visuals actually sit and retire duplicates. Name one home for final, approved imagery and move working files and personal stashes out of the path. If people keep saving to side places because the main home is slow or confusing, listen to that complaint. It tells you what the next system must do better.
Sign 6: old graphics keep slipping into new work
This one shows up in public. An old mark appears on a landing page, or last year’s campaign photo returns in a sales deck. Social posts use a palette that was replaced two quarters ago. Customers may not name the error. They feel the sloppiness.
There are usually two causes. First, deprecated files were never marked or moved, so old and new sit side by side with similar names. Second, teams outside design don’t know how to tell current from retired. Marketers and partners want to move fast. They grab what looks right.
Brand equity erodes this way, file by file. The fix starts with clear status. Mark retired assets as retired and pull them from active shelves. Keep approved visuals paired with short notes on where each one may be used and when rights or seasonal windows need a second check. Asset licensing details deserve the same care, with source and expiry kept where anyone can review them before publishing. If you can’t answer “is this cleared for this use” without a Slack hunt, your provenance notes aren’t close enough to the files.
Sign 7: searching eats more of the day than designing
Watch a designer’s afternoon. They open three drives, skim thumbnails, try three spellings of a campaign name, ping a teammate, wait, try again. Flow breaks. The layout problem they meant to solve sits untouched while they hunt.
Context switching costs time and attention. Each failed search pulls focus away from decisions about type and spacing, or the composition as a whole. People get tired and settle. They pick a passable photo instead of the right one, or stretch a small image beyond the dimensions it can support. Creative rework grows because choices made under time pressure need fixes later.
You won’t solve this with pep talks about tidiness. Individual care can’t carry a shared system. Ask your team where searches die most often, whether they’re looking for product photography, icons, or motion stills. Log which queries fail for two weeks and look for patterns. If the same gaps repeat, you don’t need more effort. You need faster paths from intent to file, with previews, filters for size and format, and plain words that match how people actually talk about the work.
What a steadier workflow looks like
A steadier setup has one door for approved work. Designers and marketers know where to look first, as do developers. Files carry status and dimensions, with related masters attached so no one has to guess. Version notes sit with the asset. Retired work is out of sight but still retrievable when you need history. That shift from loose files to a managed library is what people mean by Digital Asset Management thinking at small scale.
Before you buy or build anything, assess what search must do for image work. People should be able to filter by orientation, dimensions, color, and file type, and preview without downloading a dozen near-duplicates. They also need to see which master produced an export, whether that’s a PSD, AI, or Figma source. Can they tell an approved web export from a print master at a glance? Ask how tagging works, who can add or edit terms, and how rights records stay attached to the file. You don’t need every answer on day one. You need a short list of must-haves drawn from failed searches your team just logged.
Start lean and prove value. Audit a slice of high-use assets rather than the whole archive. Pick one product line or one campaign family. Toss clear duplicates and label masters and exports, then add plain tags with dimensions and approved uses. Move in stages so daily work never stops. Make search the default path and keep browse shallow for those who still like folders. When the pilot shelf saves time for designers and for partners who pull from it, you’ll have a story that leadership can grasp without a hard sell. Costs and tradeoffs are real, so weigh them against fewer rebuilds and fewer late-stage swaps.
Tidy files won’t save a weak system. A clear home with searchable names, honest status, and linked masters will. Fix the path to the work and the work gets better.
