Board members and staff experience the same organization from different altitudes. The board sees it through governance: strategy, oversight, sustainability, the long questions. Staff see it through operations: daily workflows, community relationships, the ground-level reality of doing the work. Neither view is the whole truth, and I've come to think a great deal of organizational health comes down to one question: do these two views ever actually inform each other, or do they just coexist politely?
I've come to think the strongest organizations build deliberate channels between the altitudes, so governance decisions absorb operational reality and daily practice stays connected to strategic direction. That two-way flow is what this piece is about, and the encouraging news is how little machinery it requires.
Why Both Views Matter
Board members bring distance, and distance sees things proximity can't: patterns accumulating slowly, risks nobody inside the daily work has time to notice, shifts in the funding landscape or the community that deserve attention before they arrive. Staff bring closeness, and closeness knows things distance never will: what's actually working, what's stuck, which strategic priority is feasible with current capacity and which one is a lovely sentence, which community relationships are strong and which need repair.
When the views connect, decisions get better in both directions: plans become realistic because they've met the ground, and ground-level problems get addressed because governance finally heard about them while they were still small. When the views don't connect, the organization develops blind spots, and blind spots, left alone, have a way of maturing into surprises.
What a Working Loop Looks Like
No new committee required. Three practices carry most of the value.
Hear from board and staff in the same assessment. When you do a structured assessment, make sure both are asked about the parts of the organization they can see (governance, strategy, finances, culture, community engagement), each person answering the questions that fit their role. Reading everyone's answers together, as one organization, is some of the most useful information your organization will ever collect, for reasons I'll get to in a moment.
Once a year, the chair listens. A single hour: the board chair sits with the staff or management team, not to direct anything, but to ask and listen. What's working from where you sit? What's the hardest thing you're navigating? What do you wish the board understood about the daily reality of this work? The discipline is resisting the urge to solve anything on the spot; the meeting exists to move information upward, not to generate assignments. I suspect this one hour can reshape how a board talks for the rest of the year.
Add one governance question to staff conversations. Somewhere in the annual staff check-in rhythm, one question: do board decisions seem to reflect an understanding of how the work actually happens here? The answers, gathered over time, tell you whether the loop is real or ornamental.
The specific mechanisms matter less than the habit. What counts is that information moves in both directions on a schedule, rather than only during crises, which is when it moves worst.
A Difference in Views Is a Clue, Not a Conflict
Now the part I find most interesting. Sometimes an assessment will tell you that people in different roles see a topic differently (imagine strategic clarity, or how well the board's decisions are understood). A careful one will say only that, and never which group rated it higher, because that protects the people who answered. The reflex is to treat the difference as a problem, or worse, to start guessing who thought what. I'd invite you to treat it as a clue, and an unusually valuable one.
What might such a difference mean? Perhaps a practice that looks solid from one seat never quite translates into support from another. Perhaps decisions are explained well in one room and arrive unexplained in the next. Perhaps everyone is answering honestly about their own vantage point, and the difference marks precisely where the connection between altitudes needs building. Any of those would be worth knowing, and none of them needs to become a fight.
It seems to me the framing matters enormously here. "Our results say people in different roles see strategic clarity differently; let's explore what might be behind that" opens a conversation. "Somebody here doesn't think the board is doing its job" closes one, and it invites the room to guess who answered what, which I'd never want a board to do. The listening hour above is a far better way to learn what's behind a difference than asking anyone how they answered. (This is also, incidentally, why a difference in views is only worth much when respondents were protected enough to answer honestly; a difference between candid answers is a clue, while a difference between careful ones is mostly noise.)
I suspect the organizations that get the most from all this share one habit: they meet a difference in views with curiosity instead of defense. "That's interesting, what's behind it?" is the sentence that turns a difference into a map.
This Works at Small Scale
If you're reading this with a board of seven and a staff of four, thinking it sounds like a program for organizations with an HR department: the practices above are, if anything, easier at your size. The chair's listening hour is one coffee. A shared survey can work too, if the tool reports only whole-organization results and never gives a small group an average of its own (though I'd be honest with a four-person staff that in a team that size nobody can promise a determined reader could never narrow things down; a tool can protect the data, but not the conversation afterwards). The conversation that follows needs one structured hour, and no retreat.
What Closing the Loop Buys
Boards that hear staff perspective make grounded decisions and catch problems while they're still inexpensive. Staff who feel heard stay longer and bring their best thinking, because someone demonstrated that their view of the work actually reaches the people steering it. And I've come to think plans built from both altitudes survive contact with reality far better than plans built at one.
And underneath the practical returns sits the quieter one: trust, accumulating a little with each cycle of honest exchange. It compounds. Each round of listening makes the next round easier, until the two-way flow stops being a practice anyone maintains and becomes, simply, how the organization talks to itself. That's the loop fully built, and I hope your organization finds it worth the building.