The numbers on top of the board represent tickets (JIRA term for cards) within each column, and clicking a ticket reveals more information about the project. I encourage designers to document as much of their research and thought process within tickets.
Building design process within teams
Jules Cheung
1.1K22

Is there a reason for sticking to a simple kanban board? Because I am really interested, as a designer, in knowing why & how a task comes to my to do list. Say maybe there’s a column which could be broad product segments or user groups or design principles. What do you think?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.