What is Investigate Science Fiction?

The best sci-fi writers are often accidental prophets. They imagine technologies that don't exist yet but solve real problems. Your job is to make those imaginary solutions real.

Which companies use Investigate Science Fiction?

Companies that exemplify the Investigate Science Fiction framework include Bitcoin - Predicted by Bruce Sterling in Heavy Weather in 1994, Google Earth - Predicted by Neal Stephenson in Snow Crash in 1992, The Metaverse - Predicted by Neal Stephenson in Snow Crash in 1992.

How do you use Investigate Science Fiction?

To apply Investigate Science Fiction, start by understanding the key components of the framework and mapping them to your specific business context. The framework works best when used systematically as part of a broader strategic analysis.

When should you use Investigate Science Fiction?

Investigate Science Fiction is most useful when evaluating strategic options, analysing competitive dynamics, or making resource allocation decisions. It provides structure to what might otherwise be an intuitive or ad-hoc process.

Investigate Science Fiction…

Investigate Science Fiction… | Faster Than Normal

Science fiction as strategic intelligence. This framework treats speculative fiction not as entertainment but as a structured repository of technology predictions — many authored by writers with deep scientific literacy — and systematically mines those predictions for commercially viable product ideas whose demand has been pre-validated by decades of cultural imagination.

Section 1

How It Works

The core insight is deceptively simple: science fiction writers are running thought experiments about human needs, and the best ones get the technology directionally right decades before engineers do. Arthur C. Clarke described geostationary communication satellites in 1945 — seventeen years before Telstar. Neal Stephenson described a persistent, avatar-based virtual world in 1992 — three decades before Meta bet $36 billion trying to build one. William Gibson coined "cyberspace" in 1984, a decade before the commercial internet existed. These weren't lucky guesses. They were rigorous extrapolations from existing science, filtered through a deep understanding of what humans actually want.

The framework works because science fiction performs two functions that are extraordinarily expensive to replicate through conventional market research. First, it validates demand at the level of human desire. When millions of readers respond to a fictional technology — when the idea of a Star Trek communicator or a Snow Crash metaverse captures the cultural imagination — that's signal. It means the underlying need is real, even if the implementation doesn't exist yet. Second, it stress-tests the concept across edge cases. Good sci-fi writers don't just describe a technology; they explore its second-order effects, its failure modes, its social consequences. Reading the fiction gives you a richer understanding of the design space than any product brief.

The practical mechanism is pattern-matching across three dimensions: the fictional technology, the current state of enabling science, and the commercial gap between what people want and what currently exists. When all three align — when a technology that has lived in the cultural imagination for decades suddenly becomes scientifically feasible, and no one has built the commercial version yet — you have an opportunity with pre-built demand and a head start on product intuition.

"The future is already here — it's just not very evenly distributed."
— William Gibson, NPR Interview, 1999

This is not about building jetpacks or teleporters. It's about recognizing that the smartphone in your pocket was a Star Trek tricorder, that earbuds were Fahrenheit 451's "thimble radios," and that someone who read those books carefully in 1990 could have started building toward those products a decade before the market arrived.

Section 2

When to Use This Framework

✓

Best Conditions for the Investigate Science Fiction Framework

Dimension	Ideal conditions
Founder profile	Technically literate builders who read widely. You need enough scientific fluency to evaluate whether a fictional technology is approaching feasibility, and enough product instinct to identify the commercial wedge. Deep-tech founders, hardware engineers, and biotech operators are natural fits. Pure business operators will struggle unless paired with a technical co-founder.
Stage	Pre-ideation and early R&D. This framework is strongest when you're choosing what to build — scanning for the next wave rather than optimizing an existing product. It can also inform long-range product roadmaps at growth-stage companies exploring adjacent categories.
Market conditions	Best when enabling technologies are reaching inflection points — when costs are dropping exponentially (compute, sensors, gene sequencing) or when regulatory barriers are falling. The fictional technology becomes buildable before the market realizes it.
Competitive environment	Ideal when incumbents are focused on incremental improvement and the fictional concept represents a category jump. The more "impossible" the idea still seems to conventional operators, the wider your window.
Inputs needed	A curated reading list of hard sci-fi (Stephenson, Clarke, Asimov, Banks, Vinge, Liu Cixin). ArXiv and Google Scholar for tracking enabling research. Patent databases (Google Patents, USPTO) for early-stage commercial activity. Technology readiness level (TRL) assessments for key enabling components.

