Investment committee vs lifestyle committee: keep them from fighting

Most family offices do not fail because markets are cruel. They fail because two legitimate committees start treating each other like enemies. One side speaks in Sharpe ratios, liquidity ladders, and manager scorecards. The other speaks in calendars, crew retention, harvest timing, and whether the mountain house can still host Thanksgiving without a roof project that somehow was “urgent” only after the deposit was wired. Both are right about their own domain. Both become wrong the moment they try to govern the other’s craft with the other’s vocabulary.

The investment committee (IC) and the lifestyle committee (LC) — sometimes branded as the household committee, legacy-assets committee, or family-experience committee — share one balance sheet and one reputation. When they fight, the principal pays twice: once in suboptimal capital allocation, and again in family friction that no private bank, no OCIO, and no eloquent holiday speech can paper over.

This post is an operating manual for keeping them separate where they should be separate, and coordinated where the money actually moves. It is not a plea for harmony theater. It is a design brief.

Why the conflict is structural, not personal

If your IC and LC are arguing, do not start with personality coaching. Start with architecture.

The IC’s job is to preserve and compound financial capital under a written investment policy statement (IPS). Its success metrics are risk-adjusted outcomes within policy bands, liquidity coverage, concentration limits, manager process quality, and clean exception logging. Its natural bias is toward optionality: keep dry powder, avoid illiquid vanity, measure what can be measured, and treat surprise cash needs as governance failures.

The LC’s job is to steward experience capital — the homes, aircraft, vessels, collections, staff ecosystems, travel patterns, and gatherings that convert wealth into a life the family still wants. Its success metrics are utilization, safety, service quality, total cost of ownership (TCO) against budget, staff stability, and whether the next generation still shows up without being bribed by spectacle. Its natural bias is toward continuity: keep the captain, keep the house open, keep the vineyard viable through a dry year, keep Christmas at the mountain place even when a spreadsheet calls occupancy “inefficient.”

Neither bias is a character flaw. The fight begins when four conditions appear together:

1. Budgets are opaque. The IC discovers a multi-million yard period or irrigation upgrade in the same quarter it planned private-equity capital calls or a tax estimate.
2. Decision rights are fuzzy. Nobody wrote down who can approve a new aircraft lease versus who can approve a new manager allocation versus who can pledge securities as collateral.
3. Language is weaponized. “Lifestyle” becomes code for waste. “Investment discipline” becomes code for indifference to family. Staff learn which vocabulary opens which wallet.
4. The principal triangulates. One spouse lobbies the lifestyle chair; the other lobbies the CIO; operators learn to route CapEx through whoever is traveling less that month.

Illustrative scenario (clearly hypothetical, not a client story): a second-generation family with roughly $180 million investable and three legacy assets — a fractional aviation program, a Napa vineyard LLC, and a Mediterranean charter-capable yacht. The IC wanted to increase private credit. The LC had already committed, informally, to a five-year survey and a vineyard irrigation upgrade. Neither committee shared a rolling liquidity calendar. The “fight” was framed as wine-and-boats versus bonds. The real issue was an invisible cash calendar colliding with two different definitions of prudence — plus a FO lead who had not been given authority to force both packets onto one page.

Structural problems produce personal heat. Fix the structure first; then coach manners if anything remains.

Separate mandates, shared constraints

Write two one-page mandates. Treat them as constitutional documents for the operating rhythm. Review them annually alongside the IPS — not only when someone is angry.

Investment committee mandate (sample language to adapt)

• Purpose: Implement the family IPS; oversee managers, custody, and risk; recommend rebalancing and new allocations to the principal or family board.
• In scope: Marketable securities; alternatives within IPS sleeves; cash and the liquidity ladder; manager selection and termination; performance and risk reporting; documented exceptions.
• Out of scope: Household staffing decisions; asset-level operations (crew, hangar, vineyard GM, registrar); family travel calendars; philanthropic grant selection (unless the IPS contains a dedicated philanthropic sleeve and the IC only executes approved transfers).
• Cadence: Quarterly formal meetings; monthly risk pack; ad-hoc sessions for material market, credit, or manager events.
• Authority: Approve manager hires and fires within IPS bands; escalate IPS amendments and any single commitment above a stated dollar gate to the family board.
• What “good” looks like: Policy adherence, predictable liquidity, no surprise forced sales of core holdings to fund ordinary lifestyle burn.

