Family business and leadership coaching for owners, successors, and teams running on EOS

Focus Forward · Leadership

Can You Have Both? How a Coach Works Alongside Your EOS Implementer — and the Boundaries That Keep It From Becoming a Mess

Yes. EOS already uses the word “coach” — and reading carefully what EOS means by it is exactly how you draw the line so the two roles strengthen each other instead of colliding.

Last updated: 13 August 2026

By Kirsten Ross Vogel, MLIR, SPHR — Focus Forward Coaching, New Hudson, Michigan. Leadership and family business coach; not an EOS Implementer.

The Short Answer

Yes, and permission is not the interesting part of this question. The interesting part is the operating contract between the two roles: who owns what, what crosses between them, what your leadership team is told, and who decides whether a given problem is an Issue for the Level 10 Meeting or a conversation that should happen somewhere else.

Get that wrong and you have two advisors quietly competing for the same hour, a team that plays them off against each other, and a coach who drifts into being a shadow Implementer. Get it right and the division is clean, because EOS itself defines the Implementer’s coaching narrowly enough to make the boundary obvious. This article is about drawing it.

First: EOS Already Has a Coach, and It Is the Implementer

Before you can put two people in the same company you need to know exactly what the first one’s job is. EOS Worldwide is precise about it. Its page describing the role states that “The role centers around three key functions: teacher, facilitator, and coach,” and defines each:

“Teacher – Implementers teach entrepreneurial leadership teams a set of simple, practical tools to help create some context for them around the Entrepreneurial Operating System and get more of the right stuff done every week.”

“Facilitator – An Implementer serves as a mediator for the leadership team. They facilitate discussion into a common answer that can be executed. The Implementer doesn’t tell business owners what to do or give them the right answer. Business owners decide that for themselves.”

“Coach – EOS Implementers also function as coaches. They serve as the third-party observer to the operation of your business. They help you see what you can’t from your perspective on the inside. An EOS Implementer will coach you, hold you accountable, and make you get more out of yourself than you thought possible.”

EOS Worldwide’s own hiring page is titled “Hire an EOS Coach” and reduces the function to a single line: “Coaching: Keeping your leadership team on track and holding them accountable.” The glossary describes a Professional EOS Implementer as “A certified, EOSW-trained coach who teaches, facilitates, and coaches leadership teams through the EOS Process.”

Read the objects of those sentences. The coaching is of the leadership team. It is about the operation of your business. It is delivered through the EOS Process. That is a real and valuable job, and it is a specific one.

And I want to give EOS its strongest argument here rather than skip past it, because the same page makes the case against hiring anybody else: “Instead of entrepreneurs who are already busy navigating the day-to-day operations of their business having to also navigate relationships with three different supporting personnel, EOS Implementers meet the needs of all three.” For the business system, that is correct. One person, three functions, no coordination tax. If your problem is that the company does not run consistently, do not add a second advisor — you would be buying the same job twice.

The case for a second person is not that the Implementer is doing their job badly. It is that a family business has a second job.

The Operating Contract

If you are going to run both, write this down before the coach’s first session. Not as a legal document — as a page everyone has read.

EOS Implementer Family business coach
Unit of work The leadership team Individuals, pairs, and the owning family
Where it happens In session, in the room Between sessions, usually one-to-one
Cadence Quarterly day, annual two days, weekly Level 10 run by your team Continuous or project-based, on its own clock
What they own The EOS toolbox and the discipline of using it purely The relationships that decide whether people can use it
What they must never do — Touch the toolbox. Introduce a competing model. Run a parallel operating system.
Default on confidentiality Everything is team-visible; that is the point of the Issues List Nothing is shared without the person’s agreement, on terms written down first
Who decides where a problem goes You do, with a rule agreed in advance — see the sort test below

That fifth row is the one people skip and the one that matters most. EOS Worldwide lists among the Implementer’s areas of expertise “Coaching EOS® purity and accountability, and helping the leadership team become its best.” Protecting the integrity of the system is literally the Implementer’s job. A coach who starts adding frameworks is not being helpful, they are creating work for the Implementer to undo. The lane is the relationship, not the tools.

The Part Most People Miss: EOS Already Publishes the Test for What Can Coexist — and It Isn’t “Is It EOS?”

The objection you have probably heard is that EOS “isn’t meant to be mixed.” That is true, and EOS says so in plain words on its main page: “EOS is designed to be implemented as a whole system — not mixed with other frameworks.” Its guidance on self-implementation is blunter still: “If you only use pieces of it or tweak the process to make it easier for the team you are now, you lose the power.”

