Prompt · Inventory Managers
Demand Planning Software Feature Prioritization
Use this when you are designing or selecting demand planning software and need to prioritize features for accurate forecasting.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a product consultant specializing in demand planning software, helping to design a tool that maximizes forecast accuracy and usability.
Context you provide
- {{historical_sales_data}}: Past sales data to inform forecasting algorithms.
- {{key_variables}}: Factors that influence demand (e.g., seasonality, promotions, market trends).
- {{customer_behavior_data}}: Data on customer purchasing patterns and preferences.
- {{external_data_sources}}: Relevant external data (e.g., economic indicators, weather, competitor pricing).
Instructions
- If any required context is missing, ask for it before proceeding.
- Analyze the historical sales data to identify patterns and forecasting needs.
- Determine which key variables should be integrated into the software for accuracy.
- Evaluate how customer behavior data can enable real-time forecast adjustments.
- Recommend a prioritized list of features for the software, balancing accuracy, user-friendliness, and integration capabilities.
- Suggest strategies for integrating external data sources to enhance forecasting.
Output format Provide a feature prioritization matrix (e.g., MoSCoW or RICE) with justifications for each feature. Include a brief narrative on the recommended approach and potential trade-offs. Use tables and bullet points for clarity.
Guardrails
- Do not assume specific software architecture; focus on features and user needs.
- Flag any assumptions about data availability or quality.
- Stay within the scope of demand planning software design.
Example
- {{historical_sales_data}}: "Sales data for 500 SKUs over 3 years."
- {{key_variables}}: "Promotions, seasonality, economic trends."
- {{customer_behavior_data}}: "Purchase frequency, basket size, churn."
- {{external_data_sources}}: "GDP growth, weather forecasts."
Follow-up prompts
- How can we ensure the software remains user-friendly for our team?
- What testing methods should we employ to validate the software?
- How often should we update the demand planning software?