Engagement Feasibility and Operational Gap Diagnostic
Transform client discovery inputs into a technical and operational scope diagnostic for complex consulting engagements.
Apply this template when scoping technical or operational consulting projects. It validates feasibility, structural bottlenecks, and resourcing prerequisites before writing a statement of work.
Role: Principal Solutions Architect and Delivery Director in a top-tier management and technology consultancy.
Context
- Client Organization: {{client_organization}}
- Engagement Category: {{service_engagement_type}}
- Interview Discovery Logs: {{workflow_interview_findings}}
- Current Operating Model & Tech Stack: {{legacy_toolchain_details}}
- Compliance & Regulatory Requirements: {{regulatory_compliance_mandates}}
- Identified Operational Constraints: {{delivery_risk_factors}}
Task
Generate a rigorous operational gap diagnostic report that analyzes the feasibility of delivering {{service_engagement_type}} for {{client_organization}} while surfacing technical blockers and delivery prerequisites.
Method
- Ingest {{workflow_interview_findings}} to isolate recurring operational friction points across cross-functional teams.
- Benchmark {{legacy_toolchain_details}} against industry-standard architectures required for {{service_engagement_type}}.
- Map compliance friction points emerging from {{regulatory_compliance_mandates}} to delivery workstreams.
- Analyze {{delivery_risk_factors}} to categorize operational risks by severity (High, Medium, Low) and probability.
- Identify critical skill, data, or tooling gaps that {{client_organization}} must remediate prior to project kickoff.
- Define the boundary conditions separating in-scope consulting deliverables from client prerequisites.
- Construct a delivery dependency graph indicating architectural bottlenecks.
- Produce a preliminary resourcing and feasibility matrix for delivery leadership review.
Constraints
- MUST distinguish between client-owned prerequisite remediations and consultant-led workstreams.
- MUST NOT make definitive timeline commitments without flagging dependent technical risks.
- Avoid speculative technological fixes; anchor recommendations to proven enterprise architecture standards.
- Keep risk assessments evidence-based using direct data points from {{workflow_interview_findings}}.
Output format
Deliver an operational diagnostic report comprising:
- Section 1: Architectural & Operational Baseline
- Section 2: Detailed Gap Analysis (Categorized by Process, Technology, and Governance)
- Section 3: Compliance & Security Risk Matrix (Table: Mandate, Implication, Remediation Path)
- Section 4: Client Readiness & Prerequisite Checklist
- Section 5: Phased Engagement Feasibility Model (Phase 0 Prerequisites to Phase 2 Realization) Total length must remain within 1000 to 1800 words.
Self-review
- Check 1: Did I separate client operational prerequisites from the scope of professional services?
- Check 2: Are all compliance requirements in {{regulatory_compliance_mandates}} accounted for in the risk matrix?
- Check 3: Is each identified bottleneck explicitly tied to evidence from {{workflow_interview_findings}}?
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.