Enablement Curriculum Designer
Team and stakeholder concern in. Rollout, curriculum, hackathon out.
Describe a customer team's roles, current tooling, adoption stage, and the concern keeping the champion up at night. Get back a sequenced capability rollout, a role-based workshop outline, a hackathon structure, and the metrics to prove it worked.
Customer scenario
Output
What this lab does
Takes a customer team's composition, current tooling, adoption stage, and the concern keeping the champion up at night, and returns a sequenced capability rollout, a role-based workshop outline, a hackathon structure, and the metrics that would prove the rollout is working.
Why this belongs here
Shipping features is one motion. Getting a whole team to actually adopt a new way of working is a different one: sequencing which capability to introduce first, designing workshops that fit the roles in the room, and building a hackathon that reinforces the behavior instead of just being a fun Friday. This lab is that second motion.
How to read the output
- The rollout sequence should respond to the stated stakeholder concern, not just list capabilities in a generic order.
- The workshop tracks should be concrete enough to put on a calendar this week, not abstract curriculum theory.
- The metrics section is deliberately conservative: directional thresholds, not invented numbers.