What I Learned the Hard Way in My First Board Meeting as a Technology Leader

I remember it vividly still, and I think it’s because we remember moments most clearly when we are embarrassed. I walked in confident, prepared, and excited. I had prepared for weeks leading up to my first board meeting as a technology leader, and I was genuinely excited about being “at a board meeting.”

So I prepared everything. Forty-seven slides.

It was the strategy, the trade-offs, the roadmap, the rationale behind every decision we had made. I was proud of it, and so was the team that helped me create it.

As I got into my update, a board member leaned in and stopped me and said, “Quick question. Are we still on Oracle or PeopleSoft?”

We had spent two or three quarters talking about this transformation, this investment, the migration plan, the possible interruption to the business, and the global impact of such a change on a company like ours. And in that moment, I realized something I wish I had understood earlier.

Boards Operate on Pattern Recognition

Boards don’t operate on continuity. They operate on pattern recognition.

They’re juggling multiple companies, multiple contexts, and a constant stream of risk signals.

My initiative was just one thread among thousands. And if you don’t reset the context, they’re not lost because they’re not paying attention. They’re lost because you didn’t bring them back into your story and your context.

That meeting was the beginning of me learning how to present to a board.

The Need to Reset Context

The next mistake, or learning, was that I presented and spoke to the board the same way I presented and spoke everywhere else.

I would start with things like, “As we discussed last quarter,” or “Building on Phase 2.” That worked really well internally because everyone had context. It failed pretty spectacularly in the boardroom.

What I eventually learned is that a boardroom interaction needs a reset, no matter how repetitive it feels to you and no matter how much you think you’ve communicated this across the company. They need grounding.

They need to know:

• Here’s what we’re doing.

• Here’s where we are.

• Here are the real numbers.

• Here’s what I need from you, if anything.

Sometimes that ask is simply awareness. Sometimes it’s a decision. But those are just words, not a presentation and not a PowerPoint.

Once I started doing that, the dynamic changed pretty drastically. Board members were more engaged. The questions were clearer because they actually understood what we were talking about. The discussions became more productive.

Technology Is Never the Topic

Here’s another learning that is so important as a technology leader: technology is never the topic. It is never the point.

Like many of you, I’m a technologist by background. Throughout my career, I often found myself explaining how things worked. I would describe the technology, the vendor, the architecture, the platform, the cloud. All the things we talk about every day.

What eventually dawned on me is that boards don’t really care about these things. Maybe one or two members will, but the vast majority do not.

They care about what could go wrong.

• Will this hurt revenue?

• Could this damage our reputation?

• Could this disrupt the business?

• Does this create dependency on a finite group of people or a single vendor?

• Could this show up in an audit, a lawsuit, or the press?

Once I reframed my thinking and kept that in the back of my mind, I stopped explaining the technology and started explaining the risk.

The risk we were removing. The risk we were accepting and why. Or the risk we would need to actively manage as we went through a transformation or major change related to technology or cybersecurity.

Always Come With a Recommendation

This next one is tough.

Often, when technology or cybersecurity leaders are invited into the boardroom, it’s not great news. There’s usually a problem, a challenge, or a risk that has emerged.

I’ve lived through situations where a major vendor fell behind, delays became real, milestones were threatened, and it was my job, like it is for many of you, to bring that story to the board with clarity.

Once you do, they will often ask, “So what do you want to do? What do you recommend?”

Be very prepared for this moment.

This is not the time to stumble through trade-offs or look for their perspective.

That’s not their responsibility. It’s yours.

They expect and deserve a point of view on how you plan to solve the problem. What you’re there to do is have your recommendation pressure-tested against their experience.

You only have to live through this once to remember it clearly. From that point on, you never bring an issue to a board without options, a recommendation, and a clear understanding of impact.

Cybersecurity Belongs in the Audit Committee

As someone who has served on multiple audit committees and continues to do so today, it is very clear to me that cybersecurity and the risk that goes with it belongs in the audit committee.

That’s where you go deep.

That’s where you talk about what could seriously hurt the business, what impact you’re seeing, how you’re protecting the company, and how you’re managing third-party risk.

What you bring to the full board is in support of the board members who sit on the audit committee. If they want you to elaborate, you coordinate with them. You do not bring your audit committee deck to the full board as if it’s a new topic.

Understanding the Private Equity Perspective

Another lesson worth sharing relates to private equity-backed boards, which affect many businesses today.

It’s critical to understand the investor perspective and the thesis behind their investment before you walk into the boardroom to talk about technology projects.

Private equity investors have a timeline for when they expect to realize value.

Technology investments don’t always align cleanly with that timeline, especially long-term programs that are depreciated over many years.

This can cause real concern if the investment impacts EBITDA during that window.

That was a wake-up call for me.

PE boards are not short-term or cynical. They have a fiduciary obligation tied to a specific horizon. Once I understood that, I learned to frame technology decisions in terms of margin, payback, and valuation.

Those conversations changed dramatically. It wasn’t that they didn’t want to invest. They wanted clarity on which investments were essential and which could wait.

Seeing the Boardroom From the Other Side

Finally, I’ve now seen the boardroom from the other side.

It didn’t fully click for me until I sat in a true board seat at different companies.

My perspective changed.

I now feel the cognitive load I once underestimated. The constant context switching. The responsibility to spot patterns, surface risk early, and ensure capital is being allocated wisely. The need to trust management without getting lost in the details.

When a management team explains how something works instead of why it matters, I catch myself tuning out. When they bring a problem without a recommendation, I notice the same hesitation I once created.

It’s not because they’re doing anything wrong. They’re just on the journey I was on.

Serving on boards gave me empathy for how hard that role actually is and reinforced the lessons I learned the long way around.

I now make a point, when appropriate, to pull technology leaders aside and share these learnings so they can be more effective in the boardroom than I was early on.

What I Wish I Had Known Before

Boards aren’t there to approve your roadmap. They’re there to govern risk and capital.

They won’t remember what you said last quarter. They will remember how you made them feel about risk and judgment. And they will decide, consciously or not, whether they trust you.

If you assume zero context, translate everything into business impact, and come in with a clear point of view on how your work prepares the company for the future, you will build trust.

And trust is the real currency in the boardroom.

I learned all of this by getting it wrong first. Sitting on the other side of the table only made that clearer.

I hope this helps you avoid some of those missteps when your opportunity comes.