Feasibility Study

Origin & evolution

Feasibility analysis grew out of large-scale engineering and information-systems planning, where the cost of a wrong commitment was measured in years and millions. A durable structure from that tradition is the TELOS frame: Technical, Economic, Legal, Operational, and Schedule feasibility, five lenses applied to one opportunity so that no class of risk🎲RiskComplianceA risk to the product or businessView reference → gets ignored. Each dimension evaluates distinct requirements necessary to justify investment, and poorly considered studies are a recognised contributor to project failure, sunk cost, and litigation.

Product practice absorbed the same logic in a lighter form. Marty Cagan's four big risks, set out in Inspired, name feasibility as one of four things that must be true for a product to succeed, alongside value, usability, and business viability. In Cagan's split, feasibility is the engineering question, owned by the lead engineer: can we build this with the time, skills, and technology we have. Business viability, owned by the product manager, carries the economic and legal weight that TELOS bundles in.

The two traditions agree on the core move. Assess buildability and sustainability against named dimensions, early, while changing course is still cheap.

How it works in practice

A team spots an opportunity: real-time collaborative editing inside their canvas product. Before committing a quarter, they run a feasibility study against the TELOS dimensions. Technical: their current data layer is last-write-wins, and conflict-free replicated data types would need🫀NeedUserA user need, pain, desire, or constraintView reference → a six-week spike to prove out, with a real chance of failure. Economic: the feature⭐FeatureProduct SpecificationA product capability or featureView reference → lifts retention in two comparable products by roughly 8%, which clears the cost at their scale. Legal: real-time presence data triggers fresh consent obligations under data-protection rules. Operational: support has no playbook📒PlaybookCustomer SuccessA standard operating procedure for CSView reference → for sync conflicts. Schedule: the spike pushes the dependent roadmap🛣️RoadmapProduct SpecificationA strategic plan of features and milestonesView reference → by two months.

The verdict is "viable with conditions": proceed only if the six-week technical spike succeeds and the consent work is scoped in. The study converts a tempting idea into a gated decision⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference → with a known failure point.

Feasibility study vs. its neighbours

• Opportunity is the upstream thing being assessed: the gap or demand worth pursuing. The feasibility study is the assessment of whether that opportunity can be realised, so the opportunity exists first and the study judges it.
• Test plan📝Test PlanValidationA structured plan for testing a hypothesisView reference → validates whether users want a thing (desirability). A feasibility study judges whether the thing can be built and sustained at all. Desirability and feasibility are different risks, and confirming one says nothing about the other.
• Business case argues that a viable opportunity is worth funding against alternatives. The feasibility study supplies the buildability evidence the business case then weighs against return.

In the graph

In the Unified Product Graph, feasibility_study🏗️Feasibility StudyDiscoveryAn assessment of technical or business viability lives in the discovery region and attaches to its subject through opportunity_assessed_by_feasibility_studyOpportunityassessed byFeasibility Studyhierarchy, a hierarchical edge running from opportunity🚪OpportunityDiscoveryA validated gap worth solvingView reference → to the study that evaluates it. That direction matters: the study is dependent on an opportunity to assess, never free-floating. From there it feeds the entities a real assessment touches, the constraint🔒ConstraintStrategyA constraint entityView reference → nodes it surfaces and the decision⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference → it informs, so the path from a raw opportunity to a go or no-go choice stays connected and auditable rather than living in a slide deck nobody can query later.