On stadium event days, operators need the live alert rule and executives need the experience trend, yet both groups were sent one identical packet. What should be delivered instead?
Select an answer to reveal the explanation.
Short Explanation
You do not put the same memo in the control-room inbox and the board book. Give operators the alert rule and give executives the experience trend, each in its own pack. A support ticket log, an object breakdown sent to both groups, or one shared paging mail erases the split those two jobs need.
Full Explanation
Operators and executives are doing different jobs on event day. Operators need the live alert rule so they can see what fires, and executives need the experience trend so they can see how the event is going, and sending both groups one identical packet fails both jobs. The replacement is separate packs, with the alert rule for operators and the trend for executives. The production-support ticket log used in place of both the rule and the trend serves a desk that is working tickets, and it removes the rule from operators and the trend from executives. The application object breakdown sent to operators and executives alike is an application-team artifact, and sending that one breakdown to both named audiences repeats the mistake of one shared pack. One combined paging mail that operators and executives both receive all day is the same packet again, and it trains leaders to live in operator noise while operators lose a distinct rule view. Exam caveat: when two audiences have different needs, one blended deliverable is the trap. Operational check: confirm the operator distribution contains the alert rule and the executive distribution contains the experience trend, and that event-day paging is not a single mail to both lists.