Q:

Different workflows on one kanban board

From reading discussions here the general consensus seems to be that you should have a ratio of one kanban board for one team.

How do you model multiple workflows in the team on one board? 

Specifically, I suppose, how do you represent processes with discrete sub-tasks that require coorindation between people, while still being able to implement a policy to limit work in progress, and being able to see the "capacity" and "backlog"?

To give a real example, our team has multiple kanban boards:

Board 1: Regular one-off team tasks, such as "check help desk"
Board 2: Article-creation workflow, which involves stages of:

Contacting people, 
Interviewing them, 
Passing the content to an editor, 
and scheduling the content to be published

Board 3: Video-creation workflow, which involves stages of:

Decide on topic
Record the video
Produce the video
Upload the video
Pass the content to an editor
and scheduling the content to be published

It works well to have multiple kanban boards describing specific proecesses. However, this also means the "capacity" of the team is not represented in any one place.

A:

I disagree with your consensus. I would say the Kanban community in general assumes a decoupling between teams and Kanban systems and that a Kanban board should probably visualize a Kanban system. Multiple workflows should be different boards. Unless they have the same or mostly overlapping steps, in which case they could be on the same board and optionally separated by swim-lanes, or card colors or something. 
Regarding the issue that total team capacity is not represented in one place, that is true I guess, but it might be ok, in the end you have statistics like "over the last year we delivered 100 one-off tasks, created 40 articles and 20 videos", having fluid capacity across systems mean pull decisions can be supported by a checklist or some heuristics (based on e.g. cost of delay or something) so help the team member decide which board to pull from. If you need to, you could set up a sort of portfolio thing one level above the "team board" to set up wip limits across accounts or products (it probably makes more sense to split team capacity along a business oriented dimension rather than something arbitrary like item type). Setting up a portfolio probably makes more sense once you have at least 3 teams to manage though.

