Academic Research Computing Support Post-Mortem Report

Role: Senior Academic Research Infrastructure Support Specialist with fifteen years of experience managing high-performance computing helpdesks and laboratory data pipelines.

Context

• Academic Institution: {{institution_name}}
• Department Under Review: {{research_department}}
• Reporting Window: {{ticket_volume_period}}
• Dominant Issue Domain: {{incident_category}}
• Core Computing Environment: {{infrastructure_stack}}
• Primary Research Bottleneck: {{primary_impact_area}}

Task

Synthesize the recurring helpdesk tickets and computing disruptions into a definitive incident post-mortem report that diagnoses technical root causes, quantifies lost research productivity, and outlines preventive support interventions for {{research_department}}.

Method

1. Review the operational telemetry and ticket logs across {{infrastructure_stack}} during {{ticket_volume_period}}.
2. Isolate the primary failure vectors associated with {{incident_category}} affecting lab workflows.
3. Measure operational drag on {{primary_impact_area}} using ticket resolution and wait-time metrics.
4. Map Tier-1 support handoffs to identify where triage protocols delayed technical escalations.
5. Categorize repeat user errors against documentation gaps in researcher onboarding materials.
6. Formulate specific infrastructure configuration fixes to prevent systemic hardware or queue faults.
7. Detail updated support triage playbooks tailored for staff at {{institution_name}}.

Constraints

• Analysis MUST explicitly isolate root causes rather than merely summarizing ticket symptoms.
• Recommendations MUST NOT propose unbudgeted commercial software replacements without justification.
• Every remediation item must specify an assigned support tier and estimated implementation horizon.
• Technical jargon must be translated into clear operational impact statements for academic deans.

Output format

Generate a structured operational report using these exact section headers:

1. Executive Summary (under 150 words)
2. Incident Analysis & Failure Categorization (3-4 analytical paragraphs)
3. Productivity & Timeline Impact Assessment (bulleted metrics)
4. Triage & Support Workflow Gaps (table or structured list)
5. Technical & Operational Remediation Plan (prioritized action items)

Self-review

• Did I directly evaluate {{incident_category}} within the context of {{infrastructure_stack}}?
• Are all remediation actions assigned clear operational ownership?
• Does the report maintain a professional, academic support perspective throughout?