Fast Research vs Deep Research

Monday morning the board had nine idea cards and zero kills. By Friday the same founder had one deep memo, three archived niches, and a validation call booked for Tuesday. Nothing magical happened. The founder stopped treating every shower thought like a bet-the-company wedge and stopped hiding in week six of "still researching" on a consumer app with weak payment signal. Depth became a calendar choice, not a mood. Fast cleared noise. Deep earned commitment. That week is repeatable.

Founders oscillate between two failure modes. Some never go deep enough and ship slop on vibes. Some never stop reading and ship nothing on fear. Depth is a choice, not a personality trait. Wise founders alternate on purpose. ARIA helps you match effort to stakes so you kill bad ideas cheaply and commit to good ones honestly.

Phase: Monday triage (fast scan)

Fast research is orientation. You learn whether language exists, whether competitors exist, whether anything looks paid, and whether the idea deserves another hour or a goodbye. Fast is not lazy. Deep is not virtue. Wrong depth is the sin. Fast on a bet-the-company wedge is reckless. Deep on every shower thought is avoidance.

The first move is triage. Run fast scans on many ideas when you are exploring. Look for immediate red flags: no buyer language, no payment patterns, crowded incumbents with love, or vague pain that never repeats. Fast research earns kills by lunchtime.

In ARIA, fast research fits early board population. Generate or sync ideas. Scan scores and snippets. Expand cards that surprise you. Kill cards that fail the "would I email a buyer tomorrow" test.

A solo founder might run fast research on five consumer app ideas in one afternoon. Four show weak payment and generic wellness language. One shows repeated forum posts about a specific workflow pain with existing tool spend. Go deep only on the survivor. That is discipline.

Fast research questions are blunt. Does anyone say this pain in their words? Does anyone pay for something adjacent? Is there a wedge I can name in one sentence? No on all three means kill, not deep dive.

Choose fast when: you are exploring broadly, stakes are low, payment signal is obviously weak or obviously strong, or you need a kill list before vacation.

Depth serves decisions, not anxiety. Fast clears the deadwood.

Phase: Tuesday through Thursday (deep pass)

Deep research is commitment prep. You follow threads, collect quotes, map alternatives, note switching costs, and write a kill-or-pursue memo you would show a skeptical partner.

Go deep when an idea survives fast triage and stakes rise: you will spend validation time, ask clients to trust you, or pitch a co-founder. Deep pass activities include reading dozens of reviews, tracing forum threads over months, cataloging alternatives buyers tried, noting regulatory or trust barriers, and writing "I might be wrong if ___" sentences.

An agency owner validating a client niche might run fast research across three scopes, pick one with budget signals, then run deep research with a client-specific focus area. Deliver a board with evidence, not vibes. Client trust follows.

Deep research should end with pressure to decide, not relief at more tabs. If deep research only confirms your priors, you did it wrong. Hunt disconfirming evidence too.

Choose deep when: validation starts next week, a client is paying for diligence, the market is opaque, switching costs look high, or incumbents win but complaints repeat.

Deep prepares honest validation. Often one to three focused days per idea, not six weeks. Calendar boxes beat vague "still researching."

Stop when five kill-or-pursue answers are written without hand-waving, when quotes repeat without forcing, and when you can name wedge and alternatives. Stop also when kill criteria trigger. More reading after a triggered kill is denial.

Phase: Friday rhythm (alternate depth like a calendar)

Founders who always pick fast because it feels productive often build on fog. Founders who always pick deep because they fear launch often build nothing. Wisdom alternates.

Suggested rhythm for solo founders: fast scan weekly on new ideas, deep pass on at most one idea per month, validation only on deep survivors. Agencies may deep more often because clients fund research as deliverables.

Cap active ideas. Three deep ideas at once is chaos. One deep track plus two fast monitors is sane.

When research finishes at any depth, write five answers: who hurts, what they say verbatim, what they pay today, who wins now, what would kill the idea. Missing answers mean wrong depth or wrong idea.

Rhythm beats heroics. Monday research blocks until five answers for active idea. Wednesday validation calls scheduled. Friday kill ritual regardless of depth. Validation begins after honest depth, not after infinite depth.

Stories show depth choices in outcomes:

Solo founder with ten ideas. Fast scan on all ten. Kill seven. Deep on one B2B scheduling niche with payment and complaints. Validate that one. Outcome: focus.

Founder stuck six weeks in deep research on a consumer app. Payment signals still weak. Deep research became hiding. Kill the idea. Outcome: time recovered.

Agency with three client niches. Fast per niche, deep only on niche with Shopify spend and sync pain. Client sees why two niches were deprioritized. Outcome: trust.

Common depth mistakes:

Deep research without kill criteria. You collect forever because nothing can falsify the idea. Fix: write kill rules before you start.

Fast research on a client bet without telling the client. Fix: label deliverables honestly: scan versus deep pass.

Confusing more tabs with depth. Depth is pattern and decision, not volume. Fifty random pages lose to twenty targeted reviews.

Skipping fast because you love the idea. Fix: force fast first even on passion projects.

Never revisiting depth after new data. Markets move. A fast idea can deserve deep later. A deep kill can reopen if payment shifts.

