Quick attempts
When quick attempts come alive, the Experimenter converts an unanswerable debate into a checkable question. Shrink the hypothesis, and next week has an answer.
Experimenter · a person who conducts experiments to find out.
Some questions cannot be settled by more discussion. The Experimenter, instead of scheduling another meeting, builds the small version and watches what actually happens.
That reads as impulsive. What this type runs is a fast loop of trying, observing, and revising, on the arithmetic that when predictions are unreliable, colliding early is the cheaper path.
Used well, this ends a long argument in a day. Under pressure, the experiments multiply while the sorting of what they taught falls behind. Growth for the Experimenter is not trying less; it is attaching a criterion and a record to each try.
To understand the Experimenter, look at its cost accounting rather than its patience. It weighs the price of thinking longer against the price of trying, and picks the cheaper.
The try-observe-revise loop sits underneath its judgment, so the first question differs. Not whether this is right, but how we could find out.
The point of reading this type is not to grade caution. It is to tell when the quick try becomes learning, and when it becomes churn.
When quick attempts come alive, the Experimenter converts an unanswerable debate into a checkable question. Shrink the hypothesis, and next week has an answer.
Learning agility and taking feedback shorten the loop: being wrong costs little because the correction comes fast.
A sense of the field keeps the experiments honest. What the real environment says outranks what the room expected.
The ability to revise shows after plans break. When the original route fails, the next route is proposed on the spot.
The Experimenter is clearest when the loop of trying and revising comes alive. The four steps below show how a hypothesis is built and carried to an answer.
Makes a hypothesis small and tries it.
Observes the actual response.
Fixes what is wrong quickly.
Keeps what was learned as the next criterion.
Low traits here are a checklist for follow-through, not a character flaw. When setting criteria, keeping records, and finishing sit low, many tries add up to little kept.
Under pressure, the trying outruns the sorting. Not from carelessness: trying has answered questions before, so the writing-down feels like delay.
So adjustment is not slowing the loop. Writing one line, before starting, on what this try is meant to reveal is usually enough.
Let us try it does not mean let us be sloppy; for this type it is the method of verification, and hearing it that way helps.
Questions with no answer until contact is this type's ground. But unrecorded results get re-run, so what was learned gets kept.
The direction is keeping the criterion and the record alongside the try. Not more hesitant; extracting more from the same number of tries.
Ask what should be checked first rather than demanding the finished design. Next week there will be a result to discuss.
The figures below do not claim that this person is a Experimenter. They are reference cases for understanding a way of operating close to this type, drawn from publicly known roles and representative moments.
American inventors of the airplane.
Glider experiments · the first powered flightThe Wright brothers measured wind data themselves, tested wing shapes in a wind tunnel they built, and learned control first through hundreds of glider runs. The first powered flight in 1903 lasted twelve seconds, and it came at the end of a long cycle of experiment and correction.
American inventor.
Invention through large numbers of experimentsHe produced results through repeated experiment and trial and error, which is the standard reference for this type.
French chemist and microbiologist.
The swan-neck flask experiment · pasteurisationWith a single flask whose neck he had bent, Pasteur overturned by experiment the accepted view that life arises on its own, and he traced spoiled wine to microbes and devised heating to stop it. Up through the rabies vaccine, he repeated the same cycle his whole life: set a hypothesis, test it by experiment.
Founder of Honda.
Prototype after prototype · motorcycles and carsHonda began as a mechanic and built the company by making engines, breaking them, and making them again. He said failed prototypes were the raw material of success, and the record of declaring, as an unknown company, an entry into world motorcycle racing, then winning within a few years, is a working example of treating the attempt itself as the lesson.
British inventor.
Iterative prototype developmentHe improved a problem across thousands of prototypes, which shows how experiment turns into learning.
See for yourself how close your result is to the Experimenter.