Public
Activity Feed Discussions Blogs Bookmarks Files

Designing and Building Your Advisory Board | Origin: CM143

This is a general discussion forum for the following learning topic:

Building and Leading Effective CTE Advisory Boards --> Designing and Building Your Advisory Board

Post what you've learned about this topic and how you intend to apply it. Feel free to post questions and comments too.

What I learned from this module is that most advisory boards — including mine — don't have bylaws, and the reason is structural: states don't require them. Sign-in sheets and meeting minutes are what get reviewed during program approval. Bylaws aren't on the checklist, so they get deferred.

The course made the case for why that's a mistake. Bylaws are what new members read to understand what they signed up for. They're the only thing that survives leadership turnover. And they shift the board from being held together by relationships to being held together by structure.

I'm writing ours this quarter, and the approach I'm taking is to separate what should be locked from what should flex.

Locked in the bylaws: purpose statement, member qualifications, term lengths, the four-subcommittee structure, decision-making authority, and the amendment process. These are the load-bearing pieces.

Held in lighter documents underneath: subcommittee charters, meeting cadence, contribution tiers, work plans. A subcommittee chair revises their charter annually without triggering a full amendment. That lets the work breathe.

The piece I'm building in that the module doesn't quite name: an annual bylaws and charter review on the calendar. The review IS the flexibility. If you don't schedule it, the document calcifies the moment you adopt it.

How I'm applying it: bylaws drafted against a year of real operating data, subcommittee charters as separate evolving documents, and an annual review built into the IAC calendar.

The onboarding process is not really something I have put much time and energy into, and I am glad it was covered because I feel like it is an area I need to focus on. 

From this module, I learn several core principles which include: (a) Advisory Board should have a clear defined mission tied to program improvement, industry relevance, compliance (accreditation standards), and student outcomes. Also, I learned about strategic composition and recruitment, Advisory Board thrives with diverse, engaged members recruited intentionally for expertise, influence, and commitment. prospecting, nomination, and onboarding processes matter. Avoid tokenism by prioritizing active contributors over prestige. To have a strong advisory board, it requires structures yet flexible processes, clear roles, expectations, leadership, goal setting, and evaluation mechanisms. Meeting management must include follow-up, and recognition keep members motivated. The major take away is having a clear defined by laws. A purposeful charter that clearly articulates its advisory (non-fiduciary) role, meeting cadence, and focus areas. A by laws must set explicit expectations for AB contributions while including flexible amendment and periodic review clauses. 

I've learned that onboarding new members is a continuation of the meet and greet. Pairing new members with long standing members is a strategy to help give meaning and purpose to both members while freeing-up your time.

Intentional design and clear bylaws will set the stage for a more efficient, productive and effective CTE advisory board.

To apply these concepts I will develop bylaws that clearly define roles, responsibilities, and expectations while allowing flexibility for updates, member input, and growth as the program and industry evolve.

I intend to craft bylaws that offer both clarity and adaptability. To do this, I will ensure that the essential structures—such as the board’s purpose, membership, meeting cadence, and roles—are clearly defined, while leaving space for innovation through optional subcommittees, flexible meeting formats, and renewable terms. I will also include a formal review process so the bylaws can evolve with the program’s needs. The goal is to create a living document that balances structure with responsiveness.

Sign In to comment