Weekly Accountability Framework

Human-Cell Level
Project Management

Transform vague task tracking into measurable, accountable weekly delivery. Monday Commitment → Friday Delivery → % Score

The Problem We're Solving

Vague Descriptions

"I'm coding", "Working on fix" — No visibility into actual progress or blockers

No Accountability

No Monday vs Friday comparison — Cannot measure team delivery

Unclear Scope

Missing acceptance criteria — No objective "done" definition

Infinite Tasks

Tasks drag across sprints indefinitely without clear ownership

No % Tracking

Cannot quantify weekly delivery rate or team performance

The Goal

Committed → Delivered → Score (0-100) — Every week, every person

Task Anatomy

Every task MUST contain these fields — no exceptions

TASK CARD ANATOMY

[Action Verb] + [Component] + [Outcome]

Example: "Implement file upload validation for PDF files with 50MB limit and error messaging"

Required Fields

* Title [Action Verb] + [Component] + [Outcome]
* Assignee Single owner (no 'Team')
* Story Points 1, 2, 3, 5, 8 (Fibonacci)
* Acceptance Criteria Checkbox list (min 3 items)
* Epic Dropdown selection

Tracking Fields

* Sprint Number Week XX
* Due Date Friday of sprint week
Blocker Status None / Internal / External / Dependency
* Progress % 0, 25, 50, 75, 100
* Deliverable Link PR / Demo URL / Screenshot

Acceptance Criteria Example

User can upload PDF files up to 50MB
Error message shows for files > 50MB
Upload progress indicator displays correctly
Unit tests written and passing

Banned vs Required Phrases

❌ BANNED ✅ REPLACE WITH
"Working on..." "Implement [specific feature]"
"Fix bug" "Fix [component]: [symptom] → [expected]"
"Research" "Document [topic] with recommendation"
"Improve" "Optimize [metric] from [X] to [Y]"
"Update" "Add [field] to [component]"
"Look into" "Investigate [issue] + document root cause"
"Continue" Create NEW task with remaining scope
"Ongoing" Break into measurable weekly chunks

Story Points Guide

Consistent estimation enables accurate forecasting

1
< 2 hours
Trivial
Fix typo, update copy, add log
2
Half day
Simple
New API endpoint (simple), basic UI component
3
Full day
Medium
Feature with logic, integration required
5
2 days
Complex
Multi-component, external integration
8
3-4 days
Very Complex
Architecture change (BREAK DOWN!)
⚠️ Tasks with 8+ points MUST be broken down into smaller tasks

Delivery Scoring

Weekly accountability with clear performance thresholds

🎯
90-100%
Exceptional
On track for promotions/bonuses
80-89%
Good
Meeting expectations
⚠️
70-79%
Needs Improvement
Coaching required
<70%
Critical
Performance review triggered

Sample Week 07 Scorecard

DELIVERY SCORECARD — Friday 14 Feb 2026
Team Member Committed Delivered Partial Not Done SCORE
James 13 pts 11 pts 2 pts 0 pts 85% ✅
Nick 11 pts 8 pts 0 pts 3 pts 73% ⚠️
Khoa 8 pts 8 pts 0 pts 0 pts 100% 🎯
Tung 13 pts 10 pts 3 pts 0 pts 77% ⚠️
TEAM TOTAL 45 pts 37 pts 5 pts 3 pts 82% ✅

4-Week Trend

71%
Week 04
78%
Week 05
85%
Week 06
82%
Week 07

Sprint Ceremonies

Structured weekly rhythm for accountability

📅
Monday
Sprint Planning
1 hour commitment ceremony
  • Review last week's delivery score
  • Discuss carry-over items + why
  • Each person states tasks + points
  • Capacity check (no over-commit)
Output
Monday Commitment Sheet
🔄
Daily
Blocker-First Standup
15 minutes max, strict format
  • 1. Blockers — What's stopping you NOW?
  • 2. Progress % — Update all tasks
  • 3. At-risk — What might not land?
Rule
No storytelling. Facts only.
🎯
Friday
Sprint Review + Scoring
45 minutes scoring ceremony
  • Demo completed work (25 min)
  • Calculate individual + team scores
  • Retrospective — what blocked us?
Rule
No demo = Not complete

Before & After

Real transformation examples

❌ BEFORE
Title:
"Work on token tracking"
Description:
(empty)
✅ AFTER
Title:
"Implement LiteLLM token usage tracking per workspace"
Story Points: 5
Acceptance Criteria:
  • ☐ Token count captured for each API call
  • ☐ Usage stored with workspace_id + timestamp
  • ☐ GET /billing/usage returns accurate totals
  • ☐ Unit tests for usage calculation
❌ BEFORE
Title:
"Fix dashboard"
Description:
"not working"
✅ AFTER
Title:
"Fix Smart Link dashboard: Chart renders blank when CSV has >10k rows"
Story Points: 3
Acceptance Criteria:
  • ☐ Dashboard loads for CSV with 50k rows in under 3s
  • ☐ Sampling indicator shows when data truncated
  • ☐ No console errors during render