Change Impact Assessment Question Bank

Questions to Ask for Your Change Impact Assessment

A complete set of Change Impact Assessment questions for discovering what is changing, who is affected, how significant the change is, and what you may be missing.

Change Impact Assessment questions should move beyond broad project statements and uncover the specific differences affected Roles and Teams will experience. The strongest questions explore the Current State, Future State, affected groups, timing, Impact Severity, Business Criticality, transition burden, and the different types of impact created by the change.

Turn Broad Change Into Specific Questions
Project statement“We are implementing a new ERP system.”CIA question: What will Accounts Payable analysts do differently in the new system?
Project statement“We are changing the approval model.”CIA question: Who will make, approve, escalate, or own decisions differently?
Project statement“We are introducing new reporting.”CIA question: What data, report, metric, ownership, or decision will change for each Role/Team?
Using the Question Bank

How to Use This Change Impact Assessment Question Bank

You do not need to ask every question on this page. Use this question bank as a menu, not a script. Start with the Essential Questions, then use the sections that apply to your change and the information you still need to understand.

Begin by identifying the right sources of information. Then explore the Current State, Future State, affected Roles/Teams, timing, and transition. Use the Impact Type questions to probe for impacts that may not surface naturally, and use the Severity, Business Criticality, missed-impact, and validation questions as the assessment develops.

Keep discovery separate from the response

Do not jump immediately from “What is changing?” to “What training or communication do we need?” First identify and assess the impact. Then use the findings to determine the right response.

This page focuses on what to ask. For the complete process for scoping, conducting, documenting, scoring, validating, analyzing, and reporting a CIA, see the Change Impact Assessment how-to guide.

Preview of the Essential Change Impact Assessment Questions page from the printable question bank PDF
Printable PDF

Want the Printable Question Bank?

Get the complete Change Impact Assessment Question Bank as a PDF you can save, print, or use during discovery conversations and workshops. Enter your email address below to get your copy.

CIA Question Bank Download
Start Here

Essential Change Impact Assessment Questions

If you need a short list to begin a discovery meeting or workshop, start with these questions. They cover the core of a useful CIA before you move into more detailed probing.

  • What is changing?
  • How does the affected work happen today?
  • How will the work happen after the change?
  • What specifically will people need to start, stop, continue, or do differently?
  • Which Roles/Teams are affected?
  • Does the same change affect different Roles/Teams differently?
  • Are managers, support teams, or upstream and downstream groups also affected?
  • When will each group begin experiencing the change?
  • Is the impact temporary, ongoing, or permanent?
  • How significant is the change for the affected Role/Team?
  • How important is the affected activity to business performance?
  • What happens if the new work is delayed, performed incorrectly, or not sustained?
  • What assumptions or unresolved decisions could change the impact?

These questions establish the basic shape of the change. The sections below help you go deeper when the answers are incomplete, too broad, or limited to the most obvious parts of the project.

Before Discovery

Questions to Ask Before You Begin Discovery

Before getting into detailed impact questions, clarify who should provide input and how you will gather the information you need.

  • Who understands how the affected work is performed today?
  • Who understands how the Future State is expected to work?
  • Which affected Roles/Teams should be represented?
  • Should we speak directly with people who perform the work, their managers, or both?
  • Which process owners, subject-matter experts, system owners, or support functions should be involved?
  • Are different locations or business units affected differently enough that they should be represented separately?
  • Are customers, vendors, partners, or other external stakeholders an important source of information?
  • Which sources of information should we use, such as interviews, workshops, surveys, observation, or existing documentation?
  • Are there topics that require live discussion and follow-up rather than a survey?
  • What do we already know, and what do we still need to learn?

Questions About the Current State

You need a reliable picture of how the work operates today before you can describe the impact created by the Future State. Formal process documents are useful, but they often miss workarounds, exceptions, local practices, and informal decision paths.

How the Work Operates Today

  • Walk me through how this work is done today from beginning to end.
  • Who performs the work today?
  • Who manages, approves, supports, or depends on it?
  • What systems, tools, data, reports, forms, or other resources are used?
  • What decisions are made during the work?
  • Where do handoffs occur?
  • What approvals are required?

