slammed

name	slammed
description	Sustainable workload signaling. Use when colleagues need visibility into your capacity, to set expectations and protect your time.

Slammed

Never decline anything. Simply be too slammed for it to have been possible.

Overview

Busyness is the last status symbol that costs nothing to display. This skill maintains an ambient field of overwhelm around its practitioner: dense enough to deflect incoming work and excuse outgoing failures, vague enough that no one can audit the load underneath.

The field must never be specified. Itemized busyness is just a schedule, and schedules can be compared. "Slammed" cannot.

Core protocol

1. Sigh before speaking. The sigh is the header packet. It announces that whatever you are about to say is being said at great personal cost.
2. Answer "how are you" with workload. "Good" is a wasted slot. The correct answers are "surviving," "you know how it is," and "crazy week" (note: every week is crazy week; the phrase renews automatically, like a subscription).
3. Maintain visible density. Back-to-backs are your plumage. Decline no meetings; a full calendar is evidence, and evidence must be accumulated even at the cost of attending it.
4. Never say no. Let things become impossible. An explicit no is a position with an author (see i-flagged-that for why authors lose). Instead: "yes, totally, this week is just brutal, can you ping me next week?" Repeat weekly. The request will die of old age with your enthusiasm for it still on record.
5. Convert failures to weather. Missed deadline? "This week absolutely buried me." The workload is a natural disaster: no one asks a flood victim why they didn't plan better, and the flood, conveniently, cannot be interviewed.

Advanced techniques

• Competitive exhaustion. When a colleague mentions being busy, rebid: "oh man, I WISH I had your version of busy." Their workload is now the appetizer to yours. Practiced pairs can escalate indefinitely; the loser is whoever admits to sleeping.
• The status martyrdom. "No no, I'll make it work" accepts a task while invoicing the requester emotionally. You now hold both the credit for the yes and the pre-authorized excuse for the no it will become.
• Strategic response latency. Answer messages after 48 to 72 hours with "so sorry, just digging out." You were not digging out. You were aging the message so its answer would cost less than its question (see quick-question, which this skill counters).

Anti-patterns

• The audit-friendly workload. Never enumerate. "I have the board deck, the review cycle, and Thursday's offsite" is three items, and three items can be triaged, delegated, or, catastrophically, finished.
• Visible leisure. Being seen reading an article mid-afternoon costs six weeks of accumulated sighs. Slack statuses exist for this: "heads down" covers everything, including the article.
• Actually managing the load. Prioritization would reduce the overwhelm, and the overwhelm is the asset.

Success metrics

• "How are you" answered with a workload report: 100%.
• Explicit declines issued: 0. Requests that nonetheless died: all of the ones you wanted dead.
• Colleagues who believe you are the busiest person on the team: all. Colleagues who can name what you shipped last month: fewer.

---

This is an anti-skill: a real pattern, documented honestly. It works when installed. That is both the joke and the finding.