When assessing the impact of proposed changes, what should be considered? Response:

Question

Options

• AOnly direct costs
• BImpact on all relevant aspects including products, processes, and systems
• CThe opinions of senior management only
• DThe time taken for implementation

• A
  9% (3)
• B
  82% (27)
• C
  6% (2)
• D
  3% (1)

Explanation

Option B is correct because effective impact assessment requires a holistic view - changes rarely exist in isolation, and their effects ripple across products (what you deliver), processes (how you work), and systems (the tools and infrastructure that support both). Limiting the assessment to any single dimension risks approving changes that create unintended problems elsewhere.

Why the distractors fail:

• A (direct costs only) ignores indirect costs, schedule impacts, quality risks, and downstream effects on other systems.
• C (senior management opinions only) confuses decision authority with assessment scope; subject matter experts closest to affected areas often provide the most accurate impact data.
• D (implementation time only) is just one input among many - a change could be quick to implement yet have severe quality or compatibility consequences.

Memory tip: Think of impact assessment as a "blast radius" check - you need to know everything within range of the explosion, not just the cost of the dynamite.

No community discussion yet for this question.