What the Formal Process May Miss

  • What happens when the normal process does not work?
  • What exceptions occur?
  • What workarounds are commonly used?
  • Where do local or site-specific variations exist?
  • Which informal practices are important even though they are not documented?
  • What parts of the current approach work particularly well?
  • Where does the documented process differ from what people actually do?
Useful prompt: Ask someone who actually performs the work to walk through a real example. That often reveals details that are missing from project documentation.

Questions About the Future State

Once the Current State is clear, examine the same work in the Future State. The difference between the two is where the actual change impact becomes visible.

What Will Be Different?

  • What will be different after the change?
  • What will remain the same?
  • What will people start doing?
  • What will people stop doing?
  • What will people need to do differently?
  • What work will be automated?
  • What work will be standardized?
  • What work will move to another Role/Team?

What Must Be Confirmed?

  • What new decisions or approvals will be required?
  • What responsibilities will be added or removed?
  • What new tools, information, or capabilities will be required?
  • What is already confirmed about the Future State?
  • What is still an assumption?
  • What decisions are still unresolved?
  • Which unresolved decisions could significantly change the impact?

Do not stop at the project deliverable

“A new system is being implemented” is a project statement, not a complete impact. Keep asking what the affected Role/Team will actually do, decide, use, produce, approve, communicate, or experience differently.

Questions to Identify Who Is Impacted

Avoid stopping at broad labels such as “Operations,” “HR,” or “Finance.” Separate groups when the change experience, timing, ratings, or follow-up needs are different.

  • Which Roles/Teams directly experience this change?
  • Which managers are affected because their employees’ work changes?
  • Which support functions are affected?
  • Which groups provide inputs to the changed work?
  • Which groups receive outputs from it?
  • Are customers, vendors, partners, regulators, or other external groups affected?
  • Does the same Role/Team experience the change differently in different locations?
  • Do different parts of a Role/Team experience meaningfully different impacts?
  • Should a broad group be separated into smaller groups for the assessment?
  • Approximately how many people experience this specific impact?

Questions to Trace Impacts Across the Work

Some of the most important impacts occur outside the part of the process being directly redesigned. Trace the change upstream, downstream, and into exceptions to find impacts the core project team may not immediately see.

Follow the Flow

  • Who provides the input to the changed activity?
  • Who receives its output?
  • What changes for those groups?
  • What happens immediately before the changed activity?
  • What happens immediately after it?
  • Does removing work from one group create work somewhere else?

Test Exceptions and Dependencies

  • Does automation create new monitoring or exception-handling responsibilities?
  • Does the change create new reconciliation or follow-up work?
  • What happens during a high-volume or peak period?
  • What happens in an exception case?
  • Which dependencies could create additional impacts if they change or fail?

Questions About Timing and Transition

The ongoing Future State and the experience of getting there are not always the same. Transition can create temporary work, dual processes, backlogs, workarounds, or concentrated workload that deserves its own attention.

  • When will each Role/Team first experience the impact?
  • Will different groups experience the change at different times?
  • Is implementation occurring in phases?
  • What changes before implementation?
  • What happens during implementation?
  • What temporary work is required during transition?
  • Will old and new processes operate at the same time?
  • Is data migration or conversion required?
  • Will backlogs, fallback procedures, or temporary workarounds be needed?
  • Is the impact one-time, temporary, ongoing, or permanent?
  • How frequently will people experience it?
  • Do several major impacts affect the same Role/Team at the same time?
  • Does the timing collide with a peak business period, month-end, seasonal demand, or another major initiative?
Important: A moderate individual impact can become much harder to absorb when several other changes hit the same group at the same time.

Questions About Less-Visible People Impacts

Not every impact is a process step or system screen. Changes to judgment, autonomy, influence, habits, workload, coordination, and accepted ways of working can be just as important.

Skills, Judgment, and Behavior

  • What new knowledge will people need?
  • What new judgment will they need to exercise?
  • What new skills will they need?
  • What established habits will need to change?
  • What informal ways of working will need to stop?
  • What will people continue doing the old way because it seems easier, faster, or safer?

Autonomy, Influence, and Workload

  • Does the change alter employee autonomy or discretion?
  • Does decision-making authority change?
  • Does the change affect how people define expertise or success?
  • Does the change increase cognitive effort?
  • Does manager workload increase?
  • Does the change create additional coordination work?
