Make Your Annual Goals Real With Rocks Your Team Can Finish

An annual plan can fit on one page while the work required to deliver it remains undefined. Increase revenue. Improve retention. Develop the team. The direction may be right, but those statements leave a practical question unanswered: what needs to be different by the end of the next quarter?

I want that question answered before the plan becomes another document people refer to when explaining why they are busy. A goal deserves more than agreement. It needs a clear connection to work somebody can own, finish, and show the team.

That is the value I want leaders to get from Rocks. Keep the annual ambition, then make a smaller set of commitments concrete enough to guide this week's choices. The discipline is in choosing what matters, defining the finish, and protecting the work when competing demands arrive.

Use the Annual Plan to Choose the Next Real Change

In EOS implementation, quarterly Rocks are the priorities for the next ninety days, while annual planning provides a broader review of vision and priorities. I want those time horizons to support each other. The annual direction helps you choose which quarterly changes deserve attention.

Start with one annual objective and ask what currently stands in its way. If customer retention matters, the obstacle might be an unreliable onboarding process. If you want people to lead more independently, the obstacle might be unclear decision authority. Each possibility suggests different work.

Do not automatically divide an annual number into four pieces and call the result a Rock. A quarterly revenue target can tell you how performance compares with the plan. It may not tell you which change will make better performance possible.

I would separate the outcome we want to watch from the project we are committing to complete. That distinction helps the team discuss whether it has chosen work that addresses the actual constraint. Otherwise, people can keep reporting the number without changing the conditions behind it.

Consider a hypothetical service business that wants customers to stay longer. Its leaders have noticed that handoffs from sales to delivery are inconsistent. Instead of announcing a broad priority to improve retention, they could define a quarter's work around creating and testing a consistent handoff.

That example still requires investigation. Perhaps the handoff is only one part of the problem. Before committing the quarter, look at recent cases, talk with the people doing the work, and confirm that the proposed project addresses something worth fixing.

Then choose. You may have several legitimate needs and insufficient capacity to pursue all of them at once. I want the leadership team to name that limitation rather than bury it under a long list of priorities. A useful plan tells people what will receive attention and what will wait.

Define Done Before You Start Reporting Progress

A vague commitment gives everyone a different finish line. One person believes improving onboarding means writing a document. Another expects the team to be trained. A third assumes customers will already be experiencing the new process. All three can work hard and still disagree about whether the priority is complete.

I want that disagreement resolved at the beginning. Describe the result in observable terms. Name what will exist, who will use it, and what evidence will demonstrate that the commitment has been fulfilled.

For the hypothetical handoff project, a completion statement might include an agreed checklist, assigned responsibilities, training for the people involved, and a pilot using five new customer handoffs. The number five is an illustration, not a universal standard. Choose a test that fits the actual work and the available capacity.

Be careful about what that completion proves. Finishing a pilot does not establish that customer retention has improved. It establishes that the team completed a defined change and gathered evidence about how it works. You still need to observe the longer-term outcome.

This matters because leaders can unintentionally reward activity by calling it results. A draft, a meeting, or a software configuration may be useful progress. Whether it completes the Rock depends on the agreement you made before the work began.

Give the commitment one accountable owner. Other people can contribute expertise and carry assigned tasks, but the team needs to know who will keep the overall commitment visible, surface problems, and bring the result back for review.

Ownership also needs practical authority. If the owner must negotiate every decision with three leaders who give conflicting instructions, the name on the plan will not solve the problem. Clarify which decisions the owner can make and how unresolved conflicts will be addressed.

I would rather spend an uncomfortable half hour defining the finish than spend the final week of the quarter debating what everybody meant. That conversation protects the person doing the work as much as it protects the business.

Protect the Work With Capacity and Honest Weekly Review

Adding a Rock does not create more hours in the week. The owner still has customers, employees, and ongoing responsibilities. If you ignore that reality during planning, the quarterly priority may become work people are expected to complete after everything else is done.

Before confirming the commitment, ask what it will require. Identify the people, time, access, and decisions needed. Then say what will pause, shrink, or move to someone else so those resources are actually available.

In the handoff example, the project owner may need time with sales and delivery staff. Those conversations will compete with current customer work. The leadership team has to make that tradeoff explicit instead of praising the priority on Monday and questioning every hour spent on it by Thursday.

