Presenting a Signal to a Portfolio Manager

A researcher walks a PM through a new signal the way they'd explain it to another researcher: the hypothesis, the data source, the construction, then the results. Ten minutes in, the PM interrupts with the question that should have been answered on slide one — "how correlated is this with what I already run?" The researcher didn't lead with it because, to a researcher, the construction is the interesting part. To a PM, the construction is a means to an end, and the end is: what does this do to my book.

What a PM is actually deciding

A PM isn't grading the research the way a peer reviewer would. They're deciding whether to give a signal book space, and book space is the scarcest resource they manage — every allocation to a new signal is an allocation taken from something already earning its keep. That decision runs through a small, consistent set of questions, and a good presentation answers them in the order the PM will actually ask, not the order the research happened.

Does this diversify the book, or duplicate it? A signal with a strong standalone Sharpe that correlates 0.6 with an existing book component is worth far less than the same Sharpe at 0.1 correlation — because the marginal risk-adjusted return it adds to the whole portfolio, not its standalone number, is what matters to a PM's risk budget.

How much capital can it actually hold, and at what point does it stop working? A PM sizing a $2bn book has no use for a signal capped at $30m, no matter how clean its Sharpe ratio looks. Capacity has to be stated in dollars the PM can compare against their existing allocations, not left implicit in a decile spread.

What does it look like when it's wrong? Every signal has a bad period. A PM needs the worst historical drawdown, how long it lasted, and — as honestly as it can be answered — whether that drawdown looked like a hurt-but-still-working period or a stopped-working period, because the two require completely different responses when it happens live.

What's the plan if it stops working? A signal presented with no monitoring plan reads, correctly, as unfinished. Stating the trigger for re-evaluating or turning it off — a specific IC threshold, a specific number of consecutive bad months — signals the research was done by someone thinking about what happens after the meeting, not just up to it.

What to do with a hostile question

A PM who asks "why should I believe this over what's already in the library" is doing their job, not attacking the researcher. The wrong response is defending the backtest methodology in more detail. The right response is answering the actual question underneath it: what does this add on the margin, specifically, that the desk doesn't already have — a different universe it covers, a different regime it fires in, a genuinely distinct data source. A researcher who can point to one concrete thing this signal captures that nothing else in the book does will win that exchange; a researcher who retreats into IC and t-statistics will not, because those numbers were never what the PM was actually asking about.