AI-assisted product development
Product teams now use AI tools for research, specs, design and prototypes, and developers use them to write, review and test code.
This training shows where the tools save time and where their mistakes look convincing enough to slip through. It also covers how a team can work with them and keep control of quality.
What the training is about
We don't walk through the buttons of a single product, because tools change every few months. The habits we cover work with whichever tools your team uses. Participants learn to give a tool enough context, to check what it produces and to notice when doing the work themselves would be faster.
The sessions are hands-on, with tasks modeled on the participants' own work.
Who it is for
Product managers
Researching a problem, writing clearer specs and testing an idea with a working prototype before it goes to the engineering backlog.
Designers
Moving from sketches to interactive prototypes faster, and exploring more variations before choosing one.
Software developers
Using coding assistants and agents in a codebase they maintain, and reviewing their output with the same care as a colleague's.
Team leads and managers
Understanding what changes in the team's process, which risks need rules and how to judge whether the tools are paying off.
Topics
The balance between topics depends on who is in the group, and we agree on it with you in advance.
- Which stages of product development benefit from AI tools
- Going from an idea to a clear spec and a working prototype
- Coding assistants and agents: giving them context, keeping changes small and reviewing their work
- Testing and checking AI-generated work before it reaches users
- Data privacy, security and intellectual property when using external AI services
- Choosing tools and setting team rules for using them
Tailored to your team
For non-technical teams
The focus is on research, specs, prototypes and judging the quality of AI output. No coding background is needed.
For engineering teams
It goes deeper into coding agents, code review, testing, tool integrations such as MCP and working inside an existing codebase.
Frequently asked questions
Can product, design and engineering teams take the training together?
Yes. In a mixed group, product, design and engineering people work on the same problem, each from their own side.
Which AI tools are used in the product development training?
Usually the tools your organization already allows, used within your existing data policies. If nothing has been approved yet, we agree on suitable tools with you.
Can the exercises use our own product and code?
Yes. Where it is possible and allowed, exercises use your own product, documents or code.
Plan a training program with us
Tell us about your team and what you want them to be able to do. We'll get back to you.
From our blog
All articles
You're not doing AI. You're doing integration.
Most AI projects depend on integration. Company data, business rules, human review, and workflow design turn a capable model into a useful product.
Read article
Why AI projects stall after the prototype
AI makes drafts and prototypes cheap. The advantage moves to organizations that can choose the right work, stop the rest, and finish what matters.
Read article
How to choose an AI model architecture
AI model architecture shapes what a system can learn and where performance plateaus. Prompting or more data cannot fix an architectural mismatch.
Read article