We just acquired a smaller competitor and need to integrate their founder into our leadership team, but their chaotic, entrepreneurial style is disrupting our structured EOS rhythm. How do we run this integration on our Accountability Chart without letting their legacy habits derail our Level 10 Meetings?

Question

Tyler Smith · Accepted Answer

Integrating an acquired founder into your leadership team is an operational challenge because founders are accustomed to complete autonomy. When forced to operate within a structured system like EOS®, they often struggle with the discipline of the weekly Level 10 Meeting™ and the boundaries of the Accountability Chart. To make this integration successful, you must address their new role immediately and transparently. Place them in a single, clearly defined seat on the Accountability Chart that aligns with their unique capabilities. They are no longer the ultimate decision-maker for the entire company, and they must accept this shift in authority. Ensure they genuinely GWC™, which means they get, want, and have the capacity to do this specific job. Next, onboard them thoroughly to the EOS® framework. Explain that the Level 10 Meeting™ is a sacred space where all leaders, including them, are equal peers who must respect the process. If they attempt to bypass the system or make unilateral decisions outside their seat, call out the behavior immediately. Use the IDS® process to discuss how their actions affect the team. By setting firm boundaries early, you can harness their entrepreneurial drive without disrupting the operational harmony of your existing leadership team.