Projects
A problem is one thing that went wrong. A project is a piece of work with several moving parts, usually spanning weeks and more than one person.
Open one when the work has outgrown a single problem record: several related problems are pointing at the same underlying thing, or a countermeasure is large enough to need a plan of its own.
Projects run on a board, and the columns are yours to name. Set them to match how your team actually works rather than how a template thinks it should.
Meetings
Meetings can be one-offs or a repeating slot, and they run in the browser without anybody installing anything.
What makes them worth holding inside Kumiko is what is left afterwards: the session is transcribed and summarized into key points, so the meeting produces a record without somebody being volunteered to take minutes.
Two things to settle with your team before you rely on that:
- Tell people the session is being transcribed. It is their conversation.
- Read the summary before you circulate it. It is a useful first draft, not minutes you have approved.
Keeping the two connected
If a meeting produces an action, put it where the work is: on the problem record or the project board, with an owner and a date. A decision that exists only in a transcript has not really been made.