EOS V/TO Examples: How to Turn Your Vision/Traction Organizer Into a 90-Day Execution Plan

2026-08-10 · Zentrix Team

A completed V/TO is useful. A used V/TO is powerful. That distinction matters because many leadership teams do the hard work of filling out the Vision/Traction Organizer, feel aligned for a few days, and then slowly drift back into reactive work. The document exists, but the execution rhythm does not.

This guide is not another section-by-section explanation of what belongs in a V/TO. It is for founders and leadership teams who already have the basic picture and now need to turn that picture into a 90-day execution plan the company can actually follow. The goal is to make the V/TO visible in weekly decisions, not just impressive in an annual planning deck.

When the V/TO works, it becomes a filter. It helps the team decide what to start, what to stop, what to postpone, and which issues deserve leadership attention. When it does not work, it becomes a reference document people admire once a quarter while the real business runs somewhere else.

The V/TO is not the finish line

The biggest mistake teams make with the V/TO is treating it like a strategic artifact instead of an operating tool. If your V/TO only appears during annual planning, it becomes static. If it appears in quarterly planning, weekly L10 meetings, Scorecard reviews, and leadership decisions, it becomes a source of focus.

The purpose of the V/TO is to answer three practical questions: where are we going, what matters most this year, and what must happen this quarter. A strong 90-day plan connects those answers to owners, metrics, Rocks, meetings, and issue-solving. Without that connection, even a well-written V/TO can sit outside the day-to-day reality of the business.

Example 1: Early-stage company trying to find focus

Imagine a 12-person software company with a founder-led sales motion, a small product team, and too many possible directions. The team has energy, but the founder keeps seeing new opportunities: a new segment, a partner channel, a product idea, a custom request from a promising prospect. Everyone is busy, but the company is not sure which path matters most.

The temptation is to turn all of that into a giant project list. The better move is to ask what must be true 90 days from now for the vision to become more real. In this example, the company does not need ten priorities. It needs proof of focus.

Notice what is not on the list. The company may still care about partnerships, new features, fundraising, content, and hiring. But a quarter cannot carry every important thought. The quarter should carry the few outcomes that make the V/TO more believable. For an early-stage team, that usually means narrowing the customer, improving the first customer experience, and creating enough visibility to stop guessing.

Example 2: Growing team losing cross-department alignment

Now imagine a 60-person company with sales, operations, finance, and customer success moving quickly but not always together. Sales is closing deals with unique expectations. Operations is absorbing custom work. Finance sees margin pressure. Customer success sees retention risk. Everyone is doing their job, but the system is creating friction between departments.

The V/TO says the 3-year picture includes higher customer retention, stronger margins, and a more consistent delivery experience. Those are useful goals, but they are too broad for 90-day execution. The leadership team has to translate them into concrete operating changes.

The Rocks might become: complete churn analysis and launch a save-playbook for at-risk accounts; implement discount approval workflow across all new deals; roll out the sales-to-operations handoff checklist with weekly audit. This is where the V/TO becomes operational. It stops being a set of aspirations and becomes a shared filter for tradeoffs.

The leadership team should also define what will not happen this quarter. If the company is focused on retention, margin, and delivery consistency, a new experimental segment may need to wait. That is not a lack of ambition. It is strategic discipline. The V/TO gives the team permission to say no without relitigating the entire strategy every week.

Example 3: Mature leadership team needing better accountability

A larger leadership team may already know the vision but struggle with follow-through. Their V/TO might be clear. The problem is that quarterly priorities compete with urgent work, and leaders mark Rocks on track because nobody wants to spend the meeting unpacking reality. In that case, the 90-day plan should include fewer Rocks and a tighter review cadence.

The weekly proof point is what keeps a Rock from becoming a vague intention. Every Rock should have a visible sign of progress that can be reviewed before the quarter is almost over. If the proof point is missing for two weeks, the Rock is not secretly fine. It is an issue.

How to translate a V/TO into a 90-day plan

Step 1: Start with the 1-Year Plan

Do not begin with random projects. Begin with the 1-Year Plan and ask which annual goals are most at risk, which require cross-functional coordination, which unlock other goals, and which will not happen without leadership attention. The answers point toward quarterly priorities.

This matters because many teams build Rocks from whatever feels loudest during planning. The V/TO should create a hierarchy. The 10-Year Target and 3-Year Picture create direction. The 1-Year Plan creates the current strategic bet. Quarterly Rocks create the next executable layer.

Step 2: Pick the few outcomes that matter most

Most teams choose too many Rocks because they confuse importance with priority. Many things are important. Very few should define the quarter. A useful test is simple: if we complete this Rock, will the company be meaningfully closer to the V/TO? If the answer is no, it may be a task, a project, or departmental work, but it is probably not a leadership Rock.

Another test is whether the Rock requires leadership focus. If one department can complete the work through its normal operating rhythm, it may not need to occupy the leadership team's quarterly agenda. Save leadership Rocks for the work that requires alignment, decision-making, resource tradeoffs, or visible cross-functional commitment.

Step 3: Assign one owner per Rock

Shared ownership sounds collaborative, but it often weakens accountability. Each Rock needs one owner who is responsible for moving it forward, reporting progress, and raising issues early. Other people can contribute. One person owns the outcome.

