Dominio
Documentation
Perfil de habilidad
User documentation: user guides, tutorials, FAQ, onboarding docs
Roles
4
donde aparece esta habilidad
Niveles
5
ruta de crecimiento estructurada
Requisitos obligatorios
10
los otros 10 opcionales
Documentation
User Documentation
17/3/2026
Selecciona tu nivel actual y compara las expectativas.
La tabla muestra cómo crece la profundidad desde Junior hasta Principal.
| Rol | Obligatorio | Descripción |
|---|---|---|
| Game Designer | Creates user documentation for the game: tutorial texts, help screens, FAQ, mechanic descriptions for players. Writes clear instructions: how-to guides, control references. Considers different player skill levels when writing help content. | |
| Product Manager | Obligatorio | Understands the importance of user documentation. Helps write help articles and FAQ. Knows UX writing basics. |
| Technical Product Manager | Understands the role of user documentation for a technical product. Knows documentation types: quickstart guides, tutorials, reference docs, FAQs. Can review documentation for accuracy and completeness. | |
| Technical Writer | Obligatorio | Understands user documentation principles: clarity, task-oriented approach, progressive disclosure. Knows user doc types: getting started, tutorials, how-to, reference. Can write step-by-step instructions for end users. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Game Designer | Designs in-game documentation system: contextual help, tooltips, codex/bestiary, tutorial system. Creates player-facing documentation for community: patch notes, dev blogs, game guides. Writes user documentation considering player journey and discovery. | |
| Product Manager | Obligatorio | Defines requirements for user documentation. Coordinates tech writers. Ensures documentation coverage for all features. |
| Technical Product Manager | Defines user documentation requirements for a technical product. Coordinates documentation creation for developer and end-user audiences. Reviews documentation for technical accuracy and user-friendliness. | |
| Technical Writer | Obligatorio | Creates comprehensive user documentation: information architecture, content hierarchy, cross-references. Writes for different audiences (beginners, advanced users, admins). Uses user feedback to improve documentation. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Game Designer | Designs comprehensive in-game knowledge system: dynamic tutorials, progressive disclosure, mastery guides. Creates community documentation strategy: wiki, guides, API docs for modders. Implements metrics-driven approach: tracks which help resources players use. | |
| Product Manager | Obligatorio | Shapes documentation strategy for the product. Integrates docs into the product release process. Ensures self-service support through documentation. |
| Technical Product Manager | Shapes documentation strategy for the product. Defines content architecture considering user journeys. Implements metrics: time-to-resolution, doc usage, search success rate. Coordinates docs with product releases. | |
| Technical Writer | Obligatorio | Designs user documentation strategy: content model, localization, accessibility, multi-product navigation. Creates interactive documentation: embedded walkthroughs, contextual help, in-app tooltips. Implements analytics for measuring effectiveness. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Game Designer | Defines documentation strategy for the game project: in-game help, community resources, developer documentation. Establishes writing guidelines and tone of voice for player communication. Coordinates documentation with community management and marketing. | |
| Product Manager | Obligatorio | Defines documentation standards for the division. Establishes a tech writing practice. |
| Technical Product Manager | Defines documentation standards for the division. Introduces docs-as-product approach with user research and iteration. Shapes documentation team structure and processes. Measures documentation quality with customer feedback. | |
| Technical Writer | Obligatorio | Defines user documentation standards for the organization. Coordinates localization into multiple languages. Establishes quality and effectiveness metrics. Builds feedback loops with product and support teams. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Game Designer | Shapes enterprise documentation strategy for the project portfolio. Defines shared documentation tools, templates, processes. Creates player communication methodology for the studio. Evaluates AI-assisted documentation and auto-generated help content. | |
| Product Manager | Obligatorio | Defines content strategy at the company level. Shapes developer experience through documentation. |
| Technical Product Manager | Shapes enterprise documentation strategy. Defines unified content platform. Integrates documentation with developer portal, support and training. Builds docs-driven customer success program for technical products. | |
| Technical Writer | Obligatorio | Shapes customer-facing documentation strategy at the company level. Determines investments in documentation tools and team. Ensures documentation supports product adoption, customer success, and self-service support. |