A rapid surge in new user onboarding places increased load on a production platform. While no major outages have occurred, the IT Operations Manager…

A weekly cadence is the most appropriate for this scenario. It establishes a regular, predictable rhythm for operational review that is frequent enough to catch and address "recurring defects" and "early warning indicators" before they accumulate into a major incident. This allows for "timely corrective action." It avoids the high operational load of daily reviews, which can become tactical incident management, and the long delay of monthly or quarterly reviews, which would be too slow to proactively manage emerging stability risks on a production platform.

A. Daily: This cadence is often too granular for trend analysis and risks becoming reactive incident management, which the manager wants to avoid.
C. Monthly: This is likely too infrequent to act on "early warning indicators" in a timely manner, allowing minor issues to escalate.
D. Quarterly: This is a strategic planning cadence and is completely unsuitable for managing day-to-day operational health and stability.

1. Beyer, B., Jones, C., Petoff, J., & Murphy, N. R. (2016). Site Reliability Engineering: How Google Runs Production Systems. O'Reilly Media. Chapter 3, "Embracing Risk," discusses the use of error budgets, which are often reviewed on a weekly or monthly basis to balance reliability with innovation, making weekly a common operational cadence.

2. Carnegie Mellon University, Software Engineering Institute (SEI). (2011). The CERT Resilience Management Model (CMU/SEI-2011-TR-012). The model emphasizes periodic monitoring and review of operational performance. For active production systems, a weekly review of key metrics and incidents is a standard practice to ensure ongoing resilience.