Hands-on, 1.5 days. The team learns to build with AI and stays in control of what ships.
Gives the team a repeatable way to use AI for real development work—code, tests, docs—while keeping decisions and quality in their hands.
The bottleneck isn't writing code anymore—it's defining the right work, checking outputs, and managing risk.
This workshop builds repeatable workflows so the team can use AI safely without lowering the bar.
Developers plan, define, and review—AI writes the code.
Each dev ships a working component to preview.
Clear agreement on what AI does vs. what humans own.
Structure work with clear objectives, acceptance criteria, and constraints so AI executes reliably.
Tests, reviews, and checklists to validate AI output without slowing delivery.
Conventions, templates, and lightweight automation that make agentic work sustainable.
Shorter cycle from idea to working preview.
Tests and docs ship by default.
AI produces, humans approve.
3 focus areas: Foundations — how agentic coding works and why it matters. Practice — real workflows on real code. Proof — ship a working component.
Mateo Mateus
Tatiana Terront
Alejandro Camacho
Johan Valbuena
Nicolas Suarez
Miguel Arbelaez
Each dev deploys a working component with tests and review trail.
How to prompt, review, and ship safely—written by the team.
Config files and checklists to make the workflow stick.
Capabilities
Can the team reliably run agentic workflows? Task structuring, validation processes, tool fluency.
Outcomes
Does delivery get faster without increasing defects or risk? Velocity, quality, and governance metrics.
Method: Define with Jamey and engineering leadership.
Specifics come after the workshop so we don't create overhead during adoption.
The workshop gives the team the tools. Jamey drives adoption day-to-day. I run three follow-up sessions to support him.
Jamey and Pedro sync on what landed and what's blocked. Pedro runs a troubleshooting session with the team.
Working session on a topic the team picks. Jamey flags what's working and what needs adjusting.
Jamey owns the playbook. Pedro does a final review, closes out gaps, and hands off fully.
Jamey already leads the engineering team—this builds on his existing role, not around it.
Next: lock dates with Jamey, confirm access, agree on guardrails.