Creating & Tracking Action Items

Why Action Items Matter

A retrospective without action items is just a conversation. Action items are the concrete commitments that transform team reflection into real improvement. They are the bridge between identifying a problem and actually fixing it. Without them, the same issues resurface retro after retro.

In Unpack, action items are first-class objects that persist beyond the retro session. They can be assigned to owners, given due dates, tracked across sprints, and synced to external project management tools.

Creating Action Items

Action items can be created during two phases: Discuss and Commit. The best practice is to capture action items as they emerge during discussion, then review and refine them during the commit phase.

During the discussion phase

1. While a topic is being discussed, click the Add Action Item button on the active topic.
2. Write a clear description of what needs to happen.
3. The action item is automatically linked to the card or group being discussed.
4. Optionally assign an owner and due date right away, or leave these for the commit phase.

During the commit phase

1. Click New Action Item in the action items panel.
2. Write the action item description.
3. Assign an owner from the team's participant list.
4. Set a due date or target sprint.
5. Review and finalize all action items before closing the retro.

Assigning Owners

Every action item should have a single owner. The owner is the person accountable for making sure the action item gets done. This does not mean they do all the work themselves, but they are responsible for driving it to completion.

How to assign an owner

1. Click the Assign button on the action item.
2. Select a team member from the dropdown list. All retro participants appear as options.
3. The assigned owner is displayed on the action item card with their avatar.

Owners receive a notification when an action item is assigned to them and can view all their action items from their personal dashboard.

Writing SMART Action Items

Vague action items rarely get completed. Unpack encourages SMART action items that are Specific, Measurable, Achievable, Relevant, and Time-bound.

Examples of good vs. poor action items

• Poor: "Improve code reviews."
  SMART: "Add a code review checklist to the PR template by end of next sprint."
• Poor: "Communicate better."
  SMART: "Post daily async standup updates in the team Slack channel starting Monday."
• Poor: "Fix the build."
  SMART: "Investigate and resolve the flaky integration test in the checkout flow by Friday."

AI-powered SMART refinement

Unpack's AI can help transform vague action items into SMART format. When you create or edit an action item, click the Make SMART button to receive an AI-generated suggestion that adds specificity, measurability, and a time frame. You can accept, modify, or discard the suggestion.

Syncing to Jira and Linear

Action items can be synced to your team's project management tool so they appear alongside your regular sprint work. Unpack supports integration with Jira and Linear.

Setting up sync

1. Ensure the Jira or Linear integration is configured for your organization (see the Integrations section of the help center).
2. During the commit phase, action items display a Sync button.
3. Click Sync to create a corresponding issue or ticket in your project management tool.
4. The action item in Unpack is linked to the external ticket, and status updates flow back to Unpack.

What gets synced

• Action item title and description
• Assigned owner (mapped to the corresponding user in Jira or Linear)
• Due date or target sprint
• A link back to the retro for context

Carry-Over from Previous Retros

Not every action item gets completed within a single sprint. Unpack tracks action items across retros and automatically surfaces incomplete items when you start a new retrospective.

How carry-over works

1. When you create a new retro for a team, Unpack checks for any incomplete action items from previous retros.
2. These items are displayed in a Carry-Over section during the draft or commit phase.
3. The facilitator can choose to carry items forward into the new retro, mark them as completed, or dismiss them if they are no longer relevant.

Carry-over creates an accountability loop. The team sees which commitments they followed through on and which ones slipped, which itself becomes valuable input for the retro discussion.

Tracking Completion Across Sprints

Unpack provides several views for tracking action item progress over time:

Team dashboard

The team dashboard shows all open action items across retros. Items are grouped by retro and sorted by due date. Each item shows its current status, owner, and age.

Personal dashboard

Each team member can see their assigned action items on their personal dashboard. This provides a focused view of what they are responsible for completing.

Retro history

When viewing a closed retro, you can see the final status of all action items that were created during that session. This gives context for whether the team followed through on its commitments.

Completion metrics

Over time, Unpack tracks your team's action item completion rate. This metric is available in the team analytics view and helps the team understand whether their retro commitments are translating into real change.