The CEO labels the slide “For Information.”
A new program appears. A second will close. Resources will shift.
Five minutes later, the board is editing the plan.
One member wants a different audience. Another favors the old program. Someone begins rearranging the timeline. The CEO brought information and received a design committee.
Miriam Carver and Bill Charney use this familiar scene in The Board Member’s Playbook. Their CEO shares incidental information about actions intended to achieve the board’s Ends. Board members want to edit, revise, and rank those plans.[1]
I have watched the phrase “This is only an update” fail in exactly this way.
The answer begins with a harder question: what has the board already decided?
Under Policy Governance, the board decides the Ends. It names the results, the people who should benefit, and the worth or priority of those results. It also states which means would be unacceptable through Executive Limitations. Once those words are in place, the CEO chooses programs through any reasonable interpretation of policy.
That delegation is not passive. It is designed.
If a board dislikes the people a program serves, it may have an Ends problem. If it fears financial exposure, inequitable treatment, unsafe practice, or damage to reputation, it may have an Executive Limitations problem. If it simply prefers one operating method over another, it may be standing inside the CEO’s job.
I would use three columns on a whiteboard.
Column one: the result we want.
Column two: the condition we will not accept.
Column three: the operating choice.
The board owns the first two. The CEO owns the third unless law or governing documents say otherwise.
That makes the conversation more demanding, not less. “We do not like this program” is easy. “Here is the result our current Ends fail to name” requires thought. “This feels risky” is easy. “Here is the unacceptable condition our policy should prohibit” requires judgment.
BoardSource describes the chief executive’s role as managing staff and implementing programs, while the board chair leads governance and oversight from a broader view.[2] The language is different from Carver’s model, but the warning is similar: responsibility becomes cloudy when the board manages the work it is meant to oversee.
What should the board do with useful program information?
Listen. Ask questions for understanding. Notice patterns. Test whether the monitoring system measures results rather than activity. Consider whether the report reveals a policy gap. Then let the CEO make the decision the board delegated.
Questions can still become instructions in disguise. “Have you considered moving this program downtown?” may sound open while announcing the answer a powerful member prefers. I would ask, “Which board policy does this information help us govern?” That question pulls the room back to its work.
There is an honest limit. Some grants, accreditation rules, statutes, or contracts require formal board approval of a program. Give the approval when it is required, but do not pretend that a required vote transfers every program decision to the board. Govern for Impact’s glossary calls this a required approvals agenda: the board can receive evidence of policy compliance and approve the item without redesigning it.[3]
The board can still be curious. Good questions may reveal that an Ends policy no longer matches the community or that a risk boundary is missing. Curiosity becomes micromanagement only when the question carries an expected operating answer. Ask to understand. Use what you learn to govern.
At your next update, label each agenda item: information, monitoring, policy discussion, or decision.
Then honor the label.
A CEO should not have to guess whether an update will cost her the authority the board gave her last month.
Footnotes
[1] Miriam Carver and Bill Charney, The Board Member’s Playbook (Jossey-Bass, 2004), rehearsal 3.4, pages 36–39.
[2] BoardSource, “Board Chair and Chief Executive Responsibilities,” sections on policy, planning, and programs.
[3] Govern for Impact, “Policy Governance Glossary,” entry for “Required Approvals Agenda”.
Additional reading
John Carver’s Boards That Make a Difference explains why strong delegation gives both board and staff more room to lead.
Richard P. Chait, William P. Ryan, and Barbara E. Taylor’s Governance as Leadership will help a board use its time for fiduciary, strategic, and generative work instead of program editing.