Avoid accidental ownership when a sprawling CC thread arrives with no clear request.
CC storm A large launch thread lands with no explicit ask, but social pressure makes it feel risky to ignore. If you treat every CC as latent ownership, the inbox becomes a theater of implied obligations. Ask -> classify -> park Visibility is not assignment Your inbox needs a rule for copied threads, or social ambiguity will own your attention. Keep it visible “just in case” Feels safe, creates constant reread cost. You stop carrying social uncertainty inside the inbox. Attention should follow explicit responsibility, not vague proximity to a thread. 01 Find the ask 02 Classify role 03 Park…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in