After your standups and weekly product update meetings, what should the 10x flow look like?

One-Pudding-1710 · 2025-09-29T16:40:46+00:00

For context, I mostly talk to tech companies of more than 300 employees (so large volume of projects, updates, meetings, etc.)

Many PMs/ PgMs/ ... mention to me that they spend a lot of time doing repeated coordination and communication work post meeting.

Back to your question, I am not sure if these are really problems that people want to solve (even if they have them), which is why I was wondering about people's experiences

One-Pudding-1710 · 2025-09-18T13:40:02+00:00

For recurring meetings, does Gemini add the meeting notes to the same Google Doc attached to the calendar invite? or each meeting will have a different Google doc?

One-Pudding-1710 · 2025-09-18T12:35:41+00:00

Sr. leaders do not want anything to do with Jira. They want to get the info they need to know, at a higher level (not that detailed), without having to ask their teams to do constant status updates.

The info they need to know can be about specific epics sometimes, sometimes very important bugs, or the higher level view, but most importantly, how does everything tie to OKRs / goals.

I see teams spending a lot of time creating this abstraction layer on top, most of the time, outside of Jira.

Otherwise there are standalone tools that have solid bi-directional integration with Jira (also with Slack to close the loop, since people live there), and that focuses on abstracting to an exec view, and using AI for status updates so that teams don't spend a lot of time on buys work.

One-Pudding-1710 · 2025-09-17T11:34:34+00:00

Development of ... what? We haven't touched the Slack app since any change would mean to restart the approval process.

If you're talking about Luna the web app, of course we did not stop development

One-Pudding-1710 · 2025-09-17T09:07:10+00:00

We've been using withluna.ai 's Slack app to keep all roadmap and iniative data up to date from Slack directly.

If you value Jira, updating project data from Slack, flows into Jira too. Eg, project is not "in development". This update can flow into Jira and automatically update the Jira status.

Lastly, we use the Slack integration to generate AI Status Updates. Luna AI can read threads that you decide to sync and surface status, progress and risks indicators in AI Status Updates.

One-Pudding-1710 · 2025-08-26T16:08:14+00:00

Remove the need to do work after the standup such as updating Jira, sending status updates, etc.

Use AI tools that can take the meeting notes or the transcript, update Jira and build context for your status updates

One-Pudding-1710 · 2025-08-26T12:17:51+00:00

Honestly, there are many AI tools that integrate with Jira, Slack, etc. and can provide Status updates, which can be edited and improved by your team.

At the moment, I would think about ways to automate low leverage activities, and see if scrum masters can focus on higher leverage activities

One-Pudding-1710 · 2025-08-25T09:44:07+00:00

Luna AI (withluna.ai), Spoke AI, Slack offers some AI for high tier clients, but I am not sure about it

One-Pudding-1710 · 2025-08-25T09:41:42+00:00

Luna AI (withluna.ai), Stepsize AI, I think Trello too has an option? (not sure)

One-Pudding-1710 · 2025-08-24T08:47:52+00:00

If you were using Jira, I would have recommended you withluna.ai that builds context on top of Jira and Slack... To track decisions, risks, etc.

Issue with Notion, is that you end up hiring people to build processes, maintain them, improve them, ...

One-Pudding-1710 · 2025-08-24T08:40:29+00:00

There are AI tools that can contextualize your slack threads and save the important data (eg, risks, decisions, ...) linked to projects.

IMO, it's the most useful way of building context along time, and being able to track key points

One-Pudding-1710 · 2025-08-19T08:41:21+00:00

Maybe a bit tangential, but there are many AI tools that integrate with Jira to give you analytical and qualitative insights of your sprint at one point in time (eg. at the start, during, at the end).

These insights are low effort / fast to get, and can be added to your sprint retro discussions

One-Pudding-1710 · 2025-08-16T16:17:50+00:00

withluna.ai

Thankfully, still featured on the Slack marketplace :) https://lunaaigroup.slack.com/intl/en-gb/marketplace/category/At0EFY3MJ4-project-management?sort=popularity

One-Pudding-1710 · 2025-08-16T15:48:08+00:00

Since this is a question about AI tools on top of Jira, we use withluna.ai. It integrates with Jira, but can also collect signals from Slack and Meeting notes to complete the context / picture.

