A strata analysis tool can add more strata features. A property document intelligence platform can analyze building inspections, planning certificates, lease agreements — anything that arrives as a dense PDF and leaves as a decision.

Same product. Different genus. Completely different expansion surface.

This is the genus problem: the category you place something in determines which adjacencies are visible and which are invisible. Not which ones are possible — which ones you can see.

The lens effect

In biology, taxonomy is descriptive. You observe an organism and classify it based on shared characteristics. But in product design, business strategy, even personal identity — taxonomy is prescriptive. The category comes first, and then constrains what feels like a natural next step.

A “railroad company” builds more railroad. A “transportation company” considers trucks, airlines, logistics software. Theodore Levitt pointed this out in 1960 and entire industries still make the mistake.

The interesting part isn’t that narrow categories limit you. That’s obvious. The interesting part is that you can’t see the limitation from inside it. The genus feels like a fact about the world, not a choice you made. “We’re a strata analysis tool” feels like a description of what the product is, not a frame that happens to hide everything the product could be.

Where else this shows up

In code: a class named StrataReportParser will never grow a method for parsing building inspection reports, even though the underlying logic (extract structured data from messy PDF) is identical. Rename it PropertyDocumentParser and the method feels obvious.

In identity: “I’m a backend developer” makes frontend work feel like someone else’s job. “I’m a software engineer” makes it feel like a skill gap. “I’m a problem solver who happens to write code” makes it feel like Tuesday.

In writing: call something an “essay” and it needs an argument. Call it a “note” and it can be exploratory. Call it a “post” and it needs to be finished. The content might be identical. The genus determines what the author permits themselves.

The transaction chain test

One way to escape the genus problem: instead of asking “what category is my product in?”, ask “what chain of actions does my user perform, and where in that chain do I appear?”

A property buyer doesn’t think in product categories. They think in transaction steps: find property, inspect it, review strata, check planning certificates, negotiate, sign contracts, arrange finance. Each step involves documents. Each document involves interpretation. The chain exists independent of any product — it’s the structure of the transaction itself.

Products succeed when they align with existing chains rather than trying to create new categories. The chain tells you your real adjacencies. The genus hides them.

The meta-problem

Of course, “the genus problem” is itself a genus. By framing this observation as being about categories, I’ve made it about taxonomy, product strategy, naming. If I’d framed it as being about perception, it would be about cognitive science, attention, framing effects. If I’d framed it as being about language, it would be about Sapir-Whorf, linguistic relativity, the way words shape thought.

Same observation. Different genus. Different adjacencies visible from each.

You can’t escape the genus problem. You can only notice when you’re inside one.