An investment committee is one of the most consequential decision-making structures in any fund. It is the mechanism through which individual judgment is subjected to collective scrutiny, through which individual bias is — in theory — corrected by the diversity of perspective in the room, and through which the fund's decision-making process is made auditable and legible to LPs, regulators, and future investors. In practice, investment committees vary enormously in how well they perform these functions. The best ones genuinely improve decision quality. The worst are a theatre of deliberation that produces the decision already determined by the most senior voice in the room.

The differences that separate high-performing investment committees from weak ones are not primarily about the quality of the people involved. They are about process design: how information is prepared and distributed before the meeting, how discussion is structured during it, how decisions are recorded at its conclusion, and how past decisions are reviewed over time. Each of these components can be significantly improved without changing the composition of the IC at all.

What separates high-performing investment committees

High-performing investment committees share several characteristics that are absent from average ones. They have a structured pre-meeting process that ensures all participants have read the same high-quality information before the meeting begins. They have explicit role definitions that clarify who is presenting, who is challenging, and who is deciding. They have a norm of structured dissent — where raising concerns is not just tolerated but expected and rewarded. They maintain a formal decision record that captures rationale and confidence, not just the decision outcome. And they run a systematic review process that connects past decisions to observed outcomes on a defined schedule.

None of these characteristics is complicated. All of them require deliberate design and consistent application. The investment committees that fail do so because they rely on the talent of the individuals involved to compensate for process gaps — and talent compensates for process gaps unevenly, unpredictably, and only up to a point.

The pre-meeting process

Written investment memos

The investment memo is the single most important pre-meeting artefact. A well-structured IC memo should cover: the investment thesis in no more than three sentences, the key financial model and assumptions, the competitive position and defensibility, the management team assessment, the key risks and how they have been assessed, the proposed terms and valuation, and the exit thesis. The memo should be completed and distributed at minimum 48 hours before the IC meeting — not circulated the morning of. Investment committees that receive memos in the 24 hours before the meeting are operating in a degraded information environment where the most prepared voice (usually the presenting PM) has an outsized structural advantage.

Structured pre-reads

Beyond the memo, each IC member should be expected to complete a brief written assessment before arriving at the meeting: their initial conviction level, the two questions they want the presenting PM to address, and any thesis concerns they hold. Collecting these pre-reads before the meeting — using a shared form or the fund's decision intelligence platform — eliminates cascade bias, where early speakers anchor the views of those who follow. When every IC member has committed their initial view to writing before discussion begins, the discussion is between genuine independent perspectives rather than between the first speaker and a series of incremental adjustments.

Role definition: who does what

Ambiguous roles are one of the most common process failure modes in investment committees. When it is unclear who is presenting, who has challenge authority, and who holds final decision accountability, the meeting defaults to whoever is most senior or most assertive. Explicit role definition corrects this.

The presenting PM is responsible for advocating the investment thesis, answering questions, and responding to challenges. Their job in the IC meeting is advocacy — which means they should not be the person running the meeting or making the final call.

The challenger is assigned responsibility for raising the strongest case against the investment — not as a devil's advocate performance, but as a genuine effort to identify the thesis weaknesses that the presenting PM may have discounted. The challenger role is most valuable when assigned to someone with relevant sector expertise who is not the presenting PM.

The chair manages the meeting process, ensures all voices are heard, prevents premature convergence, and synthesises the discussion. The chair should not express a strong personal view until the discussion is nearly complete, to avoid anchoring the group.

The decision owner — often the CIO or Managing Partner — makes the final call and owns the recorded rationale. Their accountability for the outcome should be explicit and visible in the decision record.

Running the meeting: structured dissent and explicit recording

Structured dissent

The most valuable thing an investment committee meeting can produce is the strongest version of the case against its emerging conclusion — surfaced while there is still time to act on it. Achieving this requires creating explicit space for dissent before the group converges. The most effective mechanism is a dedicated dissent round: after the presentation and initial Q&A, the chair invites each IC member, in sequence, to state the most significant concern they have about the investment as currently presented. The presenting PM responds to each concern in turn. Only after this round does the group move toward convergence.

This process takes longer than a standard IC meeting. The investment of time is worth it for the following reason: the IC members who have genuine concerns but do not raise them during the meeting raise them privately afterwards, in partner conversations, in LP updates, and in post-mortem discussions when the investment underperforms. Those concerns, raised at the point of decision, would have been actionable. Raised afterwards, they are just regret.

Confidence levels and explicit decision recording

At the moment the IC reaches a decision, every member should record their personal confidence level — from 0 to 100% — that the investment will meet its thesis. The aggregate of these confidence levels, plus their distribution, is useful information. A 75% average confidence with one outlier at 40% and one at 95% tells a different story than a 75% average from a tightly clustered group. Both tell a different story than the binary approve/reject outcome that most IC records capture.

The decision record should contain: the decision made, the stated rationale in two to three sentences, the individual confidence levels from each IC member, the key thesis assumptions that the decision depends on, and the scheduled review dates. This record should be entered at the moment of decision — not reconstructed from memory a week later.

Meeting process overview

Phase Activity Owner Output
Pre-meeting (48h before) Memo distribution; pre-read completion by IC members Presenting PM; each IC member Written memo; written initial views from each member
Presentation (15–20 min) PM presents thesis, financials, and exit thesis Presenting PM Shared baseline understanding of investment case
Q&A (20–30 min) IC members ask clarifying questions; PM responds Chair (manages flow); IC members Key assumptions tested; information gaps identified
Dissent round (15 min) Each IC member states strongest concern; PM responds Chair; each IC member in sequence All major concerns on record; PM response noted
Decision (10 min) Decision owner makes call; IC members log confidence levels Decision owner; all IC members Decision, rationale, individual confidence levels logged
Post-meeting (same day) Decision record finalised; review dates set in system Chief of Staff / Operations Locked decision record; scheduled review reminders

The quarterly review process

The quarterly IC review is the component most often absent from investment committee practice — and the one that most directly determines whether the IC produces learning as well as decisions. The review has a simple structure. Gather all decisions logged in the previous quarter plus any decisions from prior periods whose scheduled review dates have arrived. For each decision under review, read the original rationale and confidence levels before discussing the outcome. Then record what actually happened and what the outcome tells you about the original thesis assumptions.

The quarterly review produces two outputs. First, updated calibration data: for each IC member, a running record of how their stated confidence levels have corresponded with outcomes. Second, process updates: specific adjustments to the IC process based on patterns identified in the review — categories where the IC is systematically overconfident, types of thesis risk that are consistently underweighted, sectors where the IC's judgment has been reliably strong.

Common failure modes and how to fix them

The HiPPO IC. The managing partner's view dominates every discussion. Fix: require written pre-reads from each IC member before the meeting so that all views are committed to paper before the managing partner speaks.

The rubber stamp IC. Decisions are effectively made in partner conversation before the IC meeting; the IC approves without substantive challenge. Fix: require a formal dissent round as a standing agenda item; make recording "no material concerns raised" as visible as recording specific concerns.

The IC with no memory. Past decisions are not systematically reviewed; the IC learns nothing from its own track record. Fix: add a 15-minute "decisions under review" standing item to the start of every IC meeting, covering all positions with a review date in the current period.

The IC with no rationale record. Only the decision outcome is recorded; no rationale, no confidence levels, no thesis assumptions. Fix: implement a structured post-meeting decision capture form that must be completed before the day ends.

Related reading

Reflect OS is built for investment committee process

Structured decision capture, confidence logging, automated review scheduling, and immutable audit trail — purpose-built for fund teams who take process quality seriously.

See the investment management use case →