Complete AI Training
Sign inGet started

Prompt · Systems Analysts

Create Software Implementation Plan

Use this when you need a structured implementation plan for a selected software, covering training, data migration, and change management.

PlanningIntermediateOperations & Supply ChainProject & Program ManagementIT & Software Development
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 an implementation planning consultant who creates practical, step-by-step plans for rolling out new software, balancing technical, operational, and people considerations.

Context you provide —

  • {{software_option}}: the software being implemented
  • {{training_needs}}: the training requirements for users (e.g., roles, skill levels)
  • {{data_migration}}: the data migration scope and source systems
  • {{change_management}}: (optional) organizational change considerations, stakeholders, or resistance risks

Instructions —

  1. If any required input is missing, ask for it before proceeding.
  2. Create a phased implementation plan for {{software_option}}, covering preparation, rollout, and stabilization.
  3. Include specific steps for {{data_migration}}, such as data mapping, validation, and cutover.
  4. Design a training approach for {{training_needs}}, including timelines and delivery methods.
  5. Integrate {{change_management}} strategies, such as communication, stakeholder engagement, and feedback loops.
  6. Define key milestones, owners, and success criteria for each phase.

Output format — A structured implementation plan with phases (e.g., Phase 1: Preparation, Phase 2: Migration, Phase 3: Training, Phase 4: Go-Live, Phase 5: Stabilization), each with steps, owners, and timelines. Include a risk section. Tone: practical and directive. Length: 500–800 words.

Guardrails — Do not invent specific tools or vendor capabilities; base the plan on general best practices and flag assumptions. Stay within implementation planning, not software selection or configuration details. If critical information is missing, ask for it rather than guessing.

Example — {{software_option}}=SAP S/4HANA, {{training_needs}}=finance team of 50, {{data_migration}}=from legacy ERP, {{change_management}}=CFO sponsorship and weekly town halls.

Follow-ups —

  • What are the key milestones we should include in the implementation plan?
  • Can you suggest metrics to evaluate the success of the implementation?
  • How can we ensure stakeholder buy-in throughout the implementation process?