Clinical Usability Audit Synthesis to Engineering Leads
Translates clinical workflow usability friction points into prioritized remediation requests via executive email.
Use this template when usability testing reveals dangerous friction in electronic health records or diagnostic software. It drafts a clear, high-priority email to technical leadership outlining immediate and architectural design remedies.
Role: Principal Clinical UX Researcher with 15 years of experience evaluating software safety in acute care environments.
Context
- Target System: {{clinical_system_name}}
- Clinician Persona: {{target_clinician_persona}}
- Usability Audit Findings: {{critical_usability_findings}}
- Patient Safety Risk Tier: {{patient_safety_risk_level}}
- Recipient Engineering Lead: {{engineering_lead_name}}
- Proposed Remediation Milestone: {{target_sprint_cycle}}
Task
Draft an authoritative, highly actionable engineering advisory email that synthesizes recent clinical usability findings into immediate UI/UX remediation requirements, mitigating safety risks without delaying deployment milestones.
Method
- Review {{critical_usability_findings}} against cognitive load thresholds for {{target_clinician_persona}} in high-stress clinical workflows.
- Cross-reference identified interface bottlenecks with the safety severity rating in {{patient_safety_risk_level}}.
- Frame the email opener with clinical urgency, addressing {{engineering_lead_name}} with direct context.
- Formulate an executive summary itemizing cognitive friction points and potential error paths in {{clinical_system_name}}.
- Categorize required design modifications into immediate ergonomic fixes and structural component changes.
- Align each proposed UI change to acceptance criteria targeted for {{target_sprint_cycle}}.
- Provide concrete interface interaction patterns that reduce click fatigue and prescription verification error.
- Conclude with validation milestones, including next-round simulated clinical user testing.
Constraints
- The email body MUST remain between 350 and 550 words.
- Technical jargon MUST be translated into concrete user interface specifications.
- MUST NOT recommend clinical workflow changes that violate standard medical charting governance.
- Tone must be collaborative, urgent, and evidence-driven.
Output format
An email composed of:
- Subject Line (urgent and tagged with system identifier)
- Salutation
- Executive Clinical Context (1 paragraph)
- Critical Usability Deficits (3 bullet points)
- Prioritized UI/UX Remediation Matrix (table with columns: Issue, Safety Impact, UI Fix, Target Sprint)
- Next Steps & Sign-off
Self-review
- Does the email clearly explain how each UI defect impacts patient safety?
- Are engineering remediation requests technically specific and scoped to {{target_sprint_cycle}}?
- Is the tone assertive regarding clinical safety while respectful of development velocity?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.