I have watched businesses spend months searching for a clever answer to a problem that was mostly caused by irregular effort.
The sales pipeline is weak, so the team looks for a new CRM. Documentation is poor, so someone proposes a knowledge-management project. Copilot usage is patchy, so the conclusion is that the technology has not delivered. Yet when I look closer, the real issue is often much simpler. The useful activity happened for a week, then stopped.
I do not think most organisations have an ideas problem. I think they have a follow-through problem.
Repetition turns good intentions into a system
The value appears when the same useful behaviour happens again tomorrow, next week and next month.
I see this with Microsoft 365 Copilot adoption. Someone runs an impressive demonstration, people try a few prompts, and enthusiasm rises. Two weeks later, everyone is back to old habits. Nothing was technically wrong. There was simply no rhythm around the new behaviour.
I would rather see a team choose one recurring task and improve it every day. For example, before replying to a complicated customer email, I might ask Copilot in Outlook to summarise the thread, identify unanswered questions and draft a response. The important part is that I use the same workflow repeatedly until it becomes normal.
That modest habit will usually produce more value than another broad training session filled with possibilities nobody applies.
Small routines expose the real problems
Consistency does more than produce output. It creates evidence.
If I review overdue work in Planner every Monday morning, I quickly learn whether tasks are unclear, ownership is missing or priorities keep changing. If a service team records recurring fixes in a SharePoint knowledge base after each incident, gaps become visible. If I ask Copilot in Teams to recap a regular meeting and compare decisions with open actions, I can see where commitments are slipping.
Without repetition, every failure looks like an exception. With repetition, patterns become hard to ignore.
They buy a tool, restructure a meeting or create another policy. Sometimes those changes are needed. But a steady routine gives me enough information to distinguish a genuine system problem from a discipline problem.
I cannot improve what I only do occasionally.
Make the useful action easier to repeat
I do not rely on motivation. Motivation is helpful, but it is unreliable. I try to reduce the number of decisions required to begin.
That might mean pinning a standard prompt in a Teams channel, using a Loop component for the weekly agenda, or placing the client-review template where everyone already works. I want the next correct action to be obvious and close at hand.
The routine also needs to be small enough to survive a busy week. A ten-minute review completed regularly is better than a two-hour process everyone avoids. Once the habit is stable, I can expand it. Starting with a grand process usually creates a grand abandonment.
This is why I am sceptical when someone says they need a more advanced tool before they can move forward. Often they need a simpler commitment, repeated long enough to reveal what actually deserves attention.
I do not believe steady effort solves every problem. Some issues require money, expertise, authority or a difficult decision. But I have found that reliable habits remove a surprising amount of noise. They strengthen the basics, expose the exceptions and make the harder problems easier to recognise.
Before I search for a dramatic fix, I ask a more useful question: what worthwhile action have I not repeated often enough?