Lifestyle committee mandate (sample language to adapt)

• Purpose: Operate legacy and household assets within approved TCO budgets; protect safety, privacy, and experience quality; propose multi-year CapEx that preserves Smart Asset status rather than feeding Vanity Sinkholes.
• In scope: Homes and staff ecosystems; aviation, yacht, vineyard, and collection operations; vendor RFPs for those assets; annual usage calendars; experience and legacy KPIs; safety and incident reviews.
• Out of scope: Changing the IPS; selecting public-equity or hedge-fund managers; pledging investable assets as collateral without board approval; “borrowing” from investment cash without a formal liquidity request through the integrator.
• Cadence: Quarterly operations reviews; annual CapEx summit with the IC present as observers who hold a liquidity veto comment, not a taste veto.
• Authority: Approve operating expense within budget; escalate CapEx above a stated gate and any new asset acquisition to the family board with an IC liquidity memo attached.
• What “good” looks like: Assets that amplify the life the family actually lives; TCO that matches funding; next-gen participation without coercion; clean vendor accountability.

Notice the shared constraint: liquidity and collateral. That is the bridge. Taste, utilization, and manager selection can stay in their lanes. Cash dates cannot.

The liquidity bridge (where fights should be scheduled)

Create a single artifact both committees must see: a rolling 24-month Family Liquidity Calendar. This is the most important peace treaty in a lean family office.

Columns that earn their keep:

• Known CapEx (yard periods, engine overhauls, roofs, irrigation, major conservation, refits)
• Recurring OpEx peaks (insurance renewals, seasonal staff, school-year household ramp, security details for travel seasons)
• Investment capital calls and known redemption windows
• Tax estimates, trust distributions, and charitable pledges already committed
• Debt service or facility renewals if any
• Contingency reserve floor — the number below which no discretionary CapEx proceeds without board action

Rules that prevent theater:

1. No surprise CapEx over threshold. The LC files CapEx notices 90–180 days ahead for items above the agreed dollar gate. Incomplete notices do not start the clock.
2. The IC cannot starve the calendar silently. Large illiquid commitments require a showing that the contingency floor still clears after filed CapEx.
3. One integrator owns the calendar. Usually the FO lead, Chief of Staff, or Legacy Asset Manager — not the CIO and estate manager fighting for custody of the spreadsheet.
4. Red / amber / green status is visible to both chairs. Ambiguity breeds lobbying; color codes reduce narrative warfare.
5. Collateral pledges are board items. Using the securities book to backstop aviation or real-estate facilities is not an IC courtesy or an LC convenience.

This calendar is boring. Boring is the point. Drama is a fee you pay when you refuse paperwork.

How to build the first calendar in two weeks

Week one: pull contracts, insurance renewal dates, management-company maintenance forecasts, known PE/VC call schedules, and last year’s monthly cash burn by entity. Week two: reconcile with tax estimates and philanthropic pledges; assign each line an owner and a confidence tag (committed / likely / optional). Present it at a bridge session before anyone debates a new toy.

Decision rights matrix (RACI that families will use)

Use a simple matrix. Rows are decision types. Columns are Principal, Family Board, IC, LC, FO Lead, External Counsel/Tax. Customize dollar gates to scale; the existence of gates matters more than the exact numbers.