Discovery Lenses

Change Impact Assessment Questions by Impact Type

Use Impact Types to challenge blind spots after you understand the change. Not every type will apply to every initiative. The goal is to make sure the assessment is not limited to the first process or technology impacts that come to mind.

Process/Workflow

Use when steps, sequence, handoffs, approvals, exceptions, timing, or flow of work changes.

  • Which steps are added, removed, reordered, or automated?
  • Does work move from one group to another?
  • How do handoffs change?
  • How do approvals or escalation paths change?
  • Does the timing or pace of the work change?
  • Does the volume or frequency change?
  • What new monitoring or follow-up work is created?
  • What new exception handling is required?
  • How does the process work during transition?
  • What happens during peak demand or failure conditions?
Role/Responsibility

Use when tasks, ownership, accountability, authority, or role expectations change.

  • Which responsibilities are added?
  • Which responsibilities are removed?
  • Which responsibilities move to another Role/Team?
  • Who owns the work today?
  • Who owns it after the change?
  • Does anyone gain or lose authority?
  • Does accountability change?
  • Are people responsible for outcomes without having the authority or capacity needed to deliver them?
  • Do job expectations change?
  • Do manager responsibilities change?
Organization/Structure

Use when reporting lines, teams, organizational units, hierarchy, or structural relationships change.

  • Do reporting lines change?
  • Do team boundaries change?
  • Are teams being combined or separated?
  • Is work being centralized or decentralized?
  • Are new organizational units being created?
  • Are leadership roles being added or removed?
  • Does span of control change?
  • Are new coordination points required?
  • Does the new structure affect local decision-making?
  • Does it create new dependencies between groups?
Governance/Decision Rights

Use when authority, approvals, governance, escalation, or decision ownership changes.

  • Who makes the decision today?
  • Who will make it after the change?
  • Do approval thresholds change?
  • Does exception authority change?
  • Are decisions becoming more centralized?
  • Are decisions being delegated?
  • Are any decisions becoming automated?
  • Are governance forums being created or eliminated?
  • Do escalation routes change?
  • Could overlapping or unclear decision rights create delays or conflict?
System/Technology

Use when applications, tools, automation, integrations, access, or technology-supported work changes.

  • Which systems or tools are being introduced?
  • Which are being replaced or retired?
  • What user steps change?
  • Do screens, navigation, or workflows change?
  • What becomes automated?
  • What manual work remains?
  • What new monitoring or exception handling is required?
  • Do permissions or access requirements change?
  • Are different devices or authentication methods required?
  • What happens during migration, downtime, defects, or fallback?
Policy/Procedure

Use when internal policies, rules, procedures, standards, thresholds, or required methods change.

  • Which policy or procedure is changing?
  • What becomes newly required?
  • What is no longer required?
  • Do approval requirements change?
  • Do documentation requirements change?
  • Are local variations being eliminated?
  • Are new variations being permitted?
  • Who interprets unclear cases?
  • Who approves exceptions?
  • Where could different groups apply the new policy inconsistently?
Skills/Knowledge

Use when people need different knowledge, skill, judgment, capability, confidence, or proficiency.

  • What must people know that they do not need to know today?
  • What must they be able to do differently?
  • Does the change require new judgment?
  • Does it require new decision-making?
  • How much practice will be necessary?
  • How quickly must people become proficient?
  • Which skills are shared across groups?
  • Which skills are Role/Team-specific?
  • What mistakes are likely while proficiency develops?
  • Which groups face the greatest learning requirement?
Behavior/Ways of Working

Use when habits, routines, collaboration, discipline, interaction patterns, or expected behavior changes.

  • What must people consistently do differently?
  • Which old habits need to stop?
  • Which shortcuts or workarounds need to disappear?
  • Does collaboration change?
  • Does documentation behavior change?
  • Does escalation behavior change?
  • Do handoff behaviors change?
  • Which old behaviors may remain attractive because they are familiar?
  • What will managers need to reinforce?
  • What will show that the new behavior has become routine?
Culture/Mindset

