Every technique that currently defines the frontier of biology started in an academic lab. Spatial transcriptomics came out of methods development groups before it was a product line. Protein design models were trained and published by university and institute labs before anyone commissioned a binder. Organoids were a curiosity in a developmental biology lab for years before a regulator wrote guidance about them.
That is not nostalgia, it is the mechanism. Academic labs are where methods get invented, because they are the only places rewarded for working on something before anyone knows whether it will work. Companies industrialise. Universities originate.
Which creates a problem that the same labs then have to live with.
The toolset turns over faster than a PhD
Consider the timescale. A doctorate takes five or six years. In that window, the standard way to answer a question in your subfield can be replaced twice.
A student who started in 2020 planning bulk RNA-seq watched single-cell become the expectation, then watched spatial become the follow-up question at every talk. Someone who spent a year on crystallography for a structure now competes with a prediction that took an afternoon. A lab that standardised on a mouse model is reading regulatory guidance about human-relevant systems.
None of that is a complaint. Rapid turnover is what a healthy field looks like. But it has a consequence that is rarely stated plainly: the set of capabilities a competitive lab needs access to now grows faster than any lab can acquire them.
Owning a capability is a bet on it staying relevant
When a lab buys an instrument, hires a specialist, or spends a student-year building a workflow, it is making a wager that the technique will still be the right one for long enough to pay back.
Sometimes that bet is obviously correct. If a method is central to what your lab is for, you should own it, and owning it is how you push it forward. That is the work.
The bet goes wrong in a specific and common way: a lab acquires a capability it needs occasionally, pays for it continuously, and finds three years later that the field has moved to something adjacent. The instrument still works. It is just no longer what reviewers expect. Meanwhile the student who learned it has a skill with a shortening shelf life, and a year of their training spent on it.
The constraint is access, not ideas
Ask a PI what is slowing their best project and you will rarely hear that they have run out of hypotheses. You hear that the instrument time is booked out, that nobody in the lab has run the assay before, that the one person who knew the protocol graduated, or that the technique they need exists three buildings away in a group they have never met.
These are access problems wearing the costume of resource problems. The science is not blocked because the question is hard. It is blocked because the capability to answer it is somewhere else.
Core facilities exist precisely because universities worked this out decades ago for instruments. The logic was never that individual labs were incapable. It was that a shared, expertly run capability beats fifteen under-used ones, and frees fifteen labs to do their own work. That argument has not weakened. If anything the turnover in methods has made it stronger, because the half-life of the thing you would have bought keeps falling.
What follows from this
A reasonable working position, and the one this blog is written from:
- Own what you are for. The method that is your intellectual contribution, the work where tacit knowledge and weekly iteration decide the outcome, and anything so exploratory that the protocol changes constantly. Handing that away is handing away the point.
- Get access to the rest. Well-defined, standardised work outside your expertise is not where your originality lives. Doing it in-house for the first time is expensive in the currency that actually matters, which is student-years.
- Judge the capability, not the technique. The interesting question is rarely whether a method is exciting. It is whether it answers your question better than the cheaper thing, and whether the people running it have done it enough times to know its failure modes.
Why we write the rest of this blog
If the constraint is access, then knowing what is worth accessing is a real skill, and it is one nobody teaches. Deciding whether your question needs a spatial platform, whether a designed binder is a realistic route, or whether a human-relevant model beats an animal one, are judgement calls with significant costs attached and very little honest writing to guide them.
So that is what the rest of these posts are: an attempt to describe emerging methods the way a colleague would, including when the answer is that you do not need the expensive one. Academia will keep producing the techniques. The least we can do is be clear about which of them you actually need.