Jump to content

Membership Officer - Tracking: Difference between revisions

From Mensa Wiki
BethWeiss (talk | contribs)
m Created initial wow
BethWeiss (talk | contribs)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Words of Wisdom
{{Words of Wisdom
| wisdom  =  
| wisdom  =  
Track only what helps you take action.
Track only what helps you take action.   If you’re not using the information, you don’t need to track it.
 
| success =* You know which new members have been contacted and with what information
If you’re not using the information, you don’t need to track it.
* Follow-ups happen when appropriate
| success =  
* Information is easy to find
| best   =  
* The system is quick to maintain
* Another volunteer could understand it easily
| best =
* Track only information that supports action
* Keep notes brief and useful
* Use a system that can be maintained consistently
* Review tracking regularly
* Make it easy for another volunteer to understand
| pitfalls =
| pitfalls =
* Tracking more information than you use
* Creating overly complex systems
* Letting tracking become a task in itself
* Failing to update information consistently
* Storing information that is not relevant to membership work
}}
}}
== Purpose ==
== Purpose ==
Line 12: Line 24:


Tracking supports consistency, follow-up, and continuity — without creating unnecessary complexity.
Tracking supports consistency, follow-up, and continuity — without creating unnecessary complexity.
== Benefits of Tracking ==
A simple tracking system helps you:
* Remember previous interactions
* Avoid repeating the same message
* Suggest relevant events or connections
* Ensure follow-up opportunities are not missed
* Make it easier for another volunteer to step into the role
* Preserve continuity between volunteers
* Maintain consistent processes over time


== What to Track ==
== What to Track ==
Line 21: Line 50:
|-
|-
| New Members || Who joined and when they were contacted || Ensures timely welcoming   
| New Members || Who joined and when they were contacted || Ensures timely welcoming   
|-
| Outreach || Basic record of messages sent || Avoids missed or duplicate contact 
|-
|-
| Responses || Whether a member replied or engaged || Helps prioritize follow-up   
| Responses || Whether a member replied or engaged || Helps prioritize follow-up   
Line 30: Line 57:
| Notes || Brief, useful context (interests, preferences) || Keeps interactions personal   
| Notes || Brief, useful context (interests, preferences) || Keeps interactions personal   
|}
|}
== What NOT to Track ==
Avoid overcomplicating your system:
* Detailed interaction histories 
* Every message sent 
* Complex metrics or scoring systems 
* Information you won’t use 
Keep it light and actionable.


== Simple Tracking System ==
== Simple Tracking System ==
Line 53: Line 69:
* Be easy to understand   
* Be easy to understand   
* Take only a few minutes to maintain   
* Take only a few minutes to maintain   
Member information should be handled responsibly and shared only with those who need it for legitimate Local Group purposes.
== Example Tracking Fields ==
A simple tracking sheet might include:
{| class="wikitable"
! Member
! Joined
! Contacted
! Response
! Follow-Up Needed
! Notes
|-
| Jane Smith
| 6/1/2026
| 6/5/2026
| Yes
| No
| Interested in games
|}


== Basic Workflow ==
== Basic Workflow ==
Line 58: Line 96:
=== Weekly or Monthly ===
=== Weekly or Monthly ===


# Review new member report  
* Review new member report  
# Send welcome messages
* Send welcome messages
# Update tracking sheet  
* Update tracking sheet  
# Review responses  
* Review responses  
# Identify follow-up opportunities
* Identify follow-up opportunities


=== Ongoing ===
=== Ongoing ===


* Add new members as they appear 
* Add new members to your tracking list as they are added
* Update responses when they happen   
* Update responses when they happen   
* Keep notes short and useful   
* Keep notes short and useful   


== Using Tracking to Support Personalization ==
== What NOT to Track ==
Avoid overcomplicating your system by trying to add


Tracking helps you:
* Detailed interaction histories
* Every message sent
* Complex metrics or scoring systems
* Information you won’t use


* Remember previous interactions 
Keep it light and actionable.
* Avoid repeating the same message 
* Suggest relevant events or connections 
 
See:
* [[Making It Personal]]
* [[Scaling Personalization (Without Burnout)]]
 
== Using Tracking to Support Continuity ==
 