Ownership does not mean the owner does all the work. It means the owner is the person the team can look to for truth. Is the Rock on track? What changed? What support is needed? What issue needs to be solved? Without one owner, the Rock becomes a group hope.

Step 4: Define done before the quarter starts

A Rock like improve onboarding creates ambiguity. A better Rock is: launch onboarding v1 for new customers, including kickoff template, first-30-days checklist, and success milestone dashboard. That version gives the team a clear finish line.

• What does done mean?
• How will we measure progress?
• What visible evidence will show completion?
• What issue could block this?
• What will we stop or postpone to make room for it?

The last question is especially important. A plan without capacity tradeoffs is not a plan. It is a wish list. If a Rock is important enough to define the quarter, leaders should know what time, budget, attention, or opportunity cost it requires.

Step 5: Connect Rocks to the L10 meeting

Rocks do not stay alive by being written down. They stay alive by being reviewed. In the weekly L10, each Rock should be checked quickly: on track, off track, or done. If a Rock is off track, do not debate it during the status section. Drop it to the Issues List and solve it through IDS. That separation keeps meetings efficient and prevents status updates from turning into circular discussion.

This is where many teams lose discipline. They either spend too long explaining every Rock, or they rush through the list without making off-track items actionable. The point of the Rock review is not storytelling. The point is to identify which priorities need problem-solving.

Step 6: Use the Scorecard as an early warning system

The Scorecard tells you whether the business is drifting before the quarter is over. If a Rock is about improving retention, the Scorecard should include a related leading indicator, such as churn-risk accounts reviewed, onboarding milestone completion, or customer health score coverage. If a Rock is about sales execution, the Scorecard might track qualified pipeline, proposal velocity, close rate, or outbound activity quality.

The point is not to measure everything. The point is to measure the few signals that tell you whether the plan is working. A V/TO without metrics can become inspirational but vague. A Scorecard without V/TO context can become busy but disconnected. Together, they turn strategy into visible operating evidence.

Common drift signals

Even good teams drift. The earlier you catch it, the easier it is to correct. Watch for Rocks marked on track with no evidence, the same issue appearing in multiple L10 meetings, red Scorecard numbers with no IDS discussion, department priorities conflicting with the V/TO, new ideas replacing committed quarterly priorities, and owners who are unclear about what done means.

When you see drift, do not blame the team. Tighten the operating rhythm. Bring the conversation back to the V/TO, clarify the tradeoff, and decide what gets solved now versus later. Drift is not a character flaw. It is a signal that the system needs more visibility, sharper ownership, or clearer decision rights.

A simple weekly review rhythm

The V/TO should not dominate every meeting, but it should inform the decisions that matter. A team does not need to reread the entire document every week. It does need to know whether the week's decisions are supporting or diluting the plan.

How to handle new ideas during the quarter

A useful V/TO does not mean the team stops seeing opportunities. New customer requests, partnership ideas, hiring needs, product improvements, and market signals will still appear. The difference is that those ideas should be processed through the operating rhythm instead of quietly replacing the plan.

When a new idea appears, ask three questions before turning it into work. First, does this directly support the current V/TO and 1-Year Plan? Second, is it urgent enough to displace one of the current Rocks? Third, who owns the tradeoff if we say yes? These questions slow the team down just enough to protect focus.

If the answer is yes, the team should make the tradeoff explicit. Which Rock changes? Which owner gets capacity? Which Scorecard signal will show whether the decision worked? If the answer is not yet, capture the idea on the Issues List or a future-planning list so it is not lost. That gives the Visionary room to keep bringing ideas without forcing the company to chase every idea immediately.

This is especially important for founder-led companies. Founders often introduce ideas because they see real possibilities. The team often hears those ideas as new priorities. A connected V/TO gives both sides a healthier pattern: ideas are welcome, but committed quarterly execution stays protected unless the leadership team consciously changes the plan.

How Zentrix OS helps keep the V/TO alive

The hard part of EOS is not filling out the tools. It is keeping the tools connected. Your V/TO sets the direction. Rocks define the quarter. The Scorecard shows leading indicators. The L10 meeting creates the weekly accountability loop. The Issues List turns obstacles into decisions.

When those pieces live in separate spreadsheets, documents, and meeting notes, teams lose context quickly. Zentrix OS helps keep the operating rhythm connected: V/TO priorities can be linked to quarterly Rocks, Rock owners and status stay visible between meetings, Scorecard metrics reveal whether execution is drifting, L10 discussions stay tied to the work that matters most, and issues can be captured, prioritized, and solved without losing the thread.

That connection matters because strategy does not usually fail all at once. It fails through small gaps in follow-through. A missed update here, a vague Rock there, an issue that never gets solved, a Scorecard number that is red for three weeks without ownership. The V/TO stays alive when those gaps are visible enough to fix.

Final thought

The V/TO gives your team clarity. The 90-day plan gives that clarity motion. You do not need a more complicated strategy process. You need a tighter connection between vision, quarterly priorities, weekly metrics, and real accountability.

That is how the V/TO becomes more than a document. It becomes the operating rhythm your team uses to move the business forward, one clear quarter at a time.