The #1 Lesson of My Early Career: Everyone Cares. Few Care Enough.

Ask any leader if their team cares, and they'll likely say yes. I would have too. Then, at 24, a customer in Japan taught me the difference between caring — and caring enough. It was based on an philosophy the company lived by. It reshaped how I've led ever since.

I was 24 years old, sitting on the floor in a traditional Japanese meeting room at a table about 16 inches high, ready for my anticipated 10 hour meeting. Suit and tie. No A/C. Sweating. Could barely feel my legs. But I was confident — for the first time on this project, every single validation test had passed. I had no idea I was about to learn the one life-changing lesson that would define the rest of my career.

At the time I was a global lead project engineer for driveline systems, working with one of the most demanding customers our business had ever served. The global program launched in the Thailand, U.S., Brazil, and South Africa, and the customer was anchored in Japan — which meant trip after trip to present data to Toyota.

Their test plan was the hardest we'd ever faced. They were so relentless that they didn't adopt our design specs — we rewrote ours to match theirs. They were the standard.

So when we finally passed — after months of failing, redesigning, and failing again — I flew to Japan feeling like I was bringing good news for once. I walked through that lobby, shared our formal greetings, sat at that low table, and presented the program status including all the test results.

Then the room went quiet, and the Japanese engineers talked among themselves in Japanese for a while. My liaison finally turned to me: "Toyota has a question. For a particular test, you have six results. Four are comfortably above the line. One is a little higher. One is much higher. Why did the parts perform so inconsistently?"

We'd passed. But I couldn't explain the reason why the data fluctuation behaved the way it did.

That night at dinner, my liaison told me the part that changed everything. Toyota wasn't impressed that we passed. They were disappointed — not by the result, but by my inability to explain the inconsistency. And then they taught me something I'd never heard:

In Toyota philosophy, there are only two reasons things fall short.

The first is that you genuinely couldn't have known — some unpredictable, unknowable factor. (an example being the original Tacoma Narrows Bridge in Washington state, which tore itself apart in 1940 in unpredictable winds no one had modeled for.) That kind of failure is rare, and forgivable.

The second reason is that somebody in the chain didn't care enough.

That one hit me hard. I take real pride in caring — about my work, my family, my name. So hearing, even indirectly, that I "didn't care" was genuinely insulting. But I normally don't react fast. I sit with things. Reflect. And the more I sat with it, the more I understood what they actually meant.

And this wasn't motivational fluff — it was the byproduct of rigor. Toyota are the inventors of modern root cause analysis: the 5 Whys, developed by Sakichi Toyoda in the 1930s and later formalized into the Toyota Production System — the same DNA that runs through Kaizen, Lean, and Six Sigma, the disciplines I build my coaching tools around today. And what decades of that discipline revealed is this: when you trace almost any failure to its root — past the operator, past the designer, past the part — you usually arrive at the same outcome. Someone, somewhere, didn't care quite enough.

So I tested it. For days, weeks and months, then years, I held that idea up against basically everything that went wrong around me — at work and outside of it. Yes, luck exists. Yes, the universe throws curveballs. But far more often than I was comfortable admitting, the root cause could be traced back to care.

That's when I stopped seeing "I care" as a feeling and started building it as an Identity. And that's when I really started to rise.

Because when you truly care enough, you're two or three steps ahead. You anticipate the question before it's asked. You apply the resilience to dig a few "why's" deeper when everyone else has assumed its time to move on. You don't hand someone a number you can't explain — you go back, you challenge it, you understand the story, so you can tell the story.

The distinction that matters isn't caring vs. not caring. Almost everyone cares. It's caring vs. caring enough.  Caring enough is a distinguisher.

·         Caring accepts the budget you're handed. Caring enough asks why it costs what it costs and whether it can be better.

·         Caring drops the plant's numbers into the deck. Caring enough digests them, challenges them, and understands the story well enough to defend it.

·         Caring passes the test. Caring enough can explain every data point on the chart.

Here's the uncomfortable part: I think we've quietly lost this. We've gotten very good at dumping the data and moving on. "This is what they gave me." "Everything passed — why dig further?" The gap between those two columns above is exactly where most of a team's potential quietly leaks out.

So this is the only thing I want you to practice today — at work or at home. Pick one thing on your plate and ask yourself one honest question:

Did I care enough to cover the angles?

Not did I care. You did. Did you care enough. That single distinction is, in my experience, the difference between good people and the great ones.

If you're a leader who wants to build this into how you and your people operate — or you're ready to invest in your own growth — that's exactly the work I do.  You can reach me at coachsal@elevatebybeing.com or book a Discovery Call. I'm taking on new clients.