How do you analyze the impact of an architectural change?

Question

IT Interview Practice · Accepted Answer

Analyze a change by tracing its effects through **requirements, contracts, data and operational dependencies**. Start with the exact difference between the old and new requirement; “support more scale” or “make it real time” is too vague to assess safely.

## Follow the dependency graph

```text
[Changed requirement] --> [Affected business flow]
                                  |
                         [Interface contracts]
                           /              \
                    [Consumers]       [Data/state]
                           \              /
                       [Operations + tests]
```

Use traceability records and the interface catalog as a starting point, then validate them against deployed configuration, actual traffic and system-owner knowledge. Documentation may miss batch jobs, exports or consumers owned by another team.

## Example: faster stock visibility

Suppose the original agreement refreshed stock hourly, and the proposed requirement is visibility within one minute. Clarify whether that applies during outages and whether users need an estimate or an authoritative reservation.

Inspect the ERP’s ability to publish changes, downstream API quotas, cache lifetimes, freshness indicators and reporting assumptions. If the source updates only hourly, changing the portal’s refresh interval cannot meet the requirement. The analysis may conclude that the source capability or the business target must change.

## Produce an actionable assessment

- List affected components and owners, including indirect consumers.
- Separate compatible changes from contract or data-model changes requiring coordinated rollout.
- Identify evidence invalidated by the change, such as previous load tests or recovery estimates.
- Propose experiments for unknowns, with decision criteria rather than optimistic guesses.
- Define migration, rollout and rollback steps, including what happens to data written in the new format.

Rollback deserves special attention: reverting application code does not necessarily undo a data transformation or an external side effect. If reverse migration is unsafe, describe a forward-recovery plan and its operational cost.

## Interview signal

Present alternatives, effort ranges with assumptions and the business consequence of each choice. A strong architect can explain why the requested outcome needs a broader change, and can offer a smaller feasible outcome with explicit limits.

Follow the dependency graph

Example: faster stock visibility

Produce an actionable assessment

Interview signal

Related questions