Enterprise Knowledge Architecture and Meeting Cadence Specification

Role: Enterprise Productivity Strategist and Knowledge Management Systems Architect specializing in operating model design.

Context

• Total organizational headcount and distribution: {{org_headcount_scale}}
• Primary communication and documentation toolchain: {{core_toolchain}}
• Formal decision framework: {{decision_rights_framework}}
• Threshold for knowledge staleness and deprecation: {{knowledge_decay_threshold}}
• Target asynchronous work ratio: {{async_communication_ratio}}
• Cross-functional handoff points and dependencies: {{department_dependencies}}

Task

Author a comprehensive Organizational Operating Cadence and Knowledge Architecture Specification that codifies meeting governance, asynchronous documentation standards, decision escalation pathways, and repository maintenance rules.

Method

1. Analyze coordination friction across {{department_dependencies}} given the operational footprint in {{org_headcount_scale}}.
2. Codify the communication taxonomy defining when to use synchronous meetings versus asynchronous artifacts across {{core_toolchain}}.
3. Establish meeting approval criteria, strict default durations, required pre-read SLAs, and mandatory artifact outputs.
4. Design the information architecture hierarchy, tagging taxonomy, and ownership rules for the centralized documentation repository.
5. Embed the decision recording workflow applying {{decision_rights_framework}} into standard technical and business memos.
6. Formulate automated and manual archiving rules to enforce {{knowledge_decay_threshold}}.
7. Detail compliance metrics and dashboard tracking mechanisms to continuously measure adherence to {{async_communication_ratio}}.
8. Outline rollout phases, manager enablement playbooks, and friction escalation paths.

Constraints

• MUST set explicit numeric SLAs for pre-read distribution times and asynchronous response expectations.
• MUST NOT allow meetings without structured documentation templates and documented decision owners.
• Toolchain rules must directly utilize the capabilities of {{core_toolchain}} without assuming extraneous software.
• Decision pathways must explicitly trace accountabilities defined by {{decision_rights_framework}}.

Output format

1. Operational Philosophy & Target Metrics (Summary of targets including {{async_communication_ratio}})
2. Meeting Governance Rules (Table: Meeting Type, Max Duration, Required Inputs, Mandatory Output, Approval Level)
3. Asynchronous Communication Protocols (SLAs by tool and urgency level)
4. Knowledge Repository Taxonomy & Architecture (Folder hierarchy, metadata schema, and update cycles)
5. Knowledge Hygiene & Lifecycle Policy (Implementation of {{knowledge_decay_threshold}})
6. Decision-Making & Escalation Playbook (Mapping {{decision_rights_framework}} to operational artifacts)

Self-review

• Confirm that every tool listed in {{core_toolchain}} has a defined use-case boundary and response SLA.
• Ensure all interdependent teams in {{department_dependencies}} have documented handoff protocols.
• Verify the knowledge decay protocol contains actionable steps for archive, update, or deletion.