| name | role-csa |
| description | CSA role card — architecture-focused execution owner. Covers technical proof oversight, guardrail enforcement, value-realization validation, and CSA-vs-CSAM authority boundaries. Triggers: CSA, Cloud Solution Architect, architecture handoff, delivery ownership, execution readiness, architecture feasibility. |
Role Card: Cloud Solution Architect (CSA)
Mission
Own the customer technical success path — ensure committed opportunities are executable, measurable, and progressing to outcomes using MSX as the system of record.
MCEM Stage Accountability
| Stage | Role |
|---|
| Stages 1–3 | Contribute — architecture direction, feasibility assessment, technical risk management |
| Stage 4 | Lead execution readiness — drive value realization plans, partner with CSAM |
| Stage 5 | Lead optimization — maintain solution health, identify expansion pathways |
Ownership Scope in MSX
- Committed milestones: correct owners, realistic dates, accurate risk status, delivery motion captured
- Update fields for planning/forecast and technical execution
Hygiene Cadence
- Weekly: review committed milestones due in next 30–60 days
- Monthly: confirm stage alignment and that execution evidence exists
Boundary Rules
- CSA is responsible for execution readiness and technical integrity, not day-to-day delivery PM.
- CSA is NOT responsible for partner staffing, dispatch operations, or commercial ownership.
- Stages 1–3: Require CSA execution-readiness confirmation before commitment.
- Stage 4: CSA engages for technical decisions and architecture constraints. CSAM leads delivery execution escalations.
- Stage 5: CSA identifies optimization and expansion signals. Specialist/ATU owns conversion to net-new opportunities.
- Owner-motion mismatches (CSA listed as owner while delivery is Partner/ISD/Unified) must be flagged for reassignment.
Cross-Role Skill Lens
| Skill | CSA Focus |
|---|
commit-gate-enforcement | Architectural feasibility, technical delivery risk, environment prerequisites |
se-execution-check | Risk state, dependencies, execution blockers, architecture guardrails, Unified constraints |
mcem-diagnostics | Delivery motion validated, success metrics have baseline + target |
stage-5-review | Capture optimization insight; route to Specialist/ATU |
account-landscape-awareness | Adjacent pipeline for swarming, EDE coverage gaps |
CSA vs CSAM Authority
- CSA: Final authority for technical feasibility and execution integrity
- CSAM: Single point of orchestration and customer expectation management
- Tie-break: Technical disputes → CSA decision. Customer-facing implications → CSAM communicates.
Escalation Triggers
- Committed milestone at-risk/blocked with no recovery plan
- Customer success measures missing or unmeasurable
- Significant scope drift affecting outcomes or timeline
