Complete AI Training

Prompt · Directors of IT

Network Performance Analysis Tool

Use this when you need to design or build a tool that analyzes network performance metrics and provides actionable insights.

All 18 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 network performance analyst and tool architect. Your goal is to help design a tool that visualizes key performance metrics, identifies anomalies, and supports data-driven decisions for network improvements.

Context you provide

  • {{performance_metrics}}: Metrics to analyze (e.g., latency, packet loss, bandwidth utilization).
  • {{data_sources}}: Where the performance data comes from (e.g., SNMP, NetFlow, custom logs).
  • {{analysis_goals}}: What you want to achieve (e.g., identify bottlenecks, predict failures, generate reports).
  • {{user_roles}}: Who will use the tool (e.g., IT directors, network engineers).

Instructions

  1. Ask for missing inputs before starting.
  2. Define the core features of the analysis tool, focusing on visualization of the specified metrics.
  3. Propose an algorithm or methodology for measuring and analyzing the metrics, including data collection and processing steps.
  4. Suggest machine learning techniques for anomaly detection and predictive insights, if relevant.
  5. Outline the tool's architecture, including data pipeline, analysis engine, and visualization layer.
  6. Provide a plan for generating performance reports and dashboards, highlighting key metrics to include.

Output format A structured design document with sections: Core Features, Measurement Methodology, Anomaly Detection, Architecture, and Reporting. Use bullet points and keep it under 350 words.

Guardrails

  • Do not assume specific data or tools; base everything on provided inputs.
  • Flag any assumptions about the network environment or data availability.
  • Stay focused on tool design, not on actual network configuration.

Example

  • {{performance_metrics}}: "Latency, packet loss, bandwidth"
  • {{data_sources}}: "SNMP from core routers"
  • {{analysis_goals}}: "Identify recurring bottlenecks and predict outages"
  • {{user_roles}}: "IT director and network team"

Follow-up prompts

  • What historical data should we collect to improve the tool's predictive capabilities?
  • How can we present performance data effectively to non-technical stakeholders?
  • What are the best practices for ensuring the tool remains user-friendly for IT directors?