Requirements risk
Signal: Required client inputs were missing.
Response: Created a structured, easy-answer template and held a working session to close the gaps.
Schedule and capacity risk
Signal: The project was three weeks behind with reduced holiday capacity.
Response: Reprioritized business-critical workflows, aligned the developers on release order, and made escalation paths explicit.
User-impact risk
Signal: Quality-of-life work had to follow the core launch.
Response: Kept deferred work visible, created workaround job aids, and provided hands-on support.
Communication rhythmOpening update → decisions and blockers → closing update