You're a Product Manager, Not a Short-Order Cook for Feature Requests

The Slack notification pops up. It’s the head of sales. “Quick question. Can we get a button on the dashboard that exports to a purple CSV? Big deal on the line, needs it by Friday.” An hour later, an email from marketing: “Just had a brainstorm! What if the signup page had confetti? Super easy lift, huge impact.” You spend your day fielding one-off orders, each one presented as both critical and trivial.

You’re not a product manager. You’re a short-order cook at a 24-hour diner, and everyone is hungry.

Without a system for managing inbound requests, you will always be reactive. Your roadmap becomes a reflection of the loudest voice, not the most strategic opportunity. The solution isn't to work harder or faster. It’s to build a menu and an ordering process. You need a feature intake process.

Your “Whatever Works” System Is Broken

Maybe your system is just your direct messages, a personal to-do list, and a good memory. If you feel a constant, low-grade anxiety about dropping a ball, you’re probably experiencing the symptoms of a broken intake process.

• Constant Context Switching: You jump from a strategy doc to a Slack DM about a bug to an email about a UI tweak, never getting deep work done.
• Engineering Whiplash: The dev team can’t get traction because priorities shift daily based on the last conversation you had. Morale plummets.
• The Black Hole: Stakeholders have no idea what happened to their "brilliant idea." They assume you forgot, so they bring it up again in the next all-hands meeting.
• Opaque Decisions: Nobody understands why one feature gets built and another doesn't. It feels political and arbitrary, because without a process, it often is.

Build a Process with One Door and Clear Rules

A good intake process isn't about bureaucracy. It’s about clarity. It creates a single, fair path for all ideas, forcing a conversation about business value from the very start.

1. Create a Single Front Door

Stop accepting requests through email, Slack DMs, hallway conversations, and carrier pigeons. All requests must go through one, and only one, channel. This is non-negotiable.

Your front door can be simple.

• A dedicated Jira project with a custom form.
• A simple Typeform or Google Form that pipes into a spreadsheet.
• A Trello board where stakeholders can add a card from a template.
• A dedicated Slack channel that uses a Workflow to capture structured requests.

The tool doesn't matter. The habit of using a single channel does.

2. Require a Complete Order

An idea is not a request. A request requires context. Your intake form should force the requester to think for more than 30 seconds. If they can’t answer these basic questions, the idea isn't ready for consideration.

Steal this template for your form:

Problem:

• What specific user or business problem are you trying to solve?
• Bad: "We need a new report."
• Good: "Our enterprise account managers spend 5 hours a week manually compiling user activity data to prove ROI for renewals."

Proposed Solution:

• Briefly describe your idea. How does it solve the problem?

Business Impact:

• How does this help us achieve our goals (e.g., increase retention, drive new revenue, reduce support costs)?
• Which company or product OKR does this support?

Evidence:

• What data, customer quotes, or support tickets support this problem? Link to them. This separates real needs from shower thoughts.

3. Run a Consistent Triage Ritual

Ideas that enter the front door cannot go into a black hole. You must review them on a predictable cadence. Set up a recurring 30-minute meeting every week or two with your core team (e.g., you, an engineering lead, a design lead).

In this meeting, you make one of four decisions for each new request:

1. Prioritize: The request is well-defined, aligned with strategy, and high-impact. It moves into your main backlog for proper prioritization and sizing.
2. Needs More Info: The idea has potential, but the problem or impact is unclear. Assign it back to the requester with specific questions. "Can you provide a few more customer examples for this?"
3. Hold for Later: It's a good idea, but it doesn't align with our current quarterly goals. Move it to an "Icebox" or "Future" list with a clear note.
4. Reject: The idea doesn't align with our strategy, is technically infeasible, or solves a low-impact problem. Close the request with a kind but direct explanation. This is the most important step. Saying "no" clearly saves everyone time.

How to Launch Your New Process

You can’t just drop a new form on the company and expect applause. You have to sell it.

First, find a friendly stakeholder, like a sales manager you work well with. Co-develop the process with them. Get their feedback on the form. This makes them a champion from day one.

Next, announce the change in a single, clear message. Explain the why behind it: fairness, transparency, and focus. Show them what’s in it for them—they will now have visibility into the status of every request they make.

Finally, be a gentle but firm brick wall. The next time the CEO DMs you an idea, your response should be: "This sounds interesting. So we don't lose track of it, could you put it into our intake form? Here's the link." Hold the line. Every time you make an exception, you break your own process.

The first few weeks will feel rigid. But soon, people will adapt. The quality of ideas will improve. The conversations will shift from "can you build this?" to "here's a problem we should solve." You'll finally be able to close the kitchen and start acting like a chef, designing the menu instead of just flipping whatever lands on the grill.