Tasks

Tasks are available in the Enterprise package, and also in Kimola On-Premises. A task carries a finding to the teammate who can act on it, with the feedback and the numbers behind it frozen as evidence, and everyone in the team sees who is on what. Kimola drafts the title and the description, why it matters, what to do and when it is done, and you choose the assignee, the due date, the priority and the teammates to keep informed.

Use Tasks when a finding in a Space needs someone to act on it. A task can come from a Signal, a piece of feedback, a filtered view, a theme, a table, a Customer, a Department, an action of a Space's Action Plan, or your own words. Reports, their Action Plans included, don't make tasks.

Kimola is not a task tracker: the work can happen in your team's own tool. With the Jira integration, found in Integrations, a task is sent to Jira as a new issue or linked to an existing one, and its status, assignee and due date then follow Jira.

The loop closes in Kimola. After a task is done, Kimola measures the same feedback two and four weeks later, and again at eight and twelve weeks, and tells you whether customers noticed: improved, regressed, or not enough data yet. Task emails and a weekly digest on Mondays keep assignees and watchers up to date.