Two mid-level marketing managers have decision authority for a new reporting system. Which approach can identify a reliable view of requirements for this solution?

Question

Options

• AAsk a senior marketing leader to identify their top three projects to increase market demand.
• BAsk each manager to identify their top three ideas to improve employee satisfaction.
• CConduct individual and joint interviews with the managers and run through several scenarios
• DCapture data on sales force productivity and document trends for marketing managers to

• A
  7% (3)
• B
  13% (6)
• C
  54% (25)
• D
  26% (12)

Explanation

Conducting individual and joint interviews with the decision-authority managers - combined with scenario walkthroughs - is the gold standard for eliciting reliable requirements because it surfaces both personal priorities and areas of agreement or conflict between stakeholders who share ownership of the solution.

Why the distractors fail:

• A escalates to a senior leader who lacks decision authority for this system, introducing requirements that may not reflect actual needs.
• B targets employee satisfaction, which is irrelevant to a reporting system's functional requirements.
• D focuses on documenting sales productivity trends - useful analytics, but not a requirements-gathering technique; it bypasses the stakeholders entirely.

Memory tip: When two stakeholders share decision authority, you need both individual input (to capture each perspective honestly) and joint sessions (to reconcile differences) - the word "individual and joint" in option C is the signal that you're engaging all decision-makers directly, which is always the right move in requirements elicitation.

No community discussion yet for this question.