Hi, I’m Victor. I used to believe that good ideas were ignored mainly because workplaces were too conservative. If a suggestion was useful and people still did not support it, I assumed the problem was fear of change. But after watching one of my own ideas fail, and then succeed almost a year later, I realised the truth was more complicated. I was working for a company that offered online training for small businesses. Our support team kept receiving the same questions from customers: how to invite employees, how to reset access, how to choose the right course package. I suggested creating a short onboarding checklist that would appear immediately after a customer bought a plan. It seemed obvious to me. If customers were confused at the beginning, we should guide them at the beginning. I presented the idea in a team meeting with genuine enthusiasm. I explained the problem, showed examples of repeated support tickets, and described what the checklist might include. People listened politely. A few nodded. Then the conversation moved on to another topic. Nobody said the idea was bad. Nobody argued against it. It simply disappeared. At first, I felt frustrated. I thought, “How can they not see this?” But later, I understood that a good idea does not only need logic. It needs timing, ownership, and a reason to compete with everything else already demanding attention. At that moment, the company was focused on increasing sales. My idea sounded like a support improvement, not a business priority. Another problem was that I presented the idea as if the evidence spoke for itself. I showed repeated questions, but I did not connect them clearly to lost revenue, customer confidence, or team workload. For the support team, the problem was obvious. For everyone else, it was just another useful suggestion in a room full of useful suggestions. Almost a year later, the same issue returned in a different form. The company noticed that many new customers bought a plan but did not invite their teams within the first week. Some cancelled before using the product properly. Suddenly, onboarding was not just a support topic. It was a retention problem. This time, when I suggested a first-week checklist, people paid attention. The idea had not changed very much. The room had changed. The company now had a question that my idea could answer. We built a simple checklist with three steps, added it to the customer dashboard, and sent a reminder email when a customer had not completed it. Within a few months, more customers were setting up their teams successfully. That experience taught me that ideas often fail because they arrive without context. People do not judge ideas in a quiet empty space. They judge them while thinking about deadlines, targets, budgets, risks, and their own responsibilities. A good idea can be ignored if it does not speak the language of the room. I also learned that people sometimes resist ideas because accepting them creates work. Even a helpful suggestion asks someone to change a process, make a decision, or admit that the current system is not working. If the benefit feels distant but the effort feels immediate, the idea may be pushed aside. Now, when I want to share an idea, I ask myself three questions. Who owns this problem? Why does it matter now? What decision am I asking people to make? If I cannot answer those questions, I probably have not prepared the idea properly. So I no longer think ignored ideas are always bad ideas. Sometimes they are early ideas, poorly framed ideas, or ideas without a clear owner. Creativity is not only about having something clever to say. In the workplace, creativity also means helping other people see why the idea matters, why it matters now, and what should happen next.