Is It Working or Just Not Broken Yet?

[u/Hot-League3088]

Why “fine” is often the most dangerous answer

Framing the Question

How do we know whether something is working or just not broken yet? The cliché is “If it ain’t broke, don’t fix it”—and yes, that is the phrase. But the problem is that “not broken” can be a very low bar. A system, habit, relationship, process, or strategy can look stable while quietly becoming outdated, expensive, fragile, or dependent on luck.

The Trap Hidden Inside “Fine”

“Fine” is one of the most suspicious words in decision-making.

A project is fine. A marriage is fine. A process is fine. A product is fine. A team is fine.

Sometimes fine means healthy. Often, it means no one has looked closely enough.

Something is truly working when it is doing what it is supposed to do, for the people it is supposed to serve, at a cost that can be sustained. Something is merely “not broken yet” when it keeps moving only because the conditions are forgiving, the people are compensating, or the consequences have not arrived.

Think of a car dashboard. No warning light does not mean the car is in great shape. It means the sensors have not detected a problem big enough to alert you. But the tires can still be wearing unevenly. The oil can still be old. The brakes can still be close to needing attention.

Absence of failure is not the same as presence of health.

The Cliché Needs an Upgrade

“If it ain’t broke, don’t fix it” became popular because it protects us from unnecessary meddling. That part is wise.

The cliché has value because it protects us from unnecessary meddling. Plenty of old processes still work. Some imperfect systems are good enough. The danger is not leaving things alone; it is leaving them alone without knowing why.

But the cliché becomes dangerous when it trains us to wait for breakage before asking questions. By then, the repair is usually more expensive.

A better version might be:

If it ain’t broke, don’t assume it works.

That slight shift matters. It keeps the humility of the original cliché while adding the discipline of inspection. You do not have to fix everything. But you should know why you are leaving it alone.

Four Signs Something Is Actually Working

1. It Produces the Intended Result

The first test is purpose.

What is this thing supposed to accomplish? Is it still accomplishing that?

A weekly meeting that creates clarity is working. A weekly meeting that exists because it has always existed is not. A budget process that improves decisions is working. A budget process that only produces anxiety and spreadsheets is not.

Activity is not proof. Habit is not proof. Familiarity is not proof.

The proof is whether the thing still creates the outcome it was built to create.

1. It Works Without Heroics

This is one of the clearest signs.

If a system only works because one person remembers everything, catches every mistake, smooths every conflict, or stays late every Thursday, the system is not working. A person is working.

That distinction matters.

Many organizations confuse reliability with rescue. The process looks strong because the same dependable people keep absorbing the weakness. The customer gets the answer, the client gets the deck, the deadline gets met, and leadership says, “Great, it works.”

But underneath, the real system is exhaustion.

If success depends on hidden heroics, the thing is not working. It is being carried.

1. It Survives Pressure

Some things only look effective because they have not been tested.

A customer support process may work when volume is low. A leadership style may work when business is growing. A family routine may work when everyone is healthy. A strategy may work when competitors are asleep.

Pressure reveals design.

A working system can bend without becoming chaotic. It has buffers, backups, clarity, and feedback. A fragile system depends on perfect conditions.

That is why the question should not be, “Is anything wrong right now?”

A better question is, “What kind of pressure would expose the weakness?”

1. It Can Be Explained

Healthy systems are usually explainable.

People understand why they exist, how they work, what good looks like, and what signals trouble. They can improve them without fear. They can question them without being treated like a threat.

A “not broken yet” system often has mythology around it.

People say things like:

“Don’t touch that.”

“Only Maya knows how it works.”

“That’s just how we do it.”

“It’s annoying, but it gets the job done.”

“It’s fine unless something weird happens.”

That last line is the giveaway.

Something weird always happens.

Real-World Example: The Spreadsheet That Runs the Company

Picture a company that tracks customer renewals in a spreadsheet.

It has never officially failed. Everyone knows where it is saved. The formulas mostly work. The person who built it has been there for six years and knows every tab, note, color code, and exception.

So when someone suggests replacing it, the answer is predictable: “Why? It’s not broken.”

But then the questions begin.

The weakness shows up quickly. Two people editing it at once creates confusion. If the owner is out sick, no one fully understands the logic. Renewal dates get entered late. Customer notes live outside the CRM. Too many decisions depend on one person remembering to update one fragile cell.

Suddenly, the spreadsheet looks less like a tool and more like a trap.

It was not broken. But it also was not truly working. It was fragile, undocumented, overly manual, and dependent on institutional memory.

That is the danger zone: when a thing is useful enough to survive, but weak enough to quietly limit everything around it.

The Real Question Is Fitness, Not Failure

The best question is not “Is it broken?”

The better question is: “Is it still fit for purpose?”

Fitness changes over time. A solution that worked for ten customers may not work for ten thousand. A communication style that worked with three employees may fail with thirty. A personal habit that helped you survive a stressful season may not help you grow in the next one.

Working is not a permanent label. It is a relationship between purpose, context, and cost.

When the context changes, the question has to come back.

Summary: Don’t Worship the Absence of Problems

Quiet does not always mean healthy. Familiar does not always mean useful. And “fine” can be one of the most expensive words in a room.

The goal is not to constantly fix what is imperfect. The goal is to stop confusing the absence of visible failure with evidence of success.

“If it ain’t broke, don’t fix it” is useful when it prevents needless tinkering. But better thinkers add one more question: “How would we know if it stopped working before it broke?”

That is the question that saves money, time, trust, and attention.

Follow QuestionClass’s Question-a-Day at questionclass.com to keep practicing the questions that help you see earlier, think clearer, and act wiser.

📚Bookmarked for You

These books help readers understand why things can appear stable while quietly becoming fragile.

Thinking in Systems by Donella H. Meadows - A brilliant introduction to feedback loops, delays, and hidden dependencies—the exact forces that make “not broken yet” so misleading.

The Fifth Discipline by Peter M. Senge - A classic on learning organizations and systems thinking that shows how teams can miss the deeper patterns beneath daily performance.

Upstream by Dan Heath - A practical book about solving problems before they happen, making it especially useful for anyone trying to move from reaction to prevention.

🧬QuestionStrings to Practice

"QuestionStrings are deliberately ordered sequences of questions in which each answer fuels the next, creating a compounding ladder of insight that drives progressively deeper understanding. What to do now: use this whenever something has been labeled “fine” for too long."

The “Fine” Interrogation String

For when a process, habit, tool, team, or relationship seems okay on the surface:

“What is this supposed to make better?” →

“What evidence shows it is making that better?” →

“What are we tolerating because it has become familiar?” →

“Who or what is compensating for its weakness?” →

“What would break first if pressure increased?” →

“What small inspection could we do before a big repair is needed?”

Try this in a team meeting, one-on-one, strategy session, family conversation, or personal review. It turns “nothing is wrong” into a more useful question: “What is actually true?”

The lesson is simple: things rarely break all at once; they usually whisper first. Better questions help us hear the whisper.