30% of team members can't remember key decisions after meetings

[#1]

30% of team members can't remember key decisions after meetings (Atlassian ).

The problem isn't about memory though - it's about losing the context behind those decisions.

I have seen this firsthand with engineering teams.

You think you'll remember why a decision was made, but three months later when someone asks, 'Why did we do it this way?', the context is gone.

The impact of this adds up:

▪️Hours spent revisiting old discussions
▪️Sprint momentum lost to second-guessing
▪️Teams becoming misaligned
▪️The collective sigh when someone says, "I thought we already decided this."

I've learned that writing down what we decided is easy, but capturing why we decided it is the challenge.

This is why Rally for Jira has a permanent session history.

Every discussion stays linked to its Jira ticket, keeping past decisions and context at your fingertips.

How do you track the 'why' behind your team's decisions?

[Stephen_Lugton]

Thanks for sharing this @Evan Fishman - Rally for Jira I take the minutes in my meetings and I'm still one of the 30% who says 'Huh, what are you talking about?' 3 months later

[Evan Fishman - Rally for Jira]

😅😅 @Stephen_Lugton, we've all had that moment.