There is a category of work that most association professionals do without a name for it. It sits above execution and below the executive director title. It’s the work of thinking about the organization as a whole — its positioning, its sustainability, its culture, its direction — rather than thinking about a department or a function.
Most people doing this work don’t call it anything. They just do it, because the organization needs it and nobody else is doing it. Some organizations recognize it and create conditions for it to happen. Many don’t.
It’s worth naming. And it’s worth doing deliberately, because the organizations where someone is doing this work — inside whatever title they happen to hold — are measurably different from the ones where nobody is.
What This Work Actually Looks Like
ED-level thinking inside a non-ED role shows up in specific ways. It’s not about acting above your station or overstepping your scope. It’s about bringing a particular quality of attention to the work you’re already doing.
It looks like building infrastructure that will still be useful after you’ve moved on, rather than building systems optimized for your own workflow. A brand guide written for the next person who leads marketing is different from one written because you needed to organize your own files. A competitive intelligence report designed to inform organizational strategy is different from one that satisfied your own professional curiosity. The work is similar. The orientation is entirely different.
It looks like translating your department’s work into organizational language before leadership asks you to. Not “we ran a great conference campaign” but “our marketing programs contributed to the membership growth that funded the reserve we needed last year.” Not “we won three awards” but “our communications work is nationally recognized, which reflects on the organization’s professional standing in the field.” The translation is part of the job when you’re thinking at the organizational level.
It looks like anticipating the board’s questions before they ask them. What’s the competitive landscape? What are members saying that leadership hasn’t heard yet? What’s the argument for this investment in terms the finance committee will actually engage with? When you’re doing this kind of prep as a matter of course — not because you were asked, but because you understand that leadership needs it — you’re doing organizational stewardship from inside a functional role.
The Infrastructure Question
One of the most reliable markers of ED-level thinking is a preoccupation with organizational infrastructure — the systems, documents, processes, and institutional memory that allow an organization to function at a higher level than its headcount would suggest.
Most organizations are underbuilt. They have people doing the work but not the systems that encode how the work gets done. No documented brand voice. No crisis communications protocol. No competitive intelligence process. No onboarding infrastructure that transfers institutional knowledge to new staff. These absences are invisible until they’re suddenly very expensive — a staff transition that takes six months to stabilize, a reputational misstep that a crisis protocol would have prevented, a vendor conversation that went sideways because nobody could locate what the organization had agreed to before.
Building that infrastructure isn’t glamorous. It doesn’t generate immediate visible output. It’s hard to put on an agenda and harder to defend in a budget conversation. But it’s exactly the kind of work that compounds over time into organizational resilience — and it’s work that only gets done when someone is thinking about the organization’s future, not just its present.
The Growth Attribution Problem
One of the more uncomfortable aspects of doing ED-level work inside a non-ED role is the attribution question. When marketing programs contribute to membership growth, when communications work raises the organization’s profile, when the brand infrastructure you built enables a conference to run more professionally than it would have otherwise — how do you account for that accurately without overclaiming?
The honest answer is that organizational outcomes are almost never the product of one department’s work. Membership growth is a function of program quality, pricing, advocacy, community, conference experience, and external field dynamics — not just marketing. Claiming it as a marketing win would be wrong.
But the right response to that complexity isn’t to disclaim any contribution. It’s to be precise: marketing programs contributed to a set of outcomes, alongside the work of other departments, within a broader organizational context. That’s an accurate and honest framing. It also happens to be how executives think about impact — in systems and contributions, not in individual departments claiming sole credit for organizational results.
The professional who can accurately describe their department’s contribution to organizational outcomes, without inflation and without false modesty, is demonstrating executive judgment. That capacity for honest attribution is one of the things that distinguishes organizational leaders from functional managers.
ED-level thinking inside a non-ED role shows up in specific ways. It’s not about acting above your station or overstepping your scope. It’s about bringing a particular quality of attention to the work you’re already doing.
Doing It Without the Title
The reason this work matters beyond career positioning is that organizations need it regardless of whether the person doing it has the right title. An association where the marketing director is doing organizational stewardship — building infrastructure, translating departmental work into organizational terms, thinking about competitive positioning and long-term sustainability — is a stronger organization than one where those things only happen at the ED level.
It also makes the organization more resilient to the most disruptive event most small associations face: leadership transition. When the ED leaves and the organizational infrastructure is solid, the institutional knowledge is documented, and the senior staff are already operating with organizational awareness — the transition is hard but survivable. When the infrastructure doesn’t exist and the knowledge lives only in the departing leader’s head, every transition is a near-crisis.
Building that resilience is one of the most valuable things a senior staff member can do for their organization. It’s also, not coincidentally, exactly what an executive director would do if they were thinking about the organization’s long-term health rather than just their current tenure.
You don’t need the title to do the work. The organizations that figure that out tend to be the ones that thrive past any single person’s tenure.
Kitchen's Ink 
Leave a comment