Run them in order on one problem at a time. Steps one and two choose the source; three and four price it; five decides whether you keep it.
State the structure with the domain words removed.
Write your problem in one sentence containing no noun from its own field. "Our hiring pipeline stalls at the final round" becomes a queue whose service rate falls as the queue lengthens. The stripped sentence is the only thing you can shop with, because it names what a mechanism can match: states, rates, thresholds, feedback, irreversibility. If you cannot write it, you do not yet know your problem's structure — and every metaphor on the shelf will seem to fit, which is the symptom.
Shop the shelf by structure, never by vibe.
Match the stripped sentence against a page's mechanism rather than its mood. A rotting codebase feels like decay, which recommends entropy; it is structurally irreversible accumulation without recombination, which recommends Muller's ratchet — a page filed under evolution that mentions no software and predicts more about it. Scan at least three of the catalogue's clusters. A source drawn from the cluster your problem already lives in will refine what you think, and refinement is what you came here to get past.
Build the mapping table element by element.
Every load-bearing part of the source gets a row and a specific referent in your case — not "the population is the team" but "the least-loaded mutational class is the two files nobody has had to patch this year." Parts with no referent stay in the table, marked empty; they are where the loan is void, and step four needs them. A source whose parameters you cannot state in your own units — what is your barrier height, in what does your noise arrive, what is your utilization — has been invoked rather than mapped, and the table is how you tell the difference.
Hunt the disanalogy before you lean on it. The tear-line gallery below shows what the hunt finds.
Every explainer on the shelf closes with a section headed Where the metaphor tears, written by whoever built the instrument. Read it before you touch the sliders. It lists the assumptions the mechanism cannot survive without, and your case either satisfies them or it does not: Kramers escape assumes a fixed landscape, so the moment you rearrange your kitchen to make the habit easier you have left the model. A borrowing whose tear you cannot state in one sentence has not been audited, and an unaudited metaphor keeps generating fluent sentences well past the point where it means anything.
Cash out one prediction or one reframing — or return it.
The loan pays in exactly two currencies. A prediction: "drop one project, get utilization under 0.85, and the wait on the rest should fall by more than the project cost" — checkable, with a date. Or a reframing: "this is a coevolutionary race, so the exit is changing what the audience scores, not arguing better" — a different action from the one you were about to take. Name which you got, in a sentence you could not have written before opening the page. If neither arrives, put the metaphor back on the shelf; the pleasure it gave you was genuine, and it was the entire product.