What This Is

The NBA Board is where ambition becomes logistics. It limits the week to three outcomes and gives each a name, an owner, and a camera date (the Friday demo). The point isn’t neat columns; it’s honest scope.

How to Use It (5 minutes)

1. Duplicate the template for your team.

2. Drag three cards into This Week (Top‑3) — everything else waits.

3. Assign an owner and a Friday demo definition (what will we show?).

4. Instrument early — add UTMs/tags so the demo shows evidence, not opinion.

5. Move to Done on Friday and write one sentence under Learning: “Next week, we will change because .”

Rule of three: If you have four priorities, you have none. Three creates judgment; judgment creates learning.

Template Anatomy

• Backlog — Good ideas, not this week. Sorted by impact (not alphabet).

• This Week (Top‑3) — The only column that touches the calendar.

• Done — Finished items with a link to the demo and the one‑sentence learning.

• Card fields — Title, Owner, Target metric, Friday demo link, Notes.

Keep labels plain. Fancy names are how weeks disappear.

Example (Plain and Real)

• NBA‑1: Route trials by intent (router rule + tag). Owner: Maya • Target metric: % correctly labeled ≥ 75% • Demo: 60‑sec screen capture.

• NBA‑2: First‑aha checklist inside onboarding. Owner: Theo • Target metric: Time‑to‑aha ↓ 20% • Demo: live walkthrough + metric shot.

• NBA‑3: One‑page offer clarity (one promise).Owner: Kai • Target metric: Click‑through to trial ↑ 15% • Demo: before/after capture.

None of these is dramatic. Together, they move the line.

Common Mistakes (and Fixes)

• Too many cards in play. Fix: Lock Top‑3; everything else is backlog.

• Vague ownership. Fix: Put a real name on each card.

• No demo definition. Fix: Write what you’ll show — a link, a clip, a number.

• No instrumentation. Fix: Add UTMs, tags, and intent labels before polish.

Download the Template

Available in Notion and Google Sheets inside the Toolkit. Includes a filled‑in example and a Friday demo checklist.

Prioritization: RICE‑Lite (Weekly)

Score candidates in minutes and let the math pick your Top‑3.

• Reach (0–3): How many users/leads does this touch this week?

• Impact (0–3): Expected lift on the North Star if it works.

• Confidence (0–2): Evidence backing the bet (past tests, user data).

• Effort (1–3): Days to ship the smallest version.

Score = (R + I + C) ÷ E. Sort by score, break ties by effort (smaller first).

Example: - Router tweak (R2 I3 C2 E1) → 7.0 - Onboarding nudge (R2 I2 C2 E1) → 6.0 - New landing page (R2 I2 C1 E3) → 1.7 → backlog.

Friday Demo Definitions Library

Make the camera test explicit so “done” is unambiguous.

• Page/Offer: live URL + before/after screenshot; metric: CTR or click‑to‑trial.

• Email/Nurture: screenshot + ESP link; metric: opens → clicks → setup starts.

• Router Rule: screen capture of route + log excerpt (intent, score, path).

• Onboarding Step: 60‑sec walkthrough to first‑aha; metric: time‑to‑aha.

• Ad/Test: creative A/B thumbnails + spend summary; metric: primary KPI + guardrails.

• Support Macro: GIF of macro in use; metric: ticket time‑to‑first‑reply.

“Done Means Done” — Acceptance Checklist

• Owner and Friday demo link present on the card.

• Tracking in place (UTMs, tags, intent labels) and verified once.

• Target metric and guardrails are defined before launch.

• Evidence captured (URL/clip/metric) and attached to the card.

• One‑sentence learning is written.

GHL Quick‑Start (RousseauAI Stack)

Use GoHighLevel to run the board if your team already lives there.

1. Pipeline: NBA Weekly with stages Backlog → Top‑3 → Done (optional: Hold/Blocked).

2. Custom fields (per card/opportunity): Owner, Target Metric, Friday Demo URL, RICE‑Lite (R, I, C, E), Intent Label.

3. Automations:

• Monday 09:00 — send Top‑3 reminder + auto‑create empty Friday demo tasks.

• Wednesday 16:00 — verification ping if tracking fields are empty.

• Friday 16:30 — require Demo URL; tag Carryover if missing.

4. Dashboard widgets: Throughput (# Done/week), Carryover rate (% Top‑3 not finished), Median time‑to‑demo, Kill rate (cards removed from backlog).

Keep it light: the board is a sprint lens, not a project archive.

Notion/Sheets Schema (Copy‑Paste)

Columns: Status • Title • Owner • Due (Fri) • Target Metric • Demo URL • R • I • C • E • Score (formula: (prop("R")+prop("I")+prop("C"))/prop("E")) • Notes • Learning.

Create three views: Backlog (Status=Backlog, sort by Score desc), Top‑3 (Status=Top‑3, limit 3), Done (this week) (Status=Done, filter date is this week).

Metrics That Keep You Honest

• Throughput: # cards moved to Done (target: 3/week).

• Carryover Rate: % of Top‑3 not finished by Friday (target: < 20%).

• Kill Rate: % backlog items removed (target: ≥ 10%/month — pruning = focus).

• Time‑to‑Demo: median days from Monday to evidence (target: ≤ 4 days).

Use‑Case Playcards (Pick One and Start)

SaaS/Product‑Led: Router rule → first‑aha checklist → offer copy.

Agency/Services: Discovery form revamp → proposal one‑pager → scheduling flow.

Course/Membership: Lead magnet → onboarding email 1 → community prompt.

Weekly Ceremony Script

• Mon (15 min): Pick Top‑3 using RICE‑Lite; set demo definitions.

• Wed (5 min async): Tracking check; unblock anything blocked.

• Fri (20 min): Demos → decision → learning sentence → archive.

Troubleshooting

• Nothing finishes: Scope smaller; enforce demo definition on Monday.

• No signal: Add tracking first; ship a “dumb but measurable” version.

• Top‑3 keeps growing: Lock the column; excess goes to backlog without debate.