Why "I’m Fine" Is Never 'Fine' in statement analysis

And what statement analysis can teach you about everyday conversations

You know that moment...

You walk through the door after work. Your partner is in the kitchen. Something is clearly wrong. The air is different. The radio that is normally on is off. There is a silence that has texture.

You ask, "How was your day?"

And they say, "Fine."

You know it is not fine. They know it is not fine. The cat knows it is not fine! Everyone in the room knows that "fine" is doing a poor job of describing how their day was.

But here is the question: how do you know?

You did not read their body language. You did not analyze their facial expression. You did not hook them up to a polygraph. You heard a single word—"fine"—and you knew immediately that it meant the opposite of what it said.

This is basic statement analysis. You have been doing it your entire life without knowing it had a name.

What "fine" Actually Tells You

In statement analysis, there is a principle that sounds simple but changes everything once you understand it: people mean what they say. Their words are chosen—not randomly, not accidentally—by a process so fast and deep that the conscious mind barely registers it. The brain selects the word before the mouth speaks it. And the brain does not lie.

So when someone says, "I am fine," the question is not whether they are telling the truth. The question is: why did their brain choose that word?

Consider this: if your day was genuinely good, you do not say "fine." You say "good." You say "great." You say "really busy but productive." You say, "I had the best sandwich at that new place on the high street." You provide detail. You share. You open up. Because a good day is something you want to talk about.

"Fine" shuts the conversation down. It is a full stop disguised as an answer. It is the verbal equivalent of closing a door quietly but firmly. The reason people use it is precisely that it sounds like an answer without actually being one. It satisfies the question without revealing anything.

In the world of statement analysis, we would call this a "closed response"—a reply that performs the function of answering without actually providing information. The word itself is doing a job: it is managing you. It is saying, "I do not want to talk about it right now, but I do not want to say I do not want to talk about it. So I am giving you a word that sounds like everything is okay so you will stop asking."

All of that. In four letters.

The Everyday Analysis You Already Do

Here is what is interesting: you already knew all of this. The moment your partner said "fine," you heard it. You did not need training. You did not need a textbook. Your brain processed the word, the tone, the context, and the absence of detail, and it told you: that is not fine.

But here is what you probably do not do—apply that same instinct consistently. You catch it with your partner because you know them. You catch it with your best friend because you have heard their "fine" a hundred times.

But what about your colleague who says, "the project is fine" in Monday’s meeting? What about the builder who says the work is "going fine"? What about the teenager who says school was "fine" every single day for three weeks? These things easily go unnoticed to the untrained ear and eyes.

That is where statement analysis becomes a life skill, not just an investigative tool.

The same principles that help police detect deception in a suspect’s statement help you hear what your teenager is not telling you. The same principles that help investigators identify what is missing from a witness account help you notice what your colleague left out of their project update.

You are not interrogating anyone. You are just listening—properly. Statement analysis helps untangle years of dulled listening. Suddenly, you hear what people are really saying: it is a whole new world...

The "Fine" Spectrum

Not every "fine" is a red flag. Context matters—and this is important because statement analysis is not about turning every conversation into an interrogation. Nobody wants to live with someone who analyzes their every word at the breakfast table. Trust me. I have tried. It does not go well.

So here is the spectrum:

• "How is the pasta?" — "Fine." This is probably genuine. The pasta is adequate. It is not exciting enough to describe and not bad enough to complain about. "Fine" here means fine.

  
  

• "How was the meeting?" — "Fine." This might be genuine, or it might mean "I do not want to relive the meeting." Listen for what comes next. If they elaborate ("Fine—we got the budget approved"), it was fine. If they do not elaborate, there is more.

  
  

• "How are you?" — "I am fine." If this comes with eye contact, a smile, and a change of subject to something positive, they are probably fine. If it comes with a flat tone, no eye contact, and silence afterward—they are not fine. They are telling you they are not fine by using the exact word that is supposed to mean they are.

  
  

The test is simple: does detail follow "fine"? If yes, the person is sharing. If no, the person is closing. Closed responses to open questions are always worth noticing.

What to Do When You Hear It

This is where the life skill part comes in. When you hear "I am fine" and you know it is not fine, what do you do?

The worst thing you can do is challenge it directly. "No, you are not. What is wrong?" That is confrontational. It backs the person into a corner. They said "fine" because they were not ready to talk. Telling them they are wrong does not make them ready—it makes them defensive.

The better approach—and this is straight from how analysts handle follow-up questions—is to give space and then ask something specific. Not "what is wrong?" but "what happened in the meeting with Sarah?" Not "are you sure you are okay?" but "you seem quiet—anything I can help with?"

Specific questions are harder to close down than open ones. "What is wrong?" gets "nothing." "What happened with the delivery?" gets an answer—because the person has to engage with the specific topic. You are not asking them to open the door. You are walking up to a specific room and knocking.

And sometimes? Sometimes the best thing to do is nothing. Let "fine" sit there. Make the tea. Be present. Because sometimes people say "I am fine" not because they are hiding something, but because they are not ready yet. The language told you something is there. You do not have to dig it up immediately. Just know it is there.

Statement analysis is not just for crime

I teach statement analysis. Most people assume that means I spend my days analyzing criminal statements and 911 calls. And I do—that is part of it. But the truth is, the principles I teach work everywhere. In every conversation you will ever have.

The builder who says the job is "basically done"—"basically" is doing a job there. The colleague who says they will "try to get it done by Friday"—"try" is doing a job there. Your teenager who says "nothing happened at school"—something happened at school. The language tells you. Every time.

You do not need to be a detective working on criminal cases to use these principles and learn statement analysis. You just need to start listening—really listening—to what people actually say. Not what you think they said. Not what you wanted to hear. What they actually, specifically, word-for-word said.

Because most people listen to words. The real skill is listening to language.

And the next time someone tells you they are fine? Listen to the silence that follows. That is where the truth lives.

Paul

Want to learn how statement analysis works? Visit *www.truth-unlocked.com for details of our online courses in statement analysis, and for individual and group tuition. Please email Paul for any further information: paul@truth-unlocked.com