Team Training

Training for teams that need to own the work after delivery.

Makepad designs practical sessions around the team, the risk, and the behavior that needs to change. The goal is not theory. The goal is a working practice the team can apply the next day.

Book training call Back to overview

How to choose

Start with the behavior that needs to change.

Training is scoped like consulting work: audience, current level, operating context, examples from the team's real work, and clear take-home material.

Responsible usage

AI & Agent Workflows

For teams that want practical rules for using AI tools without weakening review, security, or accountability.

Inclusive products

Accessibility

For teams that need to design, build, review, and hand over product interfaces with accessibility in mind.

Delivery quality

Delivery & Production Habits

For teams that need defined release routines, review discipline, ownership, and handover habits.

Risk reduction

Secure Development

For teams that need to recognize common security risks, review changes more carefully, and handle sensitive work responsibly.

Operations

Workflow Automation

For teams that need to identify repeated work, choose what should be automated, and avoid fragile automation shortcuts.

Engineering quality

Technical Documentation

For teams that need clearer runbooks, onboarding notes, decision records, handover material, and product/system documentation.

Training catalogue

Each path becomes a tailored session.

The exact agenda is shaped after we understand the audience, current workflow, and level of responsibility.

AI & Agent Workflows

What the team learns

How to use AI in technical work while keeping review discipline, context control, security awareness, and accountability.

Good fit

  • Developers who want safer AI-assisted delivery habits
  • Product teams evaluating AI features or workflows
  • Founders who need practical rules before adoption spreads

Handover

  • Team usage guide
  • Review checklist
  • Safe task examples
  • Risk and approval rules when needed
Accessibility

What the team learns

How to catch accessibility issues earlier across product, design, implementation, review, and handover.

Good fit

  • Product teams preparing public or customer-facing interfaces
  • Design and engineering teams sharing interface ownership
  • Teams that need practical review habits before release

Handover

  • Review checklist
  • Bug template
  • Design and implementation notes
  • Testing routine for the team
Delivery & Production Habits

What the team learns

How to make releases, reviews, testing, environments, incidents, and recovery more predictable and less dependent on one person.

Good fit

  • Teams with inconsistent release habits
  • Teams onboarding new developers or technical leads
  • Teams preparing to own production responsibilities

Handover

  • Release checklist
  • Review and ownership guidelines
  • Incident and recovery templates
  • Team operating recommendations
Secure Development

What the team learns

How to notice common security risks during daily product work, review changes more carefully, and handle sensitive information responsibly.

Good fit

  • Teams adding security responsibility to normal delivery
  • Teams preparing for customer or management review
  • Teams that need a shared language for risk ownership

Handover

  • Secure review checklist
  • Risk triage workflow
  • Team-specific security playbook
  • Follow-up recommendations
Workflow Automation

What the team learns

How to spot repeated work, define a reliable process, decide what should not be automated, and measure whether automation is worth building.

Good fit

  • Operations teams repeating the same manual steps
  • Founders or managers deciding where automation helps
  • Teams that need a shared process before implementation

Handover

  • Automation opportunity map
  • Workflow diagram
  • Risk and ownership notes
  • Prioritized automation backlog
Technical Documentation

What the team learns

How to write documentation that supports onboarding, delivery, operations, decision-making, and handover instead of becoming unused files.

Good fit

  • Teams with knowledge trapped in calls or private messages
  • Teams handing work to another engineer, agency, or client
  • Teams that need clearer operating and decision records

Handover

  • Documentation structure
  • Runbook template
  • Decision record template
  • Quality checklist

Format

Scoped by audience, level, and real operating context.

Audience

  • Developers and technical leads
  • Founders, CTOs, and product managers
  • Operations, security, and support teams
  • Designers and mixed business teams

Level

  • Foundation sessions
  • Team workshops
  • Advanced working sessions
  • Mixed-level sessions with separate exercises

Outputs

  • Session plan and exercises
  • Templates, checklists, and examples
  • Team-specific workflow notes
  • Next-step recommendations