Which step is important when you define pain points for a multidepartment business initiative?

Question

Options

• APrioritize needs and opportunities across the full scope of the departments.
• BAsk each department to rate their priorities on a 1-10 scale of importance.
• CUse a survey to gain feedback on service-level expectations for network infrastructure.
• DAvoid using customer estimates of benefits since the departments are likely overstating value

• A
  80% (20)
• B
  4% (1)
• C
  4% (1)
• D
  12% (3)

Explanation

When defining pain points for a multidepartment business initiative, the critical step is to prioritize needs and opportunities across the full scope of all departments (A), because a multidepartment initiative requires a holistic view - isolated department-level analysis misses cross-functional dependencies and competing priorities that shape the real business problem.

Why the distractors are wrong:

• B is too narrow: a 1–10 rating per department produces siloed rankings without reconciling conflicts or surfacing shared pain across departments.
• C is off-scope: surveying service-level expectations for network infrastructure is a technical/IT activity, not a pain point definition exercise for a broad business initiative.
• D is counterproductive: customer and stakeholder estimates are valuable inputs - dismissing them removes crucial context for understanding perceived value and impact.

Memory tip: Think "multidepartment = multi-view synthesis." The word multi in the question is your cue that the right answer must span the whole organization, making A (full scope prioritization) the only choice that matches the scale of the initiative.

No community discussion yet for this question.