Saved, said the screen, for the rest of the afternoon
A confirmation that never leaves stops confirming anything. Four rows on one settings page: messages that stayed too long, said too little or described no save.
The store-details page in the back office had a small word beside its Save button. Press Save, and it said Saved. Change something else, press Save again, and it still said Saved, because it had never stopped. By the third change the word meant nothing. A tester filed it as the save not working, and from their chair it was indistinguishable from that: nothing on the screen moved when they pressed the button.
Feedback on success has a shape. It arrives, it is readable, and it leaves. A message that arrives and never leaves is furniture. The word now clears itself after a few seconds, so the next press of Save produces a fresh one, and a person watching the screen sees it happen.
Three neighbours with the same fault
The same page had three more rows on the sheet, and they were the same fault from different angles.
Removing the logo cleared it from the screen with no question and no message, and the removal was not saved until you pressed Save, which nothing said. It asks first now, and then says Logo removed, press Save to keep it. A message about a change you have not yet saved has to say so, or the next person to open the page finds the logo back and nobody knows why.
The welcome message, saved empty, said Saved. It says Nothing to save if it was already empty and Cleared if it was not, which are different outcomes and were being reported as the same one. And the ordering settings, saved with nothing changed, said Saved; they say Nothing changed, which is what happened.
Explaining the failure, not just naming it
The bank-details sheet on the same workbook had the opposite problem: a refusal that named the field and not the fault. The last four digits of an account number can be wrong in three ways, empty, not digits, or not four of them, and the sheet now says which, counting the digits typed when the count is the problem. The bank’s name is capped at sixty characters and the cap is quoted back. None of this is new behaviour. It is the same validation, saying out loud what it already knew.