Short notes, most weeks.

Materials R&D is shifting toward productization.

That does not mean turning research into bureaucracy. It means making workflows repeatable, measurable, and reusable.

The difference between a project and a product is compounding. A product gets better with every use. A project is reinvented every time.

Platforms make this shift possible. They turn scripts into pipelines, runs into assets, and results into shared organizational knowledge.

Productization also changes incentives: teams start optimizing for cycle time and handoffs, not just isolated results.

That is how you build a discovery engine instead of a series of disconnected projects.

Everything around us is made of materials.

Phones, planes, batteries, buildings, medicine… and yet most people never think about materials science.

It’s invisible infrastructure.

That is part of why I find this field so meaningful: small improvements in materials quietly reshape what is possible in energy, health, and technology.

If we can reduce the friction of discovery even a little, the impact compounds far beyond any single lab.

Most organizations lose knowledge at the end of every project.

The results live in files. The decisions live in conversations. The reasoning lives in someone’s head.

Then people move on, and the next project starts from scratch.

Scientific memory is not a document. It is a system.

When runs, inputs, and decisions are connected and searchable, knowledge stops disappearing. It becomes an asset the team can build on.

The best indicator of a healthy R&D organization is whether new people can become productive without inheriting a pile of undocumented folders.

Memory should live in the workflow, not in a single researcher.

Reproducibility is often described as a scientific virtue. In practice, it is the main bottleneck.

If you cannot reproduce a run, you cannot trust it. If you cannot trust it, you cannot reuse it. If you cannot reuse it, progress stays linear.

In modern labs, the bottleneck is rarely compute. It is provenance: what exactly happened, with what inputs, using what environment.

Make provenance automatic and reproducibility becomes normal. Then reuse becomes normal. That is where speed comes from.

When reproducibility is weak, teams compensate with meetings, manual checklists, and reruns. That looks like rigor, but it is mostly friction. Good systems replace meetings with provenance.