Accessing Know-How Is Not the Same as Creating It

💡 Key takeaways
Access to global know-how is a major advantage. But in my experience, when you work in a local organization, the innovative, know-how-heavy projects outside the daily routine often come from headquarters.
The real difference is the authority to decide. Implementing a ready-made system and defining a problem and building its solution from scratch teach different things.
Company size alone is not decisive. What matters is how close you are to the table where knowledge is created, and whether the team has the authority and resilience to carry that work.

At a company I worked for before, we used to discuss how systems created at the German headquarters should be adapted to local products, along with the integrations and translations they required.

Of course, we also had to take local action.

But outside the routine day-to-day work, if there was a project that stood out, could reasonably be called innovative, and required enough know-how to make people say “wow,” it usually came from abroad—from higher up in the organization.

That does not mean the work done locally was unimportant. Running a global system properly in a local market is difficult work in its own right. And learning from problems already solved and standards built over many years is a major advantage.

But the fundamental questions had often already been answered:

What are we going to build? Why will it work this way? What principles will guide our decisions?

The question on our table was more often this:

How will we make this work here? How will we adapt it to the content of our products?

Knowledge applied, knowledge created

At Vanity, I had the opportunity to design and build many systems from scratch. I also contributed here and there to other systems built by my teammates.

This time, we were not simply learning how to use a system. We were defining the requirement, seeing what worked and what did not, and making the next decision ourselves.

That is where the difference between accessing know-how and producing it became clear to me.

Not the company logo, but the design of the work

Research also suggests that the difference I experienced cannot be explained by company size alone.

A study of 374 subsidiaries across 75 multinational corporations found that knowledge existing at headquarters is not enough, by itself, for that knowledge to reach a local team. The quality of communication, the local team’s motivation to acquire the knowledge, and its ability to use it also matter.

In short, a large body of knowledge at headquarters does not automatically turn into capability in the local team. Accessing know-how and internalizing it are not the same thing.

A systematic review of 85 studies points in a similar direction: having a say in your work supports learning. Simply facing a difficult task is not enough. Being able to decide how to move it forward matters too.

This does not mean that early-stage companies are always more educational. The narrower conclusion, at least for me, is this: what teaches you is not only difficult work, but having the authority to make decisions within it. That was the difference I experienced at Vanity.

A local team is not always just an implementer

Local teams in multinational companies do not have to be mere implementers either.

A 2018 study of 563 subsidiaries in six Central and Eastern European countries found that greater decision-making autonomy in a local unit was associated with a higher likelihood of product innovation.

GE Healthcare offers a concrete example. According to GE’s own account, the Lullaby baby warmer, developed in Bengaluru around India’s needs, was later sold in more than 80 countries. The local team did not simply translate a product that came from headquarters. It turned a local problem into a solution that could be used globally.

So the point is not that global companies are bad and early-stage companies are good. The point is where knowledge is created within the organization, and how close you are to that point.

Do not romanticize early-stage companies

Early-stage companies should not all be romanticized either. A system not yet being in place can mean real responsibility and a broad space to learn. It can also mean there is no guidance and everyone is trying to finish ten disconnected jobs at once.

A study using employee records from Denmark found that startup employees earned roughly 17 percent less over the following decade than people who joined large, established companies. Around half of that difference was explained by differences in the startup employees’ initial characteristics.

The study does not measure learning, and it is based on only one country. Still, it challenges one comfortable assumption: more responsibility does not always lead to a better career outcome.

Uncertainty alone is not learning. Chaos is not ownership either.

The right question for me

When I look at a job opportunity now, I try to understand these things before I look at the company’s name:

Will I be adapting a ready-made system, or will I also contribute to defining the problem?
Which decisions does the local team get to make?
Will I be able to own a piece of work end to end and see its result?
Are there strong people I can learn from, and is there regular feedback?
Does the company have the financial and operational resilience to carry these experiments?

Implementing a ready-made system teaches scale, quality, and the discipline of standards. Building from scratch, under the right conditions, teaches judgment, prioritization, and taking responsibility for outcomes.

Both are valuable.

My personal preference, when the conditions are reasonable, is to be close to the table where knowledge is not only transferred but created.

My point is simple: you do not have to work for a global giant. At an early-stage company with the ambition to become a global leader in its field, you may have the chance to do far more important work.