A bank emails every interface flap to executives, and those leaders have started ignoring the mail. How should the executive deliverable change?
Select an answer to reveal the explanation.
Short Explanation
A weather text for every passing cloud can teach you to mute the phone, just as repeated flap alerts train leaders to ignore mail. Give executives an aggregated trend of experience over time; paging them on each flap, relabeling the same per-flap mail for production support, or sending an application object list with every flap keeps the noise.
Full Explanation
Executives who receive a mail for every interface flap learn to ignore the channel, so the executive deliverable should change from per-event alerts to an aggregated trend of experience over time. The trend shows whether experience is drifting without training leaders to discard each message. Keeping executives paged on every flap and attaching operator rule text still sends a message for each event; the added rule text is operator detail, not a solution to an ignored channel. Sending production support the same per-flap mail and calling it the executive view mislabels a support message and preserves the flap-by-flap pattern. Handing executives the application object list for each flap at the moment it happens is also a per-event feed, focused on object detail rather than an executive trend, and continues the interruption that caused them to look away. Exam caveat: aggregation for executives means a readable experience trend, while operators retain live flap information; renaming noisy mail does not make it fit a new audience. Practical check: confirm executive mail presents a periodic experience trend and individual interface flaps go to the operator rotation, not the executive list.