A simple system ensures:
 
* Someone else can step into the role if needed 
* Work is not lost between volunteers 
* Processes remain consistent over time 


== When to Simplify ==
== When to Simplify ==
 
The system should support your work — not create more of it.  If tracking feels like a burden:
If tracking feels like a burden:


* Reduce the number of fields   
* Reduce the number of fields   
* Focus only on new members   
* Focus only on new members   
* Remove anything you’re not using   
* Remove anything you’re not using   
The system should support your work — not create more of it.
== What Success Looks Like ==
* New members are consistently contacted 
* Follow-ups happen when appropriate 
* Information is easy to find 
* The system is quick to maintain 
* Another volunteer could understand it easily 
== Key Takeaway ==
Tracking is not about collecting data.
It’s about staying organized, consistent, and able to follow through.


== Related ==
== Related ==
* [[Membership Officer - Member Communication]]
* [[Managing Membership Outreach]]
* [[Making It Personal]]
* [[Making Personalization Sustainable]]
* [[Responding to Members]]
* [[Responding to Members]]
* [[Membership Officer - Templates and Samples]]
* [[Membership Officer Resources]]

Latest revision as of 02:21, 4 June 2026

Words of Wisdom

Track only what helps you take action. If you’re not using the information, you don’t need to track it.

What Success Looks Like

  • You know which new members have been contacted and with what information
  • Follow-ups happen when appropriate
  • Information is easy to find
  • The system is quick to maintain
  • Another volunteer could understand it easily

Best Practices

  • Track only information that supports action
  • Keep notes brief and useful
  • Use a system that can be maintained consistently
  • Review tracking regularly
  • Make it easy for another volunteer to understand

Common Pitfalls

  • Tracking more information than you use
  • Creating overly complex systems
  • Letting tracking become a task in itself
  • Failing to update information consistently
  • Storing information that is not relevant to membership work

Purpose

[edit | hide all | hide | edit source]

Provide a simple, sustainable way to track membership-related activity so nothing important is missed.

Tracking supports consistency, follow-up, and continuity — without creating unnecessary complexity.

Benefits of Tracking

[edit | hide | edit source]

A simple tracking system helps you:

  • Remember previous interactions
  • Avoid repeating the same message
  • Suggest relevant events or connections
  • Ensure follow-up opportunities are not missed
  • Make it easier for another volunteer to step into the role
  • Preserve continuity between volunteers
  • Maintain consistent processes over time

What to Track

[edit | hide | edit source]

Focus on a few key areas:

Area What to Track Why It Matters
New Members Who joined and when they were contacted Ensures timely welcoming
Responses Whether a member replied or engaged Helps prioritize follow-up
Follow-Up Who may need a second touch Supports connection without overdoing it
Notes Brief, useful context (interests, preferences) Keeps interactions personal

Simple Tracking System

[edit | hide | edit source]

A single spreadsheet is usually enough.

You do not need specialized tools.

Your system should:

  • Be easy to update
  • Be easy to understand
  • Take only a few minutes to maintain

Member information should be handled responsibly and shared only with those who need it for legitimate Local Group purposes.

Example Tracking Fields

[edit | hide | edit source]

A simple tracking sheet might include:

Member Joined Contacted Response Follow-Up Needed Notes
Jane Smith 6/1/2026 6/5/2026 Yes No Interested in games

Basic Workflow

[edit | hide | edit source]

Weekly or Monthly

[edit | hide | edit source]
  • Review new member report
  • Send welcome messages
  • Update tracking sheet
  • Review responses
  • Identify follow-up opportunities

Ongoing

[edit | hide | edit source]
  • Add new members to your tracking list as they are added
  • Update responses when they happen
  • Keep notes short and useful

What NOT to Track

[edit | hide | edit source]

Avoid overcomplicating your system by trying to add

  • Detailed interaction histories
  • Every message sent
  • Complex metrics or scoring systems
  • Information you won’t use

Keep it light and actionable.

When to Simplify

[edit | hide | edit source]

The system should support your work — not create more of it. If tracking feels like a burden:

  • Reduce the number of fields
  • Focus only on new members
  • Remove anything you’re not using
[edit | hide | edit source]