Why a Workshop Isn't Enough
Most teams I meet have already tried Claude Code. Individual developers use it for code reviews or quick fixes. But systematic integration into everyday development? That's almost always missing.
A one-day workshop shows what's possible. But it doesn't change habits. That's why I developed the Enablement Sprint — two weeks during which we turn Claude Code from an experiment into a standard tool.
The Process
Week 1: Foundation
The first week focuses on three things:
- Team Assessment: Where does each team member stand? Who already uses AI tools, who's skeptical?
- Setup & Configuration: CLAUDE.md, workflow templates, project-specific prompts
- Pair Programming Sessions: I work with the team on real tasks from their backlog
"The difference was that Florian didn't work with toy examples, but with our actual code." — Senior Developer, Telefónica
Week 2: Autonomy
In week 2, the dynamic flips:
- The team works independently with Claude Code
- I'm available for questions and review the results
- We document best practices specific to the team's stack
- A follow-up assessment wraps up the sprint
What Changes Afterwards
After an Enablement Sprint, I typically see:
- 3-5x faster iteration on boilerplate code
- More consistent code quality through CLAUDE.md standards
- Less context-switching — Claude Code handles the research
- Higher satisfaction in the team as routine tasks disappear
Who This Is For
The sprint is ideal for teams that:
- Already have an existing codebase (not greenfield)
- Have 3-8 developers
- Are willing to question their workflows
Interested? Let's talk — in 30 minutes we'll figure out if a sprint makes sense for your team.