Solution Architecture Positioning Matrix
Transform complex architectural workflows into stakeholder-specific technical value propositions.
Use this template when authoring technical whitepapers, RFP responses, or solution briefs that must address multiple executive and technical buyer roles simultaneously without losing architectural rigor.
Role: Lead Technical Documentation Strategist and Enterprise GTM Solutions Architect.
Context
- Solution Architecture: {{solution_architecture}}
- Enterprise Market Segment: {{enterprise_segment}}
- Primary Stakeholder Roles: {{primary_stakeholder_roles}}
- Strategic ROI Metrics: {{strategic_roi_metrics}}
- Mandatory Compliance Standards: {{compliance_standards}}
- Target Implementation Timeframe: {{implementation_timeframe}}
Task
Construct a comprehensive solution positioning matrix that translates complex architectural documentation into targeted technical narratives across executive, operational, and security buying committees.
Method
- Map the underlying components of {{solution_architecture}} across infrastructure, application, and data layers.
- Dissect the functional needs and risk profiles for each role in {{primary_stakeholder_roles}} within {{enterprise_segment}}.
- Align technical mechanisms to measurable business impact defined in {{strategic_roi_metrics}}.
- Integrate governance and audit safeguards required by {{compliance_standards}} into architecture narratives.
- Address deployment velocity and operational milestones tied to {{implementation_timeframe}}.
- Formulate precise technical positioning statements tailored to each persona's review criteria.
- Draft architectural verification points supporting each claim to prevent technical scrutiny fallout.
Constraints
- MUST structure the primary deliverable as a multi-stakeholder markdown positioning matrix.
- MUST NOT omit compliance validations for {{compliance_standards}} in any persona row.
- Technical claims MUST explicitly reference components from {{solution_architecture}}.
- Descriptions must balance architectural depth with strategic business justification.
Output format
1. Solution Architecture Overview
Concise architectural thesis contextualizing the technical framework for {{enterprise_segment}} (100-150 words).
2. Multi-Stakeholder Positioning Matrix
A markdown table with 5 columns: Stakeholder Role, Primary Technical Priority, Architectural Capability, ROI & Compliance Impact, and Key Narrative Hook.
3. Implementation Narrative Schedule
A 3-phase technical delivery outline aligned with {{implementation_timeframe}}.
Self-review
- Are all personas from {{primary_stakeholder_roles}} represented in the matrix?
- Does the matrix incorporate {{compliance_standards}} and {{strategic_roi_metrics}}?
- Is the architecture described accurately without vague marketing fluff?
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.