User: "If I change something and click save it overwrites my previous entry." Me: "Of course it does. To make a new entry you you have to click New Entry." User: "That doesn't make any sense." Me: *facepalm

users will always be the error that you can't try to catch 😢

You should have asked why he thought that and what he expected to happen. Maybe you'd discover something about your product and could have improved it. It's not the user's fault when your product doesn't communicate how it works.

Possibly they could benefit from an audit trail and archive prior to the change?

@h3ll without asking the user, how can you say anything about how they interpreted the interaction?

@h3ll what does "entry" mean?