Ask HN: What does your Kanban look like?

My current team follows a very traditional scrum model with a heavy emphasis on story pointing, but my previous one didn't like estimation as much, so we switched to more of a kanban flow while retaining some scrum rituals like a triweekly standup and retro there.

Our GitLab board looked like "Backlog" -> "In Progress" -> Review" -> "Done". All stages were handled by developers, and occasionally the product owner. Stories were usually assigned to multiple people. We didn't have a separate stage for stakeholder sign off because we did automated acceptance testing with a somewhat BDD approach.

Ours is:

"Backlog", "TO DO", "In Progress", "Code Review", "To Be Deployed", "Acceptance Testing", "Done"

Product manages "TO DO" and "Acceptance Testing". Devs do the rest.