Department-Specific Design
A marketing team's AI needs are fundamentally different from an engineering team's. Generic AI training wastes time covering irrelevant use cases while skimming the ones that matter. Role-specific playbooks solve this by providing each department with documented AI workflows, prompt templates, tool recommendations, and best practices tailored to their specific tasks. These playbooks become living reference materials that teams use daily, long after training ends.
Department-Specific Workflows
Each playbook maps AI workflows to the tasks that department actually performs. Marketing playbooks cover content creation, SEO research, campaign analysis, and social media management. Engineering playbooks cover code review, documentation generation, debugging, and architecture discussion. Sales playbooks cover prospect research, email personalization, objection handling, and CRM data enrichment.
Reference Materials
Playbooks include quick-reference cards for common tasks, decision trees for choosing the right tool and approach, troubleshooting guides for when AI output misses the mark, and a glossary of AI terminology relevant to that department. These materials are designed to be consulted in the moment of need, not read cover-to-cover.
Prompt Templates
Each playbook includes tested prompt templates for the department's most common AI tasks. Templates include placeholders for variable inputs, instructions for customization, and notes on which model works best for each template. Teams can use templates as-is for speed or modify them for specific situations.
Tool Recommendations
Different roles benefit from different tools. Developers need Copilot and a reasoning model for code. Marketers need ChatGPT or Jasper for content. Analysts need strong long-context models for document processing and data interpretation. Each playbook recommends the optimal tool stack for that role with rationale and setup instructions.
Playbook Development
Interview
Map daily tasks by department
Design
Create role-specific workflows
Template
Build and test prompt libraries
Deliver
Distribute and train on usage
Interview
Map daily tasks by department
Design
Create role-specific workflows
Template
Build and test prompt libraries
Deliver
Distribute and train on usage
Playbook Development Pipeline
Playbook Contents
Every playbook follows a consistent structure while containing completely different content. Each begins with a department overview that identifies the top ten AI use cases ranked by time saved and quality improvement. Then it walks through each use case with a step-by-step workflow, recommended tools, prompt templates, example inputs and outputs, and common pitfalls to avoid.
Playbooks also include an escalation guide: when AI is sufficient for a task versus when human expertise is required. This prevents the two most common failures, using AI for tasks where it produces unreliable results, and avoiding AI for tasks where it excels.
Playbooks are living documents. We deliver them in editable formats (Notion, Confluence, Google Docs, or Markdown) so your team can update them as tools evolve and new use cases emerge. Initial delivery includes a maintenance guide explaining how to keep playbooks current.
Example Playbooks
For a marketing team, the playbook might include workflows for blog post creation from keyword research through drafting and SEOoptimization, social media content calendars with AI-generated variations, competitive analysis using AI to process competitor content, and email sequence optimization. For an engineering team, it might cover pull request review automation, documentation generation from code, incident postmortem analysis, and architecture decision records.
Who This Is For
Role-specific playbooks are ideal for organizations with multiple departments adopting AI simultaneously. They work best when combined with hands-on workshops where teams practice using their playbooks. L&D leaders, department managers, and operations teams responsible for standardizing AI usage across the organization benefit most from investing in documented, role-specific AI guidance.
Contact us at ben@oakenai.tech