The framework is unusually fertile right now because of the convergence of several enabling technology curves. Large language models have made conversational AI — a staple of science fiction since HAL 9000 — commercially viable. Brain-computer interfaces, predicted by Gibson and Stephenson, are being commercialized by Neuralink and Synchron. Synthetic biology is approaching the programmable organisms described in Greg Bear's Blood Music. The gap between "science fiction" and "science fact" has never been narrower, which means the opportunity set for this framework has never been larger.

Section 3

When It Misleads

⚠

Failure Modes & Blind Spots

Blind spot	What goes wrong
The "cool technology" trap	You fall in love with the fictional concept rather than the underlying human need. Flying cars are a perennial sci-fi staple, but the actual need — fast urban transit — is better served by autonomous vehicles and improved public transport. The fiction points to the need; it doesn't always point to the right solution.
Timing miscalibration	The technology is still 15 years away from feasibility, but the fiction makes it feel imminent. Virtual reality headsets appeared in sci-fi in the 1980s; the first commercially viable consumer VR (Oculus Rift) didn't ship until 2016, and even then the market took years to develop. Being too early is indistinguishable from being wrong.
Dystopian signal ignored	The fiction explicitly warns against the technology, but you build it anyway without addressing the concerns. Facial recognition, pervasive surveillance, and social credit systems all appeared in dystopian fiction as cautionary tales. Building the technology without solving the ethical problems the fiction identified leads to regulatory backlash and public rejection.
Narrative bias	Sci-fi overrepresents certain categories (space travel, AI, virtual worlds) and underrepresents others (logistics, agriculture, sanitation). If you only look where fiction points, you'll miss enormous opportunities in unglamorous domains that no novelist bothered to dramatize.

The single most common mistake is confusing cultural fascination with commercial demand. Millions of people are fascinated by time travel, teleportation, and faster-than-light travel. That fascination does not constitute a market. The framework works when the fictional technology solves a problem people already spend money on — communication, transportation, health, entertainment — not when it solves a problem that only exists in the narrative. The question is never "Is this cool?" It's "What existing budget line does this replace or expand?"

Section 4

Step-by-Step Process

Step 1 — Read

Build a structured sci-fi intelligence library

Don't read randomly. Focus on hard science fiction — authors who extrapolate from real physics, biology, and computer science rather than inventing magic. Prioritize Neal Stephenson, Arthur C. Clarke, Vernor Vinge, Liu Cixin, Kim Stanley Robinson, and Iain M. Banks. As you read, maintain a running log of fictional technologies with columns for: the technology described, the human need it serves, the enabling science required, and your estimate of current feasibility. Technovelgy.com catalogs over 3,400 sci-fi inventions mapped to real-world implementations — use it as a starting index.

Tools: Goodreads lists, MIT Technology Review's sci-fi recommendations, IEEE Spectrum's fiction reviews, Technovelgy.com database

Step 2 — Map

Cross-reference fiction against current science

For each promising fictional technology in your log, search for the enabling research. Is anyone publishing papers on the underlying science? Are there patents being filed? Has the technology appeared on Gartner's Hype Cycle or MIT's annual breakthrough list? You're looking for the convergence point: a fictional concept that has moved from "physically impossible" to "scientifically demonstrated in a lab" to "approaching commercial feasibility." Rate each concept on a Technology Readiness Level (TRL) scale of 1–9. Focus your energy on concepts at TRL 4–6 — proven in lab, approaching prototype.

Tools: ArXiv, Google Scholar, Google Patents, Gartner Hype Cycle, MIT Technology Review's 10 Breakthrough Technologies list

Step 3 — Extract

Identify the commercial wedge

The fictional technology is rarely the product. Your job is to find the first commercially viable slice. The Star Trek communicator wasn't built as a communicator — it was built as a mobile phone, then a smartphone, then a pocket computer. Ask: What is the simplest version of this fictional technology that solves a real problem people currently pay to solve? Who is the first customer? What existing product or service does it replace? Build a one-page business case: problem, solution, customer, market size, competitive landscape, and the specific enabling technology that makes this buildable now.

Tools: Market sizing frameworks, competitive landscape mapping, customer interview scripts, Jobs-to-Be-Done analysis

Step 4 — Validate

Test the concept against real demand

Before building anything, validate that the demand you've inferred from fiction actually exists in the market. Create a concept video or landing page describing the product in concrete terms — not as "inspired by sci-fi" but as a solution to a specific problem. Run it past 30+ potential customers. If the concept requires deep-tech R&D, talk to 10+ domain experts to pressure-test your feasibility assumptions. The goal is to separate genuine market pull from your own enthusiasm for the fictional source material.

Tools: Landing pages, concept videos, expert interviews, pre-order campaigns, Kickstarter/Indiegogo

