Issues
Issues are obstacles, ideas, and problems that need to be resolved. EOS Hub implements the IDS (Identify, Discuss, Solve) process from EOS to help teams work through issues systematically rather than letting them pile up.
INFO
For the full IDS methodology, see EOS Methodology: IDS Process.
The Issues List
Every team has an Issues list -- a living backlog of items that need attention. Issues can come from:
- Off-track Scorecard measurables dropped during meetings
- Off-track Rocks flagged during Rock Review
- Headlines that need discussion
- Items raised by team members at any time
Creating an Issue
To add a new issue:
- Navigate to Issues in the sidebar.
- Click Add Issue.
- Fill in the form:
| Field | Description |
|---|---|
| Title | Short, clear description of the issue |
| Description | Optional detailed context |
| Priority | Low, Medium, or High |
| Created By | Automatically set to the current user |
Issues can also be created directly from other parts of the application:
- Scorecard -- Click the issue icon on an off-track measurable.
- Rocks -- Drop an off-track Rock to the Issues list.
- Meetings -- Create issues during any meeting segment.
Priority Levels
| Priority | When to Use |
|---|---|
| High | Blocking progress, needs immediate attention |
| Medium | Important but not urgent, should be addressed soon |
| Low | Minor items, nice-to-have fixes |
TIP
During the IDS segment of the L10 Meeting, the team votes on the top three issues to tackle, regardless of the priority labels. Priorities help with long-term backlog management, but the weekly meeting focuses on what matters most right now.
IDS Workflow
Issues progress through three states:
Open
The issue has been identified and is on the list. It has not been discussed yet. Most issues spend time here until they are selected for IDS during a meeting.
Solving
The issue is actively being discussed by the team. In EOS Hub, moving an issue to "Solving" status indicates that it is the current focus of the IDS segment.
When solving an issue:
- Dig into the root cause, not just the symptoms.
- Discuss openly -- every team member should contribute.
- Arrive at a solution, which typically becomes one or more To-Dos.
Solved
The issue has been resolved. A To-Do has been created to implement the solution, or the issue was resolved through discussion.
Solved issues are archived and removed from the active list but remain in the history for reference.
Dropping Issues to To-Dos
The most common outcome of solving an issue is one or more To-Dos. From the issue detail:
- Click Create To-Do.
- The To-Do is pre-filled with context from the issue.
- Assign an owner and set a due date (default: 7 days).
- The To-Do appears on the To-Dos page.
Managing the Issues List
Reordering
During the IDS segment, the team reorders issues by importance. Drag and drop issues to change their position, or use the priority vote to surface the top three.
Filtering
Filter the Issues list by:
- Status -- Open, Solving, or Solved
- Priority -- High, Medium, or Low
- Created by -- Filter by the person who raised the issue
Bulk Actions
Select multiple issues to:
- Change priority in bulk
- Move to Solved status
- Delete resolved issues
Best Practices
- Be specific. "Revenue is down" is not actionable. "Lost 3 enterprise deals in Q1 due to pricing" is.
- One issue, one item. Do not combine multiple problems into a single issue.
- Do not solve during Identify. When adding issues, just capture them. Save the discussion for the IDS segment.
- Time-box discussions. If an issue cannot be solved in the allotted time, either break it into smaller issues or assign someone to research and bring it back next week.
- Aim for 3 to 5 issues per meeting. Focus on the most impactful items.
Related Pages
- EOS Methodology: IDS -- The theory behind Identify, Discuss, Solve
- L10 Meetings -- Issues are resolved during the IDS segment
- To-Dos -- Solutions often become To-Dos
- Scorecard -- Off-track metrics generate issues
- Rocks -- Off-track Rocks generate issues