Phase: retrospective (depth, lane, and emotion)

Research in ARIA lets you pick fast scan or deeper pass deliberately. That choice is part of evidence. Boards compare ideas at the same depth when possible. Comparing a deep idea to a fast idea unfairly flatters the deep one.

Use focus areas to narrow deep passes. Vague deep research across a whole industry is still fog. Focus turns depth into wedge.

B2B deep research often means job posts, review sites, and procurement hints. Consumer deep research often means app reviews, communities, and habit signals. Same principle, different surfaces. Pick depth surfaces that match your lane for ninety days.

Consumer apps without habit or payment signal rarely deserve deep time. B2B ideas with hidden service spend sometimes need deep to find budgets.

Good deep research often feels disappointing. It narrows segments and kills fantasy. Disappointment means contact with reality. If deep research only inflates your ego, check whether you hunted disconfirming evidence.

Fast kills can feel liberating. Celebrate them. You bought back weekends.

Choose neither fast nor deep when you are replacing fear of selling with reading. That is procrastination wearing a research hat.

Retrospective questions for your sprint:

Did fast scan kill at least one idea this week?

Did deep pass end with five written answers and ten quotes?

Did I label client deliverables with depth honestly?

Did I compare ideas at the same depth on the board?

Did validation start only on a deep survivor?

Depth guarantees integrity in your next decision, not success. That is enough.

Fast versus deep: decision matrix expanded

Use the matrix when mood says deep but criteria say fast. Mood lies. Criteria keep calendars.

Depth FAQ

Can I go deep on two ideas at once? Solo founders should not. Split depth splits learning.

Is fast research enough for agencies? For triage yes. For client deliverables, label scans clearly and deep where clients pay for diligence.

How long should deep take? Often one to three focused days per idea, not six weeks. Calendar boxes beat vague still researching.

Does depth guarantee success? No. Depth guarantees integrity in your next decision.

When should I revisit fast ideas? When market shifts, new competitor launches, or payment signal changes in your lane.

One week depth sprint you can copy

Monday: Fast scan all active ideas. Kill obvious losers. Mark one deep candidate.

Tuesday: Write kill criteria. Collect quotes for deep candidate only.

Wednesday: Reviews and forums for deep candidate. Bucket complaints.

Thursday: Payment anchors and competitor map. Write five answers.

Friday: Kill or mark validation-ready. No IDE.

Repeat monthly. Depth becomes rhythm, not hero project that never ends.

Agencies run same sprint per client engagement with deliverable memo on Friday. Clients see rhythm. Trust compounds.

When fast scan lies

Fast scan can show false green when category looks paid but wedge is head-on with loved incumbent. Fast scan can show false red when payment hides in services. Deep pass resolves false signals. Calendar one deep day before abandoning surprising fast green or fast red.

Document fast scan conclusion in card: "Fast kill because ___" or "Fast pursue to deep because ___." Future you needs reasoning, not only score.

Compare ideas at same depth on board. Fair comparison prevents deep survivor from beating fast losers on unfair grounds.

Depth without kills is still Path A in sprint clothing. Friday kill ritual applies regardless of depth label.

Solo founders often ask whether to deep a passion project without fast scan. Force fast first. Passion skips triage. Triage protects passion from becoming slop. If fast confirms signal, deep honors passion with integrity. If fast kills, passion saved you a quarter.

Client-funded deep passes should never start without labeled fast scan on same invoice chain. Clients who pay for deep deserve honest depth label. Agencies who deep for free train clients to skip gates forever.

Depth calendar entry should name idea and focus area. Vague calendar block "research" becomes Path A hiding room. Named block ends with kill or validation-ready checkbox.

Track depth hours per idea in memo footer. Founders who log hours learn they deep average two days when honest, not six weeks when afraid. Logging breaks denial without shaming.

Agency invoice line item should match depth delivered: scan versus deep pass. Mismatch between invoice and memo depth is slop billing. Clients forgive kills. Clients do not forgive fake diligence.

Depth choice logged in idea card helps compare ideas fairly next month. Card without depth label gets relabeled or killed in weekly review. Unlabeled cards are Path A hiding spots.

Fast scan Friday plus deep candidate Monday is default solo rhythm. Rhythm beats debating depth philosophically every week.

Label depth on card when research starts. Future comparison across ideas requires honest depth tags. Honest tags require admitting fast kills and deep hides.

Contributions

• Run fast scan weekly on new ideas; kill obvious losers before they consume calendar.
• Deep dive at most one idea per month as a solo founder; one deep track plus two fast monitors is sane.
• Write kill criteria before any deep pass so collection cannot become infinite browsing.
• Label agency deliverables scan versus deep pass on invoice and in memo so clients know what they bought.
• Finish deep with five answers and ten verbatim quotes, then move survivors to validation without opening an IDE.

Fast research versus deep research is not a contest. It is a pacing strategy. Fast clears noise. Deep earns commitment. ARIA lets you choose deliberately so you neither ship slop nor hide in tabs. Founders who match depth to stakes run businesses. Founders who mismatch depth collect bookmarks.