Create a 2–3 minute explainer video titled ‘Modernizing Database Restore Workflows – Why Change Was Needed’. Start with a visual title screen. Then show a visual of RFMS and Augmento DBA teams coordinating through Zendesk tickets to restore databases to an Azure SQL Managed Instance. Illustrate manual steps like downloading .bak files from the Admin Portal, uploading them to Azure Blob Storage, and triggering restore scripts. Highlight common problems: filename mismatches, manual effort, shift overlaps, and communication delays. Use a timeline to emphasize how a task that technically takes 10–15 minutes can stretch to several hours or a full day. Depict the stress on DBAs and support teams, along with the impact on client delivery. Conclude with a smooth transition scene that teases the new solution—a custom-built internal Upload UI that will streamline and automate this entire workflow. Maintain a tone that is professional, empathetic, and focused on operational improvement and client value." Narration Script Explanation for Stakeholders Scene Breakdown & Intent Scene 1: Title Slide (5 sec) “Modernizing Database Restore Workflows – Why Change Was Needed” Purpose: Immediately communicates that this is about solving a current inefficiency with a better process. Scene 2: Current Workflow (15 sec) “Restoring a client database to our Azure SQL Managed Instance used to be a collaborative—but tedious—process involving the RFMS and Augmento DBA teams.” Visual: Zendesk tickets, chats between teams, and team logos/icons interacting. Scene 3: Problems Overview (20 sec) “Even though the actual database restore takes 10–15 minutes, the overall process could span hours or even an entire day. Why?” Missing or mismatched file names Manual upload/download steps Shift overlaps and time zone differences Repeated follow-ups and communication loops Visual: A horizontal timeline showing delays building up with icons for each issue. Scene 4: Manual Flow (20 sec) “RFMS lacked Azure access, so they relied on Zendesk tickets and manual downloads. The DBA team then downloaded, uploaded, and restored each backup—often working blind due to inconsistent information.” Visual: Flow from RFMS user -> Admin Portal -> DBA -> Azure Blob -> SQL Restore. Scene 5: Impact (15 sec) “This manual, error-prone process slowed down ticket resolution, burdened our DBA team, and delayed critical support for our clients.” Visual: Clock ticking, stressed DBA, paused ticket screen. Scene 6: Transition Tease (10–15 sec) “To solve these inefficiencies, we built something better: an internal Upload UI.” Visual: Fade into a clean UI screen with file upload, Azure blob icon, and a “Restore DB” button glowing. dont overlap the texts in video