The more I think about this, the more I want to underscore it. When I was thinking about how I use Kinopio at work (Kinopio business/group/team plan dream features?), it occurred to me how many times having a list component would help me help others use Kinopio. Some examples:
- List of when people are out of the office
- Making a list of todos (“action items” as we in the biz call them)
- Role call for a meeting
- I could go on…
Without having such a structure, I takes a lot of explaining to do this simple thing: “Create a card near that pile” or “Create a card and connect it to that other card”. And it’s not even a matter of knowing how to use Kinopio—the tool is too flexible that you have to define a convention/protocol every time. For example, we recently decided to have an area to keep track of PTO. I can’t simply say, add when you’ll be on PTO to that list. I have to describe to put it under so-and-so heading and connect it. If there’s no existing example, and someone comes to it, they’ll be asking, how are we doing this again?