I want weekly review to answer a useful question: based on what we know now, do we expect to finish the commitment as agreed? An optimistic answer without supporting evidence does not help the team make decisions.

Ask about the next meaningful checkpoint and what could prevent it. Has the pilot started? Are the necessary people available? Does an unresolved decision belong to the owner, or does leadership need to make it?

If the work is off track, identify the obstacle while there is still time to respond. Maybe the original scope was too large. Maybe a dependency changed. Maybe a difficult conversation has been avoided. Those are different problems, and they need more than a general instruction to work harder.

The leader's response matters here. If reporting a problem brings embarrassment or a lecture every time, people have a reason to delay the report. I want the standard to be early honesty followed by a responsible decision.

That does not mean every missed commitment gets an easy explanation. It means you examine the cause accurately. Hold people accountable for what they agreed to do, and hold yourself accountable for the priorities, resources, and decisions you supplied.

Finish the Quarter Without Rewriting the Agreement

As the quarter ends, review the evidence against the original completion statement. If the agreed result exists, acknowledge it clearly. If it does not, say what remains unfinished without stretching the language until the commitment appears complete.

This is where leaders have to resist a convenient story. A team may have invested substantial effort and produced valuable work. You can recognize that contribution while still being honest that the original Rock was not finished.

For the handoff project, perhaps the checklist and training are complete but only two of the five planned pilot handoffs have occurred. That is useful progress. The team still needs to discuss the uncompleted test and why it fell short of the agreement.

Do not assume every unfinished Rock belongs on the next quarter's list unchanged. Revisit whether the outcome still matters, whether the approach remains sound, and what you learned about capacity. Finish, resize, replace, or stop the work through an explicit decision.

When a project is complete, decide how the result becomes part of ordinary operations. Who maintains the process? Where is it documented? How will a new employee learn it? A completed project can lose its value if nobody owns what happens after the celebration.

I also want to review the choice itself. Did this Rock deserve the attention it received? What happened to the annual objective while we worked on it? What evidence suggests that the next quarter should continue in the same direction or address a different constraint?

That review gives the annual plan a practical life. You keep learning as the year unfolds instead of treating the original document as either untouchable or irrelevant. The direction remains visible, and the work can respond to what the business is actually experiencing.

For me, the leadership test is straightforward: can the people doing the work explain the priority, the finish, and the tradeoff? If they cannot, the next useful step may be a clearer agreement rather than another demand for urgency.

Action Items From Today

1. Connect one Rock to one annual objective. Write the objective, the obstacle you are addressing, and why this quarter's work is worth doing. Confirm the obstacle with relevant evidence before treating your first explanation as the answer.

1. Write a completion statement. Describe what will exist, who will use it, and what you will inspect at the end of the quarter. Ask two people involved to explain the finish in their own words and resolve any difference now.

1. Name the owner and the authority. Identify who is accountable for the whole commitment, who contributes, and which decisions require leadership approval. Give unresolved conflicts a clear path rather than leaving the owner to negotiate indefinitely.

1. Make one capacity tradeoff visible. Choose work that will pause, shrink, or transfer so the priority has a realistic place in the week. Communicate that choice to everyone whose expectations need to change.

1. Schedule the evidence review. Review the next checkpoint weekly and the agreed result at quarter end. Include a handoff decision so completed work becomes a maintained practice rather than an abandoned document.

Five Bridges Challenges

• Internal: Identify a commitment you have kept describing as on track without examining the evidence. What would an honest update say today? Give that update while there is still time for someone to help resolve the obstacle.

• Relationships: Ask the owner of a current priority which conflicting expectation is making the work harder. Listen before defending the competing demand. Agree on one clarification that will help them act without guessing what you value most.

• Environment: Inspect how your quarterly priorities appear in the actual workweek. Is there time, authority, and a dependable review process behind them? Change one condition that currently makes the important work depend on somebody's unpaid evening or last-minute rescue.

Choose a Rock your team can understand and give it the conditions required to finish. Then return to the evidence together. That is how I want the annual plan to shape the work, one accountable commitment at a time.

Inspire & Impact,

Josh