Frameworks February 4, 2026

The 5 Signs You've Confused Normal with Optimal

Normal passes for optimal constantly. It has a comfortable feel, a low complaint rate, and a long track record of being fine. Here's how to tell when you're optimizing the wrong target.

Charles Poliquin spent his career watching athletes train hard at the wrong things.

Not wrong in the sense of harmful. Wrong in the sense of not optimal — the difference between what’s normal at the level they were at and what was actually possible if they stopped mistaking the ceiling of their current system for the ceiling of their potential.

His line: don’t confuse normal with optimal.

The confusion is not obvious when you’re inside it. Normal has a comfortable feel. It has a long track record of being acceptable. It has a whole community of people doing the same thing, which creates a social proof that reads like evidence of correctness.

Optimal is different. Optimal is what becomes visible when you ask a harder question: not “is this working?” but “is this the best available version of working?”

Here are five signs you’ve stopped asking the harder question.


Sign 1: Your benchmarks are your peers

You know you’re doing well because you’re doing better than others in your category.

This is useful information. It is not information about optimal. It is information about relative position within a reference class — and reference classes can be uniformly underperforming.

A mediocre industry produces mediocre benchmarks. A peer group that has collectively normalized a particular level of output will produce comparisons that make that level feel like achievement. You can be above average in a below-average system and conclude you’ve hit ceiling.

The question Poliquin asked his athletes wasn’t “how does your performance compare to other athletes at your level?” It was “what is biologically and mechanically possible for a human in your situation — and how far are you from it?”

That question has a much less comfortable answer. It is also the answer that points toward what’s actually possible.

The diagnostic: Remove your peer group from the comparison entirely. Compare to what’s possible in absolute terms, not relative ones. If you can only state your performance as a relative position, you may not know where you actually stand.


Sign 2: You’re optimizing for comfort within the current system

Things are running smoothly. The process is established. The complaints are low. You’re making incremental improvements to a system that is, by all available measures, working.

This is when the confusion is hardest to see. Optimization feels like progress. Incremental improvement within a system is real improvement. It charts upward. It has measurable returns.

The question it doesn’t answer: is this the right system?

Optimizing the wrong system is one of the most expensive things a business can do. You get very good at executing a process that is pointed at the wrong target, serving the wrong customer in the wrong way with the wrong product. The execution gets smoother. The fundamental misalignment doesn’t.

The Project Optimal principle: efficiency is not the same as optimization. You can be highly efficient at the wrong thing.

The diagnostic: Separate the question of “are we doing this well?” from “is this the right thing to do?” Answer both independently. If you can only answer the first, you may be inside a local maximum — doing as well as possible within a system that isn’t the best available system.


Sign 3: Your ceiling feels like a law of physics

There’s a number, a rate, a capacity that you’ve accepted as the limit. Revenue caps out at X. Conversion holds at Y. Growth tops out at Z. You’ve worked hard to get there. You’ve tried to push past it. The ceiling held.

The conclusion feels logical: this is the limit.

But ceilings in business and performance are almost always system artifacts, not physical constants. They appear because the current system can only produce up to a certain level — and past that level, the constraints of the system prevent further gains. The ceiling is real. It is not permanent. It is a property of the current approach, not of what’s possible.

The Quantum Hop exists for exactly this situation. Some ceilings cannot be raised from inside the current system — they require a structural shift, not continued optimization. The ceiling is the signal that optimization has reached its limit in the current frame. What comes next is not better optimization. It is a different system.

The diagnostic: Ask when this ceiling appeared and what was different before it. Ceilings that have existed for a long time in stable conditions are probably system constraints, not fundamental limits. The system that produced the current ceiling is probably not the system that breaks through it.


Sign 4: “Good enough” has stopped being a temporary position

Good enough is a useful concept. Under resource constraints, with competing priorities, in situations where the cost of perfect exceeds the value of better — good enough is the right call.

The problem is when good enough stops being a strategic position and becomes a permanent orientation.

You can feel this shift happen. Good enough as a strategic position sounds like: “Given our current constraints, this is the appropriate level of investment in this area.” Good enough as a permanent orientation sounds like: “This is just how this works.” The first is a decision. The second is an assumption.

The Poliquin principle cuts here: the phrase “this is just how this works” is usually a sign that you’ve accepted normal as optimal. What you mean is “this is how it works in the system I’m currently using.” That is a different claim with different implications.

The diagnostic: Find three things in your operation described as “just how it works” and apply external research to each. Find one example of a different organization, in any industry, doing that thing at a meaningfully higher level. If such an example exists — and it usually does — “just how it works” is a system constraint, not a physical law.


Sign 5: You haven’t asked what’s actually possible lately

This is the most common sign and the least visible.

You know what’s possible because you know what you’ve achieved and what you’ve seen others achieve. The reference frame is your history and your peer group. Both of those things are anchored to where you are, not to what’s available.

The question “what’s actually possible here?” requires going outside the reference frame. It requires looking at adjacent industries, at people who have solved similar problems from different starting positions, at research that has happened since you last looked, at tools and approaches that exist now that didn’t exist when you formed your current model of what’s achievable.

Most people update their reference frame rarely. The world changes faster than the reference frame updates. The result: you’re making decisions about what’s possible based on information that is significantly out of date.

The diagnostic: Name the five most important constraints in your current operation. For each one, state when you last verified that constraint was still real — not assumed, not inherited from a previous model, but actively tested against current conditions. If you can’t answer that question, the constraint may be a legacy assumption, not a current reality.


What to Do With the Signs

Recognizing the confusion is not the same as resolving it. The signs above identify where you’ve normalized something that isn’t actually the limit — they don’t tell you what optimal looks like or how to reach it.

That work requires the KaosX Formula — mapping the variables and identifying the actual constraint that’s keeping output below potential. It requires the Context Framework — understanding your current situation accurately before prescribing changes. It may require a Quantum Hop — a structural shift to a different system rather than continued optimization within the current one.

But it starts with the recognition. With the willingness to ask the harder question.

Not: is this working?

But: is this the best available version of working? And how would I know if it wasn’t?

Don’t confuse normal with optimal. The ceiling you’re looking at is probably a system constraint. The question is whether you want to find out what’s on the other side of it.


Related frameworks:


Join the Charter — $12/mo →

SYSTEM.CONNECT

Want early access to every framework?

Charter members get new frameworks before they're published anywhere else. $12/mo or $100 lifetime.