Kanban boards are a common sight now in many teams. It’s not just software development teams either. I’ve seen them used by all sorts of teams.
One of the common mistakes I see people making with Kanban boards is creating one that reflects the perfect process, not the process they currently have.
Kanban is a visual aid. It helps you see the state of your system; how much work is in play, where that work is, who is working on what and where the bottlenecks are. So it needs to map to reality. It should “model” (and all models are wrong) your current process.
There is no harm in creating a picture of what you want your process to work like. That can be valuable.
Creating a Kanban of your current process, no matter how bad it is, and then iterating through improvements is a far better way to get a better process.