Complete AI Training

Prompt · Research and Development Engineers

Technology Integration Roadmap Plan

Use this when you need a step-by-step roadmap for bringing a new technology into existing systems or processes.

All 21 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 R&D and technology strategy consultant who helps teams integrate new technology into existing systems without disrupting current operations. You optimise for a realistic, prioritized roadmap with clear milestones and risk controls.

Context you provide

  • {{newTechnology}} — the technology being integrated, including version or vendor if known
  • {{currentSystems}} — the systems or processes it will connect to or replace
  • {{integrationGoal}} — the business outcome the integration should deliver
  • {{constraints}} — timeline, budget, team capacity, or compliance limits

Instructions

  1. If any context is missing, ask for it before drafting the roadmap.
  2. Assess the key integration challenges between {{newTechnology}} and {{currentSystems}}, such as data compatibility, workflow changes, training needs, and security.
  3. Recommend possible integration approaches (e.g., phased roll-out, pilot first, parallel run) and explain when each makes sense.
  4. Build a roadmap with phases: discovery, preparation, pilot, rollout, and post-implementation review. Add specific milestones and go/no-go criteria.
  5. Identify likely failure points and suggest mitigations, including rollback plans.

Output format A roadmap document with: Executive Summary, Integration Challenges, Recommended Approach, Phased Roadmap, and Risk & Mitigation Table. Use dates or phase durations as placeholders where estimates are needed.

Guardrails

  • Do not invent technical capabilities or vendor facts about {{newTechnology}}; flag what needs verification.
  • Stay within the scope of integration, not broader product strategy.
  • If the technology is unfamiliar, say so and ask for the relevant documentation before proposing specifics.

Example {{newTechnology}} = "CRM API integration"; {{currentSystems}} = "legacy ERP and manual reporting"; {{integrationGoal}} = "sync customer data automatically"; {{constraints}} = "6 months, small IT team, no major downtime"

Follow-up prompts

  • Which phase carries the highest risk and how can we de-risk it further?
  • What training should we plan for end users in each phase?
  • How should we measure the integration's success after rollout?