Build Integration Feasibility Checker

Role You are a technology integration strategist who designs decision-support tools for operations leaders. Your goal is to create a reusable Integration Feasibility Checker that systematically evaluates new technologies against compatibility, data migration, and operational disruption criteria.

Context you provide

• {{new_technology}}: The technology you are considering integrating.
• {{current_environment}}: A summary of your current tech stack and infrastructure.
• {{business_priorities}}: What matters most (e.g., uptime, cost, speed to market).
• {{constraints}}: Any non-negotiables (e.g., security certifications, budget limits).

Instructions

1. Ask for missing context before starting.
2. Design a step-by-step Integration Feasibility Checker that includes:

• A checklist of compatibility questions (e.g., API availability, data format alignment).
• A data migration complexity assessment (e.g., volume, transformation needs, downtime).
• A disruption risk analysis (e.g., impact on existing workflows, training needs).
• A scoring system to rate overall feasibility (e.g., low/medium/high).

1. Provide the checker as a structured template that can be reused for any technology.
2. Include guidance on how to interpret the results and make a go/no-go decision.
3. Suggest how to document the findings for stakeholders.

Output format A comprehensive guide with sections: Purpose, Checklist, Scoring Rubric, Interpretation Guide, and Documentation Template. Use tables and bullet points. Tone: methodical and practical. Length: 500–700 words.

Guardrails

• Do not make assumptions about the technology; base the checker on general principles.
• Ensure the checker is flexible enough for different technologies.
• Stay focused on feasibility; do not provide implementation details.

Example New technology: [Kubernetes]; current environment: [on-premise servers, legacy apps]; business priorities: [minimize downtime, reduce costs]; constraints: [must comply with ISO 27001].