# Assess technical feasibility and dependencies

Evaluates whether and how a feature can be built, plus its risks and dependencies.

- Topic: Product & UX Design
- Framework: RCTFVV
- Level: Advanced
- Tags: Sales, Analyze, Fill-in Template
- Source: https://www.thinkwithprompt.com/prompts/assess-technical-feasibility-and-dependencies

## Prompt

```text
Role: Act as a technical product manager assessing feasibility with engineering input.

Context: The capability proposed and the user outcome: [CAPABILITY_OUTCOME]. Current architecture and relevant systems: [ARCHITECTURE]. Non-functional needs (scale, latency, reliability, security, compliance): [NFRS]. Timeframe and team capacity: [TIMEFRAME_CAPACITY]. Known technical constraints and debt in the area: [CONSTRAINTS_DEBT]. Third parties / platform limits involved: [THIRD_PARTIES].

Goal: Give the product and engineering leads an honest read on feasibility, the main options and what has to be true for it to land in the timeframe.

Task: Produce: (1) 2-3 implementation approaches at a high level, each with rough effort, the NFRs it would meet or strain, and its main technical risk; (2) the dependencies (internal teams, platform work, third parties, data) and their lead times; (3) the unknowns that most affect the estimate and a spike to resolve each; (4) a feasibility verdict for the timeframe (feasible / feasible with scope cut / not feasible) with the reasoning; (5) what scope could be cut to fit.

Constraints: Estimates are ranges with stated assumptions, not points. Do not claim feasibility without naming the dependencies and unknowns that could break it. Flag anything needing a security or compliance review. Be explicit where engineering input is required to firm up the estimate.

Examples: Approach row: 'Approach | Rough effort | NFRs met/strained | Main risk | Key dependency.' Unknown row: 'Unknown: can [system] sustain [X] writes/sec? Spike: load test a prototype, 2 days. Effect if no: approach A is off the table.'

Format: Sections: Approaches (table) | Dependencies & lead times | Unknowns & spikes | Feasibility verdict & reasoning | Scope-cut options. ~650 words.

Verification: List every assumption behind the effort ranges and every dependency without a confirmed lead time.

Validation: Pressure-test the verdict: if the two biggest unknowns resolve badly, is it still feasible? State the fallback and the decision point.
```

## What to fill in

- CAPABILITY_OUTCOME
- ARCHITECTURE
- NFRS
- TIMEFRAME_CAPACITY
- CONSTRAINTS_DEBT
- THIRD_PARTIES
- system

Free to copy and use. From ThinkWithPrompt (https://www.thinkwithprompt.com/), a library of 2,663 curated AI prompts.