No Product Yet? Here's the Weekly Review That Still Produces Progress

If you're doing customer discovery and have no product to ship yet, your weekly review should track evidence shipped, not features shipped.

That means scoring your week on completed customer touchpoints, insights logged, and hypotheses changed or killed.

A week is a unit of execution. Drift kills weeks. Pre-product drift happens because there's no external scoreboard.

FocusNinja gives you one. It's like an accountability coach for your week.

The problem: pre-product founders can't "ship," so they drift

Most weekly review apps assume your output is code shipped or tasks closed. In discovery, those metrics turn into productivity theater.

Here's what drift looks like in discovery:

• You do "research" but don't talk to customers
• You talk to customers but don't write anything down
• You write notes but don't change your plan
• You change your plan weekly based on vibes and the last call

FocusNinja is built for founders who feel: "I worked all week. Why didn't the needle move?"

In discovery, the needle isn't features. The needle is customer truth you can act on next week.

Redefine shipping: ship evidence, not features

Evidence shipped (definition): Customer truth captured in writing that changes what you will do next.

What counts as evidence you can ship this week

• Interviews completed with the right persona (not just booked)
• Decision-maker conversations (budget and authority signals)
• Insights logged (usable notes, not vague summaries)
• Hypotheses invalidated (you saved months)
• Segment narrowed (you said "no" to a segment, on purpose)
• Willingness-to-pay signals (pricing reactions, budget ranges)
• Clear next test defined (one riskiest assumption for next week)

In FocusNinja terms: pick one thing. Track wins. Get a weekly verdict. When you're pre-product, the "wins" are evidence.

What FocusNinja does differently for discovery founders

FocusNinja behaves like an accountability coach, not a note dump. It forces a weekly truth loop grounded in evidence.

1) Evidence-first inputs (not task lists)

Your review starts with:

• Touchpoints: booked, completed, logged
• Insights captured: count and quality
• Hypotheses: validated, invalidated, unknown

Log wins. The coach uses wins as evidence.

2) Pipeline visibility (booked vs completed)

Discovery fails most often from insufficient customer contact and weak documentation. FocusNinja shows:

• This week: completed touchpoints
• Next week: already booked touchpoints
• Outreach health: do you have a pipeline or are you hoping?

3) Decision logging (learning that changes behavior)

A discovery review without decisions becomes journaling.

FocusNinja's weekly reflection forces this single line: Because of X, we will do Y.

4) Kill-switch support (reward killing bad ideas)

Founders get stuck because they fall in love with an idea.

FocusNinja includes:

• Kill criteria (what would falsify this)
• A place to mark a hypothesis killed
• A scoring system that rewards killing, not clinging

Busy isn't progress. Shipped is progress. In discovery, "shipped" includes killing the wrong direction.

5) Daily commitments from weekly plans

Weekly reviews fail when they don't produce daily alignment.

FocusNinja generates daily commitments like:

• 2 outreach blocks
• 1 interview
• 1 debrief write-up

Morning Anchor. Midweek Pulse. Weekly Review.

6) Quality controls to reduce founder bias

Discovery is vulnerable to confirmation bias. You overweight the last conversation. You chase the most interesting idea.

FocusNinja checks:

• Are you talking to the right persona?
• Are your notes specific and tied to recent real instances?
• Did you collect consequences, current workaround, and budget signals?

Your week gets a verdict: Shipped, Wasted, or Enjoyed.

The Discovery Shipping Score (simple, not gameable)

You need a score that rewards learning, not activity.

Discovery Shipping Score (0 to 30)

Component	Points	Notes
Completed customer conversations	+2 each (cap 10)	Completed beats booked
Conversation properly logged	+1 each	Use template below
Hypothesis killed or updated	+3 each (cap 2)	Must include reason and next test
Next week interviews booked	+2 if ≥3 booked	Makes momentum real
Wrong persona penalty	−2 if >50% wrong	Talking to wrong people is fake progress
No written insight penalty	−3 if zero insights	If it's not written, it didn't happen

How to interpret the score

• 0 to 8: You were busy. You didn't build an evidence base.
• 9 to 18: You're building contact and notes. Tighten quality.
• 19 to 30: You're shipping learning weekly. Keep cadence.

The goal isn't 30. The goal is a score you can improve weekly.

A discovery-specific weekly review template

Use this as your FocusNinja weekly reflection structure:

