Kumiko is where your organization keeps its problems. Not only the ones big enough to warrant a meeting. All of them: the recurring annoyance, the process that works only when one particular person is in the office, the thing everybody has quietly worked around for a year.
The reasoning is simple. A problem that is written down can be looked at. A problem that exists only in somebody’s head cannot.
The four places you will work
- Problems. Everything that has been reported. Each one has an owner, a discussion thread, and a record of what was done about it.
- Projects. A board for improvement work that is bigger than a single problem.
- Meetings. Sessions you can run in the browser, with the notes and key points captured for you.
- Dashboards. What is open, what is overdue, and where problems are clustering.
What is actually asked of you
Very little. Report what you notice. If something is assigned to you, say what you found in the thread and keep the status honest. That is most of it.
You are not asked to categorize your own report, decide who should own it, or judge how serious it is. That happens when the problem arrives.
One thing worth saying before you roll it out
Kumiko works in organizations where reporting a problem is not treated as a complaint, and struggles in ones where it is. No software can settle that for you, so it is worth saying out loud to your teams: the person who writes down an awkward truth is doing everybody a service.