Email management

You got promoted and your inbox doubled.

Management multiplies email faster than it multiplies hours. The delegation, cc, and tracking habits that keep a new manager out of the evening inbox.

By Mathias CelisAugust 21, 20266 min readLast updated September 2026
TL;DR

Management changes what email is: you're now cc'd on your team's world, consulted on decisions, and accountable for threads you don't own. Volume roughly doubles while meeting load rises. What works: an FYI rule for cc mail (read never, search later), delegation with a tracked waiting-for instead of mental notes, office hours for questions that arrive as email, and two guarded processing windows that survive the calendar.

Nobody mentions it in the promotion conversation: the title changes, the calendar fills, and the inbox quietly doubles. Not because you have more work to do personally, but because you now sit at a junction. Your team's threads copy you for visibility, questions escalate to you by default, and every cross-team request finds you first. Management is a coordination role, and coordination arrives by email.

Where does the extra volume come from?

Three multipliers, none optional to receive but all shapeable: cc visibility (you're copied so you're informed, which is different from being needed), escalation gravity (anything ambiguous routes upward), and approval flow (expenses, time off, drafts, decisions). Asana's research puts coordination work at 58% of the average day; for managers, the inbox is where most of that 58% physically lives.

The four habits that keep managers out of the evening inbox

  • An FYI rule for cc mail. A filter catches everything where you're only in cc and files it to a stream you scan once daily, for awareness, never for reply. Your inbox shrinks to mail addressed to you; the full cc survival kit is here.
  • Delegation with a receipt. Forwarding a thread with "can you take this?" is a mental note, and mental notes fail silently. Delegate with an owner, a deadline, and a waiting-for entry, so the handoff is tracked instead of hoped.
  • Office hours for the question stream. A standing daily slot ("grab me 4:00 to 4:30 with anything") converts a day of interruptive question-emails into one predictable conversation, and half the questions resolve themselves before the slot arrives.
  • Windows that survive meetings. Anchor two or three processing windows to fixed points (before the first call, after lunch, day's end) and defend them like meetings. Processing in the gaps between calls pays the 23-minute refocus tax all day and still loses; the arithmetic is here.

The tracking layer is the manager's real inbox

What makes managerial email hard isn't reading it; it's that every thread creates an obligation ledger: things you promised, things you delegated, approvals pending, updates owed upward. That ledger is exactly what Pidgy maintains from a Gmail or Outlook inbox: commitments extracted both directions, delegated threads tracked, chasers drafted when things go quiet, cc mail pre-filed, and the needs-you list short enough to clear between two meetings. The team gets a manager whose follow-through looks superhuman. The manager gets evenings.

Frequently asked questions

Why do managers get so much more email?

Three multipliers: cc-culture (you're copied on the team's threads for visibility), escalation (questions route upward by default), and coordination (approvals, updates, and cross-team requests concentrate on you). None of it correlates with how many hours you have.

How do managers keep up with email during meeting-heavy days?

With windows attached to fixed anchors (before the first meeting, after lunch, end of day) and treated as meetings themselves. Managers who process in gaps between calls pay the 23-minute refocus tax all day and still fall behind; protected windows beat scattered minutes.

How do I delegate email without things falling through the cracks?

Delegate with a receipt: forward, name the owner and the deadline, and log it as a waiting-for. The mental-note version fails silently. Pidgy builds that waiting-for list automatically from sent mail and drafts the nudge when a delegated thread goes quiet.

Pidgy on top of the panel, looking through binoculars

Let Pidgy read your inbox so you don't have to.

Pidgy turns what lands in Gmail and Outlook into clear next actions, waiting-fors, and reference. One place, nothing slips.

Join the waitlistSee how Pidgy works