You are tasked with creating critical user documentation for a product launch in 24 hours, but the lead developer, the primary SME, is unexpectedly out sick. How do you leverage your existing resources and problem-solving skills to deliver accurate and complete documentation under this extreme time constraint?

Leverage a MECE (Mutually Exclusive, Collectively Exhaustive) framework for documentation delivery. First, identify all existing documentation: design specs, API docs, previous release notes, internal wikis, and code comments. Second, prioritize critical user-facing sections based on product functionality and user impact. Third, delegate non-critical sections to available team members (QA, other developers, product managers) for review and initial drafting, providing clear templates. Fourth, utilize internal communication channels (Slack, Teams) for rapid-fire questions to secondary SMEs or developers familiar with specific modules. Fifth, implement a rapid review cycle with available stakeholders, focusing on accuracy and clarity. Finally, publish a minimum viable documentation set, clearly labeling any known gaps for immediate post-launch iteration.

Under such extreme time constraints, I'd immediately implement a rapid-response strategy, leveraging a combination of the MECE framework for content identification and a modified Agile approach for execution. My first step would be to exhaustively gather all existing internal resources: design documents, API specifications, JIRA tickets, previous sprint reviews, and even code comments. Concurrently, I'd identify secondary SMEs – QA engineers, product managers, or even other developers who worked on related modules – for targeted, rapid-fire questions via synchronous communication channels like Slack or Teams. I would prioritize user-facing documentation based on critical path features, ensuring core functionality is covered. For non-critical sections, I'd draft based on available information and clearly flag them for post-launch refinement. I'd then conduct an expedited review with any available stakeholder, focusing on accuracy and clarity for the most impactful sections. The goal is to deliver a high-quality, minimum viable documentation set on time, with a clear plan for immediate post-launch iteration to address any remaining gaps.