The Gap Between 'We Should Fix That' and Actually Fixing It

Every business has a graveyard of good ideas.

Someone raises a concern at a team meeting. A customer mentions something in a one-on-one conversation. A manager spots a process that keeps producing the same mistake. Everyone in the room agrees it needs to be fixed. Someone says they’ll look into it.

Three months later, nothing has changed. Sometimes six months. Sometimes it comes up again at the next team meeting, and everyone agrees again that it needs to be fixed.

This isn’t a motivation problem. It isn’t a leadership problem. It’s a systems problem — and it’s costing you more than you think.

What the Gap Actually Costs

The obvious cost is the thing that never got fixed. But the less obvious cost is what happens to the relationship that surfaced it.

When a customer tells you something in a candid conversation — a process frustration, a product gap, a recurring pain — they’re doing you a favour. They’re telling you what they’d normally just quietly absorb, or eventually take to someone else. That conversation is an act of trust.

If nothing changes, they notice. They may not say so. But the next time you ask how things are going, the answer gets a little more guarded. The candid conversations get shorter. Eventually they stop happening at all — and you lose the signal that would have told you the relationship was drifting.

Where Insights Come From

Some improvement ideas come from the inside — a process audit, a quality review, a staff suggestion. But the most valuable ones, for most small businesses, come directly from customers.

The Opterion-IT Customers module includes a structured mechanism for this called a Value Creation Conversation — a one-on-one dialogue with a client designed to surface what’s working, what isn’t, and what would make the relationship more valuable to them.

These aren’t surveys. They’re conversations. And the answers they produce aren’t data points — they’re action items. A customer who says “your delivery timing is unpredictable” or “we’d use you for this other thing if the process were simpler” has just handed you the blueprint for a business improvement.

The question is what you do with it next.

The Notebook Problem

In most businesses, the answer is: write it down and hope for the best.

The insight lands in a meeting note, a personal notebook, or an email to yourself. If you’re organised, it makes it onto a to-do list. If the to-do list is already long, it competes with everything else for attention — and unlike a deadline or an invoice, an internal improvement has no natural forcing function. Nobody chases you on it. The customer who raised it doesn’t know whether action was taken. And the team member who was going to “look into it” has moved on to the next urgent thing.

This is the gap. It’s not malicious. It’s structural. The information arrived but the system for acting on it didn’t exist.

Initiatives: The Single Point of Tracking

The Initiatives module in Opterion-IT exists specifically to close that gap.

An Initiative is any internal effort to improve your operations — a process change, a product improvement, a service redesign, a response to a customer concern. It can come from anywhere: a customer conversation, a team observation, a manager’s instinct, a supplier issue. The source doesn’t matter. What matters is that once it exists in the system, it has a home.

And that home includes everything needed to actually execute on it:

• PLAYs — the specific actions assigned to specific people, with timelines and accountability. The Initiative doesn’t just sit there; it has work attached to it that someone owns.
• Comments — the running record of what’s been decided, what’s been tried, and what’s changed along the way. Not in an email thread that three people are CC’d on — in one place, attached to the Initiative itself.
• Related files — the documents, specs, and supporting material that belong to this effort, not scattered across shared drives and inboxes.
• Budget requests — if the improvement requires spending, the request originates here, where it has context, and tracks through to approval and actuals.

The result is that everyone involved — and anyone who needs to check in — can see the full picture in one place, at any moment, without asking anyone.

From Customer Conversation to Closed Loop

Here’s what the full cycle looks like when it works:

A Value Creation Conversation reveals that a particular customer has been quietly struggling with your onboarding process. You create an Initiative: Simplify the onboarding workflow for new accounts. You assign a PLAY to the operations lead to document the current process. Another PLAY goes to the product team to identify where the friction is. A budget request is raised for the external resource you’ll need to redesign the intake form.

Three weeks later, the Initiative has a comment thread showing what was found, a revised process in the files, and a completed PLAY log showing who did what and when. The next time you speak to that customer, you can tell them specifically what changed and why — because you have the record.

That’s not just a better process. That’s a stronger relationship.

The Real Definition of Continuous Improvement

Continuous improvement isn’t a philosophy. It’s a practice — and practices require systems.

Opterion-IT’s Initiatives module is built on the observation that most businesses aren’t short of ideas. They’re short of a reliable way to take an idea from the moment it surfaces to the moment it’s done, tracked, and reported on. Once that infrastructure exists, improvement stops being aspirational and starts being operational.

The graveyard of good ideas closes. The loop closes with it.

---

The Initiatives module is part of the Opterion-IT platform — modular business management software for organisations of five people or more. See how the Initiatives module works →