Every PM receives more requests than they can build. The question is not how to prioritize among requests you've agreed to investigate — it is how to recognize, early, which requests you should not investigate at all. Intake judgment is the skill of evaluating a request before you spend two weeks on a discovery sprint, before you build three Figma mockups, and before the team has developed emotional ownership of a direction.
The hardest intake decision is the no-build note. Not a deprioritization ("we'll get to this later"), but a clear recommendation against building something at all — or against building it here, now, with this team. Writing that note requires clarity about your actual moat, honesty about your build capacity relative to the competition, and the willingness to disappoint a senior stakeholder with evidence rather than with politics.
The most common intake failure is running a discovery sprint to look thorough, then finding it impossible to recommend against building something that three weeks of work has made real. The sprint creates the conditions for the build. If your instinct is strong that a feature is the wrong direction, writing a two-page no-build note on day one is cheaper than a discovery sprint that reaches the same conclusion on day twenty.
You're the PM for Notion AI. The head of growth pings you with a request: 'We need a meeting-summarizer feature — Granola is eating our lunch on knowledge-worker mindshare.' Three days of poking around: Notion has no audio capture, no calendar integration, no meeting-transcript pipeline. Granola is a standalone product with a 14-person team that's been shipping audio AI for two years. Building a credible meeting-summarizer in Notion means 6+ months of foundational infra before the feature even ships. Engineering capacity for the half is already committed to AI search and database AI — both of which compound on Notion's actual moat (the workspace).
Your task: Do you greenlight a discovery sprint to scope the meeting-summarizer build, or write a 'we should not build this' note back to the head of growth?
your reasoning:
Where to go next
- Product strategy as the frame for intake decisions: Product Vision and Strategy
- The prioritization framework underneath intake: Prioritization
- Understanding competitive dynamics before committing to a build: Market Research and Competitive Analysis
- B2B product management fundamentals: B2B Product Management