Why Does Our Team's Documentation Fail? (1)

Many organizations recognize the need for documentation, but in practice it often fizzles out within a month. This is because documentation is seen as work for the 'future' rather than the 'present,' causing it to be pushed down in priority.

The problems by organization type identified through interviews are as follows.

• Domain organizations: Knowledge is fragmented, creating bottlenecks when searching for policies or information during collaboration, and during onboarding, the state of 'not even knowing what you don't know' persists.
• Functional organizations (chapters): There is significant unnecessary resource consumption from digging through messengers or directly tracking down the author to find history that isn't explained by the code alone. Additionally, due to the psychological hurdle around knowledge sharing, individual knowledge fails to accumulate as organizational assets.

Ultimately, the core of documentation is not simply writing text, but identifying gaps in knowledge and building the environment and systems that allow members to share knowledge.