AI coding training for engineering, product and design

Train engineering, product and design together when the team wants one way of working with AI coding tools. Engineers, product managers and designers already share the requirements and the review. The training gives them the same language for what an agent may do and what a person still decides.

We run that programme as training on your own work, onsite, offsite or remote. The method is Delegate, Review, Own.

Start from the level the team has reached

Most teams we meet have the tools and no shared way of working with them. Some engineers hand whole tasks to agents. Others still use AI to autocomplete a line. Before we plan a training, we measure where each person stands.

The team proficiency matrix does that in five levels. Everyone answers alone. Engineers get 16 questions. Product and design get 12. A person's level is the average of their answers. The shared baseline is the level three in four people have reached, and the training starts there so nobody is lost. The target is one level up for the whole team.

The levels and the film are in AI coding maturity. You can also take the free team check.

What each role practises

Engineering practises a small change on the real repository: a clear brief, the context the agent needs, a diff a reviewer can explain, and a check against the tests and the team rules.

Product and design practise the same brief from their side. They name the requirement, the boundary, and what evidence would show the change is done. They sit in the review so the acceptance criteria are not invented after the diff exists.

The stakeholder call in the engagement is there for that reason. It is a call with the owners of requirements and review, to align perspectives before a proposal is written.

How an engagement runs

The steps are the same for every tool. A 30-minute introductory call covers objectives, stakeholders and the work to be improved. The matrix comes next. Then the stakeholder call, a written proposal with scope, schedule, materials and total price, and acceptance and scheduling.

Services is the follow-on when the team wants a shared Slack or Teams channel, a briefing every two weeks, and a monthly live session. Book a 30-minute call to see which format fits.

Frequently asked questions

Do product and design attend the same training as engineering?

Yes. They share the engagement and the review habit. The questionnaire differs: engineers answer 16 questions, product and design answer 12.

What happens before the training is planned?

A 30-minute introductory call, then the team proficiency matrix, then a stakeholder call with the owners of requirements and review.

Where is the programme described?

On the training page, for onsite, offsite and remote delivery, and on the services page for the ongoing briefing.