Decision	Recommend	Approve	Informed
Rebalance within IPS bands	CIO / IC	IC (or FO lead if delegated)	Principal
Amend IPS risk target or bands	IC	Family Board / Principal	LC chair (liquidity awareness)
Hire/fire public or alts manager	CIO	IC	Custody / FO lead
Approve annual household + legacy OpEx budget	LC	Family Board	IC (liquidity comment)
CapEx mid-gate on existing asset	LC + FO lead	Principal or Board per policy	IC
CapEx high-gate or new legacy asset	LC + FO lead + tax/legal	Family Board	IC (mandatory liquidity memo)
Pledge securities for facilities	IC + counsel	Family Board	LC
Open new household / change primary base	LC	Principal / Board	Tax, risk, IC
Related-party hire into FO or asset ops	FO lead + counsel	Board	IC/LC as relevant

Print this. When someone says “I thought I could just…,” point to the row. That gesture saves more capital than another manager bake-off.

Meeting design that reduces blood pressure

Do not merge the committees

A combined “everything committee” sounds efficient. It usually produces either investment professionals bored by laundry contracts and crew rotations — which then get rubber-stamped poorly — or lifestyle voices drowning in jargon — which then get steamrolled and return as underground CapEx campaigns.

Keep separate agendas. Create a joint bridge session twice a year: 60–90 minutes, same packet, three agenda items only — liquidity calendar, CapEx roadmap, and any proposed new asset or major financing. If a topic cannot fit those three, it belongs in its home committee.

Packet discipline

• IC packet: performance, risk, liquidity, exceptions, pipeline, policy-band status.
• LC packet: TCO vs budget by asset, utilization, safety/incidents, vendor scorecards, CapEx pipeline, staff retention, Smart Asset dashboard highlights.
• Bridge packet: the calendar, CapEx list with cash dates, and one page of asks from each side.

If a chair cannot summarize an ask in one page, they are not ready for the other committee’s time. Eloquence is not a substitute for a cash date.

Facilitation norms

The FO lead chairs the bridge session. The CIO does not get to mock utilization metrics. The LC chair does not get to redefine “liquidity” as “we can always sell something.” Minutes capture decisions and open questions only — not speeches.

Scoring diagnostic: How close are you to a structural fight?

Score 0–2 for each item (0 = healthy, 2 = acute risk). A total of 12 or higher means redesign before the next CapEx season.

1. Surprise CapEx in the last 24 months that forced an unplanned securities sale, delayed a capital call, or spiked a credit line.
2. No written mandates for IC and LC (or “we all just know”).
3. Same person chairs both without a documented dual-hat protocol and conflict log.
4. No rolling liquidity calendar shared across investment and lifestyle.
5. Staff route requests to whichever principal is more sympathetic that week.
6. IPS silent on lifestyle capital — no cash sleeve, no TCO funding rule, no buffer for known asset cycles.
7. Family meetings re-litigate last year’s vineyard or jet decision instead of reviewing KPIs.
8. Advisors triangulate — private bank talks only to IC; yacht or property manager talks only to one spouse.
9. Collateral decisions happen in email threads without board minutes.
10. Exception logs do not exist; every override is “special circumstances.”

Steward response by band:

• 0–5: Tighten documentation; keep cadence; review gates annually.
• 6–11: Install the liquidity bridge and RACI within 60 days; pause nonessential new acquisitions until green.
• 12+: Pause new legacy acquisitions; run a governance reset with counsel and the FO lead present; do not hire more vendors until decision rights are written.

Funding rules that stop moralizing

The fight often hides a funding design problem. Fix the plumbing before you hire a facilitator to interpret feelings.

Rule A — Lifestyle has a budget, not a vibe. Annual OpEx and a multi-year CapEx plan are approved on a schedule. Mid-year changes require a formal variance request with liquidity impact and a named owner.

Rule B — The portfolio funds lifestyle through transfers, not raids. The FO lead executes scheduled draws from a designated cash sleeve. The CIO is not ambushed on Friday afternoon with a wire that “has to go today.”

