

Every year around this time, strategy starts hardening. Budgets close, board decks get finalized, and the plan that was a whiteboard sketch in September turns into slides, talking points and, for some companies, public commitments.
That's the moment when it gets expensive to be wrong. Once a strategy has been said out loud to employees, customers, investors or the market, leaders tend to defend it rather than test it. Which is why the most disciplined executives build in private conversations before public strategy: a deliberate stretch where the plan gets challenged by people who have no stake in agreeing with it.
This isn't about secrecy for its own sake. It's about sequence, and about who in the C-suite owns that sequence. The right answer, more often than most companies admit, is governance, risk and compliance.
Why Public Strategy Is So Hard to Walk Back
A strategy announced at an all hands, an investor day or in a press release picks up weight fast. Teams reorganize around it. Partners plan against it. Analysts model it. Reversing course later isn't impossible, but it costs credibility, and the leader who announced it usually pays the most.
That creates a quiet incentive problem. The closer a plan gets to going public, the less anyone inside the company wants to be the person raising doubts. Gary Klein made this point in his classic Harvard Business Review piece on the project premortem: projects fail at a high rate, and one reason is that too many people are reluctant to voice reservations during planning.
Private conversations are where those reservations can come out while they're still cheap to act on.
What a Private Pass Does That a Strategy Offsite Can't
Offsites are useful. They're also full of the same people who wrote the plan, reporting to the same person who has to approve it. A private conversation changes who's talking and what they're allowed to say.
Argue About Assumptions, Not Positions
In a 2023 HBR article on building consensus around difficult strategic decisions, Scott Anthony, Natalie Painchaud and Andy Parker describe what they call strategic sparring sessions. One of their core principles is to hold battles of assumptions rather than beliefs. Instead of "I think we should do this," people state the critical assumption underneath their view. Disagreements get smaller and more specific, and nobody has to lose face to change their mind.
The same article points to research by W. Chan Kim and Renée Mauborgne showing that people strongly prefer a fair process over a fair outcome. Inclusive dialogue builds commitment, even among people who end up disagreeing with the result. That matters later, when the strategy needs backing from people who weren't in the room.
The reframing itself is far easier in private. A peer at another company can tell you your pricing assumption looks thin without any of the politics that come with saying it to your own CEO.
Run the Premortem Before the Announcement
Klein's premortem flips the usual risk review. Instead of asking what might go wrong, the team assumes the project has already failed and writes down why. His article cites 1989 research by Deborah Mitchell, Jay Russo and Nancy Pennington finding that this kind of prospective hindsight increased the ability to correctly identify reasons for future outcomes by 30%.
Try that on a strategy before it goes public. Picture the plan a year after launch, and failed. Ask a few trusted people, separately, what killed it. The answers will be uneven and some will be wrong. A couple will be the thing you hadn't priced in.
Who Should Hear the Strategy First
Private doesn't mean one conversation. It usually means a few rings, each with a different job.
- The core leadership team. The CFO on cost and guidance, the CISO and CIO on what the plan asks of systems and data, the CTO on what engineering can actually deliver, and the GRC leader on controls, evidence and disclosure. The case for this kind of early collaboration is laid out in the future of C-suite collaboration.
- The board, or a committee of it. Directors shouldn't see a major strategic shift for the first time in a polished deck. A preview with the chair or the relevant committee gives them room to push back. The same principle drives good cybersecurity board reporting: no surprises.
- Trusted peers outside the company. People who have run a similar play, in a setting where everyone has agreed on discretion.
That third ring is the one most leaders skip, and it's the one with the least bias. Your own team wants the plan to work. Your board wants to support you. A peer in another industry just wants to know if it makes sense.
Why GRC Leaders Should Own the Sequence
Here's where most organizations get it wrong. They treat the move from private to public as a communications problem, owned by whoever writes the announcement. It's really a governance problem.
Somebody has to answer a set of unglamorous questions. What can be said, to whom, and when? Do private assurances given to partners or employees match what will eventually be said in public? Does the plan fit the company's stated enterprise risk appetite? If the strategy leans on AI, is there evidence behind the claims, the kind GRC teams already ask for before an AI use case scales?
GRC leaders are built for those questions. They also tend to see the early warning signs, the same ones that cause ERM programs to stall when risk shows up late and nobody owns it.
The Regulation FD Boundary
For public companies there's a hard line, and it's worth stating plainly. Under the SEC's Regulation FD, when an issuer or someone acting on its behalf discloses material nonpublic information to certain people outside the company (broadly, securities market professionals and shareholders who could reasonably be expected to trade on it), the issuer has to make that information public. Simultaneously if the disclosure was intentional, promptly if it wasn't. The rule excludes people who owe the company a duty of trust or confidence, such as its attorneys, investment bankers or accountants, and people who expressly agree to keep the information confidential.
Most peer conversations between executives aren't analyst briefings, and Regulation FD isn't a reason to avoid them. It is a reason to keep material nonpublic details out of them, to know who in the room might be covered, and to involve counsel when a strategy touches earnings, guidance or a transaction. This is general information, not legal advice.
Ground Rules for Peer Conversations
Outside the regulatory line, the best private conversations still run on clear norms. A common one is the Chatham House Rule, first devised in 1927: participants can use what they hear, but they can't reveal the identity or affiliation of the speaker or of anyone else present. Chatham House says the Rule lets people speak as individuals and express views that may not be those of their organizations, and notes it now turns up everywhere from think tank roundtables to corporate boardroom discussions.
Practical additions help:
- Talk in patterns and decisions, not customer names, deal terms or numbers that haven't been released.
- Agree at the start what can be repeated and in what form.
- Keep notes about your own learning, not about what others said.
- If something starts to sound material, stop and take it offline with counsel.
That discipline is a big part of why invitation only executive events are valuable in the first place. The guest list and the norms make candor possible.
The CFO's Year End Version
Finance leaders feel this most in November and December. Guidance, budgets and the assumptions under next year's plan all get locked within a few weeks of each other. A private sanity check with peers on how they're modeling demand, pricing or AI spend can catch an assumption that would otherwise end up in an earnings script.
The approach in how CFOs are rebuilding their forecasting models pairs well with this. Test the scenarios privately, then publish only the range you can stand behind.
There's a quieter benefit too. A CFO who has heard two or three peers explain why their automation savings arrived later than planned tends to write a more careful assumption. That kind of care rarely shows up in a headline. It shows up a year later, when the number holds.
A Simple Sequence for Taking Strategy Public
- Write the critical assumptions down. Three to five, in plain language.
- Run a premortem with the core team. Each person, independently, explains why the plan failed.
- Take it to two or three outside peers. Separately, under agreed discretion, with no material nonpublic detail.
- Do the governance pass. GRC and counsel review what can be said, to whom and when, and whether private commitments match the public story.
- Preview with the board or its committee. Show what changed after the private pass, not just the final answer.
- Then go public, once. One consistent message, delivered through proper channels.
Where Private Conversations Go Wrong
The format has failure modes. Talk only to people who think like you and the private pass turns into an echo chamber. Promise different things to different people in private and the public version will expose it. And a decision made informally among a few executives still needs to go through the company's formal approvals. Private conversation informs governance. It doesn't replace it.
Group settings can help counter the echo chamber, which is why some leaders pair individual conversations with an executive roundtable or a small executive dinner, where several peers react at once.
FAQ: Private Conversations Before Public Strategy
Why should executives test strategy privately before announcing it?
Once a strategy is public, leaders tend to defend it rather than question it, and reversing course costs credibility. Private conversations let peers and colleagues challenge assumptions while changes are still cheap to make.
Does Regulation FD prevent executives from discussing strategy with peers?
Not by itself. Regulation FD applies when a public company discloses material nonpublic information to covered people, mainly market professionals and certain shareholders. Leaders should keep that information out of peer conversations and involve counsel when in doubt.
What is the Chatham House Rule?
It's a meeting norm created at Chatham House in 1927. Participants may use the information they receive, but they can't reveal the identity or affiliation of the speaker or any other participant.
Why are GRC leaders well suited to manage the move from private to public?
Moving a strategy into public view raises governance questions about disclosure, consistency, evidence and risk appetite. GRC leaders already work on those issues and can spot gaps before an announcement locks them in.
What is a strategy premortem?
A premortem asks a team to imagine that a plan has already failed and then list the reasons why. Gary Klein described the method in Harvard Business Review as a way to surface concerns people might otherwise keep to themselves.
Find the Right People for the Private Pass
The private pass only works if you have people worth calling. That's hard to build inside one company and nearly impossible to build the week before an announcement. GRC leaders find those peers in GRCMeet, finance leaders in CFOMeet, and security and technology leaders in CISOMeet, CIOMeet and CTOMeet. It's what C-suite leaders actually want from peer communities: people who'll tell them the truth before it's public.
CXO Inc. brings CIOs, CTOs, CISOs, CFOs and GRC leaders together in curated, invitation only communities built for that kind of candor, and you can read more about the approach on the About CXO Inc. page. More executive perspectives are available through CXO Inc. Insights.