The Steps Needed for Knowledge Sharing

This article was automatically translated from Japanese by AI. Read the original Japanese version →

Table of Contents

October is almost over, and for those whose fiscal year starts in April, it's about the season to wrap up first-half retrospectives—how is everyone doing?

Speaking of retrospectives, looking around at people I know, it feels like surprisingly many set an annual goal like "we want to do more knowledge sharing as an organization." So today I'm going to ramble a bit about my thoughts on "knowledge sharing" based on my own experience. Just a heads-up: this isn't an academic or technical piece.

Shallow Thinking

For anyone working as part of a company or organization, "knowledge sharing" is an eternal challenge. I'm sure everyone has experienced working inefficiently because knowledge didn't cross team or project boundaries. Stories where multiple projects face the exact same problem, think about it separately, take different approaches, and both end up with mediocre results are everywhere.

Yet when someone declares, "Let's accumulate and share our know-how!", how often does it end up like this?

  • We spent time writing checklists and wikis, and nobody ever reads them.
  • We hold regular study sessions, yet it doesn't feel like they help with actual work (and nobody volunteers to present).

I'm guessing almost everyone has been through something like that.

So let's think a little deeper about it.

The ideal state we're aiming for is one where "knowledge is being shared, and as a result work gets done efficiently." What steps might lead up to that state?

Thinking Through the Steps to the Ideal State

For example, you could break it down like this:

  1. Understanding what others work on
  2. Recognizing others' areas of expertise
  3. Experiencing tangible benefits
  4. Building mutual trust
  5. Creating opportunities to collaborate

This isn't some established consensus or research by a famous expert—just something I thought up and named myself.

Let's look at each step one by one. For simplicity, the explanations below refer to "members," though the same applies to "projects" or "departments."

1. Understanding what others work on

First and foremost, members need to know "what each other is working on in the first place." Without shared context around the situation, hearing someone's know-how on its own won't be useful. To varying degrees, having everyone roughly aware of what others are doing is a crucial prerequisite.

2. Recognizing others' areas of expertise

This means each member recognizing that "other members know things I don't know." Sometimes simply understanding what others work on covers this automatically, though in most cases it takes sharing something a bit deeper. When people explain their day-to-day work to others, they usually don't go into that level of detail. You need opportunities that help people get a concrete sense of the skills and know-how required to do that work.

3. Experiencing tangible benefits

This is where members realize, "someone else's know-how actually looks useful for my work." Generally, this works best when members are doing somewhat similar work—which means setting up that kind of environment to begin with. For engineers, standardizing on the same programming languages or public clouds (like AWS or GCP) as much as possible is an obvious example. In a broader organization, sharing similar problems or working with the same stakeholders makes knowledge much easier to transfer. On top of that, people need to feel that benefit firsthand.

4. Building mutual trust

If people are actually going to share know-how, ask questions when needed, and collaborate, there has to be trust between members. There are plenty of theories out there on how to build trust as an individual, so I'll leave that aside—if you're tackling this as an organization, relying solely on individual effort isn't the right answer. Things like 1-on-1s, study sessions, and casual chats help, and having mechanisms where the organization recognizes individuals' achievements can also go a long way.

5. Creating opportunities to collaborate

You need to create actual opportunities where colleagues (or their knowledge) help with someone's work. Beyond the wikis and study sessions mentioned earlier, something like "asking a question in a Slack help channel and getting an answer" is a great example. And it doesn't have to stop at Q&A—there can be situations where someone actually jumps in and lends a hand. You need spaces where those interactions can happen casually.

Put another way, you should eliminate whatever gets in the way of those interactions as much as possible. The most obvious blockers are time and permissions.

To start with, packaging your knowledge for the organization or answering involved questions and consultations takes real effort. People buried in day-to-day tasks simply can't do it; everyone needs a certain amount of autonomy over how they spend their time.

Also, if project information can't be disclosed to other parts of the company, that project's know-how can't be shared either. Even just requiring a manager's approval makes it significantly harder. Conversely, having permission to browse other teams' code and documentation matters a lot—if you can look things up freely, asking questions and consulting becomes much smoother.

Summary

As I said at the beginning, what I wrote here isn't some framework invented by a renowned scholar. Still, I hope it got across that even though we casually lump it all under "knowledge sharing," there are actually distinct steps involved, and each one seems to call for a different kind of response.

As an engineer, it'd be tempting to follow this up by proposing measurable metrics for each step and building a dashboard!—but that would get pretty long, and honestly I haven't found a great way to do it myself yet. If I come up with a good approach, I'll write another post about it.