1. Your board shifts from strategic oversight to operational management when members make decisions that belong to the executive team, such as choosing specific vendors, approving individual hires, or directing day-to-day program design. These actions mean the board is doing management's work rather than ensuring management does that work well. The board's role is to set direction, allocate resources, and hold the executive accountable for results, not to execute the work that produces them. The exception is the board's fiduciary duty to hire and evaluate the chief executive, a responsibility that belongs to the board alone. Beyond that, the principle holds: governance is about the ends, management is about the means. When board meetings focus on implementation details instead of organizational direction, the board has ceded its strategic function.
  2. A board that debates vendor contracts is not more serious than one discussing strategic priorities. It is doing the wrong work. The distinction is between "what" and "how." The board should ask, "what outcomes are we committed to achieving and how will we know we achieved them?" The executive team should ask which vendor offers the best value, which hire can execute a program, and how to design services for the people the organization serves. When board members repeatedly ask "how" questions, they have entered operational territory. The line is not always clean. Choosing a vendor can be strategic when it determines whether the organization can fulfill its mission, as when a hospital selects an electronic health records system that enables or limits patient care. Even then, the board should decide whether the strategic outcome is worth the investment, not select the vendor. When a decision combines strategic weight with operational detail, the board should address the strategic question and delegate implementation to staff.
  3. Here is what this looks like in practice. A hospital trustee board reviews a proposal for a new electronic health records system. The strategic question is whether the investment supports the hospital's mission to provide accessible, high-quality care and whether the board should allocate capital for it. The operational questions are which vendor to select, what timeline to follow, and how to train staff. Those belong to hospital leadership. If the board packet includes vendor comparisons, implementation timelines, and training plans, the board is reviewing management decisions rather than governance decisions. The board approves the resources and defines the outcome. Management decides how to achieve it.
  4. The same pattern appears in community foundations and nonprofit associations. A community foundation board considering a scholarship program should decide whether its strategic plan commits to expanding access to higher education and how much to allocate. The program officer designs the criteria, selects the application process, and partners with schools. When board members decide which applicants receive awards or how questions are worded, they have moved into operational work. A nonprofit association board sets priorities for member value and advocacy impact. Staff designs member benefits, chooses conference topics, and builds policy positions. Board approval of a conference agenda word-by-word crosses the line.
  5. One complication deserves direct acknowledgment: boards sometimes must make operational decisions during transitions, crises, or periods without an effective executive team. This temporary mode is different from a governance model. The board should fill the gap while building or restoring the management capacity that belongs in that role. The distinction between a stopgap and a broken governance model is whether the board is actively restoring management or has accepted operational work as normal. A board operating for six months without an executive director while actively recruiting is not failing at governance. A board operating that way for three years without filling the role has abandoned its governance function. The test is whether operational work is temporary or the board's default mode.
  6. At your next board meeting, review the agenda and categorize each item as strategic or operational. Mark discussions in which the board answers "how" instead of "what" and "why." Flag decisions involving specific vendors, service providers, or individual hires. These are signs that the board has crossed into operational management.
  7. When you receive a proposal from the CEO or executive director, ask two questions before debating details. First, does it align with strategic priorities the board has approved? Second, is the board being asked to allocate resources or decide how they will be used? If the proposal aligns with priorities and asks for allocation, you are in governance territory. If it asks the board to choose among operational options, respond, "we delegate this to staff and will hold you accountable for the outcome."
  8. Revise committee charters to clarify which work belongs to each committee. Committees often drift into operational matters, including contracts, hiring decisions, and program designs that should remain with management. Return them to strategic planning, policy development, financial oversight, and executive evaluation. When a committee chair reports reviewing a vendor contract, ask what governance question that review was meant to address.
  9. Finally, build a standing agenda item for honest discussion of whether the board has taken on work that belongs to staff. Ask whether members have noticed the board making staff decisions. Create space for someone to say, "we are deciding this," without accusation, as a fact to correct. This practice becomes part of your governance culture, a norm you maintain and adjust for the life of your board.
← Back to all Q&As