nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

🔮 Rovo Ritual #2: The 5-Minute Meeting Pre-flight

Summer Mahmoud

Hey, Rovo Community! 👋

Welcome back to Rovo Rituals - our weekly series designed to help you build practical, low-friction AI habits in under 5 minutes a day.

If you tried Introducing Rovo Rituals! 🔮 Try ritual #1: The Morning Prioritizer - Atlassian, you’re already on your way to mastering daily planning. This week, we’re tackling another universal workday challenge: meeting prep when you have zero time.

🏅 Quick Reminder: Earn Badges & Kudos

Participate in weekly threads to level up your AI skills and earn exclusive community badges:

Rovo Ritual Explorer: Comment on your 1st Rovo Ritual discussion
Rovo Ritual Practitioner: Participate in 3 Rovo Ritual discussions
Rovo Ritual Master: Join in with 5 Rovo Ritual discussions

🔮 Ritual #2: The 5-Minute Meeting Preflight

Theme: Meeting Prep & Context Gathering
Level: Beginner
Time to test this ritual: 2–3 minutes

The why:

We’ve all been there: you’re running between back-to-back meetings, opening a doc 30 seconds before the call starts, or scrambling to remember what was decided last week.

Instead of showing up cold or skimming 10 pages of notes while someone is speaking, let Rovo do the preflight check for you. In seconds, Rovo can synthesize background context, pull past decisions, and give you sharp questions to ask.

📋 The Prompt to copy & paste (and tweak to fit your work!)

"I have an upcoming meeting about [paste topic, Confluence page link, Jira ticket key, or project name]. Summarize:
The key background context and objective
The last 3 major decisions or recent updates made
Any open blockers, risks, or unresolved items
3 sharp, insightful questions I should ask in the meeting.""

🛠️ Role-based variations

Engineering: “For [Jira epic or design doc], summarize key technical decisions and blockers. Suggest 2 questions for the review.”
Product or project: “For [project or Jira board], summarize milestone status and dependencies. Suggest 2 alignment questions.”
Cross-functional teams: “For [initiative or campaign], summarize recent commitments and shared deliverables. Suggest 2 collaboration questions.”

Want to see how fast this works in real life? Watch the quick walkthrough below where I run the Preflight live against a mock 1-on-1 meeting doc and see how Rovo catches blockers and crafts questions on the fly:

https://www.loom.com/embed/d87ae9fb7267431b8b59ab1452bce9b7

💬 How to participate

Run your preflight: Pick an upcoming meeting and use the prompt above (or a role-based variation) in Rovo with its relevant Confluence page, Jira issue, or project name. Check the briefing and choose one question to bring to the meeting.

Share your takeaways: Reply below with what helped. For example:
- Did Rovo surface a decision or blocker you had missed?
- Which suggested question sparked the most useful conversation?
- What did you change in the prompt to make your preflight more useful?

Try the 5-minute preflight before your next meeting, then tell us how it changed the conversation! 👇

(Reminder: Please ensure you don't paste confidential, sensitive, or customer data into the forum comments you share back with us!)

Comments

Gabriela - LeanZero

Hi Summer, I tried this on a test site, and since there's no real meeting on a test site I filled your bracket with a data-warehouse migration project there and asked Rovo to look the project up itself.

It took nineteen steps to read every work item with its history and the links between them, and it traced the chain from the overdue 2023 to 2026 backfill through reconciliation and the finance parallel run to the Tableau repointing. That part was genuinely useful. I also liked that it wouldn't call field edits decisions, and said plainly there were no comments or brief explaining why anything had moved. Its "recent updates" were mostly the test-data resets on that site, which it had no way of knowing, so that part only tells you what changed, not why.

The question I'd actually take in was its third one, the go/no-go criteria finance has to accept before cutover and who owns the rollback if validation fails. It did skip retiring the old ETL jobs though, so you'd still want to check the brief against the board before you walk in

Anwesha Pan

Recently, I was assigned a complex cross-team collaboration ticket with multiple subtasks and linked Confluence pages. My goal was to review everything and put together a QA/testing checklist ahead of an upcoming sync.

The challenge? The ticket was written entirely from a developer’s perspective, making it difficult to translate into Test Engineering (TE) requirements.

And there was the grand entry of Rovo. I prompted it to break down the initiative specifically through a Test Engineer’s lens and identify what needed our validation before the meeting. Rovo completely turned things around for me:

Provided a clear, accessible overview of the end-to-end story that anyone could follow.
Clarified which applications our team owned in this initiative and pinpointed exactly what needed TE coverage.
Scanned every subtask, PR, and wiki page to assemble a structured plan.
Helped me flag a missing mapping in the migration plan.

Thanks to Rovo, I didn't feel lost or overwhelmed in the sync, what initially felt like a foreign language became clear, actionable steps I could confidently speak to.

Summer Mahmoud

So great to see you back for Ritual #2, Anwesha! Walking into a meeting feeling empowered instead of overwhelmed is a total game changer 💙

Summer Mahmoud

Hi Gabriela! Tracing 19 steps of dependencies all the way to Tableau repointing is huge. Love the tip to do a quick board sanity-check before walking in. Thanks for sharing this! 🙌

Anwesha Pan

Yessss absolutely @Summer Mahmoud !! 💪

Robert - JSoft

This is a strong way to use Rovo before a cross-team sync: point it at the real ticket, the subtasks, the PRs, and the linked pages, and ask for the story through a Test Engineer’s lens.

The useful part is how specific the output is. Which applications your team owns, what needs TE coverage, and a gap you can verify yourself (the missing mapping) before you speak to it in the room.

We built a Rovo agent for the step after an overview like that, when the coverage list needs to become test work the team can actually run.

After a breakdown like yours, where does that checklist need to land so QA and Dev can still act on it?

Summer Mahmoud

Robert, that custom Rovo agent sounds fantastic. Love seeing practical automations like this - thanks for sharing! 🙌

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

rovo

rovo-rituals