Which approach should be used to decide solution interdependencies?

Question

Options

• ABased on technical staff availability,within the IT organization
• BBy the IT executive team,as part of quarterly planning activities
• CJointly,by IT and business leaders,during the 3rd phase of Transformative Networking
• DBased on business leader preferences and decisions,since they typically have the most influence

• A
  9% (4)
• B
  16% (7)
• C
  70% (31)
• D
  5% (2)

Explanation

Option C is correct because solution interdependencies affect both technical feasibility and business outcomes - neither group alone has the full picture. The 3rd phase of Transformative Networking is specifically designed for this collaborative alignment, ensuring that interdependencies are evaluated with both technical rigor and business context simultaneously.

Why the distractors are wrong:

• A is wrong because basing decisions solely on staff availability is a resource constraint, not a strategic approach - it subordinates business needs to internal IT capacity.
• B is wrong because quarterly executive planning is too infrequent and too high-level to properly address the technical nuances of solution interdependencies.
• D is wrong because business leaders, while influential, typically lack the technical depth to fully assess how solutions depend on or affect one another; unilateral business decisions here risk technically unworkable outcomes.

Memory tip: Think "interdependencies = intersection" - where IT and business intersect, decisions should be made jointly. The number 3 in "3rd phase" can remind you it takes both sides working together (two parties + one shared decision = the third element).

No community discussion yet for this question.