MEMBER INTELLIGENCE WORKSHOP MODULE
Member Expertise & Hidden Capability
Who in your membership could help—if you knew what they had done?
Make relevant experience, knowledge, and capabilities easier to understand so potential contributors extend beyond the people already known to staff.
Module 4 · Member Intelligence Workshop
Does this sound familiar?
The same names surface whenever someone needs expertise
Staff rely on familiar speakers, committee members, and established contacts because they have little visibility into what other members could contribute.
Job titles conceal the experience that matters
A directory shows someone’s current position but leaves out the projects, responsibilities, earlier roles, and practical knowledge relevant to your question.
Members have useful experience they have never been asked to describe
Someone has solved a similar problem, worked in another sector, or developed a valuable method, but that experience has no clear place in the member record.
Expertise lists contain labels without enough context
A profile says “leadership,” “AI,” or “operations,” yet staff cannot tell what the person actually did, under what conditions, or how that experience relates to the need.
Visible participation is mistaken for the full capability picture
Frequent contributors are easy to recognize. Members who attend less often or contribute elsewhere remain difficult to discover.
Potential expertise is confused with willingness to contribute
A person’s background appears relevant, but the organization does not know whether they want to share it, in what capacity, or under what conditions.
What is member expertise and hidden capability?
Member expertise is knowledge and experience relevant to a particular question, activity, or contribution.
Capability concerns what a person can do in context. Understanding it may require examining the work they performed, their responsibilities, the conditions involved, and the evidence available.
Hidden capability is relevant capability that the organization cannot readily see or interpret through its current records and relationships.
It may come from:
- Current professional work.
- Earlier roles or career stages.
- Projects and implementation experience.
- Technical or specialist practice.
- Research and investigation.
- Teaching, facilitation, or mentoring.
- Business ownership and independent work.
- Community and volunteer activities.
- Cross-sector experience.
- Practical problem-solving.
- Lessons from work that did not go as planned.
- Contributions made outside the membership organization.
Member Expertise & Hidden Capability helps participants examine those sources in relation to one real contribution need.
The aim is a clearer understanding of who may be relevant, why their experience matters, and what still needs to be confirmed.
A skill label needs a story behind it.
A member who lists “change management” may have led a company-wide transition, supported one team, researched the subject, taught a course, or participated in a change project.
Each experience may be useful. Its relevance depends on the question.
Before identifying a potential contributor, the organization may need to understand:
- What the person worked on.
- What they personally did.
- What responsibility they held.
- Which methods or tools they used.
- What conditions shaped the work.
- Which problems they encountered.
- What results or lessons they can discuss.
- How recently the experience occurred.
- What supporting information is available.
- Which parts can appropriately be shared.
- How the experience relates to the contribution needed.
- Whether the person is interested in that contribution.
Connecting capability to experience makes expertise easier to interpret and discuss.
It also helps avoid treating a broad label as a complete account of what someone can contribute.
Connect the contribution need to relevant experience.
Contribution Need
Question or problem
Intended audience
Contribution type
Relevant conditions
Expected responsibility
Member Experience
Roles and projects
Activities performed
Personal contribution
Methods and tools
Practical lessons
Capability Context
Knowledge applied
Skills used
Complexity and conditions
Recency
Relevance to the need
Evidence and Interpretation
Member explanation
Work examples
Outcomes and observations
Credentials or endorsements
Questions to confirm
Contribution Conditions
Interest in participating
Preferred contribution
Availability
Sharing boundaries
Appropriate next conversation
A useful expertise picture connects what the organization needs with what members have done, what that experience supports, and how they may wish to contribute.
How useful member expertise stays out of view
STAGE 1 — Members accumulate experience
People develop knowledge and capabilities through work, projects, learning, service, and changing responsibilities.
STAGE 2 — Membership records capture a narrow view
Directories and forms record current titles, employers, credentials, or broad interest categories.
STAGE 3 — Discovery depends on existing familiarity
When a need appears, staff turn to the people whose relevant experience they already know.
STAGE 4 — The contributor pool stays narrower than the membership
Useful perspectives remain undiscovered, familiar contributors receive repeated requests, and the organization has limited evidence about who else might help.
“Who knows about this?” needs a more specific question.
Expertise becomes easier to discover when the organization describes the contribution it needs.
A broad search for an “AI expert” could mean a researcher, a practitioner who introduced a tool, a leader who changed a workflow, or someone who can explain the topic to beginners.
“We need an AI speaker” can become:
“We want someone who has helped a small operational team introduce an AI tool and can discuss the implementation decisions, staff questions, and practical lessons with members considering similar work.”
That question gives participants a clearer basis for examining relevant experience.
The expertise review should clarify:
Describe the question, audience, activity, and responsibility involved. Distinguish speaking, advising, mentoring, reviewing, teaching, collaborating, and doing the work.
Identify the activities, situations, methods, or decisions that would help someone contribute meaningfully. Keep the connection to the actual need explicit.
Separate individual responsibility from the wider team’s work. Record whether the person led, performed, supported, observed, researched, or learned from the activity.
Examine scale, complexity, tools, setting, recency, and other conditions relevant to the contribution. Experience can transfer across contexts, but the connection may require explanation.
Consider the member’s account, examples, outcomes, credentials, endorsements, or other relevant sources. Record their limits and identify questions that require further review.
Clarify whether the person wants to participate, which contribution types interest them, and what availability or sharing conditions would matter.
Examine expertise across six dimensions.
Experience
Identify the work, projects, practice, or other activities behind the capability description.
Personal Contribution
Clarify what the individual did and the responsibility they held.
Capability
Describe the knowledge, skills, methods, or judgment used in that experience.
Context
Preserve the conditions, complexity, timing, and setting that affect relevance.
Evidence
Identify what supports the description and what remains unconfirmed.
Willingness
Distinguish potential relevance from interest, availability, and permission to participate.
Broaden discovery while preserving meaningful standards.
Experience worth making easier to discover
Relevant capability may be found in:
- Earlier roles omitted from a current directory.
- Practical implementation work.
- Projects outside the member’s current specialty.
- Volunteer and community responsibilities.
- Cross-sector experience.
- Independent or small-business work.
- Informal teaching and mentoring.
- Lessons from difficult or unsuccessful projects.
A familiar title or a prominent organizational role is not the only route to useful experience.
Questions that still need careful review
Before relying on a contribution, clarify:
- The relevance of the experience.
- The person’s actual responsibility.
- The strength and limits of supporting information.
- How current the knowledge needs to be.
- Whether the contribution requires a particular qualification.
- Whether confidential information would be involved.
- Whether the person wants to participate.
- Who is responsible for the final selection.
Broader discovery should give reviewers more relevant people to consider and better context for their decisions.
A current job title can hide an earlier contribution.
Imagine an association looking for members who can help others understand how to introduce a new operational system.
Staff initially identify several familiar technology leaders.
Another member, currently listed as a regional account manager, previously coordinated an implementation across several small sites. They helped staff prepare, documented recurring problems, and adjusted the rollout based on feedback.
Their current title does not reveal that experience.
A closer review asks:
- What did they personally coordinate?
- Which parts of the implementation did they understand directly?
- What conditions made the work difficult?
- What lessons could they responsibly share?
- What information supports the account?
- Would they be interested in a peer discussion or case example?
They may be a useful contributor for that purpose even if they would not describe themselves as a technology expert.
The exercise makes the connection visible and identifies what a follow-up conversation should confirm.
Capability and willingness answer different questions.
A member may have relevant expertise and no interest in speaking publicly.
They might prefer a small peer conversation, a written case example, occasional mentoring, or no contribution at this time.
Someone may also be interested in helping while needing preparation, support, or a narrower role.
The review records capability, contribution preferences, and availability separately. It identifies where an invitation or further conversation is needed without treating a profile as a commitment.
Designing the invitation and participation experience can follow through the relevant Member Engagement Workshop module.
Preserve the experience behind the description.
A capability summary is more useful when people can understand where it came from.
The selected example should retain a connection to the relevant activity, the member’s contribution, the source of the information, and any limits on interpretation or sharing.
An endorsement may support one aspect of an experience. A credential may establish a particular qualification. A work example may illustrate a method. Their meanings should remain distinct.
Ongoing maintenance of these records belongs in Member Intelligence Governance & Currency when deeper work is needed.
THE MATCHING WORKSHOP MODULE
Module 4: Member Expertise & Hidden Capability
This practical minicourse helps membership teams learn a repeatable method for discovering and interpreting relevant member experience.
Participants begin with one real contribution need. They identify what experience would matter, examine available member examples, and connect capability descriptions to the work behind them.
They then distinguish potential relevance from confirmed suitability, record evidence gaps, and identify the next conversation needed to understand contribution interest.
The exercise also establishes the experience, capability, evidence, and sharing relationships a subsequent Gobekli configuration would need to support.
This module helps your team:
- Define one contribution need clearly.
- Identify the experience relevant to that need.
- Look beyond current titles and familiar names.
- Connect capability descriptions to actual activities.
- Clarify the member’s personal contribution.
- Preserve context that affects relevance.
- Examine supporting information and its limitations.
- Recognize useful experience from different settings.
- Separate capability from willingness and availability.
- Identify questions requiring further review.
- Develop a focused expertise brief and discovery plan.
- Outline a potential experience and capability configuration.
What should happen when relevant experience becomes visible?
The module supports discovery and interpretation.
Clarify the Contribution Need
Define what the organization is asking someone to help with and for whom.
Expand Discovery
Identify additional sources and member populations that may contain relevant experience.
Examine the Experience
Understand what the member personally did and which conditions affect its relevance.
Confirm the Description
Identify the examples, explanations, or review needed to support a responsible interpretation.
Explore Contribution Interest
Ask whether the person wants to participate and which contribution types or conditions fit.
Route for Selection
Provide the responsible team with a contextualized expertise brief and the questions still requiring judgment.
The module supports discovery and interpretation. Invitations, appointments, and final contributor selection remain with the responsible organizational process.
What should a member expertise review examine?
The Need
What question, activity, audience, and contribution should the expertise support?
The Experience
Which roles, projects, activities, or situations provide relevant background?
The Individual Contribution
What did the member personally do, decide, develop, support, or learn?
The Capability and Evidence
What knowledge or capability does the experience suggest, and what information supports that interpretation?
The Contribution Conditions
Is the person interested, available, and able to share relevant information appropriately?
The Review and Next Step
Who needs to confirm relevance, examine qualifications where required, and determine whether to proceed?
Learn the method. Make one hidden capability easier to understand.
Bring one contribution need and a small set of member examples or profile records relevant to it.
STEP 1
Define the contribution
Describe the question, audience, activity, and responsibility involved. Connect it to the decision established through Member Intelligence Direction.
STEP 2
Identify relevant experience
List the activities, situations, methods, and practical knowledge that could support the contribution. Identify where that experience may be overlooked.
STEP 3
Examine the member’s actual work
Review available examples. Record the person’s activities, responsibilities, contribution, and relevant context separately from broad skill labels.
STEP 4
Connect capability to supporting information
Describe the capability the experience may support. Identify sources, evidence limits, and questions requiring confirmation.
STEP 5
Clarify interest and contribution conditions
Record what is known about willingness, preferred contribution, availability, and sharing boundaries. Identify the conversation needed to resolve unknowns.
STEP 6
Develop the brief and configuration outline
Document potential relevance, unresolved questions, responsible reviewers, and next steps. Specify the profiles and relationships a future implementation would need to preserve.
Participants leave with a Member Expertise & Capability Brief, contextualized member examples, a focused discovery and follow-up plan, and a starting configuration brief.
The output distinguishes potential contributors from people whose suitability and participation have been confirmed.
- Define the contribution.
- Identify relevant experience.
- Examine the member’s actual work.
- Connect capability to supporting information.
- Clarify interest and contribution conditions.
- Develop the brief and configuration outline.
FUTURE PRODUCT CONNECTION
Make experience discoverable without losing the story behind it.
The workshop identifies how member experience, activities, capabilities, and supporting information need to connect for a particular contribution purpose.
A potential TalentPass experience could help members describe relevant work and projects, clarify their personal contribution with Pythia, and organize supporting information.
Members could choose what to share through a purpose-specific profile into an appropriate TalentSync context. Organizational teams could then examine relevant experience alongside the contribution need and remaining review questions.
The starting configuration brief could identify:
- Experience records: roles, projects, professional practice, learning, service, and other relevant activities.
- Personal contributions: what the member did and the responsibility they held.
- Capability relationships: how knowledge, skills, methods, or judgment connect to those activities.
- Context: setting, complexity, tools, timing, and conditions affecting relevance.
- Supporting information: member explanations, work examples, outcomes, credentials, or endorsements with their distinct meanings.
- Purpose-specific profiles: selected experience presented for a defined contribution or organizational question.
- Organizational needs: the activities, audiences, and responsibilities for which expertise is being considered.
- Contribution preferences: interests in speaking, mentoring, advising, teaching, collaborating, or other participation.
- Sharing boundaries: what the member chooses to disclose and which audiences may use it.
- Human review: questions about relevance, qualifications, evidence, and suitability that require responsible judgment.
For example, an initial configuration might help members create profiles for sharing practical implementation experience with peers.
The implementation brief would define the initial use, member population, relevant experience structure, organizational reviewers, and criteria for assessing whether discovery becomes more useful.
PRODUCT AND DECISION BOUNDARIES
Keep experience, capability, qualification, and participation distinct.
A connected configuration should preserve the difference between:
- A broad skill label and experience using that skill.
- Participation in a project and responsibility for its outcome.
- Relevant experience and suitability for every related task.
- A member’s description and independently confirmed information.
- An endorsement and a formal qualification.
- A credential and permission to practice in a particular context.
- Potential relevance and final contributor selection.
- Capability and willingness to participate.
- Willingness and current availability.
- Sharing a profile and permitting unrestricted use of its contents.
Authorized organizational roles remain responsible for contributor selection and any qualifications or review required by the intended activity.
Product availability, configuration requirements, integrations, and any additional development would be confirmed during scoping.
The workshop produces a useful expertise brief and discovery plan independently of product adoption.
What to bring into the conversation
Begin with one situation where the organization needs expertise but tends to rely on the same familiar people.
A useful starting question is: “What experience would help here, where might it exist in our membership, and what would we need to understand before inviting someone to contribute?”
Useful inputs may include:
- The decision established through Member Intelligence Direction.
- A description of the contribution needed.
- The intended audience and purpose.
- Existing member directory fields.
- Sample member profiles or biographies.
- Examples of relevant projects or activities.
- Member-provided descriptions of experience.
- Available work examples or supporting information.
- Existing speaker, mentor, or contributor records.
- Relevant qualifications or selection criteria.
- Known limitations in current expertise discovery.
- Information about contribution preferences.
- Appropriate sharing or confidentiality boundaries.
- People responsible for reviewing relevance and selecting contributors.
Use member-authorized or de-identified examples where appropriate. A complete skills inventory is not required.
Where the exercise uses a composite example, record which assumptions would need confirmation through actual member input.
What this module can help your team produce
A Member Expertise & Capability Brief
A clear account of the contribution need, relevant experience, and capability descriptions that could support it.
Contextualized Member Examples
Structured examples connecting activities, personal contributions, conditions, and supporting information.
A Discovery and Follow-Up Plan
A focused approach to broadening discovery, resolving evidence gaps, exploring contribution interest, and assigning review responsibilities.
A Starting Configuration Brief
An outline of the experience records, capability relationships, supporting information, profiles, sharing choices, and organizational review needs a subsequent Gobekli implementation would require.
These outputs begin with the contribution need and examples examined during the module. Final scope depends on the available information, relevant participants, and decision established through Member Intelligence Direction.
Where might the work lead next?
Expertise discovery may reveal questions about member ambitions, existing contributions, or relationships through which knowledge could become more useful.
Member Goals, Needs & Career Transitions
Understand how a potential contribution relates to the member’s own goals, changing responsibilities, and preferred direction.
Participation & Contribution Visibility
Examine how existing contributions are recorded and understood, including the context they provide about member experience.
Member Relationships & Network Visibility
Understand the relationships through which relevant experience, peer support, and knowledge exchange may connect.
Findings may inform the Member Engagement Workshop when the next step concerns invitations and participation, or the Membership Value Workshop when the organization is designing ways for member expertise to create value.
Frequently asked questions
Questions membership organizations ask before beginning.
It is relevant capability the organization cannot readily see or interpret through its current records and relationships. It may come from earlier roles, projects, independent work, service, or experience outside the member’s current title.
A skill label names a capability area. Understanding expertise requires context about the person’s experience, activities, responsibility, and the contribution being considered.
A clear need establishes what experience matters and how it should be interpreted. Speaking to beginners, advising on a difficult implementation, and performing specialist work may require different backgrounds.
No. It applies a repeatable discovery method to one defined need and a manageable set of examples. The organization can expand the approach later where useful.
Yes. Earlier roles, community work, independent projects, and cross-sector experience may be relevant. The review examines the connection to the actual contribution rather than assuming relevance from the setting alone.
Some contributions can be supported by relevant practical experience and other evidence. Where a qualification is required, that requirement remains part of the review. The workshop does not treat every contribution as having the same qualification needs.
Ask what the individual actually did, decided, developed, supported, or observed. Preserve the wider team context and avoid attributing the complete outcome to one participant.
Useful sources may include a member’s detailed account, work examples, outcomes, observations, credentials, or endorsements. Each supports different conclusions and may have limitations.
It can provide a useful starting point. The review records its source and identifies what requires clarification or confirmation for the intended use.
Define the experience being sought and examine where current discovery methods may miss it. Use clearer questions and appropriate opportunities for additional members to describe relevant work.
No. Capability and willingness are separate. The organization should understand contribution preferences and conditions before treating someone as a prospective participant.
Participation & Contribution Visibility examines what members have contributed through relevant activities and how those contributions are recorded. This module examines the wider experience and capability that could be relevant to a new contribution need.
Network Visibility examines connections among people and groups. This module examines the experience and capability a person may bring. A network relationship can help discover expertise, but it does not establish that expertise by itself.
Include the people who understand the contribution need, current discovery methods, and relevant review criteria. This may involve membership staff, program leaders, subject specialists, and members contributing appropriate examples.
The exercise identifies the experience records, activities, capability relationships, evidence context, purpose-specific profiles, sharing choices, and review needs that should stay connected. These become a starting point for implementation scoping.
No. The expertise brief, contextualized examples, and discovery plan can be used with existing tools and processes. A Gobekli configuration is a possible continuation when its available capabilities fit the agreed needs.
Participants leave with a focused Member Expertise & Capability Brief, structured experience examples, a discovery and follow-up plan, and a starting configuration brief.
DISCOVER THE EXPERIENCE ALREADY IN YOUR MEMBERSHIP
Find relevant expertise beyond the familiar names.
Connect what members have done to the contribution your organization needs. Leave with clearer experience profiles, better review questions, and a practical discovery plan.
This module is part of Gobekli’s configurable Member Intelligence Workshop. Begin with Member Intelligence Direction, then select the modules that address your organization’s particular challenges.