"We've been focused on improving quality" is forgettable. "Last month a customer emailed to say a bug we'd normally have shipped got caught before it ever reached them" is the kind of thing people actually remember and repeat.
Most workplace communication defaults to summary, trends, averages, general statements about direction. Summary is efficient, but it's also forgettable, because it doesn't give anyone a specific image to hold onto. A single, well-chosen story does something summary can't: it makes an abstract point concrete enough that people can actually picture it, and repeat it to someone else later in their own words.
People don't remember your bullet points. They remember the one specific thing that happened, and what it proved.
The structure that works in a professional setting is short and disciplined: what was the situation, what specifically happened, and what does it prove. Skip the temptation to narrate every detail, a workplace story isn't a novel, it's a data point with a human face on it, and it should take under a minute to tell.
"Our new onboarding process has been really well received by new hires."
"A new hire told me on their second day that they already understood our escalation process better than they had after a month at their last company. That's the kind of thing the new onboarding flow is designed to do, and it's happening in days instead of weeks."
The second version proves the same point as the first, but it does it through something specific and vivid enough to stick. It also implicitly builds trust, because a concrete, attributable detail reads as more credible than a general claim, it's much easier to dismiss "well received" than it is to dismiss a specific thing a specific person said.
One discipline worth holding onto: use real, honest examples, not composites or invented ones dressed up as if they happened. A fabricated anecdote might sound just as polished, but it collapses the moment someone asks a follow-up question you can't actually answer, and it costs you exactly the credibility the story was supposed to build. If you don't have a real example yet, say so plainly and use data instead, a borrowed or invented story is a worse bet than an honest "I don't have a story for this yet, but here's the number."
Save stories for the moments that actually need them, a key recommendation, a hard-to-believe result, a point you want people to remember after the meeting ends. Not every update needs one. The ones that do stand out precisely because they're not everywhere.