The Boardroom Doesn't Have an ESG Problem. It Has an EQ Problem

Here's a pattern I keep seeing across boardrooms this year. A sustainability committee walks in with a fully compliant report — the numbers are right, the disclosures map cleanly to the framework, the consultant's sign-off is attached. And the meeting still goes sideways. Not because the data is wrong. Because nobody in the room can answer the question the chairman is actually asking, which was never about the data in the first place.

The question underneath the question is usually something like: do you actually understand what this number means for how we run the company next year? And that's not a reporting problem. That's an emotional intelligence problem wearing a spreadsheet as a disguise.

Know Yourself is the first pursuit in the Six Seconds model for a reason — before a team can present numbers with conviction, they have to accurately see what they're actually feeling about those numbers. Anxious about a target they privately doubt? Confident because the framework says so, not because they've stress-tested it? Most compliance teams skip straight to presenting and never do that internal audit. So the report is technically correct and emotionally hollow, and a room full of experienced directors can feel the difference in about six seconds, whether or not they could name why.

This isn't a call to make ESG reporting softer or more feelings-based. It's the opposite. The teams I've watched handle board scrutiny well are the ones who did the harder work first — naming, specifically, where their own confidence is real and where it's borrowed from a template. That's consequential thinking: pausing long enough to evaluate what you actually know against what you're hoping is true, before you walk into the room.

And underneath that is a systems question most compliance functions never ask out loud: is this report a stock or a flow? Is it a snapshot of where things stand, or is it feeding a loop that either builds credibility over time or quietly erodes it? A report produced once a year by a team that doesn't touch operational decisions the other eleven months is a stock with no flow behind it — accurate today, disconnected from tomorrow. The boards that get this right treat the report as one visible output of a system that's actually running year-round, not the system itself.

So before the next reporting cycle, here's the question worth sitting with, not solving immediately: when your team presents next quarter's numbers, will they be reporting on a system they helped build, or reading a document someone else produced on their behalf?