KENNY CHIEN / COACHING / TEAM WORKSHOPS
Team Workshops
One- and two-day intensives that rewire how a team builds with AI — on your codebase, not toy demos.
Team workshops are one- and two-day intensives that change how an engineering or product team builds with AI. They run on your codebase and your backlog — not toy demos — so the new way of working starts inside the work you already have. By the end of day one, the team has shipped real backlog items with the new method.
A workshop is the fastest honest intervention I offer. It will not transform a team in a day — nothing does — but it will replace vague AI enthusiasm with a shared working method, and it names precisely what the team should practice next. Teams that want the longer arc pair a workshop with the bootcamp or a Vibe Teaming engagement.
“A team that watched a demo learned nothing. A team that shipped together learned a method.”
How a workshop runs
Scoping call
We pick the codebase, the backlog items, and the outcome that would make the day worth it. I prepare on your actual repository, not a slide deck.
Build together
Morning: the agentic working method — decomposition, prompting as specification, review discipline — taught by doing. Afternoon: the team ships real backlog items with the method, pairing in rotations.
Deepen and standardize
Agentic patterns for your architecture, evaluation cases, and a written team standard: how we prompt, how we review, what we never merge. The second day turns a good experience into a durable convention.
Follow-through
A written summary of what the team shipped, the standard we agreed on, and a concrete practice plan for the next thirty days.
Format
On-site by default
Workshops work best in one room with a whiteboard and no competing meetings. I travel to you.
Remote when needed
A remote format exists for distributed teams — shorter, high-intensity blocks across two or three days instead of one long one.
Team-sized
Built for one team that ships together — roughly five to fifteen people. Larger groups split into cohorts rather than diluting the room.
Your codebase
All exercises run on your repositories and your backlog. Nothing synthetic — the point is that Monday looks different.
If what you need is weeks of embedded delivery rather than days of training, that is forward deployed engineering.
What you walk away with
Real backlog items shipped during the workshop with the new method
A written team standard for building with AI — prompting, review, merge criteria
A shared vocabulary that ends the tools-versus-craft argument
A concrete practice plan for the next thirty days
Common questions
Who should be in the room?
The whole team that ships together — engineers plus the product or design partner who shapes the work. Mixed roles is a feature, not a compromise: it is how Vibe Teaming works at full scale.
One day or two?
One day changes how the team works. The second day makes it stick — agentic patterns for your architecture and a written team standard. If budget forces a choice, one great day beats two thin ones.
Remote or on-site?
On-site by default — the format works best in one room. The remote version runs as shorter blocks across two or three days and works well for distributed teams.
How do I book a workshop?
Email kenny.chien@gmail.com with a paragraph about the team, the codebase, and what you want to be different afterward. You will get a scoping call and an honest read on one day versus two.
Book a workshop
Tell me about the team and the codebase. I will send a scoping call slot and an honest read on one day versus two.