How to say “Refer to undocumented knowledge” professionally

“Refer to undocumented knowledge”

Say this insteadLV.1 Professional

“To ensure consistency and scalability, could we consider formally documenting this process for future reference? I can provide the information I have, but having it captured in a central repository would be beneficial for the entire team.”

SafeUnhinged

The Anatomy

The chain of dysfunction that forced you to say this.

Tap to expand

The Multiverse

You said one thing. Everyone heard something different.

YOUR INTENT

This information is tribal, a ticking time bomb, and I'm tired of being the human database for a process you should have documented ages ago.

YOUR BOSS'S READ

You're saying you know it but are too busy to share. Classic gatekeeping. I'll just ask someone else, or maybe delegate documenting it to you.

PM'S READ

Opportunity to create a new 'documentation initiative' project for Q3, adding 3 sprints to the roadmap and requiring a new budget line item for 'knowledge architect' software.

HR'S READ

A valuable team member identifying areas for 'knowledge transfer optimization' and 'institutional memory preservation.' Let's create a new training module!

How to say "Refer to undocumented knowledge" to your boss

Level 1: To ensure consistency and scalability, could we consider formally documenting this process for future reference? I can provide the information I have, but having it captured in a central repository would be beneficial for the entire team.

Level 2: This specific insight currently resides within our operational experience rather than a formal repository. I can share my understanding, and perhaps we can initiate a process to capture this critical institutional knowledge systematically.

Level 3: Per the unwritten tenets of our organizational folklore, I believe this information exists within the collective consciousness of those who have survived previous iterations of this project. I'm happy to perform an archaeological dig through my personal archives, but perhaps we should update the 'Knowledge Base' section of our JIRA tickets beyond just 'TBD'.

Level 4: While I can provide this information from my personal experience, it's critical that we document such core processes. Relying solely on individual memory introduces significant risk and impedes new team member onboarding, which could impact project timelines and our overall efficiency.

Level 5: It's in my head. Find it there.

How to say "Refer to undocumented knowledge" to your client

Level 1: This specific detail isn't included in our formally documented deliverables or specifications for this engagement. Could you provide any existing internal documentation or context from your team's side that might help?

Level 2: While this particular insight is not part of our current documented scope or previous handover materials, we can certainly explore how best to acquire or formalize this information, potentially as a follow-on engagement after a formal scope review.

Level 3: Ah, yes, the mystical knowledge residing beyond the bounds of our Statement of Work and official project documentation. We specialize in deliverables, not clairvoyance, but perhaps we can draft an addendum to define the scope of our telepathic services.

Level 4: The information you're requesting is not formally documented within our agreed project scope or deliverables. To proceed, we would require formal documentation from your team, or this would need to be scoped as a new engagement and potentially incur additional costs.

Level 5: Not in the contract. Pay more.

How to say "Refer to undocumented knowledge" to your coworker

Level 1: This particular detail isn't formally documented in our shared resources, but I can share my understanding of it. Perhaps we could add it to our team's wiki for future reference to help everyone?

Level 2: While it's not currently formalized in our shared documentation, I'm happy to walk you through it based on my experience. We should consider logging this in our team wiki to ensure everyone has access.

Level 3: Ah, yes, the sacred texts of 'how we do things around here,' largely passed down through whispered anecdotes and ancient Slack threads. I'll translate the oral tradition for you this time, but maybe next we can consult the Ouija board to divine the 'official process'.

Level 4: This information currently relies on individual experience rather than a documented process. Moving forward, for critical operational steps, we need to ensure it's captured in our official guides to prevent repeated inquiries and ensure consistency across the team.

Level 5: Ask the ghosts of projects past.

The Decoder's Analysis

In corporate settings, the need to reference undocumented knowledge often arises when project scope boundaries are unclear or when effective delegation and workload management are lacking. Professional communication requires individuals to articulate when information critical to a task is not readily available, prompting the establishment of clearer processes. This ensures operational efficiency and prevents reliance on individual 'tribal knowledge,' which can hinder scalability and create bottlenecks.

When to use this

USEWhen a colleague or manager asks for information that is critical to a task but has never been formally recorded.

USEWhen onboarding new team members who struggle to find essential process details because they only exist as tribal knowledge.

USEWhen a project's progress is stalled due to a dependency on uncodified institutional memory.

AVOIDWhen you actually possess the information and could easily provide it, but choose to withhold it to appear superior or avoid work.

Related Deflections

More deflections coming soon.

Also searched as

professional way to say tribal knowledge