Free corporate training agendas
Claude Code, Codex and role-specific AI workshop agendas.
Start with a three-hour applied session or a full-day adoption workshop. Choose an engineering, DevOps, CRM, sales, marketing, business, leadership or production AI track, then adapt the labs to your approved tools and real workflows.
The design rule
Every session ends with work the team can reuse.
The workshop is organized around an approved workflow, a quality standard and an adoption decision. Participants leave with a completed task, reusable instructions, a review checklist and named next actions, not only a list of features.
Choose the track
One operating method, adapted to the real work in each role.
01
Claude Code and Codex for engineering teams
For Developers, tech leads, QA and platform engineers
- Explore unfamiliar repositories and turn requirements into bounded plans
- Use repository instructions, permissions and review gates consistently
- Debug, refactor, create tests and document changes with evidence
- Evaluate tools on accepted work, review burden, defects and cost per task
02
AI-assisted DevOps and incident response
For SRE, DevOps, cloud and production support teams
- Investigate logs, alerts and deployment failures without exposing secrets
- Draft and validate runbooks, infrastructure changes and post-incident reports
- Design approval boundaries for commands, infrastructure and production access
- Turn recurring operational work into governed, auditable workflows
03
AI for CRM, sales and lead operations
For Sales, revenue operations and customer-success teams
- Research and qualify accounts with a repeatable evidence standard
- Prepare CRM records, follow-ups, call summaries and next actions
- Build human-approved outreach and lead-routing workflows
- Measure time saved, data quality, conversion and handoff quality
04
AI for marketing and content operations
For Marketing, content, brand and growth teams
- Create briefs, variants and repurposing workflows from approved source material
- Use brand, factuality and approval checks before content is published
- Analyze customer language and campaign data without inventing insight
- Build a reusable prompt and workflow library for the team
05
AI for business and knowledge teams
For Operations, finance, HR, legal and shared-services teams
- Summarize, compare and extract information from business documents
- Create repeatable analysis and reporting workflows with source checks
- Identify tasks suitable for automation and tasks that need human judgment
- Apply confidentiality, data-handling and output-verification rules
06
AI leadership, policy and adoption
For Executives, business leaders, L&D, security and transformation teams
- Prioritize use cases by value, feasibility, risk and adoption effort
- Choose tools and rollout controls without relying on feature demos
- Define a practical responsible-use policy and ownership model
- Measure adoption through business outcomes instead of seat counts
07
Agents, RAG and production AI engineering
For AI, data and application engineering teams
- Design retrieval, tool use, state, evals and human escalation
- Build a focused agent or knowledge assistant on the team's stack
- Test grounding, failure recovery, safety, latency and cost
- Prepare deployment, observability, ownership and handover artifacts
Three-hour workshop
One audience, two applied workflows, one adoption decision.
Best for a focused developer, business or leadership cohort that needs a practical common method and a clear first use case.
| Time | Session | Outcome |
|---|---|---|
| 00:00-00:20 | Baseline and safe-use rules | Agree on approved data, tool boundaries, verification and the workflow the cohort will improve. |
| 00:20-00:55 | Core operating method | Turn a broad request into context, constraints, a verifiable end state and a review plan. |
| 00:55-01:35 | Guided use-case lab | Apply the method to one role-specific task using representative material from the team. |
| 01:35-01:45 | Break | Short reset and instructor review of recurring issues. |
| 01:45-02:30 | Team build | Participants complete a second workflow in pairs and record the reusable instructions. |
| 02:30-02:50 | Review and failure clinic | Compare strong and weak outputs, test edge cases and identify when a human must take over. |
| 02:50-03:00 | Adoption plan | Choose the first approved use cases, owners, success measures and follow-up actions. |
Full-day workshop
Practice, governance, integration and a thirty-day plan.
Best for teams that need deeper hands-on work, two use-case labs and agreement on how approved usage moves into measurable adoption.
| Time | Session | Outcome |
|---|---|---|
| 09:00-09:30 | Business goal and baseline | Define the cohort outcome, current workflow and the measures that matter. |
| 09:30-10:15 | How to direct AI systems | Practice context, constraints, examples, verification and iteration. |
| 10:15-11:00 | Safety and governance | Apply data boundaries, permission rules, review requirements and escalation paths. |
| 11:00-11:15 | Break | Short break. |
| 11:15-12:30 | Use-case lab one | Complete a guided role-specific workflow and review it against a quality rubric. |
| 12:30-13:15 | Lunch | Lunch break. |
| 13:15-14:30 | Use-case lab two | Build a repeatable workflow using approved team material, tools and templates. |
| 14:30-14:45 | Break | Short break. |
| 14:45-15:45 | Integration and automation | Map the workflow from individual prompting to a governed system integration. |
| 15:45-16:30 | Failure, review and measurement | Test edge cases, define human review and calculate a practical value baseline. |
| 16:30-17:00 | Thirty-day adoption plan | Assign use-case owners, office hours, success metrics and the scale-or-stop review. |
Frequently asked
Workshop planning questions
Can the workshop combine Claude Code and Codex?
Yes. An engineering workshop can teach a shared operating method, then compare Claude Code and Codex on representative repository tasks. The goal is not a feature tour. The cohort practices task definition, repository context, permissions, review, tests, failure recovery and measurement across the tools approved by the company.
Can Mindela use our internal repository or business data?
Yes, after the company approves the environment and handling rules. The workshop can run inside a sandbox, a representative repository or approved internal tools. Sensitive data, credentials, production access and publication boundaries are agreed before the session.
Which format is best for a first cohort?
A three-hour workshop is suitable for one narrow audience and one or two workflows. A full day is better when the team needs safety and governance, two applied labs, workflow integration and an adoption plan. A multi-session program is stronger when behavior change and measured rollout matter more than awareness.
Are these agendas only for technical teams?
No. The same structure supports engineering, DevOps, sales, CRM, marketing, operations, leadership and knowledge-work cohorts. The examples, tools, risk boundaries and participant outputs change for each audience.
Private company delivery
Choose the audience, region and workflow that matters first.
Mindela will recommend the shortest format that can produce a useful outcome and a written scope for customization, delivery and follow-up.