Board meetings and the engineering blind spot

The same moment, every time

I have sat in dozens of board meetings across very different companies, stages, and industries. Different markets, different products, different teams. And yet, there is one moment that feels almost identical every time.

The CTO presents: Slides are shared, metrics are shown, there is talk about velocity, roadmap progress, hiring plans and the trending topic around AI adoption. The narrative is coherent, the story makes sense, and for a moment it feels like we are getting a clear view of how engineering is performing.

Then the questions start and it’s not so clear anymore.

The questions nobody can answer

There are some questions I hear at every board I attend nowadays:

• Are we shipping faster than before?

• Are we getting a good return on what we are investing?

• How do we compare to others?

• Is AI actually making us more productive or just changing how work is done?

• Did costs scale responsibly and accordingly?

• Do we have the best people we could have?

• Is everyone contributing at the level we expect?

• What are our best engineers doing differently, and can we replicate that across the team?

These are not complex questions. They are the most natural questions any board should ask.

Engineering represents 30 to 40 percent of the company’s spend, it shapes the product, the pace of execution, and ultimately the company’s ability to compete.

But yet, in most cases, these questions don’t have clear answers.

The problem is the data

The problem is that the data we bring into those conversations is not designed to answer these questions.

We rely on operational metrics like story points, tickets closed and velocity trends. Metrics that help teams organize their work, but that do not translate into a clear understanding of value creation at a board level.

So the conversation becomes interpretative: Each person builds their own version of reality. Confidence depends more on narrative than on evidence.

And for something that represents such a large share of the company’s investment, that is a fragile place to be.

The missing piece: consistency

I have experienced this from both sides: As a non-tech executive trying to explain engineering performance, and as a board member trying to understand it.

What has always been missing is not more data, but consistency: If every team measures work differently, if complexity is subjective, if outputs are not comparable across time or across teams, then no amount of dashboards will give you clarity.

Without consistency in how work is measured, you cannot answer the same question twice and get the same answer. And without that, you cannot build trust in the numbers.

Why this finally changes

For a long time, I assumed this was just part of the job: Engineering would always be harder to understand and board conversations would always rely on interpretation. You would ask the right questions, get partial answers, and move forward with a degree of uncertainty.

It felt uncomfortable, but also inevitable.

What changed is that it no longer is.

For the first time, I’ve seen see what it looks like to walk into a board meeting and answer those questions with actual clarity. Not by simplifying engineering, but by making execution visible in a consistent way.

You can see how work moves. You can understand what is being delivered and how complex it is. You can compare teams over time. You can evaluate whether AI is improving performance or simply increasing activity and cost.

And most importantly, you can answer the same question twice and get the same answer.

That is what was missing: Not more data, but a way to make sense of it that both technical and non-technical leaders can trust.

Once you experience that, it’s very hard to go back.

Because you realize that the gap was never about engineering being too complex. It was about not having the right way to understand it.

That’s why I believe this changes how boards operate.

And it’s why we built Pensero.