On most design teams, inspiration is personal. Each designer has a folder, a board, a bookmarks bar. When someone leaves, their references leave with them. When two people work on the same feature, they find the same examples twice. And the brilliant onboarding flow the senior designer saved last year never reaches the junior designing onboarding this quarter.
A shared design reference library fixes this without anyone giving up their own collection. Here is how to set one up so it stays useful.
Decide what is shared and what is personal
Not everything belongs in the team library. Personal taste, half-formed ideas and things you saved because they were pretty can stay in your own library. The shared one is for references the team will act on.
- Screens from your own product, for before-and-after and for consistency.
- Competitor and adjacent-product screens, tagged by company.
- Patterns the team has agreed to use, and examples of them done well.
- Patterns the team has agreed to avoid, with a note on why.
- Anything a stakeholder has pointed at and said "like this".
Make search do the organising
Teams default to folders because folders feel shared. They also fail faster with five people than with one, because five people file the same thing five ways. See when folders stop working.
Instead, pick a tool that reads the text in each screenshot and tags what it sees, so anyone can find "competitor pricing pages" or "empty states" by typing that, regardless of who saved them or where. Then agree one convention that humans have to follow: every save gets one line on why it is there.
Assign an owner
Shared things without an owner rot. One person, rotated quarterly if you like, is responsible for the library: deleting duplicates, sharpening notes, removing references to products that no longer exist. It takes about thirty minutes a month.
Review it together, briefly
Ten minutes at the start of a monthly design review. What got saved, what surprised anyone, what is stale. This is also how new references reach the people who need them, because the person who saved the great table pattern mentions it out loud to the person about to design a table. The individual version of this habit is in a weekly inspiration review.
Which tools support it
- GetRef offers shared libraries where every member can capture with the browser extension, and everything is read and tagged automatically so search works across the team's saves. Built for exactly this use.
- Eagle libraries live in a folder, so sharing means a synced folder through Dropbox or similar. Works for small teams; the sync is your responsibility. Alternatives in the best Eagle alternatives.
- Milanote and Figma boards are collaborative and good for curating a shared moodboard for one project. Weak as a long-term searchable archive. See how to make a UI moodboard.
- Are.na channels are collaborative, thoughtful and public by default. Good for research in the open, less so for a competitor library.
- Pinterest group boards work but are public unless secret, and offer no text search inside images.
For a deeper comparison, the best reference saving tools covers capture, search and privacy across all of them.
A note on privacy
A team reference library often contains competitor screens, unreleased internal work and stakeholder feedback. Default to private. Are.na and Pinterest are public unless you remember to change it; check before you save.
Setting it up in a week
- Pick the tool and create the shared library.
- Each designer moves their best 20 work-related references into it, with one line each.
- Agree the one convention: every save gets a note.
- Name the owner.
- Put ten minutes on the next monthly review.
After that the library grows on its own, because saving into it is the same one-click action as saving into a personal one.
Common questions
- Why should a design team share a reference library?
- Because otherwise every designer keeps a private hoard, the same references get saved five times, and the pricing page one person found never reaches the person designing pricing. A shared library turns individual taste into team knowledge.
- What should go in a shared design library?
- References tied to problems the team actually works on: your product areas, your competitors, patterns you have agreed to use or avoid. Personal inspiration can stay personal.
- How do we keep a shared library from becoming a dump?
- One owner, one note per item explaining why it is there, and a short monthly review to delete what has gone stale. Search matters more than structure, so pick a tool that reads and tags images automatically.
- Which tools support a shared reference library?
- Eagle libraries can be shared through a synced folder, Milanote and Figma boards are collaborative, Are.na channels are collaborative and public by default, and GetRef offers shared libraries for teams. The right choice depends on whether you need search inside screenshots.
