Source · OIDA Cloud

# Observation 005: Knowledge Sharing and Information Architecture **Date:** October 10, 2025 **Observer:** Nora Chen (Co-lead Consultant, Meridian Labs LLC) **Location:** ClearPath Solutions Inc., Florence **Duration:** 4 hours (including informal interviews and document review) **Participants:** Interviews with 6 team leaders, 1 consultant, review of internal systems --- ## Context This observation examined how compliance-related knowledge and reference materials are shared across ClearPath. The goal was to understand whether consultants have systematic access to compliance standards, regulatory changes, internal methodologies, and best practices. ## Team Structure Identified During interviews, six team leaders were identified across ClearPath: 1. Marco Fiore (Audit Lead) 2. Laura Galli (Controls Assessment Lead) 3. Riccardo Boni (Reporting & Documentation Lead) 4. Chiara Lentini (Client Relations Lead) 5. And two additional leads whose names and portfolios were not fully clarified in the time available The organization matrix provided by Priya Anand (Head of Operations) listed a different structure, which is noted as a discrepancy for follow-up. ## Knowledge Repositories ### Internal Wiki (Defunct) ClearPath maintains an internal Confluence wiki that is intended to serve as a central knowledge base. The wiki contains: - Compliance standard summaries (ISO 27001, SOC 2, GDPR, etc.) - Internal process guidelines - Template library - FAQ section **Critical Finding**: The wiki was last updated in **March 2023** — nearly 2.5 years prior to this observation. Consultants are aware the wiki exists but do not trust it as a source of current information. During interviews, when asked about specific compliance updates, none of the consultants referenced the wiki first. ### Slack as Default Knowledge Channel Informal knowledge sharing occurs primarily through Slack channels: - #compliance-updates - #iso-standards - #audit-procedures - #client-templates However, this creates an ephemeral knowledge base. Information is easily lost or difficult to search retroactively. One consultant said, "I know someone mentioned the ISO 27001 2022 controls update in Slack... somewhere... but I can't find it now." ### Email-Based Distribution Regulatory updates and standard revisions are sometimes communicated via email to all staff. However, these emails are not systematically filed or indexed. ## Case Study: ISO 27001 Information Gap During the observation, a consultant (Luca) needed information about recent updates to the ISO 27001 standard. When asked where he would look, he responded: "Honestly, I'd probably email Marco [Fiore] or search Slack. But if neither of those works, I have a contact at a partner firm who might know — I'd ask them." When prompted, Luca did not reference the internal wiki as a first option. When I showed him the wiki article on ISO 27001, he noted it was last updated in 2023 and seemed skeptical of its reliability. **This represents a systemic knowledge gap**: internal compliance expertise exists but is not systematically documented or referenced. External contacts are treated as more trustworthy sources than internal systems. ## Positive Observations - When consultants do interact, knowledge transfer is direct and practical - The Slack channels exist and are used actively - Individual team leaders maintain up-to-date personal reference files (though these are not shared) ## Systemic Issues 1. **No single source of truth** for compliance standards and methodologies 2. **Knowledge is fragmented** across email, Slack, personal files, and a defunct wiki 3. **No systematic tracking** of regulatory/standard updates — changes are discovered ad-hoc 4. **Institutional knowledge is person-dependent** — if a team lead leaves, their knowledge goes with them 5. **External sources are preferred** over internal ones due to perceived currency ## Recommendations for Exploration 1. Assess why the wiki was abandoned and what barriers exist to maintaining it 2. Clarify the actual team structure (discrepancy between interviews and org chart) 3. Consider implementing a systematic standard monitoring process 4. Evaluate whether Slack should be replaced or supplemented with a searchable knowledge management system --- **Note**: Slight discrepancies were observed between the number of team leaders identified in this observation (6) and information provided earlier in engagement discussions. This requires clarification in follow-up meetings.

Observation 005 — knowledge sharing and information architecture

What was taken from it