The Weekly Shipping Score: Grade Your Week Without Productivity Theatre

If you want to score your week objectively, you need proof of shipped outputs, lead indicators tied to your current constraint, and a penalty for low-leverage motion. That is the Weekly Shipping Score (0–100).

It's like an accountability coach for your week. Pick one thing. Track wins. Get a weekly verdict.

Busy isn't progress. Shipped is progress.

Why most weekly reviews fail

Most weekly reviews turn into notes like "busy week" or "lots of meetings" or "made progress." That is productivity theatre. It feels responsible, but it does not tell you if the business moved.

A week is a unit of execution. Drift kills weeks. If you cannot point to what changed in the real world, you did not ship.

FocusNinja is built around this: log wins as evidence, then get a weekly verdict that does not accept vague explanations.

The core loop: Morning Anchor. Midweek Pulse. Weekly Review.

Step 1: Define "shipped" so scoring stays objective

"Shipped" needs a definition that survives your Friday-night rationalizations. In FocusNinja, a "win" is strongest when it includes proof. Proof makes the review objective.

Output vs activity

Outputs are externally observable changes:

• A feature deployed to production
• A landing page published at a live URL
• A proposal sent
• A customer call booked
• An invoice sent
• An experiment launched with a defined success metric

Activities are inputs:

• Research
• Planning
• Meetings
• Refactoring "for cleanliness"
• Reading docs
• Rearranging the backlog

Activities can be necessary. They just are not the score.

What counts as "shipped" if nothing is public yet?

Use private but verifiable proof:

• Screenshot of a flow working end-to-end
• Commit hash or PR merged
• Staging link shared with a tester
• Loom video demo sent to a user
• "Payment test passed" screenshot

In FocusNinja, this becomes a win log with proof. Log wins. The coach uses wins as evidence.

Step 2: The Weekly Shipping Score (0–100)

This model is designed for founders who drift. It is simple enough to do every week, strict enough to stop self-deception, and flexible enough to fit product, sales, or content weeks.

The 3 buckets

Weekly Shipping Score = Outputs (0–60) + Lead Indicators (0–30) + Low-Leverage Guardrail (0–10)

• Outputs shipped (0–60 points). Up to 3 outputs only.
• Lead indicators (0–30 points). 2–4 reps tied to your current constraint.
• Avoidance of low-leverage work (0–10 points). A guardrail that detects drift.

This is how FocusNinja thinks: one intention for the week, wins as evidence, and a verdict you cannot talk your way around.

Scoring table

Bucket	Max	How to score it	What "proof" looks like
Output 1 (highest leverage)	25	0 = not shipped. 15 = shipped, low leverage. 25 = shipped, high leverage.	Live URL, deploy, sent email, invoice, booked calls list
Output 2	20	0 / 10 / 20 using same rule	Same
Output 3	15	0 / 8 / 15 using same rule	Same
Lead indicators	30	Pick 2–4. Score by hit rate: (completed / planned) × 30	CRM count, calendar count, timer sessions
Low-leverage guardrail	10	Start at 10. Subtract points for avoidable motion.	Calendar, time log, obvious "tooling spiral"

Why only 3 outputs? Because scatter is drift. Limiting outputs forces a real tradeoff.

How to weight "leverage"

Use one question: "Would I pay real money to have this done by Monday?"

If yes, it is leverage. If no, it is probably activity dressed up as progress.

In FocusNinja, the weekly intention and North Star give you context to label outputs as high leverage. You are not scoring random work. You are scoring what you said mattered.

Lead indicator examples

Pick the constraint that blocks shipping right now. Then choose 2–4 lead indicators.

If sales is the constraint:

• Outbound touches sent (40)
• Demos completed (4)
• Proposals sent (3)

If product is the constraint:

• Deep work blocks completed (8 blocks of 50 minutes)
• User interviews completed (3)
• Experiments launched (1)

If marketing is the constraint:

• Published posts (1)
• Newsletter sent (1)
• Partnerships contacted (10)

FocusNinja's focus timer ties to intention. That matters because "8 deep work blocks" only counts when those blocks aimed at the One Thing.

Low-leverage guardrail

This bucket detects drift, not shame.

Start at 10 points. Subtract:

• -2 if you had 2+ avoidable meetings
• -2 if you spent 2+ hours on tool tinkering
• -2 if you did a refactor without a reason tied to shipping
• -2 if inbox went reactive for half a day
• -2 if you changed priorities midweek without logging why

FocusNinja's Midweek Pulse catches this. Start aligned in the morning. Correct drift midweek. Review on Sunday.

Step 3: Anti-gaming guardrails

When a measure becomes a target, it stops being a good measure. Use these guardrails so your score stays honest.

Outputs need binary proof

Outputs must be "done" in a way that could survive a screenshot.

Good: "Deployed onboarding fix to prod. Link to PR." Bad: "Worked on onboarding."

FocusNinja pushes you toward proof-based wins because wins logged sharpen coaching.

Cap outputs at 3

You do not get extra credit for starting 12 things. Your score rewards finishing.

Add one quality question per output

After each output, answer:

• "Did this move a KPI?"
• "Would a customer notice?"
• "Did this create a learning that changes next week?"

Label "Enjoyed" weeks on purpose

Some weeks are for recovery or exploration. Those are not wasted if declared.

In FocusNinja, that is an Enjoyed week. The key is honesty: declare intent upfront in your weekly intention.

Step 4: Turn the score into a verdict

A score is only useful if it produces a decision. In FocusNinja, the weekly review ends with a verdict: Shipped / Wasted / Enjoyed.

Thresholds

