Three questions to gut-check any feature or idea for virality on the spot — in a meeting, a ticket, a Slack thread — before you over-invest in analysis.
A feature comes up in a meeting. Someone says "could this be viral?" and the room either shrugs or schedules a workshop. Both kill the idea. The shrug skips the question; the workshop buries it under analysis no one has time for.
The Quick Test fixes that. It is the 60-second operational version of The Loop Question — fast enough to run on the spot, sharp enough to tell you whether a feature deserves a real look. Its job is not to be right. Its job is to keep loop-thinking alive across every feature, so the question gets asked before the code gets written.
Ask them out loud, in order, about the feature in front of you. If you cannot answer one in a sentence, that is already a result. (New to the terms? Start with what a viral loop is.)
The test is only useful if you can tell a strong answer from a hopeful one. Here is the difference, question by question.
Strong: a specific person at a specific moment — "the client who opens the shared report, the second they click the link." Weak: "anyone could see it eventually." If you cannot name the person and the moment, there is no loop yet.
Strong: they see value before they see your logo — "a clean report that answers their question." Weak: "they see we made it." A loop pulls people in with value, not with branding.
Strong: you can count the steps on one hand and most of them deliver value before the sign-up wall. Weak: "they'd create an account, verify email, then maybe explore." Every extra step before the first taste of value leaks people out of the loop.
Say your analytics tool gets a "Share report" feature — a user sends a link to a teammate or client. Run the test:
Q1 — Who & when: the recipient (a client or colleague who is not a user), the instant they open the link. Clean answer.
Q2 — First second: they see the actual report — the numbers they wanted — rendered cleanly, branded subtly at the edge. They stay because the report is genuinely useful to them. Clean answer.
Q3 — Steps to active: view report → "make your own" → sign up. Three steps, and value lands at step one. Tight enough.
All three pass. This feature carries a loop and earns a deeper pass. Now compare a "Share report" that emails a PDF attachment with no link back: Q1 still works, but Q3 collapses — there is no path from "saw the PDF" to "active user." Same feature name, different architecture. The test catches the difference in under a minute.
A clean answer to all three means the feature deserves real design attention. Take it through the Feature Review — 17 questions across brief, design, build, and evaluation — before anyone writes code.
A weak answer is not a dead end. Either redesign the feature so a loop becomes natural — usually by fixing Q3 — or ship it as a non-viral feature on purpose and stop expecting it to spread. Both are wins; pretending is the only loss.
When you are ready to put a number on the loop you designed, take it to the K-Factor Calculator and project growth cycle by cycle.