Script & Storyboard
Jim’s Misfortune  It’s up to the Lending Department to enter Loan Applications into the company’s Mortgage System.  It’s a process initiated daily by Supervisor Jim. 
Twice each day, at 12 p.m. and at 4 p.m.,  he sends the completed Applications to a third party to be scanned and returned to the lenders.  After that the Lending Department no longer has access to them.  This means that for the Mortgage System the Recovery Point Objective (RPO) is 4 hours. 
If there were a system glitch, the Lending Department could easily recover Applications entered over the last 4 hours.  But suppose there was a massive failure, like if lightning struck at 3 p.m. on Wednesday  and fries the servers housing the Mortgage System. 
No problem you say. The Mortgage System is backed up every midnight, making it a 24-hour back-up cycle.  However, for the IT department to replace the server and restore the backups,  it will take 12 hours (RTO – Recovery Time Objective).  Only then can the recovered Loan Applications be entered into the system.
Here’s the problem. The current RPO of 4 hours is way short of the 24 hour back-up cycle.  If a failure occurs anytime between 4 p.m. and midnight, the entire days Loan Applications will be lost.  If the failure occurs during the day, up to 4 hours worth of Loan Applications could be lost. 
Panic time! The restored Mortgage System is as of Tuesday midnight.  It’s missing all the work that was entered Wednesday.  Since the strike was after 12 p.m., all the morning’s work is gone.  Jim can only recover from noon to 3 p.m.  Jim quickly sees that an RPO of 4 hours is inadequate, but it too late. 
Solution. Either change the back-up cycle to 12 hours: noon & midnight.  Or increase the RPO to 24 hours by holding the Loan Applications until the next day.