workshops and training, for teams of 1 to 24
The way I run workshops looks more like working sessions than lectures. I'm in your tools with your team, on your actual problem, building something together. Nobody is watching slides. The room is the work.
The point is peer collaboration, not transfer of slide content. By the end, the team has built something real, and at least one person on the team can run the next round without me in the room.
01 five shapes
The five shapes go from a single hour with one person to a multi-week embedded program with a whole function. Pick by how much room you have, and how much commitment the team is ready for.
A single hour to put shape on something you're starting. The pre-work pulls the messy thinking out of your head and into a structured doc; the session works the thing live; the post-work writes up what we landed on so you can act on it Monday. Useful on its own, and the easiest way to find out if working together is worth more time.
Half a day to pick one workflow and build one artifact together. The team chooses the workflow with me a week ahead. We open the session with framing, spend the bulk of the time building, and close with a working artifact in your tools that the team made themselves.
A full day, two workflows, two artifacts. Big enough that the team can take on a harder problem and still leave with something built. Lunch and the coffee ritual are part of the day; the muscle to extend either artifact is the point.
For a team that needs to come out the other side genuinely different, not just exposed. Three or four working sessions across two weeks, two builds in between, an internal lead trained to run the next round without me in the room. The teaching is woven into the doing.
The full re-architecture. I sit inside the team for several weeks, work on how the work gets made, and leave a documented operating model behind. The biggest shape, and rarely the right one. When it is the right one, it tends to be very right.
All prices are ex-VAT. EUR figures are rounded for readability, not the rate of the day. Larger groups, on-site travel, or unusual scope changes the price; the floors above are the starting point.
02 what the room actually looks like
03 scenarios, who shows up
Use the toggle to see the scenario menu for your side of the room. Ten examples in total, two per shape, one for each audience.
One hour. They bring the workflow that's costing them the most. We run the pre-work, the session, and the writeup. They go back to the team with a concrete proposal for what to do next.
→ shape 01, startupWe pick one PM workflow: sprint review prep, customer-call synthesis, requirements drafting. We build a Copilot agent the team uses in front of you before the session ends.
→ shape 02, half-dayTwo workflows ported from one heroic IC to documented, team-owned, version-controlled flows that survive that person going on vacation.
→ shape 03, full-dayThree working sessions, two real builds, a champions program. We pick the workflows from the team's actual backlog so nobody can claim it doesn't apply to their world.
→ shape 04, teaching sprintSix to twelve weeks embedded in the function. We rewrite the operating model, build a training program, and leave behind a team that can teach the next round themselves.
→ shape 05, multi-weekOne hour to pressure-test the shape. The pre-work forces the assumptions onto the page; the session works the riskiest one; the writeup is something you can show a co-founder or a first hire.
→ shape 01, startupOne product workflow, picked the week before. We build a skill that captures how the team makes the decision, then runs it on the next three live calls.
→ shape 02, half-dayTwo artifacts: a positioning doc with real evidence, and a prompt library the team uses to maintain that voice as they ship. Everyone in the room builds, not just the founder.
→ shape 03, full-dayTwo weeks and three sessions, set up so that AI use ends up feeling like reviewing a junior teammate's PR. Taste, instinct, sequencing. The work happens at the skill level, with the tool sitting underneath it.
→ shape 04, teaching sprintEmbedded for four to eight weeks. We design how product gets made, how decisions get logged, and how AI shows up in the loop. The next hires walk into something running.
→ shape 05, multi-week04 what teams leave with
The point isn't certificates or "exposure." What teams take home are artifacts that are shipped, owned, and reusable by the people who built them.
A working build that lives in your tools: a Claude skill, a Copilot agent, a flow, a template.
Someone on your team trained to run the next round of this without me in the room.
Built in your tenant, your account, your repo. You own the artifact and the documentation.
If a slide deck is the main artifact a workshop produces, the workshop didn't do its job.
/ next move
