From Activities to Architecture: Designing How Associations Work

The associations I have worked with have a strategic plan, a committee structure, and a conference that runs every year. Many have invested in technology, brought in consultants, and built onboarding packets for new board members.

Those are activities, and they matter. What is often less developed is the design that connects them — how decisions, knowledge, and daily work hold together when the people change. That distinction is what this article is about.

A Pattern I Keep Seeing

In my enterprise change work, I saw large organizations put deliberate effort into operating design: defined decision rights, documented standards, and processes intended to outlast any one leader. They did not always succeed, but the intent was explicit.

In association work, I have more often seen organizations that run on particular people. The executive director who "knows where everything is." The board chair who sets the tone for the year. The committee leader who personally carries an initiative forward. These people are assets. The difficulty comes when they move on — and volunteer terms are designed to end — because the organization can lose context along with the person.

I have watched new boards reopen questions that earlier boards had settled. I have seen staff rebuild processes that existed only in a colleague's head, and growth add strain rather than capacity because the work depended on a few individuals.

When this happens, it is tempting to ask who fell short. I find it more useful to ask how the work was organized: what was written down, who owned it, and what the successor was given to work with. Often, a meaningful part of the answer is design.

What I Mean by Architecture

When I say "architecture," I don't mean a strategy document or a governance manual. I mean the underlying logic of how an organization operates — who decides what, how knowledge is kept, how work moves, and how members receive value.

Associations accumulate activities over time: programs, events, committees, policies. Each one usually made sense when it was added. What can go undesigned is the way they fit together. When that is the case, the organization functions, but transitions are harder than they need to be and growth is harder to absorb.

Architecture is the difference between an organization that depends on the right people being in the room and one that gives whoever is in the room clear responsibilities, shared standards, and the context they need.

Four Systems, Often Developed Separately

In my work I use four systems to look at how a membership organization operates. Every association has them in some form, whether or not they were designed intentionally.

Leadership and Governance covers how authority flows, how decisions are made, and how accountability works. A useful test is whether an incoming board member can find out how decisions are made and why recent ones were made, or whether each leadership cycle starts from a partial picture.

Institutional Memory and Continuity covers how knowledge and standards carry through leadership change. In my experience this is the system that most often has no owner. Knowledge sits in email threads, in someone's memory, in "the way we've always done it," and it is hard to hand to a successor.

Operations and Execution covers how work moves from idea to decision to action to result. Without intentional design, it can come to depend on particular staff members who hold the process in their heads.

Member Experience and Value Delivery covers how members consistently receive value: service quality, belonging, participation, and, in some associations, governance responsibilities. Designing it means reflecting the rights, expectations, and relationships of the organization's actual membership, and checking on the experience regularly rather than occasionally.

The question I ask is whether these four systems were designed together or grew up separately. When they grew up separately, handoffs between them are where friction tends to appear.

Why This Matters Now

Members can often find professional development, community, and credentials from other sources. An association's value is easier to sustain when it is delivered consistently, rather than depending on a particular staff member or an especially engaged chair.

Leadership transition is also a built-in feature of association life. Board terms end, chairs rotate, and executives move on. That is healthy; rotation brings fresh perspective. The practical question is what each transition costs the organization in momentum and context, and whether its design reduces that cost or adds to it.

More programs, more committees, or a new strategic plan will not answer that question on their own. Clear decisions, documented handoffs, accessible knowledge, and consistent service practices can help.

The Approach I Developed

I developed Association Architecture™ as an organizational design approach for membership-based institutions. It looks at the four systems above together, along with the workforce capability needed to run them, and helps leaders turn what they find into defined responsibilities, usable processes, and priorities for change.

It is meant to be used alongside established governance and management practices, not in place of them.

My graduate training in Industrial-Organizational Psychology taught me to look at organizations as behavioral systems before looking at them as process systems. My career since has included enterprise change work in insurance, healthcare, and financial services, and association operations through MBM360, the company I founded and own. Association Architecture draws on both.

A Question Worth Asking

The next time you sit in a board meeting, consider this: if several key people — the chair, the executive director, a long-tenured staff member — moved on this year, what would their successors have to work with?

If the honest answer is "not much," that is not a verdict on anyone in the room. It is a starting point for deciding which responsibilities, records, and routines are worth designing first.

Activities are what an association does. Architecture is what helps it keep doing them well as people and priorities change.

---

Selina Parker, M.A., developed Association Architecture™, an organizational design approach for membership-based institutions. She writes on governance, member experience, organizational change, and technology adoption. Connect with her on LinkedIn.