Step 5 — Build

Prototype the minimum viable version of the fictional concept

Build the smallest possible version that demonstrates the core value proposition. This is almost never the full fictional technology — it's the first useful slice. Focus on the interaction model the fiction described (voice interface, gesture control, ambient computing) rather than the full capability set. If the technology requires significant R&D, consider partnering with a university lab or applying for government innovation grants (DARPA, NSF, Horizon Europe) to fund the pre-commercial phase.

Tools: Rapid prototyping platforms, 3D printing, no-code tools, university lab partnerships, SBIR/STTR grants for deep-tech

Section 5

Questions to Ask Yourself

Discovery

Which fictional technologies from the last 50 years have I seen move from "impossible" to "almost feasible" in the last 5 years?

What human need does this fictional technology serve — and how do people currently solve that need with existing, inferior tools?

Is the enabling science at TRL 4+ (lab-proven), or am I projecting feasibility based on narrative excitement?

Has any serious researcher or company filed patents in this space in the last 3 years?

Validation

Can I describe this product to a non-sci-fi reader in one sentence without referencing the fictional source — and have them immediately understand the value?

What existing budget line (consumer or enterprise) would this product replace or expand?

Have I identified at least one customer segment willing to pay for a V1 that delivers 20% of the fictional capability?

Did the fiction also describe failure modes or social consequences I need to design around?

Feasibility

What is the single hardest technical problem between here and a working prototype — and do I have a credible path to solving it?

Is the cost curve of the enabling technology declining fast enough that my product becomes affordable within my funding runway?

Am I building toward a product that can ship in 2–3 years, or am I funding a 10-year research program disguised as a startup?

Risk

If this technology works, will regulators embrace it, tolerate it, or ban it — and what does the fiction suggest about public reaction?

Is a well-funded incumbent (Google, Apple, Meta) already pursuing this concept with 100x my resources?

Am I in love with the fictional vision, or have I honestly evaluated whether the market wants this?

Section 6

Company Examples

Section 7

Adjacent Frameworks

Science fiction intelligence doesn't operate in isolation. Here's how it connects to the broader strategic toolkit:

Pairs well with

Spot the fringes — what are nerds doing on weekends

Sci-fi readers and makers are often the same people. The hobbyist building a fictional technology in their garage is the leading indicator that the concept is approaching feasibility. Combine both frameworks to triangulate timing.

Pairs well with

Industry timing arbitrage

Fiction tells you what to build; timing arbitrage tells you when. A concept from a 1990s novel might only become viable when a specific enabling technology (LLMs, cheap sensors, CRISPR) crosses a cost threshold. Use timing arbitrage to identify the trigger.

In tension with

Focus on what won't change

Bezos's framework asks what human needs are permanent. Sci-fi investigation asks what new capabilities are emerging. The tension is productive: the best sci-fi-inspired products serve permanent needs (communication, health, knowledge) with radically new implementations.

In tension with

Build a Copycat

Copycat says replicate what's proven. Sci-fi investigation says build what doesn't exist yet. They're fundamentally different risk profiles — one de-risks through imitation, the other accepts higher risk for category-defining upside.

Section 8

Analyst's Take

Faster Than Normal — Editorial View

Let me be direct about something most people get wrong about this framework: it is not about reading sci-fi and getting inspired. Inspiration is cheap. The framework works when you treat science fiction as a structured dataset of technology predictions and apply the same rigor to it that you'd apply to a market research report.

The reason this approach has an edge is that almost no one in venture capital or product development is systematically doing it. VCs read pitch decks, not novels. Product managers read user research, not Vernor Vinge. This creates an information asymmetry: the insights embedded in decades of hard science fiction — insights about interaction models, failure modes, social adoption patterns, and second-order consequences — are sitting in plain sight, unread by the people making billion-dollar technology bets. Meta spent $36 billion on the metaverse without apparently reading the part of Snow Crash where the metaverse is a symptom of civilizational collapse, not a cause of human flourishing.

The founders I see using this framework well share a specific trait: they read the fiction for the problems, not the solutions. The fictional technology is a pointer to a human need. The actual product you build may look nothing like the fictional version. Star Trek's universal translator pointed to the need for real-time cross-language communication; the actual product was Google Translate, then real-time earpiece translation from companies like Timekettle. The form factor changed completely. The need was exactly right.

