I spent about 12 years in the association world before joining Achurch. I’ve planned meetings, run operations, and served as an executive director, much of it at association management companies supporting multiple organizations at once. I know how associations work, how members think, and what staff do on a Tuesday afternoon.
Even so, the move to technology consulting made me question my competence. That second-guessing has a name: imposter syndrome. Conversations about integrations, data architecture, and API limitations move quickly, making it easy for imposter syndrome in association technology to seep in despite someone’s deep operational experience. In my work with association teams, I see the new person on a tech-focused team, the association generalist, and the sole woman on a tech team question whether their experience carries the same weight in a technical room. It does. As leaders we can help quiet the inner critic, so more voices are heard around association technology.
Why Technology Turns up the Imposter Syndrome Volume
Imposter syndrome is the persistent feeling that your success is undeserved and that you’re one question away from being found out. It’s remarkably common and technology seems to amplify it.
In a Hays survey of more than 8,000 professionals, 64% of technology professionals reported experiencing imposter syndrome at some point, a higher rate than any other industry surveyed. More than a third said it became more frequent as their careers advanced.
Why? A few reasons stand out:
- The vocabulary is a gatekeeper. Acronyms and jargon can make smart, capable people feel like outsiders in a conversation they are fully equipped to have.
- Continuous change. No one can know everything about technology, especially now that AI tools change month to month. Expertise always feels a step behind.
- Mistaking confidence for competence. The person who speaks most fluently about a platform isn’t always the one who understands its actual use.
When You Change Lanes, Not Careers
Moving from association staff work into technology consulting didn’t mean starting over. It meant bringing a different kind of expertise into a room built around a different vocabulary.
What I’ve learned is that “less technical” sounding knowledge is exactly what our clients need. A platform can do a hundred things. Whether staff and members will actually use those things depends on understanding renewal season, board dynamics, volunteer burnout, and the stubborn workaround someone built in a spreadsheet in 2014. That’s operational knowledge: You only get it by living it.
If you’ve made a similar move, from member services to a vendor, from events to IT, or from a generalist role into a specialist team, name what you bring rather than tally what you lack. The best technology teams include people with different skill sets and knowledge.
Women in Technology: a Familiar Feeling with a Long History
Psychologists Pauline Clance and Suzanne Imes coined “imposter phenomenon” in 1978 after studying high-achieving women. Nearly 50 years later, the pattern persists in tech. The same Hays research found 68% of women in tech have experienced imposter syndrome, compared with 61% of men. A study of 624 software engineers found a similar gap.
AI is adding a new layer. In research from iCIMS, just 14% of women said they felt prepared and confident to adapt to AI, compared with 27% of men.
This matters in our field because associations are a workforce where women hold many of the leadership and operations roles. When the people closest to members and day-to-day operations hesitate to speak up in technology decisions, organizations lose the very perspective that makes technology work. Feeling less confident is not the same as being less capable: That’s worth saying out loud.
The Accidental Technologist: Association Generalists who Own the Tech Stack
In many associations, especially smaller ones, no one was hired to be the “tech person.” The director of operations, the membership manager, or the executive director inherited the AMS, the LMS, the website, and the stack of integrations holding them together. They are now expected to evaluate vendors, approve contracts, and lead implementations, often without formal technical training.
That’s a setup practically designed for imposter syndrome. It can show up as:
- Deferring to vendors on decisions that should be driven by the organization’s own needs.
- Staying quiet in demos instead of asking the “basic” question everyone else is also wondering about.
- Avoiding the tech conversation altogether until a system is failing and the decision feels urgent.
- Over-preparing to compensate, spending hours researching before every meeting to avoid looking uninformed.
Here’s the reframe: you don’t need to know how an API is built to know what your members need from it. Your job is to understand the problem, the people, and the priorities. The technical details can be learned, translated, or delegated. The institutional knowledge you carry cannot.
Overcome Imposter Syndrome in Association Technology
For individuals:
- Ask the question. If you’re unsure what a term means, someone else in the room probably is too. A simple “Can you walk me through what that means for our staff?” moves the whole conversation toward what matters.
- Lead with the problem, not the platform. You may not know every feature, but you know where members get stuck and where staff lose hours. That’s the foundation of every good technology decision.
- Keep a “proof file.” Save the emails, outcomes, and wins that remind you why you’re in your role. It’s harder for the inner critic to argue with evidence.
- Learn in small, steady doses. Pick one system or concept a month to understand more deeply. Fluency builds faster than you think.
- Find your translators. Every team needs people who can bridge technical and operational language. Find them, learn from them, and eventually, become one.
For leaders:
- Make “I don’t know” safe. When leaders model curiosity, teams stop pretending.
- Invite operational voices into technology decisions early, not just at user acceptance testing.
- Define jargon in the room. A quick glossary at the start of a project can level the playing field for everyone.
- Recognize expertise in all its forms. Knowing members, workflows, and culture is expertise. Say so.
You Belong in the Room
Imposter syndrome is a feeling, not a fact. The operational perspective that can feel out of place in a technical conversation is often what helps a technology project land with the people it’s meant to serve.
Whether you’re new to a tech-focused team, a woman navigating a field that hasn’t always made space for you, or an association generalist who suddenly owns the tech stack, your experience counts. Technology decisions are better when more voices are part of them. So, ask the question, share what you know, and take your seat at the table.
Want to better understand how to help your team showcase their experience and strengths? Ask about how CliftonStrengths can improve team dynamics.