How Product Managers Can Effectively Manage Their Demand Pool
The article explains why most product requirements are driven by stakeholders, then offers three practical rules—creating a "cold storage" for stale items, prioritizing by money, life, and face, and setting strict entry gates—to keep the demand pool manageable and aligned with business goals.
Managing a demand pool is a core soft skill for product managers; most requests come from bosses, business units, or customers rather than the product team itself.
Who really decides the demand?
When a company has only 1‑2 products, the boss decides everything. With 3‑10 products, the senior product leader makes the call. In larger organizations, the decision‑making authority becomes unclear, so product managers must collect, organize, and document all stakeholder requests without assuming they can prioritize them.
Three actionable rules for demand‑pool management
1. Create a “cold storage” zone – any request that has seen no activity for three months should be moved to a frozen area. If the request is truly critical, the stakeholder will come back; otherwise it will naturally die, freeing mental bandwidth.
2. Prioritize by “money, life, face” instead of simple high/medium/low tiers
Money : Does the feature help the company collect revenue or save costs? Does it enable the customer to increase income?
Life : Is the request a compliance or policy‑driven requirement (e.g., a mandatory government platform integration) that could cripple the product if ignored?
Face : Is the request coming directly from senior leadership for demo or presentation purposes, valuable for relationships even if it has limited functional impact?
Requests that fall only under UI polish or “just looks better” should stay at the bottom of the pool and will likely die due to tight schedules.
3. Stop being a trash‑can; become the gatekeeper – Reject any request that lacks a clear business loop, is based on a gut feeling, or serves only a temporary personal need. The first step in managing the pool is to control your own hand and set clear entry criteria.
Why these rules matter
By freezing stale items, you prevent “zombie” requirements from occupying valuable mental space. By categorizing by money, life, and face, you align prioritization with real business impact rather than arbitrary scores. By enforcing entry gates, you avoid the pool becoming an endless backlog that even senior stakeholders cannot understand.
Overall, the process consists of collecting all stakeholder demands, classifying them, regularly cleaning the frozen zone, and applying the three‑step framework to keep the demand pool focused and actionable.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
PMTalk Product Manager Community
One of China's top product manager communities, gathering 210,000 product managers, operations specialists, designers and other internet professionals; over 800 leading product experts nationwide are signed authors; hosts more than 70 product and growth events each year; all the product manager knowledge you want is right here.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.