We made alternative improvements for all the shortcomings we saw in the small launch and usability tests before the crypto product. Now it's time to test them. In this way, we will have the chance to validate the new changes.

Most of the time, we can't continue after the first test. I think this is the most important step. Publishing the changes we've made without getting confirmation whether they actually solve the problem we're seeing makes this whole testing process pointless.

At least we can think that it has improved from the previous version. Yes, the fact that the designer was able to make the move to solve the problem most of the time is a result I foresee. However, sometimes our efforts to solve the problem may have made the problem more complicated. After a while we become blind because we get away from the problem itself, we can make the wrong decision with unnecessary additions / subtractions.

For these and similar reasons, I think the most important stage of usability tests is that the solutions produced or the improvements made (if possible, together with alternatives with different solutions) should be tested and published if it is confirmed that it really brings a solution.