Day 60 · 2026.07.19

Boards & Governance: Who Really Owns the Company Decides Whom You Fight For

Theme: Boards & Governance·4 principles

"The board doesn't run the company — the board decides who runs it, and watches whether they run it well." See the top of the chessboard, and your managing-up finally has a ceiling to reach.

This issue's premise: You're a tech lead manager at a big company, and the board seems worlds away — yet every "align on strategy" ask, every slashed budget, every sudden reorg traces back to that boardroom table. This issue hands you a governance lens: see the company's real chain of delegation, understand whom the CEO fights for, and map the highest-level power rules back onto your own managing-up. Four principles — governance ≠ management, fiduciary duty & the agency problem, stakeholders vs shareholders, and the CEO–board "no surprises" rule — upgrade you from "someone who does the work heads-down" to "someone who sees the whole board." That is exactly the divide between senior and staff/management.

PRINCIPLE 01

Governance Is Not Management: Noses In, Fingers Out Governance Is Not Management — Noses In, Fingers Out

governance boundaryboard's roleoversight

The Principle + The Source

A board's job isn't to run the company — it's to make sure the company is run well. It does only three big things: set direction (approve strategy), manage one person (hire/fire the CEO and set pay), and watch risk (finances, compliance, big bets). The day-to-day is handed to management. Cross that line and a board that meddles in operations becomes overreaching micromanagement; one that never asks becomes a negligent rubber stamp.

"Noses in, fingers out." Get your nose in (ask everything that must be asked), but keep your fingers out (don't do management's job for them). — A classic maxim of corporate governance, from John Carver's Policy Governance tradition

In Practice: Your First Report to a Steering Committee

Situation: your platform project has to report to a senior steering committee — your first time facing a "board-style" setting. You've prepared a pile of progress.

✗ Treat it as a status update

"This week we shipped A, B, C; next week we plan D, E…" — You've turned a governance forum into a standup. The committee doesn't care about your task list; all they can give you is decisions, resources, and risk judgment. Filling the time with status wastes the one thing that could move them.

✓ Treat it as a governance forum

"I need a decision today: Option A is fast but incurs tech debt; Option B is slower but sustainable. I lean B and need you to approve two more sprints."

"And an early risk flag: if the third-party API misses its June bar, the whole line slips two weeks — I want you to know now, not be blindsided later."

Governance vs Management Checklist

Facing leadership/a committee, do I bring "decisions and risks awaiting judgment," or a list of completed tasks?
Can I say in one sentence whether a call is mine to make or must escalate to the governance level?
When above wants to reach into my execution details, do I politely draw the line back ("you set direction, leave the how to us")?
Is the information I give upward rich enough to let them "get their noses in" and see the whole picture, not filtered into good-news-only?

Common Mistakes

Treating a governance forum as a reporting show. Filling the time with progress while dodging the hard calls they should actually adjudicate — you look busy but move nothing.
The reverse: waiting for the top to decide everything. Handing up every call your level should own makes people doubt your judgment. The essence of governance is layering: big things escalate, daily things self-decide.

This Week's Exercise + Question

Exercise: Re-sort your next upward report into three columns — "decision / risk / FYI." Delete pure status updates; keep only what needs the other side's action or judgment.

Question: When I complain "the top micromanages," how much is because I only gave them a status log, forcing them to guess and meddle in details?

PRINCIPLE 02

Fiduciary Duty & the Agency Problem: Whom Does a Director Answer To Fiduciary Duty & the Principal–Agent Problem

fiduciary dutyagency problemindependence

The Principle + The Source

Directors owe a fiduciary duty to shareholders (the principals) — two ironclad rules: the duty of loyalty (no self-dealing, no conflicts of interest) and the duty of care (due diligence, real oversight). Governance exists to solve exactly one core problem: the agency problem — the people running the company (agents) may not act in the owners' interest. Independent directors, audits, tying CEO pay to the stock price — all exist to narrow that gap. Grasp it and you'll understand where a big company's countless "seemingly redundant processes" come from.

"Too often, directors have behaved not as watchdogs but as cocker spaniels — wagging their tails at management rather than barking at questionable moves." Warren Buffett's blunt line: too many directors act like cocker spaniels wagging their tails at management, instead of watchdogs that bark at questionable moves. — Warren Buffett, Berkshire Hathaway 2002 Letter to Shareholders

Framework: The Principal–Agent Chain of Accountability

In Practice: Map the Agency Problem Back onto Your Own Team

Situation: a senior engineer on your team always picks the "flashy, promo-packet-friendly" work and dodges the unglamorous grunt work the team actually needs. That's a miniature agency problem — personal incentive ≠ the team's collective interest.

✗ Scold the motive

"Could you stop obsessing over your own promotion and think more about the team?" — Blame doesn't change incentive structure; it just teaches them to hide the self-interest better.