1) Current target

• Target segment:
• Role and context:
• Job-to-be-done (current wording):

2) Touchpoints (this week)

• Interviews booked:
• Interviews completed:
• Interviews logged:
• % right persona (estimate):

3) Quality check

A "quality interview" includes:

• Recent real instance (last 30-90 days)
• Consequences (time, money, risk)
• Current workaround
• Budget or authority signals

Quality this week: Yes or No

4) Top 3 pains (with verbatim quotes)

5) Current workaround and cost

• Workaround:
• Cost (time, money, risk):

6) Hypotheses tracker

• Hypothesis A: Validated / Invalidated / Unknown. Evidence:
• Hypothesis B: Validated / Invalidated / Unknown. Evidence:
• Hypothesis C: Validated / Invalidated / Unknown. Evidence:

7) The one decision

Because of ________, we will ________.

8) Next week evidence plan

• Target interviews completed:
• Minimum booked by Monday:
• Outreach blocks (days and times):
• Debrief routine (same-day slot):

9) Discovery Shipping Score

• Score:
• What will raise it by 3 points next week:

How FocusNinja makes this work daily (not just Sunday)

A weekly review doesn't fix drift by itself. Your daily loop wins the points.

Morning Anchor: start aligned to evidence

Your Morning Anchor ties your day to your One Thing.

In discovery, your Morning Anchor should say:

• Who am I trying to talk to?
• What's the one assumption I'm testing?
• What's the evidence action today (outreach, interview, debrief)?

Midweek Pulse: catch drift early

Most founders realize on Friday they avoided outreach. The week is gone.

FocusNinja's Midweek Pulse forces a Wednesday correction:

• Are interviews happening?
• Are debriefs logged?
• Is the assumption still the riskiest one?

Weekly Review: verdict and next week made inevitable

FocusNinja's AI coach gives a verdict based on wins logged. In discovery, that means:

• Evidence shipped
• Hypotheses changed
• Next week scheduled

This is the anti-busywork framework in practice.

When to graduate from discovery to building

You stop pure discovery and start building when evidence makes an MVP test the next logical experiment.

Discovery-to-build triggers

Start building when you have:

• A clear ICP you can name in one sentence
• A pain that shows up repeatedly across conversations
• A stable narrative you can say in plain words
• Willingness-to-pay signals (budget ranges, buying process hints)
• A specific MVP hypothesis you can test in 2-4 weeks

Building isn't a reward. It's the next experiment in build-measure-learn.

FAQ

What am I "shipping" if I'm not building anything? You're shipping evidence. Completed interviews, debriefs logged, and hypotheses changed are real output. FocusNinja treats these as wins and uses them as evidence in your weekly verdict.

How do I know if my discovery week was good or just busy? A good week changes decisions. Use the Discovery Shipping Score. If you have touchpoints completed, notes written, and at least one hypothesis updated or killed, you made progress.

How many interviews should I do per week? Use 5-15 conversations per week as a guideline. The right number depends on access and market. FocusNinja helps by turning the weekly target into daily outreach blocks and a midweek correction.

What counts as a real discovery win: calls booked or calls completed? Completed calls are the win. Booked calls are pipeline health. Score both, but weight completed higher.

How do I avoid talking to the wrong people? Define your current target segment and include a wrong-persona penalty in your score. If more than half your calls are wrong, your week should feel expensive.

What should I log from interviews so it becomes usable later? Log: recent real instance, consequences, current workaround, and budget or authority signals. Add verbatim quotes. FocusNinja's daily wins logging should link to this debrief so your evidence compounds week to week.

How do I turn insights into next week's actions? Write one decision: "Because of X, we will do Y." Then choose one riskiest assumption for next week and schedule touchpoints using FocusNinja's Weekly Intention plus Morning Anchor.

When should I stop discovery and start building? Start building when the next riskiest assumption requires an MVP test and you have repeated pain signals and a clear ICP.

How do I handle weeks where I can't get interviews? Score the pipeline, not your effort. If interviews aren't happening, your One Thing becomes fixing outreach: list building, referrals, and booking. FocusNinja's Midweek Pulse catches this on Wednesday so you can still salvage the week.

How do I score progress without vanity metrics? Only score evidence tied to decisions: completed touchpoints, logged insights, and hypotheses changed. If it doesn't change what you do next week, it's noise.