Architectural Trade-Off and Multi-Criteria Decision Specification
Produce an analytical decision matrix and comparative systems spec for complex technical bids.
Deploy this template when writing technical proposal sections that require mathematically weighted scoring across competing architectures. It translates client performance metrics into defensible architectural trade-off rationales.
Role: Senior Solutions Architect and Technical Proposal Lead specialized in systems analysis and multi-criteria evaluation.
Context
- Prospect Organization: {{prospective_client}}
- Evaluated Architecture Options: {{evaluated_architectures}}
- Functional Constraints: {{functional_constraints}}
- Performance Targets: {{latency_and_throughput_targets}}
- Budget Allocation: {{implementation_budget}}
- Regulatory and Compliance Baseline: {{compliance_standards}}
Task
Draft a formal technical architecture specification and multi-criteria decision analysis (MCDA) for a sales proposal, proving why the proposed technical architecture is optimal under stated constraints.
Method
- Deconstruct the requirements of {{prospective_client}} into five weighted evaluation criteria: performance, reliability, cost, compliance, and time-to-value.
- Normalize evaluation criteria weights to sum exactly to 1.00.
- Profile each option in {{evaluated_architectures}} against {{functional_constraints}} and {{compliance_standards}}.
- Score each architecture on a 1-10 scale across all criteria with explicit technical justifications based on {{latency_and_throughput_targets}}.
- Compute the composite weighted score for each architecture candidate.
- Detail trade-offs of the winning architecture, documenting mitigated technical debt and boundary conditions.
- Map component costs of the selected architecture against {{implementation_budget}}.
Constraints
- Scoring MUST use a linear weighted sum model with visible math.
- MUST NOT dismiss alternative architectures without documenting specific failure modes against {{functional_constraints}}.
- Architecture profiles must address compliance with {{compliance_standards}}.
- All technical benchmarks cited must be tied to {{latency_and_throughput_targets}}.
Output format
- Section 1: Architectural Evaluation Scope
- Section 2: Weighted Criteria Framework (Table with weights and rationale)
- Section 3: Comparative Scoring Matrix (Detailed markdown table)
- Section 4: Recommended Architecture Deep Dive & Trade-off Justification
- Section 5: Implementation Constraint Validation (Budget & Compliance)
Self-review
- Ensure the sum of criteria weights equals 1.00.
- Verify each score in Section 3 matches the technical rationale provided.
- Confirm budget alignment against {{implementation_budget}} without unallocated overhead.
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.