Education and onboarding
Review what a developer reads, runs and tries when learning the product, including the first lesson, exercises and follow-up material.
I review developer onboarding, learning material and community programmes with the teams responsible for them.
We look at how someone gets from signing up to building with the product, what brings them back, and which parts of that experience need work.
At Postman, I designed API learning material and student programmes that reached 200,000 registered participants. I led a four-person programme team and grew its Discord community to more than 13,000 members.
At Pieces, I worked on onboarding, technical content, workshop tools, and a regular feedback loop with engineering.
More about my workReview what a developer reads, runs and tries when learning the product, including the first lesson, exercises and follow-up material.
Define who the programme is for, what participants can do, and where partners or community leaders can contribute.
Plan technical content around developers’ questions and the next task they need to complete.
Decide what registrations, participation, downloads and retention can tell you. Keep the measures separate when judging the programme.
Bring recurring questions from workshops and support conversations into product planning.
A review of agreed materials and stakeholder input, followed by a prioritised recommendation memo.
A programme outline covering who it serves, how people take part, who owns the work and what to measure.
Regular reviews and advice on the decisions agreed at the start of the engagement.
I provide focused advice; your team keeps day-to-day ownership. We agree the scope, people involved, and deliverables before starting.
Describe who the programme serves, what you want participants to do and where they stop taking part. Include the decision you need help making.