Skip to main content

Which step of the scientific method do we return to if the prediction is wrong?

 It might seem natural to assume that your hypothesis is wrong, and therefore rethink your hypothesis. In fact, in a popular article for LiveScience (see link below), that's exactly what the author suggests: The scientist either rejects the hypothesis outright, or modifies the hypothesis to account for the failed prediction. Either way, the implication is that the scientist "goes back to the drawing board" to come up with new predictions to test.


But in the real world, scientists don't always assume there is something wrong with the hypothesis. Before you reject your hypothesis, it's important to check your reasoning. You might have made a mistake at the step of generating predictions. Does your prediction necessarily follow from your hypothesis?


Or you might have made a mistake during the testing process. Did you execute a clean experiment? Did you successfully control for other factors that might have influenced the results?


It's not hard to imagine how you could make a mistake during testing. You might fail to control for all the underlying differences between your treatment and control groups. Many phenomena are caused by multiple factors. If you fail to confirm your prediction, it could be because there was something different between groups that you failed to account for.


But what about the validity of your prediction? It's important to check that step too. For example, let's suppose your hypothesis is that gorillas are capable of visually recognizing themselves, and so you make the following prediction: If gorillas possess the ability of self-recognition, then if they look in the mirror, and see a smudge of white paint on their foreheads, they will try to rub it off.


You perform this experiment -- applying paint to gorillas while they sleep, and then allowing them to look in the mirror after they wake up. They look at their reflections, but fail to touch the paint spot or try to rub it off.


Should you abandon your hypothesis that gorillas are capable of visual self-recognition just because your prediction was wrong? On reflection, the prediction has problems. We can imagine cases where human beings -- who have self-awareness -- might not react in the predicted way.


This experiment is a real one. It's been called the "mirror test" and it has been performed on a variety of species. But some researchers have pointed out that the prediction doesn't necessarily follow from the hypothesis. For instance, gorillas might ignore the paint spot because they simply don't care how they look. These researchers haven't rejected the hypothesis merely because the prediction was wrong. Their approach, instead, is to go back to the step where you generate predictions from your hypothesis -- taking better care to come up with predictions that are more tightly entailed by your hypothesis.

Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...