✓ Change accountability and incentives

"Let me recalibrate how I'll rate this: that migration nobody wants to touch — pull it off and it's the hardest line in your promo story; I'll personally champion it at calibration."

"Everyone wants the flashy work, but what makes the committee remember you is carrying what others couldn't." (Align interests with accountability and incentives, not sermons about attitude — which is exactly what a board does to a CEO.)

Fiduciary & Independence Checklist

Do the incentives I set for reports reward "output of real value to the team," or accidentally reward "flashy but useless performance"?
Do I have a "cocker spaniel" tendency at my level — wagging along with the boss instead of speaking up when I should question?
When I decide, do I self-check for hidden conflicts of interest (favoring my own people, protecting my own projects), the way a duty of loyalty demands?

Common Mistakes + A Note on Women's Perspective

Mistaking "loyalty" for "obedience." Fiduciary loyalty means loyalty to the principal (the organization's long-term interest), not to a particular superior's ego — when the two conflict, the former wins.
Believing the agency problem is solved by "finding people with good character." Even the most principled person is pulled by incentives; governance relies on structure (accountability, transparency, aligned incentives), not on betting on human nature.

Women's Perspective Board diversity is itself a governance issue: research (Adams & Ferreira, 2009) finds more diverse boards oversee more actively and attend more reliably. But "the only woman in the room" is often pushed into symbolic ornamentation, or assigned to lower-weight committees. If you ever enter such a setting, beware of being treated as the face of diversity rather than a vote with real power: actively push to join the core committees where the money and power sit.

This Week's Exercise + Question

Exercise: Pick one case on your team where personal incentive is misaligned with collective interest, and design one accountability or reward mechanism to align it — instead of appealing to attitude in a meeting.

Question: In my boss's eyes, am I the watchdog that "barks" at the critical moment, or the spaniel that just wags its tail? Do I want more to be trusted, or to be liked?

PRINCIPLE 03

Stakeholders vs Shareholders: Whom Are You Actually Optimizing For Stakeholders vs Shareholders — Whose Interests?

stakeholdersshareholder primacymulti-party trade-offs

The Principle + The Source

Governance has had a half-century argument: shareholder primacy (Friedman: a business's social responsibility is to make money for shareholders) versus stakeholder capitalism (Freeman: a firm answers to shareholders, employees, customers, regulators, and community). A real board is forever weighing multiple constituencies, with no single right answer. Bring that "for whom" awareness down to your level: on any important decision, don't optimize only for the loudest voice — first put every stakeholder on the table.

"The social responsibility of business is to increase its profits." Milton Friedman's famous thesis — a business's social responsibility is to increase its profits — was directly challenged half a century later by Freeman's stakeholder theory. — Milton Friedman, The New York Times Magazine, 1970.09.13

In Practice: A Technical Decision — For Whom Are You Optimizing?

Situation: the PM keeps pushing you to ship a feature that boosts the quarterly metric. It looks good on this quarter's numbers, but it adds tech debt, burdens downstream teams, and coarsens the user experience.

✗ Optimize only for the loudest

"Fine, the PM's under pressure — let's get the quarterly metric up first." — You answered only the loudest stakeholder (the PM's KPI) and quietly sacrificed users, downstream teams, and your future self. Short-term peace, long-term landmine.

✓ Lay out every stakeholder first

"Let me list who this decision touches: the PM wants the quarterly number, users want the experience, downstream teams fear being dragged by our debt, and the us of six months from now has to maintain it."

"A compromise: ship a lean version this quarter to protect the metric, and schedule a debt-repayment window next quarter. I'll put this trade-off to the parties together for confirmation, rather than silencing others on one party's behalf." (Governance thinking: make trade-offs explicit; don't let the silent party pay for the loud one.)

Stakeholder Trade-off Checklist

Which parties does this decision touch? Can I name them one by one, instead of staring only at the loudest?
Is there a "silent stakeholder" (a future maintainer, a downstream team, the end user) being quietly sacrificed?
When constituencies genuinely conflict, do I honestly admit "there's no win-win here" and explain why I chose as I did?

Common Mistakes

Using "stakeholder capitalism" as a people-pleaser's excuse to satisfy everyone. It doesn't free you from trade-offs; it makes you know whom you're sacrificing and own it — trade-offs always exist; dodging them is the real dereliction.
Optimizing only for the party with a voice, ignoring those with no advocate. User experience, technical health, long-term maintainability often have no volume in the room — which is exactly why you must speak for them.

This Week's Exercise + Question

Exercise: For one tough decision this week, draw a minimal stakeholder map (who's affected × how much × who speaks for them) and see whether a silent party is being systematically ignored.

Question: Over the past six months, were my technical decisions more like "optimizing for this quarter's number" or "optimizing for long-term health"? Was that bias a choice I made, or one pressure pushed me into?

PRINCIPLE 04

CEO–Board Relations: "No Surprises" Is Managing Up at Its Peak CEO–Board Relations — "No Surprises" Is Managing Up at Its Peak

no-surprises rulemanaging uppre-wiring

The Principle + The Source

The board can hire and fire the CEO, so the relationship between them is, at heart, the company's highest form of managing up — it runs on trust, and trust is held together by one ironclad rule: never surprise the board. Bad news gets delivered early, delivered privately, delivered before the formal meeting. This maps one-to-one back to you: don't let your boss hear your bad news for the first time in front of others, in the big meeting, or after the fact.

"The board hates surprises. Bad news does not get better with age — deliver it early, deliver it straight." A governance truism for CEOs: the board hates surprises; bad news doesn't improve with age — deliver it early and deliver it straight. — A widely held CEO maxim in corporate governance (see the thesis of Ram Charan's Boards That Deliver, 2005)

In Practice: A Project Is Slipping — How You Let the Boss Know

Situation: your critical project is confirmed to slip by a month. Next week is your boss's quarterly review where they report up to their boss.

✗ Sit on it until the big meeting

(In the quarterly review, in front of everyone) "This project… may slip a month." — Your boss gets hit by the surprise in front of their boss, caught flat-footed and embarrassed. What they remember isn't the slip — it's "you made me look bad." That's how trust burns in one shot.

✓ Pre-wire privately before the meeting

(Three days before the review, privately) "Heads-up on bad news we need to figure out how to frame together: Project X will slip a month, because of Y."

"I've got a recovery plan and a new timeline ready. I want to align on our shared message before you go in, so you're not caught flat-footed in the room." (Early, private, with a plan — turning them from the person surprised into the person controlling the situation with you.)

"No Surprises" Checklist

My last piece of bad news — did I tell the key person early and privately, or let it burst out in a public setting?
Might my boss hear something I should have told them first — in the meeting, from someone else, or after the fact?
When I deliver bad news, do I bring "here's what I plan to do" along with it, instead of just dumping a problem on them?
Before an important formal meeting, do I "pre-wire" key people one-on-one, digesting the shocks and disagreements in advance?

Common Mistakes

Mistaking "no surprises" for "report only good news." Exactly the opposite — it demands that bad news be told even sooner. Hiding bad news manufactures precisely the most damaging kind of surprise.
Communicating only inside formal meetings, never pre-wiring. A pro's meeting exists to "confirm an alignment already reached"; the real persuasion and digesting of disagreement happen in the one-on-ones beforehand.

This Week's Exercise + Question

Exercise: Before your next important review, list the key people in the room, pick the one or two most likely to be "shocked" by your content or to object, and pre-wire them one-on-one beforehand.

Question: Do I harbor a hope that "if I sit on bad news long enough, maybe it fixes itself"? In the end, did that delay protect me, or burn others' trust in me?

Deeper Reflection

I'm just a middle manager — the whole board world is light-years away. Do I really need to understand it?

Yes, and the payoff is high. (1) Explanatory power — those "baffling" reorgs, budget cuts, and sudden strategy pivots above you almost always trace to governance-level pressure (quarterly results, board accountability, activist investors); understand it and you can anticipate instead of getting blindsided. (2) The ceiling on managing up — the rules a CEO uses with the board (no surprises, decisions not status logs, explicit trade-offs) are, one altitude down, exactly the rules you should use with your boss. (3) A promotion signal — people who can speak "governance language" (accountability, risk, multi-party trade-offs) get read as "thinking one level above their role," which is precisely what staff/management promo committees look for.

Won't the "no surprises" rule swing to the other extreme — asking permission for everything, never daring to decide?

It can, so guard against it by separating "surprise" from "delegation." No surprises ≠ no autonomy. What you must sync is bad news or big pivots that materially affect the boss or exceed your authority — not every daily decision. The healthy move is to settle once with your boss: "what level do you want to know about in advance, and what level do I just call myself" (echoing Principle 1's layering). Carry the calls you should own on your own, and only give a heads-up on things that would "hit them as a surprise." Asking about everything actually exposes weak judgment — the opposite of the maturity "no surprises" is after.

Does this governance logic hold across cultures and company forms?

The skeleton is universal, the flesh varies with context. The agency problem, fiduciary duty, and no surprises are cross-cultural underlying structures — wherever "owners entrust others to run things," these tensions exist. But the implementation differs widely: the US/UK favor a single-tier board, Germany has a supervisory board plus employee codetermination; founder-led tech giants often use dual-class stock to keep voting control, so board checks are weakened; in state-owned or family firms the principal isn't dispersed shareholders at all. So don't treat any single governance doctrine as universal truth — first ask "who is this company's real principal, and where does power actually sit," then apply the framework.