A status is a sentence your customer reads without you there to explain it. "Under review." "Planned." "Shipped." Each one is a tiny promise, and customers read them far more literally than teams write them.
So it's worth asking, for every status on your board: what does a customer conclude when they see this?
Statuses are for them, not for your sprint board
Teams often copy their internal workflow onto the public board. Triaged, Groomed, In design, In QA, Blocked. Every one of those means something precise to the team and nothing to a customer. Worse, some of them invite questions you don't want. "Blocked" on a public post means "please email us asking why".
Keep the public vocabulary small. Most boards need five or six states at most, and each should answer the question a customer actually has: is anyone looking at this, and should I expect it?
What each state should promise
Open means it's been received and others can vote. That's all.
Under review should mean someone is actively learning about it. If a post sits in review for six months, the status is lying. Move it back, or close it with a reason.
Planned is the strongest word on your board. Use it when you genuinely intend to build the thing. Not when you'd like to, not when it's in a big maybe-list. Customers will tell their boss it's planned.
In progress means work has started. People will expect it soon, so put things here late rather than early.
Shipped means they can use it today. Link to where.
Closed needs a reason, every time. "Closed" on its own reads as "go away".
Change the status when it means something
A status change is news, so it should happen when something meaningful happened. Moving a post between two shades of the same state, back and forth, teaches people to ignore your updates. Moving it when the situation really changed teaches them that an email from your board is worth opening.
Say a sentence with it
The best status changes come with one line of context. "Planned for the next quarter, starting with CSV and adding Excel after." "Closed: we're focusing on the API, which covers this for most teams." One sentence turns a label into an answer, and it costs you thirty seconds.
If you read your board as a customer once a month, you'll spot the statuses that have stopped telling the truth. Fix those first.