When the Board Doesn't Understand Your Role

The first board meeting I attended after taking a combined product-and-engineering role, I got asked two questions that illustrated the problem perfectly. The first question was about our infrastructure scalability — phrased in a way that assumed I was primarily a technical leader, with product as a secondary responsibility. The second question, from a different board member, was about our pricing strategy — phrased in a way that assumed I was primarily a product leader who happened to have engineering reporting to me. Neither frame was wrong, exactly. But they were incompatible, and navigating between them in real time while trying to give useful answers to both is a structural inefficiency that compounds over time.

Boards are pattern matchers. They’ve worked with CTOs, they’ve worked with CPOs, and they’ve developed frameworks for how those people think, what they’re likely to know, and how to evaluate their judgment. When you walk in as a CPTO, you’re asking them to use a different framework — one most of them haven’t used before — without giving them any explicit help building it. The result is that they use whichever of the two familiar frameworks fits their current question, and you end up ping-ponging between two different versions of yourself across the meeting.

What you can control

The framing you establish before and around the board meeting matters more than anything you say during it. The materials you send, the way you structure the narrative, the topics you proactively surface versus the ones you leave to Q&A — these set the frame. If your board pre-read is organized as a product update followed by an engineering update, you’re reinforcing the two-track mental model. If it’s organized around strategic decisions and tradeoffs — “here’s the choice we’re navigating between X and Y, here’s the customer context, here’s the technical constraint, here’s where we landed” — you’re demonstrating the integrated frame in action.

The other thing you control is what you bring to the board proactively. Most technical leaders bring to the board the things they’re proud of and the things they’re asked about. The CPTO who builds genuine board trust is the one who brings uncomfortable tradeoffs before they become crises. “We have a technical decision in front of us that has a material impact on our product strategy over the next 18 months, and I want to walk you through the options and my recommendation.” That kind of proactive framing accomplishes two things: it gives the board a window into how the integrated role actually works, and it gives them something substantive to engage with rather than asking pattern-matching questions.

The problem with educating the board

There’s a version of the “board doesn’t understand your role” problem where the instinct is to explicitly educate them — to carve out time in a board meeting to explain the combined role, its philosophy, its advantages. I’ve watched this go badly. Boards don’t enjoy being taught. They enjoy being consulted. The distinction matters.

You can’t tell a board member that their mental model for your role is wrong. But you can demonstrate, over the course of several meetings, that your judgment about the intersection of technology and product has been reliable. That your technical calls have held up in ways that mattered to the business. That your product instincts have been informed by technical constraints in ways that led to better outcomes than a pure product perspective would have produced.

The board’s mental model for your role will update based on evidence, not argument. The evidence you need to provide is the quality of the integrated judgment you bring to real decisions over a meaningful period of time. That takes longer than you’d like, and it requires patience with a process that can feel frustrating when you know your mental model for the role is more sophisticated than theirs. The only way through it is to keep doing the job well and let the record build.

One thing that accelerates the process: find the board member who is most technically sophisticated — usually a former founder or operating executive — and invest in that relationship disproportionately. If one board member deeply understands how the combined role creates value, they become your interpreter to the rest of the board in the conversations that happen when you’re not in the room.