The biggest risk is timing. Science fiction is structurally biased toward technologies that are 20–50 years away. If you're building a startup, you need the technology to be 2–5 years away. The discipline is in the filtering: reading broadly but investing narrowly, only in concepts where the enabling science has crossed from theoretical to demonstrated. The sweet spot is a fictional technology that felt impossible 10 years ago, plausible 3 years ago, and buildable today. If you can find that convergence point before the market recognizes it, you have a genuine first-mover advantage backed by decades of pre-built cultural demand.

One more thing worth noting: the best sci-fi doesn't just predict technologies — it predicts the resistance to those technologies. Asimov's robot stories are fundamentally about human anxiety around automation. Gibson's cyberspace novels are about the social stratification that digital technology creates. If you're building a sci-fi-inspired product and you haven't read the fiction's warnings alongside its predictions, you're building with half the blueprint.

Section 9

Opportunity Checklist

Use this scorecard to evaluate whether a specific sci-fi-inspired concept is worth pursuing commercially. Score each item as yes (1 point) or no (0 points).

Sci-Fi to Startup Scorecard

The fictional technology serves a human need that people currently spend money to address with inferior solutions.

The enabling science is at TRL 4+ (demonstrated in lab conditions, approaching prototype stage).

The cost curve of the key enabling technology is declining at 20%+ per year.

I can describe the product to a non-technical person without referencing the fictional source and they immediately understand the value.

No well-funded incumbent has publicly committed to building this specific product in the next 2 years.

I can identify a first customer segment willing to pay for a V1 that delivers a fraction of the full fictional capability.

The fiction also described failure modes or social consequences, and I have a plan to address them.

At least one peer-reviewed paper in the last 3 years demonstrates a key breakthrough in the enabling technology.

Section 10

Top Resources

Zero to One — Peter Thiel (2014)

Book

Thiel's core argument — that the most valuable companies create something genuinely new rather than copying what exists — is the philosophical foundation for this framework. His concept of "definite optimism" (having a specific vision of the future and building toward it) maps directly to the practice of extracting product visions from science fiction. Essential reading for anyone attempting to build something that doesn't exist yet.

Seeing What's Next — Clayton Christensen, Scott Anthony & Erik Roth (2004)

Book

Christensen's framework for predicting industry change complements the sci-fi investigation approach. The book provides rigorous tools for evaluating whether a disruptive technology is ready for commercial deployment — exactly the analytical layer you need to apply on top of fictional inspiration. The signals-of-change methodology is directly applicable.

Crossing the Chasm — Geoffrey Moore (1991)

Book

Once you've identified a sci-fi-inspired product concept, Moore's framework for moving from early adopters to mainstream market is indispensable. Sci-fi-inspired products face an acute version of the chasm problem: early adopters love the vision, but mainstream customers need practical utility. This book is the bridge between fictional inspiration and commercial reality.

'Why Software Is Eating the World' — Marc Andreessen (2011)

Essay

Andreessen's thesis that software would transform every industry was itself a prediction that read like science fiction in 2011. The essay demonstrates the analytical method at the heart of this framework: identifying a technology trend that feels speculative to most observers but is actually inevitable based on underlying cost curves and capability improvements. A masterclass in the kind of thinking this framework demands.

Technovelgy.com — Science Fiction Technology Database [VERIFY]

Tool

A comprehensive database cataloging over 3,400 science fiction inventions alongside their real-world implementations. Each entry links the fictional description to the original text, the author, the publication date, and (where applicable) the real technology it predicted. This is the single most useful operational tool for systematically applying the Investigate Science Fiction framework — essentially a searchable index of fictional predictions organized by technology category.

Investigate Science Fiction

Continue exploring

How It Works

When to Use This Framework

Best Conditions for the Investigate Science Fiction Framework

When It Misleads

Failure Modes & Blind Spots

Step-by-Step Process

Build a structured sci-fi intelligence library

Cross-reference fiction against current science

Identify the commercial wedge

Test the concept against real demand

Prototype the minimum viable version of the fictional concept

Questions to Ask Yourself

Company Examples

Adjacent Frameworks

Analyst's Take

Opportunity Checklist

Sci-Fi to Startup Scorecard

Top Resources

This connects to...

Continue exploring

More like this, in your inbox

How It Works

When to Use This Framework

Best Conditions for the Investigate Science Fiction Framework

When It Misleads

Failure Modes & Blind Spots

Step-by-Step Process

Build a structured sci-fi intelligence library

Cross-reference fiction against current science

Identify the commercial wedge

Test the concept against real demand

Prototype the minimum viable version of the fictional concept

Questions to Ask Yourself

Company Examples

Adjacent Frameworks

Analyst's Take

Opportunity Checklist

Sci-Fi to Startup Scorecard

Top Resources

This connects to...