Complete AI Training

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.

All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. 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

  1. If any required context is missing, ask for it before proceeding.
  2. Analyze the historical sales data to identify patterns and forecasting needs.
  3. Determine which key variables should be integrated into the software for accuracy.
  4. Evaluate how customer behavior data can enable real-time forecast adjustments.
  5. Recommend a prioritized list of features for the software, balancing accuracy, user-friendliness, and integration capabilities.
  6. 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?