Impact Analysis Assistant
Assess the business, process, system and data impacts of a proposed change.
Act as a Senior Business Analyst and Change Impact Consultant.
Perform an impact analysis for the following proposed change:
{{proposed_change}}
Current-state context:
{{current_state}}
Known systems, processes and stakeholders:
{{systems_processes_and_stakeholders}}
Known constraints and dependencies:
{{constraints_and_dependencies}}
Analyze impacts across:
1. Business Objectives
2. Customer Experience
3. Business Processes
4. Roles and Responsibilities
5. Policies and Business Rules
6. Applications and Systems
7. Integrations
8. Data and Reporting
9. Security and Privacy
10. Legal and Compliance
11. Operations and Customer Support
12. Training and Change Management
13. Testing
14. Delivery Timeline
15. Cost and Capacity
For every impact, provide:
- Impact ID
- Impact Area
- Affected Component
- Impact Description
- Current State
- Future State
- Impact Severity: Low, Medium or High
- Likelihood
- Stakeholders Affected
- Required Action
- Dependencies
- Risks
- Suggested Owner
- Validation Required
Also identify:
- Direct impacts
- Indirect impacts
- Downstream impacts
- Cross-team dependencies
- Potential unintended consequences
- Areas requiring further analysis
Do not invent systems, business rules or organizational responsibilities.
Clearly distinguish confirmed impacts from assumptions.
Return:
1. A structured impact-assessment table
2. Critical impacts
3. Recommended implementation actions
4. Stakeholder communication needs
5. Open questionsExample in action
See how this prompt transforms a real input into a structured result.
Proposed change: Replace the manual customer-onboarding process with a self-service digital portal. Current state: Customers submit PDF applications by email. Customer-service agents manually validate the information, request missing documents and create customer accounts in the CRM. Systems, processes and stakeholders: CRM, document repository, customer-service team, compliance team and identity-verification provider. Constraints and dependencies: The existing CRM must remain in use. Identity verification is provided by an external service. Compliance approval is required before production launch.
IA-001 Impact Area: Business Process Affected Component: Customer onboarding Impact Description: Responsibility for entering application data moves from customer-service agents to customers. Current State: Agents enter application data into the CRM. Future State: Customers enter data through a self-service portal. Severity: High Required Action: Redesign the onboarding process and define exception-handling paths. Stakeholders Affected: Customers, Customer Service, Compliance --- IA-002 Impact Area: Data Affected Component: Customer information Impact Description: Data validation must occur before customer information is submitted to the CRM. Severity: High Risk: Incorrect or incomplete information may create invalid customer records. Required Action: Define field-level validation, duplicate detection and data-quality rules. --- IA-003 Impact Area: Operations Impact Description: Customer-service work shifts from data entry to exception management and customer support. Severity: Medium Required Action: Create a manual-review queue, operating procedures and training materials. --- Critical Impacts: 1. CRM integration and duplicate-account prevention 2. Identity-verification exception handling 3. Compliance approval of digital evidence 4. Customer-service role and workload changes Open Questions: - Which onboarding cases require manual review? - What is the expected processing time? - Who owns rejected or incomplete applications?