But look at how EOS applies that rule in its own FAQ, because the distinction it draws is not the one people assume.

On Scaling Up, a rival business operating system, EOS says the two “are operating systems for entrepreneurial companies but differ in structure, terminology, and delivery… don’t mix them.”

On Agile and Scrum, EOS says something different: “Agile and Scrum are software-development frameworks. EOS is a business operating system. They solve different problems and coexist easily.“

So EOS’s own published test for coexistence is not “is it EOS or not.” It is does it solve a different problem. Competing operating systems: don’t mix. Different-problem disciplines: coexist easily. I want to be careful here — EOS has not published a statement about family business coaches specifically, and I am reasoning by analogy to a test EOS itself set out. But the analogy is clean. A coach working on whether two siblings can make a decision together is not a rival operating system. It is not an operating system at all.

Now the proof point, and it is EOS’s, not mine. EOS designed a recurring meeting that exists purely for a relationship. The Same Page Meeting is described by EOS Worldwide as a “two-hour (preferably off-site) meeting each month” in which the Visionary and Integrator work “on the business by working on their relationship.” Gino Wickman’s own post recommends it to “all business partners and anyone that has a visionary/integrator relationship,” as a way to “air out issues, build and strengthen your relationship, and keep you in sync.”

Note what that concedes: relationship work needs its own container, off-site, on its own schedule, outside the leadership team sessions. EOS worked that out and built a tool for it. In a family company there are simply more of those relationships than one Visionary–Integrator pair, and some of them involve people who do not attend leadership meetings at all — the parent who still owns the shares, the sibling who works in the business, the spouse who does not.

Then look at the arithmetic of contact. EOS Worldwide states that “EOS Implementers conduct approximately five sessions a year with each client,” and describes the annual session as “Two days with your leadership team each year to work on team health.” Five days in your building. Two of them on team health. Those are good days and they are not many.

Your Implementer has about five days a year in your company. Everything that happens in the other three hundred and sixty is somebody else’s problem — and in a family business, most of it has a surname.

Where Coaching Lands Inside a 90-Day Cycle

Sequencing is where this either works smoothly or turns into a scheduling argument. What I have found holds up:

  • Before the quarterly, not during it. If two people are going to disagree hard in the session, the useful conversation happens the week before, privately, so that the session is spent deciding rather than discovering.
  • The first two weeks after the quarterly are the live window. The Rocks are set and nobody has slipped yet. That is when individual coaching turns a commitment into a behaviour.
  • Never between the coach and the Level 10. The weekly meeting belongs to your team. A coach sitting in it changes what people say, and changes it in the wrong direction.
  • Escalate on a rule, not on a feeling. Agree in advance: anything that is a business decision goes on the Issues List. Anything that is about one person’s behaviour, or about ownership and family, goes to the coach. Anything that is both gets named as both, out loud, by the person who owns it.

EOS’s own material describes exactly the pattern that signals you are in the second category. Its page on when to hire an Implementer notes that “Everyone may agree in the room, then leave and operate from different assumptions,” and that when “the same Issues keep coming back, your team may be discussing symptoms instead of solving root causes.” Those are EOS’s words about EOS teams generally. In a family company, the reason the same Issue keeps coming back is often that solving it would require telling a relative something nobody is willing to say in front of the leadership team.

The Confidentiality Problem, Which Nobody Sets Up in Advance

This is the hardest question in running both, and it has an answer that predates your company.

Your Implementer works in a forum built on visibility. Your coach works in conversations built on the opposite. So what happens when a leader tells the coach something in a 1:1 that is also, plainly, a live Issue for the leadership team?

The professional standard is that this gets settled in writing before anybody starts. The ICF Code of Ethics requires a coach to “Communicate (before coaching begins) with coaching client(s), sponsor(s), and/or other involved parties that the coach is in a direct relationship with to explain the nature of coaching and to co-create a coaching agreement regarding roles, responsibilities, confidentiality, financial arrangements, and other aspects of the coaching engagement,” and to “Have a clear agreement about what information is exchanged and how it is exchanged among all parties involved during all coaching engagements.”

