Rocks
Rocks are the most important priorities for the quarter. In EOS, each leadership team member owns 3 to 7 Rocks -- specific, measurable goals that must be completed within 90 days. EOS Hub makes it easy to create, track, and review Rocks at both company and department levels.
INFO
For the EOS theory behind Rocks, see EOS Methodology: Rocks.
Company vs. Department Rocks
EOS Hub distinguishes between two levels of Rocks:
| Level | Description | Who Sets Them |
|---|---|---|
| Company | Organization-wide priorities for the quarter | Leadership team |
| Department | Team-specific priorities that support company Rocks | Department teams |
Company Rocks are owned by the leadership team and represent the top priorities for the entire organization. Department Rocks are set by individual teams and should align with and support the company-level Rocks.
TIP
During quarterly planning, set company Rocks first, then cascade to department Rocks. This ensures alignment across the organization.
Creating a Rock
To create a new Rock:
- Navigate to Rocks in the sidebar.
- Click Add Rock.
- Fill in the form:
| Field | Description |
|---|---|
| Title | Clear, specific name for the Rock |
| Owner | Team member responsible for completion (type a name to find them in a long list) |
| Level | Company or Department |
| Description | Optional detailed description |
| Due Date | End of the quarter (auto-populated) |
Writing Good Rocks
A well-written Rock is:
- Specific -- "Launch v2 of the mobile app" not "Improve the app"
- Measurable -- "Hire 3 senior engineers" not "Grow the team"
- Achievable -- Can be completed in 90 days
- Relevant -- Supports a company Rock or strategic goal
- Time-bound -- Due at the end of the quarter
Editing and Deleting Rocks
ADMIN and OWNER roles can edit a Rock after it has been created. Open the Rock and choose Edit rock to change its:
- Title and description
- Owner
- Quarter and year
- Level (Company level is available only on the leadership team)
Deleting a Rock asks for confirmation first. Its milestones are deleted together with the Rock.
INFO
Company Rocks also appear on other teams' Rocks pages for visibility. They are managed (edited, updated, deleted) on the page of the leadership team that owns them.
Milestones
Each Rock can have milestones -- intermediate checkpoints that break the Rock into smaller steps. Milestones help track progress throughout the quarter rather than waiting until the end.
To add milestones:
- Open a Rock.
- Click Add Milestone.
- Enter the milestone title and target date.
- Mark milestones as complete as you progress.
Milestones can be changed later with Edit milestone or removed with Delete milestone (a confirmation is shown before deleting).
Example milestones for a Rock titled "Launch Customer Portal":
| Milestone | Target Date |
|---|---|
| Complete wireframes | Week 2 |
| Finish backend API | Week 6 |
| User acceptance testing | Week 10 |
| Production deploy | Week 12 |
Status Tracking
Each Rock has a status that owners update regularly. A Rock's status and milestones can be updated by the Rock's owner or by an ADMIN or OWNER of the team:
| Status | Meaning |
|---|---|
| On Track | Progressing as planned, expected to finish on time |
| Off Track | Behind schedule or facing obstacles |
| Done | Completed |
WARNING
Be honest about status. An "Off Track" Rock is not a failure -- it is a signal that the team should discuss obstacles and adjust. Marking a struggling Rock as "On Track" only delays the conversation.
Weekly Reports
Every week each Rock gets a report: On Track, Off Track or Done, with an optional note. The reports make up the Rock's history (see the progress view below), and the Rock's status is always its newest report.
- In the meeting a report is for the meeting's week (see Rock Review).
- Anywhere else -- the status items in a Rock's ⋯ menu, Report with a note…, the API or an AI assistant -- a report is for this week, or for next week once this week's meeting is over. So a report on Friday counts for Monday's meeting and never overwrites what the meeting recorded.
- An owner can report in advance: the meeting then shows "Reported in advance" with the time.
- A week can be reported or corrected later from the progress view (up to next week). The owner, or a team ADMIN or OWNER on their behalf ("Entered by …").
A week nobody reported is not reported (–). A ? means nobody knew: the owner missed that week's meeting and hadn't reported in advance. Weeks before the team's first report, weeks the team skipped (no meeting, no report at all) and weeks after a Rock is done expect nothing.
The statuses feed the Dashboard: its Rocks pillar is the share of this quarter's Rocks on track or done (target 80 %), and its Rocks card shows them by status, by owner and by milestones, with overdue milestones marked. Off-track Rocks appear under Needs attention, Rocks finished in the last 7 days under Wins.
Card, Table and Progress View
EOS Hub offers three ways to view Rocks:
Card View
Rocks are displayed as cards grouped by status (On Track, Off Track, Done). Each card shows the Rock title, owner, milestone progress, and the quarter's weekly reports as small squares. This view is great for quick visual scanning.
Table View
Rocks are displayed in a table with columns for title, owner, status, milestones, and progress. Click a column header to sort by it, and click again to reverse the order. This view is better for detailed review. On a phone each Rock is a card, with the title on top and the details below.
Progress View
The quarter week by week, like a spreadsheet: a Rock per row, a column per week (W27, W28, …, this week highlighted).
| Mark | Meaning |
|---|---|
| ● | On Track |
| ◆ | Off Track |
| ✓ | Done |
| – | Not reported |
| ? (dashed) | Unknown: the owner missed the meeting |
| ○ | This week, not reported yet |
Click a week to see who reported it and when, the note, or the meeting the owner missed; the owner or an admin can report or change that week there. The last row counts the reported Rocks per week (e.g. 9/10), the last column sums up the quarter (weeks off track, weeks not reported). On a phone the Rock column stays in place and the weeks scroll sideways, starting at this week.
Switch between views using the toggle in the top-right corner of the Rocks page.
Exporting to Excel
Export to Excel next to the quarter downloads the quarter's Rocks as an Excel workbook (.xlsx): company Rocks first, then the team's own, each with its level, owner, current status, milestones done, every week's report and the latest note. Statuses and weeks are coloured -- on track green, off track red, done blue, unknown (?) or owner absent amber, not reported grey -- and always say it in words too; a legend explains the marks.
Filtering Rocks
The filter bar above both views narrows the Rocks of the chosen quarter (the quarter and year pickers work as before):
- Search -- in the title
- Status -- On Track, Off Track, or Done
- Owner -- one or more people
- Level -- Company Rock or Department Rock
- Milestones -- Overdue milestones keeps the Rocks with an unfinished milestone past its due date
For example, Status = Off Track together with Milestones = Overdue milestones shows the Rocks to raise in the next Rock Review. The filters are kept in the address -- see Filtering Lists.
Rock Review in Meetings
During the Rock Review segment of the L10 Meeting every Rock of the meeting's quarter is reported for the meeting's week:
- The facilitator marks who is absent (tap a name; the closing rating takes it over).
- Each Rock shows its last 4 weeks and the buttons On Track, Off Track, Done; none is selected until this week is reported. A note can be added.
- A Rock whose owner is absent and hasn't reported in advance shows Unknown – recorded as ?; whoever knows may still report it.
- An Off Track Rock can be added as an issue for IDS with one click.
- The line above the Rocks counts them: "Reported 5 of 8 · 1 unknown (absent) · 2 waiting".
Reporting is expected every week, but it doesn't block the meeting: Conclude lists the Rocks still waiting, and the meeting can end anyway.
Quarterly Workflow
The typical Rock lifecycle follows the EOS quarterly cadence:
- Quarterly Planning -- Leadership team sets company Rocks. Department teams set their Rocks.
- Weekly Review -- Rock status is reviewed in every L10 Meeting.
- End of Quarter -- Rocks are evaluated. Completed Rocks are archived. Incomplete Rocks are either carried forward or dropped.
- New Quarter -- New Rocks are set based on the V/TO and organizational priorities.
Related Pages
- EOS Methodology: Rocks -- Why Rocks work and how to set them
- L10 Meetings -- Rocks are reviewed in segment 3
- Issues -- Off Track Rocks generate issues
- V/TO -- Rocks should align with the 1-year plan
- Dashboard -- The Rocks pillar, status, owners and milestones