Our team’s got generative AI tools scattered all over the place—it’s a common headache. Designers each use their own thing, some on MJ, some on SD, and prompts, assets, and styles are all stuck on personal machines. The moment someone leaves, the assets just vanish.
We tried to rein it in, not by forcing everyone onto one tool, but by setting a unified output and standards: pick a few core tools, build a shared team library for common prompts and LoRAs, and agree on delivery formats and naming conventions. Tools can be diverse, but style standards, asset accumulation, and review workflows need a single point of control. Otherwise, you’re starting from scratch every time, and even the best tools won’t help you build anything up. How does your team handle this mess?
We’ve been burned on shared prompt libraries before—if nobody maintains them, they turn into a dumpster in six months.
Honestly, it’s hard to settle on one main tool—different designers have their own habits, and forcing it on them will just cause drama.
The hardest thing to actually enforce is naming conventions. I’ve told people a hundred times and they still just save everything however they want.
We ended up setting up an internal wiki with a LoRA list, so at least the assets stay even if people leave.
Totally agree on the style consistency thing. Use whatever tool you want, but the output should look like it’s from the same family.
We do a weekly asset archive—everyone’s gotta dump their stuff into the shared drive, no exceptions. Otherwise, you’ll never build up a decent collection.