In practice, for a company running both, that means answering four questions on paper on day one:

  • Does the coach speak to the Implementer at all, and if so about what — themes, or specifics?
  • Who is told when a coaching conversation surfaces something that belongs on the Issues List, and by whom? (The right answer is almost always: by the leader whose issue it is, coached on how to raise it — not by the coach going around them.)
  • Does the person paying receive any report? What is in it?
  • What ends the confidentiality — and the ICF code is explicit that this too must be agreed up front, covering what “may need to be disclosed to the appropriate authorities.”

Families that write those four answers down almost never have a problem here. Families that assume everyone will be sensible have one within a quarter.

The Ways Running Both Actually Fails

Not theoretical. These are the four I watch for.

  • Triangulation. A leader tells the coach one version and the Implementer another, and neither advisor knows. The fix is the escalation rule above, plus both advisors knowing the other exists.
  • The shadow Implementer. The coach starts opining on the Accountability Chart. Now you are paying two people to do one job badly. The fix is the boundary in the table.
  • The verdict problem. A coach introduced mid-rollout reads to the team as a judgement on somebody — usually the Implementer, sometimes one person. The fix is who makes the introduction and how: the owner does it, in the same breath as recommitting to EOS, and names the reason as family-specific rather than performance-specific.
  • Calendar load. Between the quarterly day, the annual two days, weekly Level 10s and a coaching cadence, you can quietly commit a lot of leadership time. Count it before you start, and phase it rather than stacking it.

A Sort Test: Take Last Quarter’s Issues List

This one takes ten minutes and it will tell you whether you need a second person at all.

Pull your Issues List from the last 90 days. For each item, put it in exactly one of three columns.

  1. Tool. It would be solved by using an EOS tool properly — a clearer seat, a real Scorecard number, an actual owner.
  2. Person. It is about one individual’s behaviour, capability or willingness, and everyone knows who.
  3. Family. It involves ownership, inheritance, a parent, or a relationship that exists outside this company.

Then answer three more:

  1. How many items appeared on the list more than once?
  2. Of the repeat offenders, which column are they in?
  3. Is there an item that has never made it onto the list at all, because nobody will type it?

How to read it. If almost everything is in column one, you do not need a coach — you need to run EOS more purely, and your Implementer is the person for that. Say so and save your money. If your repeat offenders cluster in column two, that is individual coaching and it does not necessarily need a family specialist. If they cluster in column three, or if the honest answer to question 6 is yes and it involves a relative, that is the case for a second person — and it is a case your Implementer will very likely agree with.

Questions Leaders Ask Me About This

Do I tell my Implementer I’m bringing in a coach?

Yes, before you hire, not after. Two reasons. It removes any suggestion that you are going behind them, and it lets you agree the escalation rule with both people in the same conversation instead of discovering the gap later. In my experience Implementers are relieved rather than threatened — many of them came from coaching backgrounds themselves. EOS’s own recruiting material describes prospective Implementers as “Professionals operating under titles like ‘business coach’ or ‘consultant’.”

What is my coach allowed to tell my Implementer?

Exactly what you agreed in writing before the first session, and nothing else. My own default is that I share nothing specific and that anything belonging on the Issues List gets raised by the person whose issue it is, with coaching on how to raise it. That default has to be stated, not assumed — a coach who tells you “of course everything is confidential” and leaves it there has not done the contracting properly.

Should my coach attend the quarterly session?

Usually no, and I would push back if you asked me to. The quarterly belongs to your leadership team and your Implementer, and adding an observer changes the room. The exception is a specific, agreed, one-off piece of work — a conversation the family has decided to have with everyone present — and even then it should be scheduled as its own block, not folded into the session.

Isn’t this two invoices for one problem?

It is two invoices only if it is one problem. Run the sort test above. If your Issues List is column one all the way down, you have one problem and you already have the right person for it. The reason to add a second is that column three items do not get solved by better tools — they get more precisely measured by them.

When should we not do both?

Three cases. If you have not started EOS yet and your family cannot have a civil conversation, start with the relationship work and bring in the Implementer when there is a team capable of committing to a system. If money or calendar is genuinely tight, pick one and do it properly rather than doing two things thinly. And if what you actually want is a second advisor to overrule the first, do not hire anybody — sort out why you do not trust the first one.

Where I Fit — and Where I Do Not

