Back to blog

A Culture of Experimentation and Learning

CultureKang Dongju2025.05.16
A Culture of Experimentation and Learning

"Build fast, learn fast" can sound uncomfortable coming from a company that supports decisions in the pharmaceutical and chemical industries. It can easily be read as permission to skip validation or documentation.

At Alche, speed does not come from removing necessary controls. It comes from testing uncertain assumptions in shorter cycles. That is why we distinguish between what we can test quickly and what we will not compromise for speed.

What We Test Quickly

Which questions matter in real workflows, which interfaces help users make decisions, and which model configurations work with a given dataset cannot always be settled through discussion alone.

In these areas, it is often more effective to build something small and test it directly. We implement the core workflow before completing every feature, then observe where users hesitate or lose context. Rather than refining one model indefinitely, we compare multiple approaches and identify the one best suited to the available data.

The purpose of an experiment is not to be right on the first attempt. It is to obtain the information needed for the next decision sooner.

What We Do Not Compromise

We do not relax the evidence behind a customer-facing assessment, agreed boundaries for customer data, or the process used to validate results simply to move faster.

A prediction should be connected to the data and sources used to produce it. The scope of data processing, storage location, and access rights should be defined in advance and managed within the agreed boundaries. Model outputs should be reviewed in a way that reflects their intended use and level of risk.

Validation and security practices can and should improve over time. But providing a result without adequate review, or changing an agreed data boundary for convenience, is not what Alche means by experimentation.

Once those boundaries are clear, the team can move more boldly within them. Everyone knows what can be changed and what must remain protected.

We Keep the Evidence Behind Decisions

One of Alche's product principles is to retain the evidence behind a prediction or assessment. We apply the same principle to decisions within the team.

When we make a decision, we record more than the conclusion. We also note the facts and assumptions available at the time, along with what remained unknown. If the outcome later differs from what we expected, this helps us distinguish whether the original reasoning needs revision or the underlying conditions have changed.

Without that distinction, it is easy to judge a past decision only from the outcome visible today. Preserving the original evidence and uncertainty allows a retrospective to focus on improving the next decision.

The purpose of documentation is not to justify every choice. It is to leave enough context for the next person to examine the same problem from a better starting point.

We Say When an Approach Is Not Working

Experimentation only works in a small team when people can quickly surface an approach that is not producing the expected result. If it is easier to continue defending a direction than to say it is not working, the team is more likely to stay with an existing direction than test a better one.

At Alche, attempts that do not produce the expected result still become part of the learning record. We document what was tried, what happened, what we currently understand about the cause, and what should change next time. The goal is not to treat an unexpected outcome as success. It is to help prevent the next person from repeating the same experiment under the same assumptions.

What matters is what the outcome revealed and how that knowledge changes the next action.

Keeping Product and Team Principles Aligned

Alche builds products that structure chemical data and connect predictions and assessments to their supporting evidence. We try to carry that same principle into the way the team makes decisions.

Experiment quickly, but define the boundaries first. Preserve the reasoning behind a decision, not just its outcome. When a direction proves unsuitable, share it early and use it to improve the next attempt.

That is the culture of experimentation and learning we are building at Alche.