What you are asking for
“What did we ship this week?”
The question makes additions visible. A simplification or an inquiry has little room in the answer.
What the system hears
“How do I show the value of work that takes something away, or avoids a difficulty?”
What that produces
A new feature shows in one screenshot. Removing an approval step that has become useless, clarifying a calculation or dropping a dependency means explaining what got simpler. If your review only asks what shipped, that work disappears.
The team learns fast. It adds, because adding is easy to tell. Six months later, everything is slower, more fragile and more expensive to change, without anyone having made a single bad decision.
A simplification is measured by its effect: less waiting, fewer errors, less upkeep time, one step fewer for the customer. Ask for that number, with the same attention as a delivery number.
An inquiry that concludes a step still protects an important case is a result too. It prevented a mistake.
The decision
At the next review, ask for one example of a simplification or an avoided risk, next to the deliveries. Have people say what changed, for whom, and by how much.
Give a simplification the same time and the same visibility as a feature. A month later, check whether the gain holds and whether a load moved elsewhere.
To discuss
Which recent simplification went unnoticed in our reviews?