Are We Asking Rovo the Right Questions?

[#1]

One thing I've noticed while using Rovo is that the quality of the answer often depends on the quality of the question.

In the beginning, I asked very generic questions and got generic answers. Over time, I started asking more specific things related to my daily work.

For example, I often ask:

How many bugs have I created so far?
Which automation cards have I completed?
What tasks are currently in Done status?
What work did I complete this month?
What are my recent Jira activities?

These types of questions save me from manually searching through boards, filters, and reports.

It made me realize that Rovo isn't just about getting answers it's about getting information faster from the tools we already use every day.

I'm curious how others are using Rovo.

What is the most useful question you've asked Rovo that saved you time?

[s_gridnevskii]

I don't think you need Rovo to answer these questions. Existing tools provide answers without heating up planet Earth and eating your tokens.

[Kerrie Gottschalk]

I don't want to disregard your use of Rovo because I think one of the challenges of Rovo is to find solutions that work for you and your users.

I am trying to encourage strategic use with Rovo instead of having it answer questions one can get from JQL or dashboards. For example, I have developed a Marketing Calendar and Audience analysis agent. The questions can include, "what's on the marketing calendar for the next week or month or quarter?" The agent includes audience analysis each time and the results can be published to Confluence. This is much more sophisticated than a general calendar, dashboard, or JQL result can offer.

Our project management team is using Rovo to analyze requirements and cross-department documents to develop project plans.

I use Rovo to help troubleshoot automations, JQL problems, and other admin functions.

Our Service Desk team is getting ready to launch a Service Desk agent.

So, to answer your question, as an admin, I'm pushing our users to think about how Rovo can provide service beyond what we can get from searches, dashboards, etc. That said, the process usually starts with a simple question, such as,  "how many emails, social media posts, and web pages  are we deploying?", "how many service desk tickets could be answered by an agent?", "how can I consolidate requirements and documents into a comprehensive project plan?"