• 75–100: Shipped - You shipped meaningful outputs and kept leading indicators healthy.
• 45–74: At risk - Some progress, but the week did not match intention.
• 0–44: Wasted - High motion, low proof of shipping.
• Enjoyed (override): Only if the week was intentionally restorative and declared upfront.

What each verdict means for next week

• Shipped: Keep the same constraint focus. Raise leverage, not volume.
• At risk: Shrink scope. Reduce WIP. Increase one lead indicator.
• Wasted: Cut low-leverage sources first. Then pick a smaller One Thing.
• Enjoyed: Re-enter with a tight week. One output plus one lead indicator.

FocusNinja turns this into a weekly reflection that ends in decisions, not feelings.

Step 5: Trend it over time

One weekly score is a data point. The value is the trendline. Founders do not lose quarters in one day. They lose them through quiet drift.

FocusNinja tracks momentum so you can see patterns across weeks, not just read old notes.

How to read the trendline

Lead indicators high, outputs low

• You are working, but not closing loops.
• Fix: Cut the output in half. Define "done" tighter.

Outputs high, lead indicators low

• You shipped, but pipeline is drying up.
• Fix: Lock 2 lead indicators as non-negotiable reps.

Low-leverage guardrail trending down

• Drift is rising.
• Fix: Add boundaries. Fewer meetings. Office hours for support.

A simple rule

If your score drops 2 weeks in a row, change the plan, not the effort.

This is why FocusNinja runs the loop weekly.

How FocusNinja makes scoring consistent

Most apps store reflections. FocusNinja turns them into a weekly shipping signal you cannot talk your way around.

Consistency is the hard part. Not math.

FocusNinja does it by:

• Forcing a weekly One Thing outcome
• Encouraging wins logged with proof
• Using Morning Anchor to start aligned
• Using Midweek Pulse to catch drift
• Using Weekly Review to produce a verdict and next steps

You get a verdict, not a mood

At the end of the week:

• Shipped
• Wasted
• Enjoyed

The verdict is grounded in the evidence you logged. More wins logged means sharper coaching.

Trends show drift early

The point of a score is not judgment. It is early warning.

FocusNinja tracks wins over time, consistency of check-ins, and momentum patterns so you can see when "busy" starts replacing "shipped."

Simple example week

Here is what an objective week looks like using the rubric.

Early-stage SaaS founder (product + sales)

Outputs (max 60)

• Output 1 (25): Deployed onboarding step reduction. PR link. = 25
• Output 2 (20): Published pricing page update. Live URL. = 20
• Output 3 (15): Sent 3 proposals to qualified leads. = 15

Outputs subtotal = 60

Lead indicators (max 30)

• Planned: 40 outbound touches, 4 demos.
• Completed: 30 touches, 3 demos.
• Hit rate = 0.75
• Lead score = 0.75 × 30 = 22.5

Low-leverage guardrail (max 10)

• Avoidable meetings: 1. Tool tinkering: 0.
• Deduction: 0

Guardrail subtotal = 10

Weekly Shipping Score = 60 + 22.5 + 10 = 92.5 Verdict: Shipped

In FocusNinja, this week would generate next-week actions: keep the constraint focus and set next week's One Thing.

FAQ

What counts as "shipped" if I'm still building and nothing is live?

Shipped means "done with proof," even if private. Use commit hashes, merged PRs, Loom demos sent to testers, or staging links shared. In FocusNinja, log the win with proof so the weekly verdict stays honest.

How do I score sales progress when revenue has not landed yet?

Score sales outputs (demos completed, proposals sent, contracts out) and sales lead indicators (outbound touches, follow-ups, qualified conversations). FocusNinja ties these to your weekly intention so you do not confuse networking with pipeline.

How do I avoid gaming the score by shipping tiny tasks?

Cap outputs at 3 and weight by leverage. Add one quality question per output: "Would a customer notice?" or "Did it move a KPI?" FocusNinja reduces gaming by requiring proof-based wins and reviewing against your One Thing.

What if I did important thinking or research all week?

Label the week intentionally. Either score research as a lead indicator (interviews completed, decision memo shipped) or declare an Enjoyed week upfront. FocusNinja supports Enjoyed as a valid verdict when it is honest and planned.

How many outputs should I aim to ship each week?

Aim for 1–3 meaningful outputs. More than 3 often signals scatter. FocusNinja is designed around one weekly outcome plus supporting wins, so you ship fewer things with higher leverage.

Should I score by hours worked, tasks completed, or milestones?

Score by outputs shipped first. Hours and tasks are easy to inflate and reward busyness. Use hours only as a lead indicator when tied to the One Thing, like FocusNinja's intention-based focus sessions.

How do I handle weeks with emergencies, travel, or personal obligations?

Lower the planned lead indicators and shrink the One Thing. Then score honestly. If the week was intentionally lighter, mark it as Enjoyed. FocusNinja's Morning Anchor and Midweek Pulse help you reset expectations before the week is gone.

Can this score work for long-cycle work like enterprise sales or deep tech?

Yes. Use fewer outputs and stronger lead indicators. For enterprise sales, outputs can be "stakeholder meeting completed" or "security review submitted." For deep tech, outputs can be "benchmark results report shipped" or "prototype demo recorded." FocusNinja keeps the score anchored to proof and trends it across weeks.

What's the minimum data I need each week to make the score reliable?

You need: (1) one weekly intention, (2) 1–3 proof-based wins, (3) 2–4 lead indicators with planned vs completed, and (4) a quick note on low-leverage drift sources. FocusNinja collects exactly this through Anchor, Pulse, and Weekly Review.

How do I use the score to plan next week?

Use the verdict. If Shipped, raise leverage. If At risk, shrink scope and increase one lead indicator. If Wasted, cut low-leverage sources first, then pick a smaller One Thing. FocusNinja turns the review into next week's intention automatically.