Custom Engineering · Development Testing and Delivery
Feasibility Assessment
A feasibility assessment is only useful if it can return a no. It should identify the constraint that decides the answer.
Overview
- Test the proposed approach against the hardest constraint first, so the answer comes early.
- Separate technical feasibility from operational and regulatory feasibility; each can independently stop a project.
- State assumptions explicitly, and say what happens to the conclusion if an assumption fails.
- Recommend the smallest trial that would falsify the approach.
Related pages
- Scenario CustomizationView
- Production StrengthView
- Technical StrengthView
- Procurement and Selection GuidesView
More in this area
- Project Requirement DiscoveryRead
- Feasibility AssessmentThis page
- Confirming Scope and DeliverablesRead
- Prototype Development ProcessRead
- Interface and Integration TestingRead
- Field Testing and Data CollectionRead
- AI Performance Acceptance MethodsRead
- Pilot Batch Trial and Issue ClosureRead
- Delivery Training and Operating DocumentationRead
- Maintenance Upgrades and Change ManagementRead