Knowledge Base Done Right

In Brief

Each financial company eventually codifies processes and proprietary knowledge. As companies grow, data stockpiles expand, creating significant costs when valuable insights remain inaccessible. During early digitalisation, corporations addressed this through file storage systems — a logical approach when command prompts were the primary interface. This mental model persists today, with major organisations like PWC, BNP Paribas, Audi, and Capital Group continuing to treat knowledge bases as organised file directories despite having access to superior alternatives.

Issues Caused by FTP-Alike Approach

• The search does not work at full capacity. Search functionality remains inadequate; while PDFs offer limited searchability, manual tagging and descriptions cannot compensate for fundamental limitations.
• Version control and instant updates are not available. Users download documents locally to circumvent poor search, missing critical updates and losing contextual discovery value available through online access.
• Collaboration barriers. Tools designed around file storage create silos between potential collaborators, forcing offline coordination and messenger-based draft sharing.
• Integration and interlinking barriers. Locally downloaded files disrupt the natural discovery flow that converts information into actionable knowledge within organisational networks.
• Higher risk of duplicates. Search inadequacy drives authors to recreate existing research rather than building upon established work.

The Solution

Knowledge bases require a wiki-based design approach rather than FTP folder methodology. Numerous open-source and commercial solutions exist. For organisations prioritising privacy, control, and custom features, building a custom wiki remains relatively straightforward. The straightforward and obvious choice could save numerous productivity hours and avoid the non-calculable loss of forgetting lessons learned.

Summary

Financial institutions commonly employ outdated file storage systems for knowledge management, resulting in weak search, absent version control, collaboration obstacles, integration limitations, and duplicative effort. Wiki-based approaches offer superior search capabilities, version management, and collaborative features, ultimately preserving institutional knowledge and enhancing productivity.