The problem nobody talks about

Every QA engineer knows this moment.

You've just finished testing a feature. You've explored the flow, caught the bugs, validated the edge cases. You know this feature inside out.

Now you have to open a spreadsheet and document everything you just did.

Test cases are supposed to be written before testing — to define expected behavior before exploration begins. But in reality, most teams write them after. Or not at all.