Use when norms, identity, autonomy, trust, influence, status, values, or accepted ways of succeeding change.

  • Does anyone lose or gain autonomy?
  • Does discretion change?
  • Does the change affect professional identity?
  • Does the source of expertise change?
  • Does anyone gain or lose influence?
  • Does the change affect trust?
  • Does the definition of success change?
  • Which existing norms conflict with the Future State?
  • What beliefs about quality, customers, control, leadership, or performance may need to change?
  • What could cause people to publicly follow the new approach while continuing the old approach informally?
Communication/Information

Use when information content, source, ownership, flow, channel, cadence, feedback, or availability changes as part of the work itself.

  • What information will people receive differently?
  • What information will they create differently?
  • What will they need to share or escalate differently?
  • Who owns the source of truth today?
  • Who owns it after the change?
  • Do communication channels change?
  • Do meetings or notifications change?
  • Does the frequency of information change?
  • Will people lose informal sources they currently rely on?
  • Do customers, employees, partners, or other stakeholders need different information as part of the new operating model?
Data/Reporting

Use when data creation, definitions, ownership, quality, reporting, access, migration, or use changes.

  • What data is newly created or captured?
  • What data is migrated or converted?
  • What data is retired?
  • Do definitions or business rules change?
  • Do required fields or formats change?
  • Who enters the data?
  • Who owns or approves it?
  • Which reports or decisions depend on it?
  • What happens if the data is late, incomplete, duplicated, or incorrect?
  • How will data be managed during transition?
Performance Measures/Incentives

Use when KPIs, targets, scorecards, performance visibility, evaluation, goals, rewards, or consequences change.

  • Which measures change?
  • Do formulas or thresholds change?
  • Are new measures being introduced?
  • Are any existing measures being eliminated?
  • What performance becomes newly visible?
  • Are employees evaluated differently?
  • Are managers evaluated differently?
  • Do existing incentives encourage behavior that conflicts with the new way of working?
  • Do old and new measures conflict during transition?
  • Could the new measures unintentionally encourage the wrong behavior?
Capacity/Workload

Use when workload, work volume, effort, pace, staffing, competing priorities, cognitive load, or available capacity changes.

  • Does the amount of work increase or decrease?
  • Does work become more complex?
  • Does the pace change?
  • Is new manual work created?
  • Is additional monitoring or reconciliation required?
  • Will old and new processes temporarily operate together?
  • Is staffing sufficient?
  • Is manager capacity sufficient?
  • Where could workload peaks collide with training, implementation, or normal business demands?
Customer/Stakeholder Experience

Use when customers, clients, partners, suppliers, regulators, patients, citizens, members, or other external stakeholders experience a change.

  • What will the external stakeholder experience differently?
  • Do service channels change?
  • Do wait times or service levels change?
  • Do points of contact change?
  • Do external stakeholders need to provide different information?
  • Do they need to complete different steps?
  • Are they expected to use a different channel?
  • Will frontline employees need new explanations or scripts?
  • Do escalation or exception processes change?
  • Could accessibility, service, complaint, or relationship risks increase?
Physical Environment/Work Location

Use when workspace, location, equipment, travel, physical access, shifts, safety, or physical work conditions change.

  • Does work move to another location?
  • Does remote or hybrid work change?
  • Do workspaces change?
  • Is different equipment required?
  • Do storage or physical access requirements change?
  • Does the movement of people, materials, or inventory change?
  • Do security or safety requirements change?
  • Do travel or commuting expectations change?
  • Do shift arrangements change?
  • Are temporary physical arrangements required during transition?
Compliance/Control

Use when legal, regulatory, security, privacy, audit, risk, safety, control, assurance, or mandatory requirements change.

  • Which requirement or control is changing?
  • Why is it changing?
  • Who performs the control today?
  • Who performs it after the change?
  • Who reviews or approves it?
  • Do thresholds change?
  • Does segregation of duties change?
  • Do audit trail or retention requirements change?
  • What happens if the requirement is missed or performed incorrectly?
  • What new documentation, monitoring, or proof will be required?
Common blind spot: Process and technology impacts are often easiest to see first. Decision rights, workload, behavior, culture, performance measures, customer experience, controls, and downstream impacts can be easier to miss.

Questions for Assessing Impact Severity and Business Criticality

