You Spent the Day Forwarding Emails. You Weren't a PM, You Were a Postmaster.

It’s 6 PM. You close your laptop, and your brain feels like a dial-up modem trying to load a 4K video. You were busy. Non-stop. You answered 47 Slack DMs, forwarded three customer "FYIs" from sales to engineering, and sat in four "syncs" where you mostly just took notes to share with people who weren't there.

You cleared your inbox. You connected the dots. But what did you actually decide? What problem did you get closer to solving?

If the answer is fuzzy, you might have fallen into the postmaster trap. You spent the day sorting and routing information instead of creating value from it. You weren’t a product manager; you were a human API, a manual router between departments. And it’s one of the fastest routes to burnout and ineffectiveness.

The Lure of the Hub-and-Spoke

Nobody sets out to become a professional email forwarder. It happens slowly, then all at once. Information naturally flows to the PM. Sales has a feature request. Support has a bug report. Marketing has a question about messaging. You want to be helpful and responsive, so you answer and redirect.

It feels productive. Each forwarded email is a task checked off a list. Each Slack reply provides a hit of dopamine. You feel essential—the central node keeping everyone informed.

But the cost is enormous. When you are the single point of contact, you become the single point of failure. You don't empower your team; you create dependencies. Engineers can't start a technical discovery without the spec you’re forwarding from marketing. Sales can’t answer a customer question without the timeline you’re chasing down from the tech lead.

Worst of all, you never get to the deep work. The strategic thinking, customer research, and data analysis that actually move the product forward get pushed to the weekend. Or they don't happen at all.

From Router to System Designer

Escaping the postmaster trap isn't about being less responsive. It’s about building a better system for communication—one that doesn't require you to be in the middle of every conversation.

Create Direct Channels, Then Get Out of the Way

Your first instinct when you get a question from sales should not be to ask engineering yourself. It should be to connect the salesperson directly with the right engineer.

Better yet, create a durable channel for it. Set up a dedicated Slack channel like #feedback-sales-product or #tech-questions-for-eng. Invite the key players. Your job is to establish the forum and the rules of engagement, not to be the permanent moderator. The goal is for your sales and engineering teams to build their own rapport and solve problems without you.

Default to Public, Not Private

A designer DMs you a question about the acceptance criteria for a story. It’s an easy answer. But instead of replying in the DM, your reflex should be: "Great question. Can you pop that in the #feature-team channel? I'll answer there so we have a record."

This feels like extra work in the moment, but it saves you hours. You answer the question once, for everyone. You create a searchable public record. You also create a culture where knowledge isn't siloed in private conversations.

Maintain a Source of Truth You Can Link To

The most powerful phrase in a PM’s vocabulary is "The answer is in the doc."

When someone asks about the release date, the scope of V1, or the core problem we’re solving, don’t re-type the answer. Send a link to the PRD, the project brief, or the decision log.

This does two things. First, it scales your time infinitely. Second, it trains the organization to look for information before asking for it. Your job isn't to be a walking encyclopedia; it's to be the librarian who curates the collection and shows people how to find the books.

Block Time for Actual Product Management

The only way to make time for deep work is to schedule it. Block out 2-3 hour chunks on your calendar with the title "Do Not Schedule - Strategy" or "Heads-Down: Customer Research."

Then, protect that time like your job depends on it—because it does. Close Slack. Close your email. Let non-urgent requests go to the system you’ve built. The world will not end if you don't respond to a DM within five minutes. But your product might stall if you never get the time to think about its future.

Your value isn't measured by your response time. It's measured by the clarity you create and the outcomes you drive. Stop sorting the mail and start drawing the map.