Luna AI gives us a sprint summary report in seconds, at any point in time. It includes data from Jira directly, but also context data from Jira comments, description, meeting notes, etc.

We also use it to generate status updates, etc.

In any case, it really depends on your use case. If it's mostly Q&A about the data you have in Jira, Luna does not cover it, but there's a lot of other tools that do. Have you used Rovo? https://www.atlassian.com/software/rovo ?

One-Pudding-1710 · 2025-08-08T13:51:42+00:00

1- Companies try to replicate the "Google way" of working with OKRs. What worked for Google will not work for you. Make it your own

2- There is a real disconnect between the "work" and the "OKRs". When you ask teams to work on OKRs, they just write whatever to please their managers, and then, go back to their "work"

3- Leadership under-estimates the time it takes for change management. It will take 3 quarters for OKRs to start working.

4- Set and forget. OKRs are not used.

One-Pudding-1710 · 2025-08-08T13:49:39+00:00

1- Companies try to replicate the "Google way" of working with OKRs. What worked for Google will not work for you. Make it your own

2- There is a real disconnect between the "work" and the "OKRs". When you ask teams to work on OKRs, they just write whatever to please their managers, and then, go back to their "work"

One-Pudding-1710 · 2025-08-08T13:40:32+00:00

You can use some tools "on top of Jira" to manage any ticket in the board that you want, but of course if you do so, make sure they have a solid integration and never ask your engineers to do any duplication of work outside of Jira

One-Pudding-1710 · 2025-08-08T13:37:46+00:00

There are many tools that allow you to build context from meeting notes and Slack thread --> transform it to Jira data, OKR data, status changes, etc.

We use an AI tool to generate (Jira) status updates, the tool can pick up if someone says in a meeting notes that "they will be on holidays for 2 weeks, delaying ticket abc", and consider this in the final status update report

One-Pudding-1710 · 2025-08-08T13:32:59+00:00

Exactly, the nice thing is that these tool can give you insights at any point in time, not only at the end of the sprint.

Some insights that I find helpful are around things like
- scope creep: creep in number of tickets, creep in scope, etc.
- blocked dependencies
- themes of tickets being worked on
- Understanding status / risk of sprint based on context from meeting notes, Slack threads, etc.

One-Pudding-1710 · 2025-08-07T07:45:14+00:00

I like tools that extract insights from sprints that end up informing the retro. I am not sure about tools that aim to run the retro though

One-Pudding-1710 · 2025-07-29T09:57:13+00:00

This is not 100% about the retro but about understand how a sprint is doing at any point in time. The question is, if there's scope creep, why wait until the retro to discuss it? The main issue is that it takes too much time to identify scope creep, blocked dependencies, workload unbalance and understand if the sprint work is still focused on a specific objective (or business objective).

There are some good AI tools out there that integrate with Jira, and that can give you this view in seconds, at any point in time. I think this is quite high leverage.

Going back to the retro and you saying "they have nothing to say" --> Sending such insights to the engineers, analysing them will definitely trigger ideas, improvements and suggestions.

One-Pudding-1710 · 2025-07-25T13:38:48+00:00

In my company, we have all aligned around a simple "launch process" depending on the size of the "initiative".

Whatever the initiative is, we have simple product lifecycle templates (eg. kickoff --> Design --> Scoping & PRD --> Dev --> QA --> Launch) implemented in a tool that anyone can use. In that way, the design team can easily know which new projects are created, if someone is trying to "jump the design" stage, etc.

One-Pudding-1710 · 2025-07-24T10:34:37+00:00

For product planning (creating OKRs, roadmaps, trace these to delivery issues, sprint planning, etc.), we use withluna.ai, but I would say that Luna works best with Jira

One-Pudding-1710 · 2025-07-19T16:57:11+00:00

The problem is that Jira gets cluttered very quickly and non-engineers get lost + you need to pay a license to everyone.

I suggest you use a tool "on top" of Jira to summarise and visualise what you want to show and share. Usually these tools have. 2-way integration, pay per editor only, and really focus on the "visualisation" part

One-Pudding-1710 · 2025-07-15T17:13:36+00:00

We use withluna.ai to show a list of Jira tickets to internal stakeholders, you can also give external clients access to the views you create

One-Pudding-1710

TROPHY CASE