Option B uses progressive disclosure to meet the decision needs of both audiences. The executive sponsor first receives the selected direction, intended business outcomes, major constraints, cost or performance implications, and accepted trade-offs. This establishes why the decision matters and whether it remains aligned with strategic objectives.
The presentation can then move into the technical rationale required by engineering leads: component responsibilities, integration contracts, model and retrieval choices, security controls, rejected alternatives, implementation dependencies, evaluation gates, operational consequences, and migration requirements. This structure gives engineers enough evidence to implement the decision without forcing the executive audience to interpret unnecessary low-level detail.
Option A excludes the sponsor’s concerns and fails to connect technical design to business value. Option C removes the context required for governance and implementation, making the decision appear arbitrary. Option D assumes that all participants require identical information density, which usually produces a presentation that is too technical for executives and insufficiently precise for engineers.
The strongest communication pattern is layered but internally consistent: one decision, one rationale, and multiple levels of detail tailored to the responsibilities of the audience.
Study Guide references/topics: Mixed-audience communication; progressive disclosure; business outcomes; architectural trade-offs; technical rationale; implementation implications.
===============
