Signal capacity proactively with operational language — not reactively with complaints

Why This Is a Rule

How you communicate capacity determines how it's received. "I'm swamped and can't take anything else on" is complaint-based and reactive — it arrives when someone asks for something and reads as excuse-making. "Current status: Yellow. Available hours this week: 4. Queue: 3 items, next opening April 7" is operational and proactive — it arrives before anyone asks and reads as professional transparency.

The framing matters because capacity limits are easily misread as personal weakness, poor time management, or lack of commitment. Operational framing eliminates these interpretations by presenting capacity as system data rather than personal limitation. A traffic light doesn't complain about being red — it communicates a state. Your capacity signal should work the same way.

The timing matters because reactive signals (declining at request time) feel like rejection. Proactive signals (sent before requests) feel like planning. Collaborators who know your capacity status before requesting can self-schedule around your availability, reducing the frequency of awkward declines entirely.

When This Fires

• Setting up regular capacity communication with frequent collaborators
• When reactive declines are creating relationship friction
• After noticing that capacity conversations feel defensive or emotional
• Any time you need to set expectations about availability without sounding like you're complaining

Common Failure Mode

Using emotional language: "I'm really overwhelmed right now" or "I've been slammed all week." These are genuine feelings but counterproductive signals — they invite sympathy rather than planning, and they frame capacity limits as personal distress rather than system state. Operational: "Status: Red. Available hours: 0. Next opening: March 15." Same information, zero emotional baggage.

The Protocol

Weekly, to frequent collaborators: (1) Send a brief capacity status using neutral operational format: traffic light (green/yellow/red), available hours, current queue with expected completion dates. (2) Send proactively — at the start of the week, not in response to a request. (3) Use facts, not feelings: numbers, dates, queue positions. (4) No apology or justification. The signal is informational, not defensive. Over time, collaborators learn to check your status before requesting, which eliminates most reactive declines.