I have seen excellent technology teams handed a nearly impossible assignment: “Transform the association.” They can select a system, manage an implementation, and solve difficult technical problems. They cannot, on their own, decide how the organization should create value or persuade every team to work differently.

Those are leadership decisions.

If the goal is a better member experience, membership, education, finance, communications, and technology need to work from the same picture of the member’s journey. If the goal is to use AI well, leaders need to decide which work should change, how staff will be supported, and what quality looks like. A vendor contract does not make those choices for you.

Start with a small group that has authority and direct knowledge of the work. Give them a specific outcome, such as making it easier for a new member to find the right education and community in the first 90 days. Let them map the experience, identify barriers, test changes, and bring decisions back to leadership.

Make one executive accountable for the result. Make the people who do the work part of the design. Give the board visibility into outcomes without asking it to manage the project.

The group also needs permission to challenge familiar boundaries. A new member does not experience your organization as separate departments; they experience one association. When an invoice, login, welcome email, and education catalog do not fit together, the member feels the friction even if each team met its own target. Give the cross functional group a way to resolve those gaps instead of sending every issue back into separate departmental queues.

Share progress in terms of what changed for members and staff. Did it take fewer steps to get help? Did staff spend less time fixing records or directing people to the right place? Those results build support for the next round of work. A system launch date may be a useful milestone, but it is not the outcome the organization is trying to achieve.

When responsibility is shared clearly, the technology team can do its best work and the organization can own the change it has asked for.

Try this with your team: Look at your largest active change initiative. Who owns the member or mission outcome, and who has authority to change the process across departments?

.orgSource helps associations connect strategy, operations, technology, and people. Start the conversation here: https://orgsource.com/