As the founder and Visionary, I am used to stepping into every operational problem, but in our first 90 days on EOS, my Integrator says I am derailing the rollout by solving issues outside our weekly Level 10 Meeting. How should a Visionary adjust their behavior during this initial 90-day window?

Question

Tyler Smith · Accepted Answer

During the first 90 days, your natural instinct as a Visionary will actively work against the operating system. You are accustomed to walking into offices, slinging quick directives over Slack, and solving fires the moment you smell smoke. When you do that, you teach your leadership team that the EOS disciplines are performative and that the real company runs on your impromptu whims.

Your primary job in this window is to let the tools catch the weight of the business. When an operational fire flares up, do not solve it on the spot. Ask two questions: is it on the Scorecard, and is it on the Issues List for the next Level 10 Meeting? If it is not, tell the leader to drop it on the agenda.

You must also step back and empower your Integrator. The Integrator needs the operational authority to enforce the Level 10 Meeting cadence, police To-Dos, and hold people to their quarterly Rocks. If you step around them to direct department heads, you create organizational whiplash and undermine your Integrator's credibility.

Focus your energy on what only you can do: client relationships, big market ideas, and culture. If an operational issue cannot wait until the next meeting pulse, walk directly into your Integrator's office and hand it to them. Then walk away. This restraint will feel uncomfortable, but it is the only way your team builds the operational muscle to run without your constant supervision.