Let me be direct with you, because that is what I would want. I am not an EOS Implementer. I do not sell the system, I am not part of the franchise, and I will not touch your toolbox. If what you need is somebody to run your Focus Day, I am not that person, and I will tell you so on the call rather than after the invoice.

  • The credentials behind the work. Kirsten Ross Vogel, MLIR, SPHR. A master’s degree from Michigan State University, one of the top human resource programs in the country, and certification as a Senior Professional in Human Resources.
  • Thirty years in the relationship layer. More than 30 years working with leaders in privately held companies, family businesses and non-profits, and a practice launched more than 25 years ago.
  • Fluent in EOS without selling it. I have coached leaders and teams running on the Entrepreneurial Operating System for more than 25 years. Your team will not have to stop and explain Rocks, the Scorecard, GWC or a Level 10 Meeting to me, and you will not pay for that tutorial.
  • Endorsed by the man who built EOS. Gino Wickman, creator of EOS and author of Traction and Get A Grip: “I cannot say enough about the wonderful work she has done with my clients. I get unsolicited rave reviews.”
  • Methods matched to the problem. Team assessments that begin with an interview-style survey of your employees in a safe space where they can share openly, producing a Report of Findings that pairs every issue with a prescribed action. Facilitated difficult conversations. Conflict resolution. Business transition and transfer planning. Group coaching for up to eight people. Individual leadership development built on three steps: Awareness, Motivation, Change.
  • Sent here by Implementers. EOS Implementers refer more work to me than any other source. They are very good at what they do. This is simply the part that is not theirs to do.

Where to start. Schedule a Discovery Call — and bring last quarter’s Issues List. It is a relaxed, no-pressure conversation, and if the answer is that your Implementer already has this covered, I will say so. Sessions run via Zoom or in person in New Hudson, Michigan. Call 248-973-7595. You are closer than you realise to the business and team of your dreams.

A note on one claim: the statement that EOS Implementers refer more work to Focus Forward Coaching than any other source is my own account of my practice, not independently published data. The sequencing advice and the four failure modes are also my practice judgement rather than published research. Every figure and quotation in this article is sourced below.

Sources

All URLs accessed 13 August 2026.

EOS Worldwide (official)

The EOS Implementer®: A Breakdown of the Role — the three functions, session volume, and the path into the role https://www.eosworldwide.com/blog/the-eos-implementer-a-breakdown-of-the-role · Hire an EOS Coach — “Keeping your leadership team on track and holding them accountable” https://www.eosworldwide.com/hire-an-eos-coach · EOS Glossary — definition of a Professional EOS Implementer https://www.eosworldwide.com/glossary · What is an EOS Implementer — “Coaching EOS® purity and accountability” https://www.eosworldwide.com/what-is-an-eos-implementer · What is EOS — “designed to be implemented as a whole system — not mixed with other frameworks” https://www.eosworldwide.com/what-is-eos · EOS FAQ — the Agile and Scaling Up coexistence answers https://www.eosworldwide.com/faq · DIY EOS: 10 Self-Implementation Lessons Learned the Hard Way — running EOS “pure” https://www.eosworldwide.com/blog/diy-eos-10-self-implementation-lessons-learned-the-hard-way · The Power of Same Page Meetings® — the monthly off-site relationship meeting https://www.eosworldwide.com/blog/power-same-page-meetings · Gino Wickman, The Same Page Meeting — “all business partners” https://www.eosworldwide.com/blog/659-eos-the-same-page-meeting · The EOS Process — quarterly and annual session structure, “two days with your leadership team each year to work on team health” https://www.eosworldwide.com/eos-process · When to Hire an EOS Implementer and When You Might Not Need One https://www.eosworldwide.com/blog/when-to-hire-an-eos-implementer-and-when-you-might-not-need-one · Partnership Rules of the Game™ https://www.eosworldwide.com/blog/partnership-rules-of-the-game · Become an Implementer — the four-step path and coaching backgrounds https://www.eosworldwide.com/become-an-implementer

Professional standards

International Coaching Federation, ICF Code of Ethics (current Code effective 1 April 2025) — sections 1.1, 2.2 and 2.3 on contracting and confidentiality with clients and sponsors https://coachingfederation.org/credentialing/coaching-ethics/icf-code-of-ethics/

Focus Forward Coaching

Home https://focusforwardcoaching.com/ · About https://focusforwardcoaching.com/about/ · Services https://focusforwardcoaching.com/services/ · FAQ https://focusforwardcoaching.com/faq/ · Testimonials, including the Gino Wickman endorsement https://focusforwardcoaching.com/testimonials/ · Contact https://focusforwardcoaching.com/contact/

Need help with a conversation carrying real stakes?

Kirsten can help you prepare the message, facilitate the discussion, or address the deeper pattern behind recurring conflict.

Keep reading

Related insights