Try this with a leadership team that has been running on EOS for a year. Put the seven of them in separate rooms, give each a blank sheet, and ask: why does this company exist? Then compare.
Most teams do not survive this test. Not because the V/TO is wrong — it's usually perfectly serviceable — but because the team filled it in rather than fought it out. There is a real difference between a box that has words in it and a question a group of people have genuinely settled.
That distinction is what Lencioni's second discipline, Create Clarity, is built to expose. He frames it as six questions a leadership team must answer, and answer identically. Set against the V/TO, the overlap is close enough to be reassuring and the differences are sharp enough to be useful.
The six questions, against the V/TO
| The Advantage | Where it lives in EOS | What the question forces that the box does not |
|---|---|---|
| Question 1Why do we exist? | Core Focus — the Purpose / Cause / Passion half | A reason beyond money that is not a description of what you sell. Most teams answer this question with their product and never notice they've done it. |
| Question 2How do we behave? | Core Values | Lencioni's taxonomy — core, aspirational, permission-to-play, accidental — is a harder filter than the EOS discovery exercise alone. Most lists of five values contain one real one and four that are table stakes. |
| Question 3What do we do? | Core Focus — the Niche half | A flat, literal, almost boring description. The test is whether a stranger understands it. This is where aspiration is supposed to be absent, and usually isn't. |
| Question 4How will we succeed? | Marketing Strategy — 3 Uniques, Proven Process, Guarantee — plus the 10-Year Target and 3-Year Picture | Lencioni's strategic anchors are decision filters, not marketing claims. The test isn't "is this true of us" but "would this let us say no to something attractive." Three Uniques that no competitor could also claim are rarer than most teams think. |
| Question 5What is most important, right now? | Quarterly Rocks and the 1-Year Plan | Singularity. Lencioni wants one qualitative rallying cry with a three-to-twelve month horizon. EOS wants three to seven Rocks. Both are useful; only one of them is a priority. |
| Question 6Who must do what? | The Accountability Chart | Peer-level clarity rather than structural clarity. The Accountability Chart proves the seats are drawn correctly. The question asks whether each leader can state what the person beside them owns. |
Read down the middle column and the case for EOS gets stronger, not weaker. The V/TO answers all six, in two pages, in a format a team can actually hold in their heads. Lencioni's own output — six answers on a page — is looser. If you already run on EOS, you have the better artifact.
The V/TO tells a team what to write down. The six questions tell them whether they know it.
What the questions add
They separate the why from the what. EOS fuses Questions 1 and 3 into a single Core Focus, which is elegant and occasionally costly. Purpose and niche are different things, and a team that has never been forced to answer them apart will typically produce a Core Focus that is really just a well-written description of the product line. Pulling them back into two questions is a twenty-minute exercise that regularly changes a V/TO.
They introduce the thematic goal. This is the most practically valuable import. EOS sets three to seven Rocks per quarter, each with an owner. That is a good execution mechanism and a poor communication one — nobody outside the leadership team can hold seven priorities, and frankly neither can the leadership team. Lencioni's thematic goal is a single, qualitative, temporary rallying cry that the whole company shares: this is the quarter we fix delivery. Layer it over the Rocks rather than instead of them. The Rocks become the defining objectives beneath it, and the quarter acquires a narrative that survives contact with the front line.
They impose a sequence. The six questions are causally ordered. You cannot honestly answer Question 4 before Question 3, and Question 5 is meaningless without Question 4. A V/TO is a form, and forms get filled in whatever order the room finds comfortable — which is why teams so often arrive at a beautiful 3-Year Picture built on a Core Focus nobody stress-tested. Working the questions in order during Vision Building forces the dependencies into the open.
They set a pass mark. Lencioni's standard is not that the answers are good. It is that the leadership team gives the same answers, from memory, without the document. That is a test the V/TO makes possible but does not require, and it is the single fastest way to find out whether a Vision Building Day produced alignment or just produced a document.
Where to use them
For a team about to start EOS, the questions are best used inside Vision Building Days One and Two — as the conversation that generates the V/TO rather than a separate exercise alongside it.
For a team already running, they work better as an audit. Run the separate-rooms test at an Annual. If the answers diverge, you have not found a vision problem so much as a shared-vision problem, and it is worth knowing that before you set another year of Rocks on top of it.
The honest summary
On Discipline 2 — Create Clarity — EOS and The Advantage are largely answering the same brief, and the V/TO is the better instrument. This is not a case where you need both systems.
What the six questions contribute is rigour about the process that fills the V/TO in: the order of the conversation, the separation of purpose from niche, a single rallying cry the whole company can carry, and a hard test for whether the answers are actually shared. Those are refinements to how you run Vision Building — not a second system to install. Which is exactly what makes them worth the afternoon.
The Advantage: Why Organizational Health Trumps Everything Else in Business is a work by Patrick Lencioni and The Table Group; the six critical questions and the thematic goal are described there. EOS®, the V/TO™, Core Focus™, the Accountability Chart, and Rocks are tools of EOS Worldwide, described in Traction by Gino Wickman. The two bodies of work are independent; neither organization endorses the other.
← Back to all articles