I’ve learned something the hard way: if the same problem keeps showing up, eventually you have to stop blaming the report, the process, the system, or the way it has always been done.
At some point, you either keep working around the problem — or you build something better.
That is usually where the best ideas start. Not in a boardroom. Not in some polished strategy session. They start when you are close enough to the work to see the drag.
You see a report that gets pulled every month but still does not answer the real question. You see a process that technically works, but only because people have learned how to fight through it. You see a promotion that has been done the same way for years because nobody stopped long enough to ask whether there was a smarter way to execute it.
I think about something as simple as promotional scratch-offs.
For years, that kind of promotion made sense. Print the cards. Ship them out. Put them in the field. Let the customer scratch and win. It was physical, simple, and familiar. But it also had limits. You had printing costs. Mailing costs. Timing issues. Inventory headaches. No clean visibility. No easy way to track engagement in real time. Once the cards were out there, they were out there.
Then you start asking better questions.
Why does this have to be printed? Why does it have to be manual? Why can’t it be digital? Why can’t the customer engage from their phone? Why can’t we track participation, winners, claims, locations, timing, and results in one place?
That is where building starts.
Not because the old way was stupid. The old way may have worked for a long time. But working and being optimized are not the same thing.
The same idea applies everywhere.
If the report is bad every month, build a better report. If the website looks half-done, redesign it. If the workflow makes people guess, create the tool that removes the guessing. If the promotion feels outdated, rethink the experience. If the same question keeps getting asked in every meeting, build something that answers it before the meeting even starts.
That is the difference between complaining and creating.
Complaining says, “This is broken.”
Building says, “Here is a better way.”
And the better way does not have to be perfect on day one. It almost never is. The first version is usually ugly. It is usually rough. It may only solve one part of the problem. But it gives people something real to react to. It creates momentum. It moves the conversation from opinion to execution.
Most people wait for permission, budget, a vendor, a committee, or the perfect timing. Sometimes those things matter. But a lot of times, waiting is just drag dressed up as process.
I would rather build the rough version, test it, learn from it, and keep improving it.
That is how better tools get created. That is how better promotions get launched. That is how better reports, better workflows, better customer experiences, and better business decisions happen.
You do not have to be the person with all the answers.
But if you are close enough to the problem to see what is missing, you might be close enough to build the first version of the solution.
Build the thing.
Then make it better.
Leave a Reply