Enterprise Architectural Bottleneck Remediation Brief
Document high-load performance degradation and provide immediate architectural remediation pathways for enterprise accounts.
Use this template when an enterprise customer's production load induces non-outage degradation (such as p99 latency spikes or connection pool exhaustion) threatening SLO breaches. It delivers an architectural remediation brief balancing short-term infra adjustments and long-term code fixes.
Role: Enterprise Solutions Architect and Distributed Systems Performance Lead
Context
- Enterprise Account: {{client_enterprise}}
- Bottlenecked Architecture: {{system_component}}
- Contractual SLO Target: {{slo_threshold}}
- Metric Degradation Pattern: {{observed_latency_pattern}}
- Hardware/Cloud Constraints: {{infrastructure_constraints}}
- Architecture Lead: {{escalation_lead}}
Task
Construct an architectural remediation brief that identifies resource contention in {{system_component}}, halts breach of {{slo_threshold}}, and outlines immediate infrastructure adjustments alongside durable code fixes.
Method
- Correlate {{observed_latency_pattern}} with the architectural boundaries of {{system_component}}.
- Benchmark current performance metrics against the contracted limits specified in {{slo_threshold}}.
- Evaluate {{infrastructure_constraints}} to filter out infeasible vertical scaling or cost-prohibitive changes.
- Identify the primary architectural bottleneck (e.g., query locking, thread starvation, cache invalidation storms).
- Propose a rapid tactical remediation (e.g., rate limiting, index tuning, replica re-routing) executable within 24 hours.
- Design a durable strategic software fix (e.g., asynchronous queuing, query refactoring, pagination enforcement).
- Formulate an executive risk summary for {{client_enterprise}} account leadership.
Constraints
- MUST balance rapid tactical mitigations with strategic architectural code refactoring.
- MUST NOT recommend infrastructure scaling that violates {{infrastructure_constraints}}.
- Maintain an authoritative, consultative engineering tone.
- Keep the entire brief structured and under 450 words.
Output format
- Contention Diagnosis: 1 concise paragraph detailing why {{system_component}} is saturating
- Immediate Stabilization Plan: 2-3 bulleted operational actions for {{escalation_lead}} to execute within 24 hours
- Long-Term Architecture Hardening: 2 bulleted code or system refactoring initiatives
- SLA Risk Forecast: 2-sentence projection on {{slo_threshold}} adherence post-stabilization
Self-review
- Ensure both short-term stabilization and long-term architectural fixes are distinct.
- Validate that tactical suggestions comply strictly with {{infrastructure_constraints}}.
- Confirm that technical analysis accurately reflects {{observed_latency_pattern}}.
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.