S2 Day 035Human & AI6 min readChinese original ↗

How much should I trust AI when it sounds right?

AI 说得头头是道,我该信它几分?
TL;DR
  • Before I ask AI anything, I first figure out what kind of question it’s answering: facts need checking, inferences need to keep their uncertainty, and value choices ultimately come back to me.
  • AI tends to tell people what they want to hear, following my story and my emotions toward ever more persuasive explanations. Feeling understood doesn’t mean my judgment has been confirmed.
  • How much I put into checking should match the cost of being wrong: for low-risk things I just try it, for important but checkable things I check the key evidence, and for hard-to-check, high-cost things I look for outside evidence and limit permissions.

I’ve been working with AI more and more lately, and it often feels like I’m driving a Ferrari.

It’s just so fast. Sometimes I only throw out an idea, and it comes back with a technical plan, writes the code, runs the tests, and does things I never would have been able to do on my own.

But I’m also starting to doubt whether I can actually handle it.

And this doesn’t only happen with development work.

These days I ask AI about almost everything, from financial planning and health to career choices and relationships.

It always comes up with an analysis that seems reasonable. But a lot of the time, I don’t have the expertise to tell whether those answers are right.

What makes it harder is that sometimes its answer happens to be exactly what I was hoping to hear.

If I can’t tell whether AI is right, how much should I trust it?

01. First, not every question has the same kind of “right”

I’ve found that before we can talk about how to trust AI, we have to be clear about what kind of question it’s actually answering.

The first kind: questions of fact.

Like what a particular bank policy is, what side effects a certain medication has, or what features a technical API supports.

These questions have facts that can be checked. For important information, I can ask AI for sources and then check the key evidence.

The second kind: analysis and inference.

Like whether someone not replying to a message means they don’t care. Or whether feeling tired lately is because I’m under too much stress.

AI can offer explanations, but it doesn’t have all the facts. A perfectly logical explanation can still rest on wrong or incomplete assumptions.

Here, what I need more is for it to tell me what other reasonable possibilities there are, not to rush to a conclusion.

The third kind: values and decisions.

Like whether I should change jobs, whether to spend more money on a better place to live, or whether a relationship is worth continuing.

Even if all of AI’s facts and analysis are correct, that doesn’t mean there’s one single best answer.

These questions also involve my preferences, my needs, and what costs I’m willing to bear.

Facts need checking, inferences need to keep their uncertainty, and value choices ultimately come back to me.

02. Why can an AI answer sound right and still not be reliable?

There’s another problem worth watching out for here: sycophancy, AI’s tendency to tell people what they want to hear.

In 2023, research from Anthropic found that in training with human feedback, answers that matched what the user already believed were sometimes preferred over answers that were more correct.

In April 2025, OpenAI also rolled back a GPT-4o update because the model had become overly sycophantic toward users.

The problem isn’t just that AI likes to flatter us.

It can also follow our story, our emotions and the judgments we’ve already made, and give us more and more persuasive explanations.

Say I tell it that someone’s behavior made me feel I don’t matter to them.

AI can understand how I feel, but it doesn’t know what the other person is really thinking.

If it goes further and interprets my feeling as proof that they really don’t value me, it may reinforce a judgment that hasn’t been confirmed.

Feeling understood shouldn’t be mistaken for having my judgment confirmed.

That’s why I increasingly want AI not just to back up my view, but also to point out other reasonable explanations and what I might be missing.

Of course, asking AI to argue against itself doesn’t guarantee the answer is right either. It just helps surface more of the uncertainty.

03. A framework worth borrowing from: NIST AI RMF

Later I came across the AI Risk Management Framework, published in 2023 by the US National Institute of Standards and Technology (NIST).

It was originally designed to help organizations manage the risks of AI systems, not as a guide for individuals using ChatGPT day to day.

But its four core functions are well worth borrowing:

  • GOVERN: Make responsibilities, rules and permissions clear.
  • MAP: Understand the context of use and what could go wrong.
  • MEASURE: Assess risk through testing, evaluation and evidence.
  • MANAGE: Decide how to control risk, take action and keep managing it over time.

These four are interconnected functions, not a checklist to follow in a fixed order.

It made me realize that judging whether AI is trustworthy shouldn’t only be about whether an answer is right, but also about how it might go wrong and what the consequences of a mistake would be.

Even if I can’t guarantee every answer is correct, I can still control how much I rely on it.

04. I can’t check every answer, so what do I actually do?

I think the cost of checking has to be part of the picture.

If every time I asked AI I had to read the official documentation, run a set of tests, or even find an expert, there wouldn’t be much efficiency gain left.

So how much I put into checking should match the cost of being wrong.

For low-risk things that are easy to undo, I can just try it.

Like recipes, study methods, simple tools. If it doesn’t work, I can try another way. There’s no need to rigorously argue it out every time.

For things that are important but can be checked, I check the key evidence first.

Like when AI recommends a particular technical approach, or cites a particular financial policy.

I can ask it for official sources and have it point out the most important assumptions and potential problems.

I don’t need to verify every sentence, but I should focus on the facts that, if wrong, would change the final decision.

For things that can actually be tested, I can also try them on a small scale first.

For things that are hard to check and costly to get wrong, I need to limit the risk of acting on them.

Like large investments, major medical decisions, or high-privilege operations on a production system.

In these cases, just asking AI to double-check a few more times isn’t enough.

I need more reliable outside evidence, and when necessary I should consult a qualified professional. For operations that can be done in stages, I try to limit permissions, narrow the scope, and keep a way to recover.

This doesn’t mean I have to go to an expert for every question I don’t understand. It means letting the risk decide whether the extra cost of checking is worth it.

05. Judging trust and checking the work are both skills built over time

My original question was: if I’m not enough of an expert, how do I check what AI produces?

Now I think I need to build two abilities at the same time.

One is judging trust.

Knowing which answers have solid factual grounding and which are just inferences; knowing when I can take an answer as is, and when I should stay skeptical.

The other is the ability to check.

Being able to turn important judgments into questions that can be verified, to look for independent evidence, and when needed, to check through testing, real-world feedback or professional help.

One doesn’t replace the other.

First I decide how to check based on the question and the risk, then I decide how much to trust based on the evidence I get. As I gain experience, I keep adjusting my judgment.

There’s one more thing I think matters a lot:

However expert AI’s analysis is, that doesn’t mean I have to hand all my judgment over to it.

Especially when it comes to what kind of life I want, how I understand my own feelings, and what costs I’m willing to bear. These things don’t always have a right answer that AI needs to approve.

Back to the Ferrari metaphor.

Of course I want to make the most of AI’s speed and get into more areas I wasn’t familiar with before.

But the faster it goes, the more I need to understand where its limits are, and when to slow down.

I can’t become an expert in every field, and I shouldn’t have to re-research every answer just to use AI.

What I hope to gradually learn is this:

Not to trust AI completely just because it sounds right, and not to be afraid of using it just because I lack the expertise.

To build a kind of trust, between evidence, risk and cost, that I can keep adjusting.

This may be one of the kinds of judgment we all need to relearn in the age of AI.

Written in Chinese and translated into English with the help of AI. Read the original