Workshop
WURK-shop
A hands-on educational session where developers build something guided by an instructor, learning by doing.
A workshop is a hands-on session where developers follow along and build something with an instructor's guidance. Unlike a conference talk (listen and watch) or a meetup talk (shorter, less structured), a workshop is interactive: everyone codes together.
Workshops are the highest-conversion DevRel activity. A developer who spends 2-3 hours building with your product has invested significant time and has a working project at the end. They are far more likely to continue using the product than someone who watched a 30-minute talk.
The downside is scale. A workshop requires preparation (a tested curriculum, working code samples, clear instructions), infrastructure (development environments for all participants), and support (the instructor plus helpers for when people get stuck).
Examples
A company runs a workshop at a conference.
The 3-hour workshop walks 50 participants through building a full-stack application using the product. Each participant ends with a deployed, working app. The company provides pre-configured development environments so no time is wasted on setup.
A virtual workshop reaches a global audience.
The 2-hour Zoom workshop is recorded and published afterward. 100 people attend live. 500 watch the recording in the following month. The workshop recording becomes an evergreen onboarding resource.
A workshop curriculum becomes documentation.
The workshop materials (step-by-step guide, code samples, explanations) are polished and published as a tutorial on the docs site. The workshop content serves double duty: live education and permanent documentation.
In practice
Read more on the blog
Frequently asked questions
How long should a developer workshop be?
2-3 hours for a focused topic. 4-8 hours (full day) for comprehensive coverage. Anything under 90 minutes is too short to build something meaningful. Include breaks every 45-60 minutes. Developers need time to debug and ask questions.
How do you handle different skill levels in a workshop?
Clearly state prerequisites. Provide a pre-workshop checklist (install X, create an account). Have helpers available for people who fall behind. Include 'stretch goals' for advanced participants who finish early. Accept that not everyone will finish at the same pace.
Related terms
A step-by-step guide that teaches a developer how to accomplish a specific task or build a specific project using a product.
A local, informal gathering of developers to learn, network, and discuss technical topics.
A presentation at a developer conference where a speaker shares technical knowledge, experience, or insights with an audience.
Programs that teach developers new skills and concepts, including courses, workshops, and learning paths related to a product or technology.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.