The Decisions Investors Read as Messages

Dear Colleague,

There is a scene near the end of Francis Ford Coppola's The Conversation, from 1974, that I keep coming back to.

Gene Hackman plays Harry Caul, a surveillance expert hired to record a young couple as they walk through a crowded square in San Francisco. The recording is full of noise, and Harry spends much of the film cleaning it up, playing it again and again until he can make out every word. One line stays with him: "He'd kill us if he got the chance." He concludes that the couple are in danger, and he starts to worry about what his client will do with the tape.

Near the end he plays the tape once more and hears it differently. The words are the same, but the stress falls on a different word, and the sentence now means something quite different. Harry had every word right from the start. He misread it because he assumed he already knew the context.

I have thought about that scene a lot in relation to our work. In IR we spend a great deal of time on words: the results script, the Q&A document, the wording of guidance, the investor presentation. Investors listen to those words carefully. They also read what the company does, and they bring their own emphasis to it. Much of what a company does is decided a long way from the IR office.

The ordinary decisions investors notice

The decisions that send a message are usually ordinary ones. For example:

the results date moves by a week, or the call moves from the morning to the evening a KPI that has been in the investor presentation for years is no longer there the CEO, who usually joins the call, is absent this quarter guidance changes from a single number to a range the company stops attending a conference it has attended every year a senior executive leaves, and the announcement is two lines long

Each of these may have a perfectly good internal reason. The results date moved because of the audit timetable. The KPI was dropped because it no longer reflects how the business is run. The CEO was traveling.

Investors don't see the reason. They see the change, and they fill in the reason themselves. I suspect most of them fill it in with the more cautious explanation, because that is what their job asks of them. An analyst who sees a KPI disappear will ask whether it was removed because it stopped looking good. A portfolio manager who notices the CEO missing from two calls in a row will start to wonder whether something is going on at the top.

None of this is unreasonable. It is simply how an outsider reads a company. They have the recording, and they supply the context.

Why this is harder than it used to be

Two things make this more difficult for IR today.

The first is that more of a company's decisions are visible, and they are visible sooner. Filings arrive continuously on public disclosure platforms. Job postings, supplier announcements, executives' own public profiles and local news all tell investors something about what a company is doing, often before the company has explained it. An investor who follows a company closely can put together a picture of its decisions from many small pieces.

The second is that many of the decisions investors read are made outside finance. The CFO and the IR team are used to thinking about how the market will read the numbers. Colleagues in operations, HR, legal and strategy make decisions that investors read just as closely: the timing of a plant investment, a round of redundancies, the settlement of a legal case, a partnership that is announced and then goes quiet. These colleagues rarely meet investors, and in most companies nobody asks them how a decision might look from outside before it becomes final.

That is the gap I want to look at this month. It sits between the people who make the decisions and the people who will have to explain them.

A practical tool: the Investor Reading Log

The simplest way I know to close that gap is a short log kept by IR. I call it the Investor Reading Log. It is a table with one row per decision, and five columns:

The decision, described in one line. Who made it, and when investors will be able to see it. How an investor who doesn't know the reason is likely to read it. Be honest here, and write down the cautious reading as well as the intended one. What we would say if asked, and whether we should say it before anyone asks. Whether it changes anything we have said before: a guidance statement, a strategic priority, a KPI definition.

How to use it:

Build the intake first. Agree with each executive a short list of decision types that should reach IR before they are final. For most companies that list includes results timing, changes to KPIs or guidance format, senior departures, changes to event attendance, and the timing of large investments. The list matters more than the log, because it is how IR gets told early. Keep it in the monthly meeting with the CFO. Ten minutes is usually enough to go through new entries and decide which ones need a line in the next communication. Take it to the executive team before each results period. This is where the log does most of its work. The heads of operations, HR, legal and strategy see their own decisions described from the investor's side, often for the first time. Summarize it for the board once a year. A one-page note on which decisions investors read differently from what was intended, and what the company did about it, tells the board more about how the market sees the company than another sentiment score.

A word on limits. Most rows will end with "no action needed", and that is fine. The log exists to make sure someone considered the investor's reading. It should not become an approval step that slows the business down, and it doesn't mean every decision has to be explained publicly. Some decisions are better left without comment. The point is that leaving them without comment should be a choice.

The question to put to the C-suite

At the next executive committee meeting before results, ask this:

"What did we decide this quarter that investors will read as a message, and did anyone ask how they would read it?"

If the room goes quiet, that is useful information too. Take the last three decisions people mention and make them the first three rows of the log.

Back to Harry Caul

What stays with me about The Conversation is that Harry had the whole recording. Nothing was missing. He got the meaning wrong because he supplied the emphasis himself.

Investors are in a similar position with our decisions. They see what we do, often in full, and they supply the emphasis. The Investor Reading Log gives the company a chance to hear that emphasis before the market does, and to decide whether to say something first.

I'd like to hear from you: which ordinary decision have you seen investors read as a message, and how did your company respond?

Your fellow IR Enthusiast, Müge

About the author Müge Yücel is the founder of Müge Yücel IR Advisory, an independent practice focused on investor relations advisory, training, and speaking. She led investor relations at listed companies, where her expertise in proactive strategies that leverage digital technology and AI, particularly in shareholder targeting, was instrumental in communicating the company’s growth story. She is a board member of TÜYİD, the Turkish Investor Relations Society, and serves on the editorial board of IR Impact. Now dedicating her focus to independent advisory work, Yücel partners with management teams to modernize their workflows and future-proof their IR programs. Learn more at mugeyucel.com.

She is the author of “The Investor Relations Playbook - Achieving Sustainable Success,” a hands-on guide to investor relations operations featuring templates, checklists, and how-to guides. The book is available in print in Turkish and in digital format in English.

Yücel also shares her insights with the global IR community through her monthly LinkedIn newsletter, IROVISION, which is now available as a video podcast on Youtube and Spotify. Find the show on Spotify here.