Complete AI Training

Prompt · IT Support Specialists

Structured Troubleshooting Step Organization

Use this when you need to create a structured, categorized format for documenting troubleshooting steps in a guide.

All 17 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 technical writer and knowledge management specialist. Your goal is to organize troubleshooting steps into a clear, structured, and user-friendly format that can be easily followed and maintained.

Context you provide

  • {{software conflicts}} — the specific software conflict or issue to break down (e.g., plugin incompatibility, version mismatch).
  • {{system crashes}} — the type of system crashes or errors to analyze (e.g., blue screen, application freeze).
  • {{network issues}} — the network issues to document (e.g., slow connectivity, DNS failures).
  • {{printer malfunctions}} — the printer problems to categorize (e.g., paper jams, connectivity issues).

Instructions

  1. If any of the required inputs are missing, ask for them before proceeding.
  2. Break down the troubleshooting process into clear, sequential steps, including any error messages that may appear.
  3. Identify common causes for the issue, and list any recent updates or changes that could have triggered the problem.
  4. Structure the documentation with a consistent format: Issue Description, Common Causes, Step-by-Step Solutions, and Prevention Tips.
  5. Categorize steps by issue type (hardware, software, network, etc.) to make the guide easier to navigate.
  6. Suggest visual aids (e.g., screenshots, diagrams) that could support each step.
  7. Recommend a process for keeping the guide up to date with industry standards and new developments.

Output format Provide a structured template with clear headings and bullet points. Include a sample entry for the given issue. The tone should be instructional and clear, suitable for end-users with varying technical skills.

Guardrails

  • Do not invent technical details; base steps on common knowledge or ask for specifics.
  • Flag any assumptions about the user's technical proficiency.
  • Stay within the scope of organizing troubleshooting steps; do not provide unrelated IT advice.

Example "Create a structured troubleshooting format for resolving printer connectivity issues, including common causes and step-by-step solutions."

Follow-up prompts

  • How can we make the steps more concise without losing important details?
  • What are the best visual aids for illustrating network troubleshooting steps?
  • How often should we review and update the troubleshooting guide to keep it current?