Rule C — Passion allocation is capped. If the family wants a passion or legacy sleeve inside the IPS (for example, a single-digit percentage for concentrated or experiential capital), write it down. Lifestyle proposals then compete inside that sleeve instead of raiding core compounding capital.

Rule D — Collateral is a board decision. Full stop. Document tenor, recourse, and unwind triggers.

Rule E — Intangible returns get measured, not mocked. Utilization days, next-gen participation, philanthropic leverage hosted on an asset — these belong on the LC dashboard. The IC does not dismiss them; the LC does not invent them without evidence. This is the same Stewardship Triad logic used for Smart Assets: financial acumen, operational mastery, and legacy intentionality must all appear somehow in the reporting system.

Rule F — Emergency lanes are predefined. True emergencies (safety, structural failure, medical, security) use a pre-authorized spend path with post-hoc review within seven days. Fake emergencies that are actually preference changes do not get the emergency lane.

Failure modes and steward counter-moves

Failure mode 1: The heroic principal. One founder overrides both committees in real time and enjoys being the court of appeal. Counter-move: require written exceptions logged to the board packet within seven days. Heroes hate paperwork; that is why paperwork works.

Failure mode 2: The captured CIO. The CIO becomes the lifestyle referee because “someone has to say no.” Counter-move: return the CIO to IPS adherence; give the FO lead the integrator role; give the board the no.

Failure mode 3: Lifestyle veto by delay. CapEx packets arrive incomplete until the yard slot is lost and “we have no choice.” Counter-move: incomplete packets do not start the clock; lost slots caused by late packets are LC process failures, not IC cruelty.

Failure mode 4: Spouse-versus-spouse proxy war. Committees become factions with staff as infantry. Counter-move: external facilitator for one annual governance day; separate marital issues from asset policy with counsel if needed. Do not let the IC become marriage counseling with Bloomberg terminals.

Failure mode 5: Vendor capture. A management company or private bank “helps” by siding with one committee. Counter-move: vendors report to the FO lead against written KPIs; dual informal reporting to a family member is a red flag in the vendor scorecard.

Failure mode 6: Metric contempt. Each side refuses to learn the other’s five most important numbers. Counter-move: bridge packet requires each chair to present the other side’s top metric accurately before presenting an ask.

A 90-day peace plan

Days 1–15: Draft IC and LC one-page mandates. Confirm dollar gates. Name the integrator. Inventory the last 24 months of surprise cash events.

Days 16–30: Build the 24-month liquidity calendar from contracts and schedules — not from memory. Tag confidence levels.

Days 31–45: Approve the RACI with the principal or board. Circulate to counsel, tax, custody, and key vendors so nobody can claim ignorance about who can bind the family.

Days 46–60: Run the first bridge session with a thin agenda. Practice saying no with a calendar reason, not a moral reason. Record minutes.

Days 61–75: Align IPS funding language — cash sleeve, optional passion sleeve, collateral policy — with Tuesday’s IPS work in mind.

Days 76–90: Schedule the annual CapEx summit in the same week as the IC’s annual strategy meeting — sequential days, not simultaneous chaos. Retire informal override habits in writing.

Closing: two committees, one stewardship

The Stewardship Triad does not live in a single room. Financial acumen leans IC. Operational mastery leans LC. Legacy intentionality is the North Star both must serve — the same intentionality that separates a Smart Asset from a Vanity Sinkhole.

When committees fight, families often pick a winner and call it leadership. Stewards pick a design. Separate the craft. Share the cash calendar. Write the decision rights. Measure both returns that show up in NAV and returns that show up in whether the next generation still wants the asset without resentment.

If you do only one thing after reading this: put the next major CapEx date and the next known capital call on the same page, in the same ink, with one owner. That page prevents more damage than another eloquence contest between “discipline” and “lifestyle.” Peace is not the absence of strong opinions. Peace is opinions forced to meet at a liquidity bridge before they meet at a dinner table.

---

Related reading and tools live on the Books and Resources pages. Educational only — not legal, tax, or investment advice for your situation.