We can perfect an idea in our head for a long time, without finding out how it works in real conditions. A conversation with the user or a small test sometimes reveals a problem that we could not see from the blueprint.
Before trying, we should determine what we are checking, how much time and money we are investing and when we will stop. This way we get a result that we can interpret, instead of just an impression that something went well or badly.
If the assumption does not hold, it is worth changing it. Not every failed test is a reason to give up, but neither is it an invitation to repeat the same procedure endlessly. The next attempt should show what we really understood from the previous one.
Comments