Hi, I’m Mark. A few years ago, I worked for a small marketing team. Every Friday, we had to send a short report to our manager. It included the number of new clients, the results of our online campaigns, and a few comments about what had worked well that week. The report was not difficult, but it was boring. We copied numbers from three different files, pasted them into a document, and wrote almost the same sentences again and again. Everyone knew it took too much time, but nobody changed the process because it had always been done that way. One Thursday evening, I was tired and in a hurry. I opened the wrong spreadsheet and copied last month’s numbers instead of the current week’s results. I noticed the mistake only after I had already sent the report to my manager. My first feeling was panic. I imagined an angry email and an uncomfortable meeting the next morning. Instead, my manager called me and asked a surprising question: “Why do we still do this manually?” At first, I thought she was trying to make the mistake sound less serious. But then she explained that the mistake showed a bigger problem. If one tired person could copy the wrong numbers, then the process was not reliable enough. The next week, our team spent one afternoon building a simple template. The numbers were pulled from the original files automatically, and each person only had to add a short comment. The report became faster, clearer, and less stressful. What used to take almost two hours now took about twenty minutes. Of course, I was still responsible for my mistake. I apologised and checked my work more carefully after that. But the mistake also helped us see something we had ignored for months. That experience changed the way I think about problems at work. A mistake is not always just a failure. Sometimes it is a signal. It can show that a system is confusing, too slow, or too easy to break. If people react with curiosity instead of blame, a mistake can become the beginning of a better idea.