Use Issues to manage and resolve incidents by the team. Issues are a more formal and structured way of noting responsibility for actions than to-dos, and are also less likely to be planned up front.

Basic issue information

• Issue name.
• Description: Briefly describe what the issue concerns.
• Person responsible: Assigning personal responsibility maximises the chance of getting issues resolved.

Issue categories

• Issue domain: what knowledge area the issue belongs to (e.g. Editorial, Production, etc.).
• Issue severity: how bad the consequence would be if the issue is left unsolved (vital, major and minor).

Issue date information

• Resolution deadline: the final date to get the issue settled.
• Date resolved: when the issue is actually solved.

Issue status

• Current status: the current status the issue is within (e.g. investigating, resolved OK, etc.).
• Resolution: The final resolution to settle the issue.

The issues that you log appear at company level (Workflow > Issues) and also appear on the work affected, in the workflow section. Consider using them as an agenda for regular meetings.