These are different judgments and should be explored separately. Impact Severity is about the magnitude of change experienced by the Role/Team. Business Criticality is about the importance of the affected activity and the consequence if it is disrupted, delayed, performed incorrectly, or not sustained.

Impact Severity

How much does the work change?

  • How different is the Future State from the Current State for this Role/Team?
  • How much of the person’s work changes?
  • Are responsibilities changing?
  • Are decision rights changing?
  • Are new skills or behaviors required?
  • Is the group learning a completely new system or making a minor adjustment?
  • How much established behavior must change?
  • How difficult will the new way of working be to perform reliably?
  • Is the impact limited to one task or spread across much of the role?
  • Does the impact create significant temporary transition burden?
Business Criticality

How important is the affected activity?

  • What business activity does this impact affect?
  • What happens if the activity is delayed?
  • What happens if it is performed incorrectly?
  • What happens if employees continue using the old approach?
  • Could the impact affect customers?
  • Could it affect revenue or cost?
  • Could it affect safety?
  • Could it create legal, regulatory, security, or compliance consequences?
  • Could it interrupt a critical operational process?
  • Could it affect important business decisions?
  • Is there a particular period when the activity becomes more critical?
  • How quickly would the organization feel the consequence of failure?

Do not use one rating as a substitute for the other

A large change can affect relatively low-criticality work, while a small change can affect highly critical work. Keeping the two ratings separate produces a more useful picture of where attention is needed.

Questions to Test Whether You Have Missed an Impact

Before concluding discovery, deliberately challenge the assessment. Use these questions as a final blind-spot check for impacts that may not surface through the more structured questions above.

  • Who is affected that we have not represented?
  • What informal work might not appear in the documentation?
  • Who gains or loses authority, autonomy, access, expertise, or influence?
  • What workaround is likely to continue?
  • Which assumption would cause the largest problem if it proves wrong?
  • What impact would be easiest for the project team to overlook?
  • What will people doing the work notice that the project team might not?
  • What have we not asked?

Questions to Validate the Change Impact Assessment

Discovery identifies impacts. Validation tests whether the impacts you documented are accurate, complete enough to use, and scored for the right reasons.

Validate the Facts

  • Is the Current State accurate?
  • Is the Future State accurate?
  • Is the affected Role/Team correct?
  • Have we combined groups that actually experience the change differently?
  • Is anyone affected who is currently missing?
  • Does the Impact Description describe the actual change?
  • Is the timing correct?
  • Is the estimated number impacted reasonable?

Validate the Ratings and Open Items

  • Is the Impact Type appropriate?
  • Does the Severity rating match the actual degree of change?
  • Does the Business Criticality rating match the consequence of disruption?
  • Which assumptions still need to be confirmed?
  • What would cause this impact or rating to change?
  • Is anything in this record based on an unresolved decision?
  • What are we missing?
When reviewers disagree: First check whether they actually disagree about the underlying facts. A scoring disagreement often hides a different understanding of the Current State, Future State, affected group, timing, or consequence.
Preview of the Essential Change Impact Assessment Questions page from the printable question bank PDF
Printable PDF

Keep the Full Question Bank Handy

Get the printable PDF version with the complete question bank, checkboxes, and working notes pages so you can use it during interviews, workshops, and assessment reviews.

CIA Question Bank Download

Frequently Asked Questions

What questions should I ask in a Change Impact Assessment?

Start with what is changing, the Current State and Future State, who is affected, when the impact occurs, and how significant and business-critical it is. Then use targeted questions based on the type of impact and what still needs to be understood.

Do I need to ask every question on this page?

No. Use the question bank as a menu. The right questions depend on the initiative, the Roles/Teams affected, the quality of existing information, and what you still need to understand or validate.

Should I ask the same questions to every Role/Team?

Not necessarily. Some core questions should be consistent, but different groups may require different follow-up questions because their systems, responsibilities, timing, customer interactions, controls, or transition conditions differ.

What comes after the Change Impact Assessment questions?

Document the distinct impacts, assess Impact Severity and Business Criticality, validate the findings, analyze where consequential change concentrates, and then use those findings to guide downstream work such as communication, learning, manager support, readiness, implementation, and resourcing. The full CIA how-to guide explains that process.

Shopping Cart