Knowledge Base Management

Documents knowledge about game systems in wiki/Confluence: mechanic descriptions, balance rules, design decisions. Creates structured entries about game design decisions with rationale. Uses templates for standardizing the knowledge base.

Maintains product knowledge base in Confluence/Notion. Documents decisions, specs, meeting notes. Keeps documentation up to date.

Understands the importance of structured knowledge management for a technical product. Can create and maintain documents in Confluence, Notion or similar tools. Knows principles of knowledge base organization for a technical team.

Creates a structured knowledge base for the game design team: design patterns, balance formulas, postmortem insights. Organizes knowledge sharing: design reviews, brown bag sessions, retrospectives. Ensures searchability and documentation currency.

Builds the knowledge base structure for the product. Defines information architecture. Ensures knowledge accessibility for the team.

Independently designs knowledge base structure for the product: architecture docs, runbooks, decision logs. Defines information architecture for different audiences — developers, TPMs, stakeholders. Maintains freshness.

Designs knowledge management system for game design: taxonomy, tagging, cross-referencing. Creates living documents that update alongside the project. Implements lessons learned and postmortem processes for accumulating knowledge between iterations.

Builds knowledge management practice for the product line. Standardizes documentation processes. Implements docs-as-code.

Builds knowledge management strategy for the product. Implements docs-as-code approach for technical documentation. Defines lifecycle management for documents: creation, review, deprecation. Integrates with dev workflows.

Defines knowledge management strategy for the game design team. Establishes documentation processes: GDD templates, balance decision logs, design rationale. Ensures knowledge transfer during new designer onboarding and between projects.

Defines knowledge sharing strategy for the division. Ensures cross-team knowledge transfer.

Defines knowledge management standards for the division. Introduces cross-team knowledge sharing practices. Shapes information architecture for 10+ products. Evaluates knowledge base health metrics.

Shapes enterprise knowledge management for the studio: shared game design knowledge, cross-project learnings, industry best practices. Creates institutional memory for the game design organization. Defines tools and processes for large-scale knowledge sharing.

Shapes organizational knowledge management strategy. Defines investments in knowledge infrastructure.

Shapes enterprise knowledge management strategy. Defines unified information architecture for the organization. Integrates knowledge bases with developer portal, onboarding and training programs. Evaluates impact on productivity.