A board member has a smart idea for a children’s banking program.
He tells the CEO. The CEO does not implement it.
What happens next?
Carver and Charney use that small disappointment to open chapter 4 of The Board Member’s Playbook.[1] The question is not whether the idea is good. The question is what authority one board member has after the CEO says no.
The answer is none, unless the board has given that member a specific board role.
An individual trustee may offer advice. The CEO is free to use it or reject it. The trustee may ask the full board whether its Ends adequately state the result it wants for children. The trustee may propose a policy change.
He should not keep lobbying the CEO, recruit staff, or bring the program to the board for operational approval.
I think this distinction protects ideas rather than suppressing them.
If the program would produce a result the board has not named, the member has found a governance question. What benefit should exist? For which people? At what worth? The full board can debate that without selecting the program.
If the End already exists, the CEO may choose another means to achieve it. The member’s preferred program remains advice.
Govern for Impact’s Source Document says board authority is held by the body and that individual members have no authority to instruct staff.[2] That rule can feel limiting to an energetic trustee. It is also what lets the CEO know which words count as direction.
The board should create a safe path for member ideas.
One agenda section might invite policy implications from what members have learned. The chair can ask, “Does this suggest a missing End or boundary?” Ideas that remain operating suggestions can be forwarded to the CEO without expectation.
Minutes should not convert a discussion into a hidden order. “The board discussed a children’s banking concept” is different from “The board directed the CEO to develop the program.”
There is a limit. A tiny all-volunteer organization may have board members doing staff work. They should name which hat they are wearing and receive operating authority through the management structure, not through board membership. Role clarity matters even when the same person fills two roles.
You can test your own idea with one question:
Am I asking what result should exist, or am I prescribing the means I prefer?
A strong board member can release a good idea when it belongs to someone else’s decision.
That restraint is not disengagement.
It is respect for the accountability the board created.
Here is the practical test I would use at the next meeting.
First, write the proposed outcome without naming the program. Second, compare that outcome with the existing Ends. Third, ask the CEO whether the idea is already permissible as a means. Fourth, decide whether the board needs to change policy or simply let management choose.
That sequence keeps the board curious without making it the program department.
The CEO also owes the member a clear response. “No” should not mean “I refuse to talk.” It can mean the program is too costly, duplicates another service, conflicts with current priorities, or is weaker than an alternative. The CEO can explain the decision without surrendering the authority to make it.
This is where trust becomes disciplined. The member respects the CEO’s choice. The CEO respects the member’s concern. The board decides only what belongs to the board.
Footnotes
[1] Miriam Carver and Bill Charney, The Board Member’s Playbook (Jossey-Bass, 2004), rehearsal 4.1, pages 106–109.
[2] Govern for Impact, “Policy Governance Source Document,” principle on Board Holism.
Additional reading
John Carver’s Boards That Make a Difference explains why individual expertise must serve the board’s policy role.
Peter Greer, David Weekley, and Tiger Dawson’s The Board and the CEO helps turn advice into partnership without turning it into control.