Welcome back to The 2x2 - the ultimate newsletter for executive consultants!
Not every comment said in a board meeting is a directive.
As the consultant in the room, your job is to translate comments — and find out which one actually needs action.
Read on to decode comments better…
⏰ Today in 5 minutes or less:
The same comment can mean different things depending on how — and by whom — it’s said
Always watch out for political theater — subtle comments that send a bigger message to the room and influence decisions.
Be a thought partner to your client and help them see other perspectives.
WORK WITH ME
My firm Keenan Reid Strategies builds 9-figure business models and the financial engines behind them. We help enterprise B2B leaders:
MORE FROM THE 2X2
🔊THE PODCAST → Listen to the world’s greatest podcast for indie consultants.
📚 THE LIBRARY → Our full archive of content. Sign up FREE for a limited time.
💬 ASK ME ANYTHING → I share the unspoken rules of building a serious indie consulting practice. 👉 Got more questions? Drop them here.

What the Board Said vs. What the Board Meant: A Decoding Guide for Consultants
Your client walks out of a board meeting ready to launch a task force for international expansion.
But when you replay the conversation, you only remember the board member saying:
"Have we thought about international markets?"
You knew it was offhand. Exploratory. But your client thought it was a command.
What they missed is that not every board comment is a directive.
Yet executives routinely misinterpret commentary as a command, creating organizational whiplash and misallocating resources.
As an independent consultant, your job includes translation.
In this article, we’ll show you how to do it.
Reading the Room
First, you need a framework to decode what the board said versus what they meant:
Identify the mode of communication used.
Decipher what they meant based on their interest and incentive.
This is what helps the client respond appropriately.
First, Recognize the Four Communication Modes
Board members don't speak in a single register.
They shift between four distinct modes, often in the same meeting.
Your ability to distinguish between them determines whether your client responds appropriately or overreacts.

GIF by MastercClass on Giphy
Commentary: Thinking Out Loud
The board member is processing information in real time – just exploring possibilities, not yet issuing instructions.
What it means: They're curious and connecting dots but not demanding action.
The tell: No follow-up asked for. If they don't circle back or request updates, it was commentary.
Pressure Testing: Validating Your Approach
The board is probing your strategy to see if it holds up. It feels like resistance, but it's engagement.
What it means: They're checking your work and want to see that you've thought through risks. They're validating, not rejecting.
The tell: If they accept your answer and move on, it was testing. If they keep pushing or request analysis, you're moving into directive territory.
Direction: Expecting Action
The clearest mode, though executives often miss it while processing earlier commentary.
What it means: They expect follow-through. This is a clear request for action with a timeline and accountability.
The tell: Specific language with timelines and explicit expectations. They'll ask about it again a few minutes later, or likely in the next board meeting.
Political Theater: Messaging the Room
The board member isn't primarily speaking to you, but rather to others in the room – advancing a different or broader agenda.
What it means: They're shaping perception or reinforcing a priority without directly asking for action.
The tell: No follow-up requested. The comment reframes the discussion or signals a position others are meant to hear.
Then, Decode Based on Interests and Incentives
Understanding what drives each board member helps you decode their true intent.
The same sentence means different things depending on who says it and what they're incentivized to care about.

Let’s put this framework into practice with an example.
Imagine walking out of a board meeting where the client presented Q4 projections.
Based on the notes you wrote, the board members said:
The operator, a former COO: “In my last company, we got burned by being too aggressive with Q4 hiring. Have we thought about staging the ramp?”
The investor, a PE partner: “Walk me through the unit economics again. What happens to margin if we miss revenue by 15%?”
The tech expert: “I’m seeing competitors invest heavily in AI capabilities. We should probably accelerate our roadmap.”
Using the two-step framework, we can decode that:
The Operator's comment: Commentary. He's sharing a war story, not demanding you change your hiring plan. The tell? He said "have we thought about" and offered no follow-up timeline.
The Investor's question: Pressure testing. She wants confidence that you've modeled downside scenarios. Answer thoroughly, and if she moves on, you're good. If she says, "Send me that analysis," it becomes direction.
The Tech Expert's suggestion: Direction. He used "should" and "accelerate"– action language. Plus, it's his domain. This requires a response plan.
The client suddenly wants to overhaul hiring, rebuild financial models, and launch an AI initiative.
But you know that only one of those requires immediate action, so you direct them to the right path.
How to Offer Constructive Pushback
As the consultant, your job is to be constructive and objective – steering clients in the right direction and helping them work on it.
Sometimes, the client will insist that commentary is direction.
Instead of just saying they’re wrong, it’s your responsibility as the thought partner to offer different perspectives and help them think through the possibilities.

GIF by LateNightSeth on Giphy
Here are different ways to push back effectively:
Acknowledge before you correct: Starting here builds trust before redirecting their interpretation. "I hear that this feels urgent to you. Let's talk about why."
Use evidence from the room: Politely let them know what you noticed and what it meant. "When I replay the conversation, here's what I noticed. The board member didn't ask for follow-ups. No one else built on the comment. Those are signals that it wasn't a priority."
Propose a wait-and-see approach: Diffuse urgency without dismissing their concern. "What if we monitor this for the next 30 days? If it comes up again, we act. If it doesn't, we know it was exploratory."
Frame the opportunity cost: Make the tradeoff visible. "Every time we shift priorities based on commentary, we're pulling resources from initiatives the board actually directed us to focus on. That creates risk."
Play the devil’s advocate: Walking through the discussions helps the client self-correct without feeling challenged. "Let’s play devil’s advocate and pressure test it.”
Your Role as the Translator
Board members speak in four distinct modes – commentary, pressure testing, direction, and political theater. Understanding which mode they're in, combined with decoding their underlying incentives, is how you prevent costly misinterpretations.
Master this decoding framework and you become the strategic advisor who protects your client from overreaction, preserves organizational focus, and ensures they respond to what the board actually needs.
Turn AI into Your Income Engine
Ready to transform artificial intelligence from a buzzword into your personal revenue generator?
HubSpot’s groundbreaking guide "200+ AI-Powered Income Ideas" is your gateway to financial innovation in the digital age.
Inside you'll discover:
A curated collection of 200+ profitable opportunities spanning content creation, e-commerce, gaming, and emerging digital markets—each vetted for real-world potential
Step-by-step implementation guides designed for beginners, making AI accessible regardless of your technical background
Cutting-edge strategies aligned with current market trends, ensuring your ventures stay ahead of the curve
Download your guide today and unlock a future where artificial intelligence powers your success. Your next income stream is waiting.

Framework Focus: The Driver Tree
If you’ve been consulting long enough, you know that clients rarely bring you the problem.
They bring you the headline – or the symptoms.
The Driver Tree framework is how you get to the cause.
This tool lets you visually deconstruct a messy issue into smaller, logical pieces until you reach on a root cause you can solve.
It lets you organize your thinking and gives the team a shared map.

For example, imagine a fractional COO hired to fix a “sales problem” at a services firm with flat revenue.
Instead of replacing the sales lead, she used the framework to break revenue into clear drivers and push to root causes.
Win rates were fine.
The real issue? Client churn after project handoff.
By clarifying the ownership between sales and delivery and tightening the transition process, retention improved within two quarters.

