At the end of January, we hosted our first CUG event of the year. I ran a “Rovo for beginners” prep session, timed with our company‑wide rollout of Rovo.
The session went over really well. We:
Broke down some core Rovo/AI terminology
Shared Atlassian learning resources so people could keep exploring on their own
And I tempted the demo gods with a live build of a Rovo Agent for a real, common use case our attendees cared about
That last part is what sparked the idea for our next experiment.
So, how do we plan our next event? Use ROVO!
As I started thinking about what to do for our next meetup, I realized: “Why not use Rovo itself to help us plan it?”
So I built a Rovo Agent dedicated to CUG event planning.
The prompts and configuration are still a work in progress (far from “perfect”), but here are the key things we’ve wired up so far:
Event design & topic ideation
Suggests themes and topics based on what’s trending internally
Helps draft agendas and outline presentation formats
Some other ideas I have that I would like to use to augment this are:
FAQ mining from real work
Ingests JSM tickets we’ve already solved in our team’s JSM project
Surfaces frequently asked questions that could become future talk topics, demos, or lightning talks
Signal from our Slack channels
Looks at our Slack channels where people ask questions
Identifies recurring pain points and interests
Uses those as input for new session ideas
The result: instead of guessing what our community wants, we’re letting our own data guide us.
Ironically (or maybe inevitably), our next CUG event in April is going to be a “next iteration” session on Rovo and AI. Interest in AI is huge right now, and our first session only scratched the surface.
The good news is:
Thanks to this Rovo Agent, we’ve now got a steady pipeline of:
Topic ideas
Format experiments
FAQs we can turn into demos, deep dives, and hands‑on exercises
So it feels like our well of content won’t be running dry anytime soon.
Jimmy Seddon
1 comment