How to eliminate team politics, silos, and turf wars as CEO

Executive overview

Politics and silos emerge when leaders prioritise their own department over the company. The fix starts at the leadership team level: every department head must treat the company as their primary team, their function as secondary.

A vivid 3-year vision, skip-level meetings, and a culture of cross-team recognition are the main levers. Compensation structure, vacation policy, and acquisition integration each reinforce or undermine the effort.

The company is always the most important team — the department is always second.

Reorienting the leadership team

• Politics typically surface between 100–300 employees; address the culture before you hit that threshold.
• Finance leads must celebrate marketing wins; marketing leads must celebrate ops wins — model it at every leadership meeting.
• Use a Slack channel for core values recognition to make cross-team praise visible and habitual.
• When confronting problems, frame debates as "good for the company," not "good for my area."
• Ask the team: "What do you think we should do to make this disappear?" rather than dictating the fix.

Vivid vision as an alignment tool

• A 4–5 page vivid vision covering all aspects of the organisation anchors decision-making across all teams.
• Roll it out in person: have employees read it aloud together, paragraph by paragraph.
• Tell the team directly: "About 15% of you may not like this future — that's okay, but this is what we're building."
• Offer departing employees a severance incentive to exit quickly; misaligned people leaving fast is a feature, not a failure.
• A players and B players (racehorses and workhorses) are both fine; C players and the misaligned need to go.

Skip-level meetings

• Skip-level = you meet directly with a department's staff, bypassing their VP or head.
• Purpose: understand how direction is landing, what's broken, what support people need.
• The critical rule: do not engage or commit to fixing anything on the spot — you only have part of the story.
• Say "thank you, I appreciate that" and take it back to the relevant leader for context before acting.
• Frequency: once per quarter per business area at most; informal walk-arounds count.
• A mentor running skip-levels across eight of your direct reports and then debriefing you over dinner is one of the highest-leverage feedback formats available.

Delegation vs abdication

• Delegation means knowing the person's skill level and confidence before handing off; abdication is dumping and disappearing.
• If a CEO keeps stepping in to do functional work, the fix is building a system — not the CEO doing the task.
• The Starbucks example: don't ask why one letter on one sign is broken; ask what system ensures all signs stay working.
• CEOs can reassign traditionally "CEO" tasks (e.g. investor calls) to a CFO if those tasks drain rather than energise them.
• Shared EAs create prioritisation conflicts; track hours and split only when you can define who trumps whom.

Compensation structure

• Bonuses become demotivators for most roles: A players already perform at full effort regardless; bonuses don't change their output.
• Pay people fairly for 52 weeks; any bonus should be discretionary — a share-the-wealth gesture, not a performance lever.
• Performance-based pay works in three cases only: outbound salespeople, defined project roles with measurable outcomes, and piecework.
• Never structure bonuses as all-or-nothing; use a sliding scale (e.g. 100% payout at goal, 75% at 95%, 50% at 90%).
• Don't share profit at early-stage growth companies — every dollar of profit should be reinvested in growth and economic value.

Vacation policy

• Two weeks paid vacation actively harms retention and attraction of strong people.
• Five weeks paid (including sick time), use-it-or-lose-it by December 31, is the right structure.
• Unlimited vacation is proven not to work — no one actually takes it because senior leaders signal it's not really allowed.
• Coaching employees to take vacation forces cross-training, reduces single-point-of-failure risk, and raises morale.
• A COO who left after four consecutive 20% pay raises did so to get more vacation time — she didn't have time to spend the money.

Budgeting by outcome, not headcount

• Don't allocate budget by functional area percentage; allocate by what actually needs to get done.
• For every request: can we say no? Can we say not now? Can we optimise first? Can we automate?
• Customer service example: 900 open tickets were caused by four fixable problems (product, service, expectations, FAQs) — fixing root causes reduced projected headcount from 8 to 1.
• Ask IT to find 12 free tools to replace 12 current expenses — it's a valid project even if they don't enjoy it.
• Zero-based budgeting from outcomes up, not top-down percentage allocation by department.

The dream manager program

• Have every employee write a bucket list of 101 things they want to do, see, or experience.
• Your job as dream manager is to provide resources, connections, and group opportunities — not to pay for everything.
• Example: seven people want guitar lessons → start a group guitar club; three want to go hang gliding → organise a group trip.
• John Ratliff granted 120 employee wishes over 3 years at $3,000 each ($420K total) and sold the company for $107M.
• The program creates internal cult-like engagement and word-of-mouth that compounds retention over time.

Acquisition integration

• In the first 90 days post-acquisition: focus entirely on cultural alignment, core values, and making people feel safe.
• Do not rush system migrations, SOP adoption, or rebranding in the first quarter.
• People need to feel secure (Maslow's hierarchy) before they can absorb operational change.
• Changing the company name is one of the least important things — delay it; equal billing first, then transition.
• Start moving to shared systems and branding only after the culture integration is solid.

Offsites and team building

• Two Airbnbs close together beat hotels for real connection — shared mornings in casual clothes matter.
• Split the group into three teams of four; rotate who cooks breakfast, lunch, and dinner across the days.
• Give each cooking group a fixed budget (e.g. $500) and send them grocery shopping — the dynamic is revealing.
• Cooking in fours leaves the other eight free to connect without structured activities.