I had a patient years ago who was a farmer. He came in cracking jokes, and every so often he'd offer a piece of farm wisdom.
One day he asked me, "Doc, do you know the difference between knowledge and wisdom?"
I told him I did, but I wanted to hear his version.
"Knowledge is knowing a tomato is a fruit. Wisdom is knowing not to put a tomato in a fruit salad."
That's stayed with me for years, because it's the cleanest description of that difference I've ever heard. Knowledge is the fact. Wisdom is knowing what the fact means in practice.
What Does "A Bee Is Faster Than a John Deere Tractor" Teach?
A while later I went looking for more of that kind of thinking, and found a list of farm sayings online. I sat there laughing out loud at how simple and how right they were.
One in particular stopped me: **a bee is faster than a John Deere tractor.**
That's it. That's the whole statement.
Think about the difference between how a scientist and a farmer approach that. A scientist wants to know the bee's maximum velocity, its flight trajectory, its rate of turn, the horsepower of the tractor, and the conditions under which the comparison holds.
The farmer's position is that none of that matters if you don't know the bee is faster. What matters is that you get off the tractor and take cover, because you don't want to get stung.
Both approaches have value. The failure mode is getting so deep into the detail that you lose sight of the plain statement that summarizes the whole thing.
Why Does This Matter for Understanding Your Own Condition?
That's the standard I've tried to hold in my own work with mild traumatic brain injury, and it's the standard I'd suggest you hold for any explanation you're given about your health.
**A proposed explanation should make plain sense first.** You should be able to hear it and think, yes, that follows. Then the scientific work is testing whether that plain-sense observation holds up under scrutiny — measuring it, checking it against the research, seeing whether it predicts what actually happens in real cases.
Both halves are necessary. Plain sense without testing is just a guess that sounds nice. Testing without plain sense produces detail nobody can act on.
But notice the order. The plain-sense version comes first, and the detail confirms or refutes it. When an explanation can only be expressed in a form nobody can follow, that isn't automatically a sign of sophistication. Sometimes it's a sign that the underlying idea doesn't hold together.
What Should You Listen For?
Here's the practical version of this.
If you've been given an explanation for your symptoms, ask yourself whether you could repeat it to someone else and have it make sense to them.
"You have a chronic condition, and we'll manage it" isn't an explanation. It's [a plan without a reason](post-why-managing-symptoms-is-not-the-same-as-healing.html). **Why** is it chronic? What is producing the symptom? What would have to change for it to stop?
Those questions have answers, or they have an honest "we don't know yet" — and both of those are acceptable. What isn't acceptable is a description of your symptoms handed back to you with a label on it and presented as understanding.
A real explanation connects a cause to an effect in a way you can follow. If your [headaches](condition-headaches.html) come from irritation of a specific structure at the top of your neck, [that can be explained to you in two minutes](post-why-head-and-face-pain-often-starts-in-the-neck.html), and you should be able to explain it to your spouse afterward. If your [dizziness](condition-dizziness.html) comes from your position sensors and your inner ear disagreeing about where your head is, same thing.
You don't need to be a clinician to evaluate whether an explanation actually explains something.
What Do I Try to Do With This?
When someone comes in, my job is to distinguish. Is this congenital or traumatic? Is it coming from the neck or somewhere else? Is it one origin or several? That distinguishing work is where most of the effort goes, and the clearer the roots of a problem become, the better the chance of a complete outcome.
Not every time. I wish it were every time. But considerably more often when the source is actually identified.
And when I can see there's a problem, can see roughly what system it's in, but don't know what question to ask next — my job is to send you to whoever does know. I'd rather say that plainly than perform certainty I don't have.
The one thing I try not to do is hand someone a complicated non-answer and let them assume the complexity means it was understood.
You should be able to understand your own problem about as well as the person treating it does. If you can't, it's fair to ask why.
Has Anyone Actually Explained Your Condition to You?
If you've been managing symptoms for years without anyone explaining where they come from, that isn't a dead end. It's a question that hasn't been asked yet.
Finding the root and explaining it in terms you can follow is the work we do at Cerebral. If you'd like a real evaluation, we're here.