A résumé lands on the table with "20 years of experience" printed near the top. In a New York or London hiring meeting, that line often does half the work by itself. In a Japanese owner-manager's office, it rarely does. Business still prizes people described as "experienced." Stacking years, though, does not by itself produce growth. Experience carries no automatic worth. What matters is what you drew from it, and what you did with that lesson the next time you sat down to decide. This essay looks at why celebrating or mourning the result is the wrong habit — and how the executives who actually compound skill put a lived year to work.
Why Does Experience Itself Have No Value?
Experience is not a spell that grows a person on its own. If you take the knowledge and methods of year one and run them unchanged for ten years, you have not lived ten years of experience. You have lived one year, ten times. A long tenure can still produce almost no new lesson if the same pattern is simply copied forward.
The reverse is also true: some people with few years on paper grow unusually fast. The difference is how they read the experience. Two people can sit through the same event; only one of them pulls a usable lesson from it, and their later work diverges. The years themselves are not the prize. The prize is the meaning you assign to what happened, and the next action that meaning produces.
This way of reading a career is uniquely Japanese, and it is easy for a Western hiring culture to miss. In the United States and the United Kingdom, "years of experience" is a résumé field: ten years in acquisitions, twelve in asset management, a number that stands in for competence before anyone has heard the candidate speak. A Western reader who has heard of nenko (年功) — promotion by years of service — may assume Japanese firms simply count tenure too. That is half the picture, and the wrong half for an owner-manager. In a closely held Japanese company, keiken (経験) is closer to a judgment ledger than a calendar. The years only count if they changed the next call. If you ran the same leasing playbook for a decade and never altered a clause, they do not hear "ten years of experience." They hear one year, repeated. For an overseas operator sitting across from a Japanese partner, that is the first mismatch to name: tenure is not the credential; interpretation is.
How Do You Learn from the Process Without Getting Trapped by Success or Failure?
Cling too hard to the labels "success" and "failure," and you will miss the lesson sitting inside the work. The process matters more than the result. A plan that did not hold can be filed as a simple miss — or booked as material for the next attempt. Those two choices produce very different later years.
A miss hurts. It also hides a large number of seeds. The work of asking why the result did not appear, and of designing a better next step, is itself the path to the next win. Success needs the same treatment. Even when a deal closes, you still have to ask why it closed, or you cannot carry the method forward. Conditions change; last year's winning pattern can stop working. The habit of learning from what you have just lived — after a win as well as after a miss — is what compounds into long growth.
A second mismatch shows up the moment a deal is scored. In a US private-equity shop or a UK property fund, the scoreboard is the IRR, the occupancy, the exit. The meeting after a miss is often a post-mortem with a quiet subtext: who is accountable. Japanese owner-managers are not indifferent to the number. They are slower to file the episode as success or failure, because they treat the lived judgment itself as something that can be booked — almost as an asset class. The partner who can say, "we underwrote this tenant mix in 2019, the corridor stayed empty, and here is the clause I will not sign again," is holding an asset the spreadsheet does not show. If you are investing alongside such a person, that pause after the result is not indecision. It is the conversion of a year into a rule you can use on the next building.
How Do First-Class Executives Put Experience to Work?
How do the better operators and business leaders actually read what they have lived through, and how do they put it to work? Their stories offer a few working hints for turning a raw episode into something you can spend.
The Idea of Turning Failure into an "Asset"
Thomas J. Watson Sr., the first president of IBM in the United States, left a well-known story. A member of staff made a serious error and cost the company a large sum. Watson did not fire the person. He said, in effect, "You have just paid a high tuition fee," and treated the miss as material for that person's later work. The habit of treating an episode as an investment, and banking it for later use, shows up again and again among serious leaders.
A Culture of Constant Review and Continued Learning
At Toyota Motor Corporation, and at other Japanese firms of that standing, a project is not finished when the deliverable ships. The team sits down and names what went well, what must change, and what will be done differently next time. That habit has a name in Japanese management: hansei (反省), structured reflection. It is not the same as a Western "lessons learned" slide produced after a loss. Hansei is supposed to happen after ordinary work, including work that succeeded. The point is a mechanism: the lesson has to reach the next job, not stay in the room. At the personal level, a surprising number of leaders still keep a daily note of what they noticed, then review the week at the weekend.
Leaders Who Turned Adversity into Fuel
Steve Jobs was forced out of Apple, the company he had built. He accumulated a second body of work at other firms, then returned to Apple carrying those lessons and that craft, and the later run is now a matter of record. It is a clean example of the claim at the center of this essay: the event itself does not decide the next chapter; the reading of the event does.
Five Hints for Turning Experience into Something You Can Use
- Keep a regular review habit. At the weekend, or when a project closes, write down what went well, what did not, and what you learned. The act of writing is what turns a week into a usable note.
- Bank the miss. Once the feeling has settled, analyze it in the cold. Ask why it failed, and what you will do the next time the same situation appears.
- Do not settle into a win. Some wins are luck, or a market that happened to run your way. Ask why it worked, and whether the method can be repeated.
- Learn from other people's years. Talks with people further along, and books or essays, are a way to borrow experience you have not yet had to live.
- Hold a growth mindset. Walk into each episode on the assumption that it contains a usable hint. That is not optimism as a mood. It is a working rule.
Frequently Asked Questions (FAQ)
Q. Why do I not feel myself growing, even with many years of experience?
Because the years are being repeated rather than reviewed. The same pattern, run without a look back, produces tenure without a new skill. A regular review, followed by one changed action, is how a year becomes growth instead of a reprint.
Q. What is a concrete way to learn from a failure?
Break the miss into 5W1H — who, what, when, where, why, and how — and list the fixes. Then write the action you will take if the same situation returns. Preparing that plan before the next round is more useful than a general vow to "do better."
Q. What is a growth mindset?
It is the belief that ability can be stretched by effort and by learning. The contrasting idea is a fixed mindset: ability is given at birth and does not move. A growth mindset raises the odds that a person will take the next challenge rather than protect the current one.
