Which approach is recommended when you justify a solution?

Question

Options

• ASupport solutions that can be fully implemented with current capabilities on the IT staff.
• BGive extra weight to projects that give the business unit responsibility for risky activities.
• CBring the IT and business executives together where possible to forge a unified viewpoint.
• DPush investments out to the future, where possible, to delay larger investments.

• A
  2% (1)
• B
  2% (1)
• C
  91% (40)
• D
  5% (2)

Explanation

When justifying a solution, aligning IT and business executives into a shared perspective (C) is critical because it eliminates conflicting priorities, builds organizational commitment, and ensures the solution is evaluated holistically rather than from a single silo - making approval and implementation far more likely to succeed.

• A is wrong because limiting solutions to current IT capabilities stifles innovation and ignores necessary growth; good justification should address capability gaps, not avoid them.
• B is wrong because offloading risky activities to business units is an avoidance tactic, not sound governance - risk should be managed transparently, not shifted.
• D is wrong because deferring investments to delay decisions is poor strategic practice; it can increase costs and missed opportunity windows over time.

Memory tip: Think "C = Convergence" - justifying a solution means converging IT and business onto one unified voice, because executives who agree are far more likely to approve and fund.

No community discussion yet for this question.