The first few icons are easy. Search, add, settings. Then your dashboard needs a billing destination, a share action and a way to export a report. Those choices deserve a review before they become imports scattered across your components.
Here is a practical exercise you can use when evaluating a candidate icon family. Take twelve actions from one screen, record a candidate for each, and review them together in the layout where they will appear.
The worked example uses Heroicons v2.2.0, 24-pixel outline variants, with twelve named source files. It is an illustrative selection exercise. There are no user-study results or rankings attached to it.
The twelve candidates used in this exercise. Icons by Tailwind Labs, from Heroicons v2.2.0, under the MIT license.
1. Write down what each action actually does
Give each row a concrete outcome before opening the icon picker. “Billing” could open invoices, payment methods or a subscription page. “Share” could copy a URL or invite someone to collaborate.
For this example, the outcomes and candidates are as follows.
| Action | Outcome in this example | Heroicons filename |
|---|---|---|
| Search | Find a report by its title | magnifying-glass.svg |
| Filter | Limit the visible reports | funnel.svg |
| Sort | Change the order of the report list | arrows-up-down.svg |
| Add | Create a new report | plus.svg |
| Edit | Modify one report | pencil-square.svg |
| Delete | Remove one report after confirmation | trash.svg |
| Download | Save an exported report locally | arrow-down-tray.svg |
| Share | Open the report-sharing dialog | share.svg |
| Notifications | Open recent account notifications | bell.svg |
| Settings | Open workspace settings | cog-6-tooth.svg |
| Billing | Open payment and subscription settings | credit-card.svg |
| Sign out | End the current account session | arrow-right-on-rectangle.svg |
These mappings are candidates for this particular interface. If your billing page is primarily an invoice archive, review a document or receipt candidate as well. If Share only copies a link, compare that choice with a link symbol and the label “Copy link.”
The useful deliverable is a table that another developer can understand without repeating your searches.
2. Check coverage before polishing individual icons
Try to fill every row from the same family and variant. Record any unresolved row immediately.
All twelve candidates above are present in the chosen Heroicons release. That establishes file availability for this exercise. Whether each candidate communicates the intended action still needs review in your product.
Give every row one of three review statuses.
- Ready for implementation — a candidate is selected, with a label and a destination or action defined.
- Needs comparison — two candidates remain plausible, or the intended meaning needs clarification.
- Needs another solution — the family lacks a suitable candidate for the product requirement.
Avoid quietly filling a difficult row with an unrelated family's icon. Record the exception so the team can decide whether to use a text label, commission an additional asset, or reconsider the family.
3. Put the candidates into a small screen fixture
A grid makes omissions easy to spot. A screen fixture reveals the spacing and density of the actual controls.
In the example below, the same report layout uses 16-pixel icons on the left and 24-pixel icons on the right. Search, Filter and Sort keep visible labels. The repeated row actions use Edit, Download and Share in the same order.
Illustrative screen fixture rendered from the original SVG paths. Display sizes are defined in the source artwork. Resize or zoom the article image only for inspection, then check the icons at actual CSS sizes in your application.
Look at the busiest row first. Can you distinguish the pencil, download tray and share symbol at the size your layout allows? Do their surrounding spaces remain comfortable when a report title is long?
Review the control's clickable area separately from the visible icon. A 16-pixel drawing can sit inside a larger button. The illustration shows candidate placement, while your implementation must provide the actual controls, labels and interactions.
Repeat the check on the backgrounds your application uses. Keep any conclusions specific. “We prefer the 24-pixel version in this report row” is an actionable design decision. A universal verdict about the icon family would require much broader evidence.
4. Resolve the rows that need more than a symbol
Two rows deserve particular attention in this sample.
Sort needs to communicate more than its availability. Once a user chooses an order, the interface should expose the current field and direction, for example “Date, newest first.” Record that requirement beside the icon choice.
Delete needs a clear scope. “Delete report” and “Delete selected reports” should not become indistinguishable actions just because they share a trash symbol. Keep the scope in the label and any confirmation text.
This review produces implementation requirements as well as SVG selections. Keep them together so they survive the handoff.
5. Keep the source and license beside the selection
For each chosen asset, record the family, variant, version, original filename and source URL. For this example, all files come from the optimized/24/outline directory of the Heroicons v2.2.0 release.
Retain the upstream license notice with your asset package. The Heroicons release includes an MIT license from Tailwind Labs. Consult the actual license text for its terms, and check the relevant source separately when adding assets from another family.
Heroicons v2.2.0 source directory · Heroicons license
6. Leave a record that survives the next redesign
A small selection record can contain both the asset identity and the decision around it.
{
"action": "download-report",
"label": "Download report",
"family": "Heroicons",
"version": "2.2.0",
"variant": "24/outline",
"file": "arrow-down-tray.svg",
"source": "https://github.com/tailwindlabs/heroicons/blob/v2.2.0/optimized/24/outline/arrow-down-tray.svg",
"license": "MIT",
"reviewStatus": "needs-in-context-review"
}
This is an example record, with an explicit pending status. After reviewing the actual interface, update it with the chosen display size and any context-specific notes.
Your final checklist can be short.
- [ ] Each required action has a candidate or a documented exception.
- [ ] The outcome and label are recorded for each action.
- [ ] The busiest screen has been reviewed at its real display sizes.
- [ ] Sort direction, destructive scope and other state requirements are recorded.
- [ ] Source filenames, versions and license notices accompany the assets.
You can start your candidate search on SVGicons, then use this twelve-action sheet to keep track of the decisions. Change the actions to match your product before evaluating a family.
Explore SVGicons for SaaS dashboards
For more on assigning meaning to dashboard symbols, our earlier article covers that part of the process.


Top comments (0)