Advice Ages Badly and Meeting Notes Make It Worse
An advisor call produces no decision, no owner and no due date, so most capture systems reduce it to a list of topics. The part worth keeping is the reasoning, and it is the first thing every summary throws away.
The call that produces nothing you can file
Once a month there is an hour with an advisor. Maybe it is a board member outside the board meeting, maybe an operator two stages ahead who took a small amount of equity and answers the phone. They spend forty minutes on how they would think about the pricing change, or the first sales hire, or whether the second product is a distraction. Then the call ends.
Nothing was decided. Nobody owes anybody anything. There is no due date, no owner, no follow-up to assign. Every test a team uses to decide whether a meeting matters, and every field a note-taking tool is built to fill, comes back empty.
So the summary says: discussed pricing, discussed the sales hire, discussed roadmap focus. Which is accurate. Four months later, when the pricing change is actually on the table and somebody asks what the advisor thought, that line is worth nothing at all.
The only conversation that leaves nothing behind
Decisions are recoverable even when the notes are bad. Someone got hired, so there was a decision to hire. The price on the site changed in March, so there was a decision about pricing in March. The feature is in the changelog. The world holds a copy, and a team with thin notes can usually work backwards from the artifact to the decision, badly and slowly, but it can be done.
Advice produces no artifact. If you took it, it stops looking like advice within a quarter and starts looking like something the team worked out on its own, because by then it has been argued over, adapted, and half rebuilt. If you did not take it, there is nothing at all. No trace, no dissenting opinion filed anywhere, no record that the option was ever raised.
That leaves companies in a strange position with their advisors. The relationship is often paid for in equity, or in a board seat, or in the kind of favour that gets repaid later. It is one of the more expensive inputs a young company has. And it is the only input with no audit trail whatsoever.
The practical version of this shows up as repetition. The same advisor gets asked a version of the same question three times across eighteen months, because nobody on the team can remember what was said the first two times, and the advisor answers slightly differently each time because they cannot remember either. Nobody notices, because there is nothing to notice it against.
The recommendation expires and the reasoning does not
Here is the part that makes advisory calls different from every other meeting a team captures. In a decision meeting, the conclusion is the valuable part and the discussion is context. In an advisory call it runs the other way.
An advisor's recommendation is indexed to a moment. It answers your numbers that week, your team as it was, the market as it looked that quarter. Say they tell you to hold pricing until retention is stable. Three months later retention has moved, two competitors have repriced, and you have lost the customer segment that was driving the original worry. The recommendation is now answering a question you no longer have.
The reasoning is what survives. If what they actually said was that a price increase collects its damage on renewal rather than on signup, so the number to watch is not new revenue but the shape of the next renewal cohort, that holds in March and it holds in September and it holds for the second pricing change too. It is the part you can apply to a situation they never saw.
Every summarizer keeps the recommendation. It is a clean sentence with a verb in it, which is exactly what summarizers are built to find. The reasoning is diffuse, spread across ten minutes, full of hedges and asides, and it looks like preamble. It gets cut first.
The best minute is usually a question
Good advisors do a specific thing early in a call. Before answering what you asked, they ask something that changes what you were asking. What did the last three churned accounts have in common. Who would have to be wrong for this plan to work. How long has this been true and you have not acted on it.
Those questions are the transferable part of the hour. They apply to problems that have nothing to do with the one you brought. A founder who collects six of them from a good advisor has something closer to a method than a set of answers.
No capture system keeps them. A summary is built around outcomes, and a question is not an outcome. It reads as process, or as small talk before the real content, so it lands in the discarded half. The single most valuable sixty seconds of the call is structurally the most likely thing to be dropped.
A summarizer is not failing here. It is doing exactly what it was built to do, on a conversation shaped unlike the ones it was built for.
You discount advice in the room, and the record removes the discount
There is a long research literature on what people do with advice, and it points at something uncomfortable about the record.
Ilan Yaniv's work on advice taking found that people consistently place more weight on their own opinion than on an advisor's, an effect strong enough to have its own name, the self other effect, and the discounting gets stronger the more the person already knows. That comes down to access. You can see every reason behind your own view and none of the reasons behind theirs, so the two opinions arrive with very unequal support even when the advisor is the one more likely to be right.
Later work by Xiuxin Wang and Xiufang Du pinned the mechanism to two things acting together, how confident you are in your own answer and how much you trust the advice, and found that the discount shrinks when the advice comes from an expert rather than a novice. So the discount is not fixed. It moves with what you can see about where the advice came from.
Now put a record in the middle of that. In the room you push back. You ask why, you say that will not work here, they hedge, you both land somewhere more careful than where either of you started. Four months later the record says: our advisor recommended hiring a VP of Sales. Flat sentence, named expert, no pushback, no hedges, no conditions. The reasons behind their view are still invisible, so the discount that made you argue in the room is gone, and it is gone at the exact moment nobody can ask a follow-up question. A record that keeps only the recommendation quietly converts a discounted opinion into an instruction.
Capture is not free in a coaching conversation
The honest complication is that recording an advisory call changes the call.
Renee Adams and Daniel Ferreira built the cleanest version of this argument about boards. A board both advises and monitors, and that dual role puts the CEO in a trade off: reveal more and you get better advice, but a better informed board also monitors you harder. Their conclusion, which sounds wrong until you sit with it, is that a friendlier board can be the optimal one, because the CEO actually tells it things. The advising and the evaluating pull against each other, and information is the currency both of them run on.
Most advisors are in some version of that position. The board member coaching you on the sales hire also votes on your compensation. The angel who talks you through the co-founder tension also decides whether to write the next cheque. Everybody in the room knows it, and nobody says it.
That awareness is not a small effect. Jonathon Penney studied traffic to a set of forty eight privacy sensitive Wikipedia articles before and after the June 2013 surveillance revelations, and found average monthly views fell by roughly nineteen and a half percent, with a regression controlling for overall trends putting the immediate drop above thirty percent. Reading an encyclopedia article is about as low stakes and as lawful as behaviour gets, and knowing it might be observed moved it by a third. An advisor deciding whether to give you their real read on your co-founder is nowhere near that low stakes.
Scope the record, not the meeting
The wrong response to that is to stop capturing advisory calls, which puts you back at the first section. The other wrong response is a consent ritual at the top of the call that nobody believes, which mostly teaches the advisor to be careful for ninety seconds and then forget.
The workable version is narrower. Say who will read it, before the call, in one sentence. Then scope what is kept to reasoning rather than remarks. In practice advisors have almost no objection to their reasoning being kept, because reasoning is the thing they are proud of and the thing they would repeat in public. What they object to, correctly, is their candid read on a named individual sitting in a searchable company archive for the next five years.
So the boundary that matters is not about the meeting, it is about the person who is not in the room. An advisor's assessment of an employee's ceiling is not a performance record, was not offered as one, and should never end up functioning as one. Keep the reasoning about the decision. Do not keep the character sketch of the third party.
Stated that way, the constraint is easy to hold, and it is the one thing that keeps an advisor talking freely for the next two years.
What to keep from an advisory call
Seven things, none of which require anyone to behave differently during the hour. The first two are the ones nobody currently captures.
- The question you brought, in the words you brought it in, before the advisor reframed it. Your original framing is evidence about how you were thinking, and it is gone the moment the conversation improves it.
- The question they asked first, and what it turned out you had not looked at. This is the transferable part and it survives every change in circumstances.
- What they think the real constraint is, which is frequently not the constraint you named when you set up the call.
- The recommendation with its conditions attached. If they stated no conditions, record that they stated none, because an unconditioned recommendation from an experienced person is a specific and slightly worrying fact.
- What they had not seen. The numbers you did not show them and the context you did not have time to give are the outer boundary of what the advice is worth.
- Whether they were speaking from one company they know deeply or from a pattern across many. Both are useful and they fail in opposite directions.
- What you decided to do about it, written on the day you decided, kept separate from what they said. Advice and response are two different records and merging them is how a suggestion becomes a mandate.
The pile nobody expects to be biggest
Once a quarter, pull every piece of advice from the last two quarters and sort it into three piles: taken, deliberately not taken, and never resolved.
Teams expect the first two to hold almost everything. The third one is usually the largest. Advice that was neither followed nor rejected, that simply never reached a moment where anyone had to do something about it. It was interesting on the call, it did not attach to a decision that came up in the next few weeks, and it evaporated.
That pile is the actual finding, and it is worth more than any judgement about whether individual advice was good. It tells you which advisor is worth the standing hour and which conversation is enjoyable but not connected to anything you are doing. It also tends to contain, once or twice a year, something that was right and early and that everybody agreed with and nobody acted on, which is a specific and recoverable kind of expensive mistake.
None of this works if the raw material is a list of topics. It needs the reasoning to still be there.
This is the case Driffle is built for. Capture runs continuously and without a bot joining the call, which matters more here than in a status meeting, because an advisory conversation is exactly the kind of call where a visible recorder changes the tone. Screen context keeps the numbers that were actually on screen while the advice was being given, which is what tells you months later what the advisor was and was not looking at. And because it all stays searchable, pulling up what somebody said about pricing in April is a query rather than an appeal to memory.
Sources
- Receiving other people's advice: Influence and benefit (2004), Organizational Behavior and Human Decision Processes 93(1), 1 to 13, on the self other effect, egocentric discounting of advice, and why more knowledgeable judges discount advice further - Ilan Yaniv, Hebrew University of Jerusalem research record
- Why Does Advice Discounting Occur? The Combined Roles of Confidence and Trust (2018), Frontiers in Psychology, on confidence and trust jointly predicting the degree of advice discounting and the discount shrinking for expert sources - Xiuxin Wang and Xiufang Du, Frontiers in Psychology
- A Theory of Friendly Boards (2007), The Journal of Finance 62(1), 217 to 250, on the board's dual role as advisor and monitor and the CEO's trade off in disclosing information - Renee B. Adams and Daniel Ferreira, The Journal of Finance
- Chilling Effects: Online Surveillance and Wikipedia Use (2016), Berkeley Technology Law Journal 31(1), 117 to 182, reporting a 19.5 percent fall in average monthly views of forty eight privacy sensitive articles after June 2013 and an immediate modelled drop above 30 percent - Jonathon W. Penney, Berkeley Technology Law Journal
FAQ
Is this not solved by just sending the advisor a recap after the call?
A recap helps and it captures the wrong half. Recaps are written to confirm outcomes, so they hold what was recommended and drop the reasoning that made the recommendation worth having. They are also written by the person who asked the question, which means the advisor's framing has already been translated into the framing the team arrived with. Send the recap, and keep the record separately.
Should we record an advisory call at all if the advisor might hold back?
Yes, with the audience named in advance and the scope stated plainly. The thing advisors guard is their candid read on named individuals, not their reasoning about the business. A record that keeps reasoning and does not keep character assessments of third parties gets you almost all of the value with almost none of the chilling effect. If an advisor asks for something to stay out, that is a reasonable request and honouring it is what buys the next two years of frank conversation.
How is this different from capturing a board meeting?
A board meeting produces approvals, resolutions and minutes, so it has a decision spine that survives on its own. A coaching conversation with the same person has none of that, and it is often where the more useful thinking happens. Treating the two as the same meeting type is what causes teams to capture the formal one carefully and lose the informal one entirely.
What about advice that turns out to be wrong?
Wrong advice held with its reasoning is still useful, because you can see which assumption failed and whether the advisor was wrong about the world or wrong about your company. Wrong advice held as a bare recommendation teaches you nothing except to trust that person less, which is a crude and often unfair conclusion. This is one more reason the conditions matter more than the conclusion.
We only have two advisors and speak to them rarely. Is this overkill?
It is lighter at that size, not heavier. Two advisors and six calls a year is twelve hours of senior judgement, and a team that small has the least slack to waste on asking the same question twice. The seven items above take a few minutes each when the capture is already happening in the background.