The correct answer is that existing and frequently used apps reveal integration opportunities that can make the Slack launch more productive. Discovery is not just a fact-finding exercise; it is how the consultant identifies how work actually happens today and how Slack can improve that work. If employees rely heavily on tools such as Salesforce, Google Drive, Jira, ServiceNow, Zoom, Microsoft 365, or project-management platforms, those systems may become high-value Slack integrations. Bringing core work tools into Slack reduces context switching, improves visibility, and creates practical launch use cases that make Slack immediately useful. Option B is not the best answer because the question asks specifically about the Slack launch experience, not general training on non-Slack apps. Option C is possible in rare cases, but the primary consultant objective is to identify productive integration opportunities. Option D may surface during access discovery, but it is not the main reason to ask about frequently used applications.

Reference topic: Discovery --- current-state analysis, app ecosystem assessment, integration opportunities, launch use cases, and productivity-centered Slack adoption.

==========