THE SHAME
ENGINE
Annoying by design. Effective by necessity. When someone hasn’t touched their critical-path task in 48 hours, Scrumb stops being polite.
WHAT IS THE SHAME ENGINE?
Small teams run on social accountability. When a critical-path task hasn't moved in 48 hours, the polite approach has already failed. Scrumb's Shame Engine generates named, task-specific accountability reports to restore momentum before the deadline becomes a casualty.
A REAL SHAME REPORT
RECIPIENT: @Rohan
TASK: [ backend/auth/jwt-middleware ]
STATUS: STALLED — 52 HOURS, 14 MINUTES
CRITICALITY: CRITICAL PATH — blocking 4 downstream tasks
IDE sessions since assignment: 11
Git commits pushed: 0
Files modified in assigned module: 0
DOWNSTREAM IMPACT:
✗ [ frontend/dashboard ] — cannot start
✗ [ backend/api/user-endpoints ] — cannot start
✗ [ integration/tests ] — cannot start
// RECOMMENDATION: Close the system design video.
// Open src/auth/middleware.py. Write the function.
// It is 40 lines. You have done harder things today.
WHEN IT FIRES
THE GHOST
Assigned a task. No updates, no commits, no response. Shame Engine drafts a full impact report delivered to the team channel.
THE SCOPE CREEP
Core task marked "done" prematurely while building an unrequested feature. Integrity Guard blocks it first; Shame Engine logs the distraction.
THE OPTIMIST
Estimated 2 hours. It's been 9. "Almost done." The Shame Engine updates the downstream impact calculation and shares it with the team.
THE BLOCKED DEV
Task stalled because an upstream dependency is unfinished. Shame Engine correctly redirects the report to the root blocker. Innocent party cleared.
IT'S CONFIGURABLE
Opt-in per team. Tunable per sprint.
YOUR TEAM IS STALLING.
You know which task. You know whose it is. Scrumb just says it out loud.
→ GET EARLY ACCESS