You've been staring at the same error for two hours. The terminal keeps printing the same message. You've tried the obvious fixes. Now what?
Knowing when to stop searching solo and reach for help is one of the most valuable skills a volunteer tech lead can develop. This guide gives you a clear decision framework — when to search, when to ask, and when to hire.
Level 1: Search First (0–20 minutes)
Before asking anyone, try:
- Copy the exact error message into a search engine in quotes. Most errors have been seen before.
- Check the official documentation for the tool you're using. Many projects have a "Troubleshooting" or "FAQ" section.
- Check the project's GitHub Issues — search for your error. Someone may have filed a report with a solution.
If you find a fix, try it. If it works, write down what you did and why — this becomes your own knowledge base.
Move to Level 2 if:
- You've spent 20+ minutes and found nothing useful
- The search results assume knowledge you don't have
- The error message is too generic to search meaningfully
Level 2: Ask the Community (20 minutes – 2 hours)
Good places to ask:
- Project forums or Discord servers — most active open-source projects have one. Start at the project's official website — most tools link their community forum or chat from the documentation or README. This is where the people who wrote the software answer questions.
- Local makerspace or tech volunteer groups — someone nearby may have solved the same problem on similar hardware.
- Communities like r/selfhosted, r/raspberry_pi, or r/homelab — large, generally helpful communities for self-hosted tech.
How to ask well:
- Describe what you were trying to do
- Share the exact error message (copy-paste, not a paraphrase)
- Describe what you already tried
- Mention your OS, hardware, and software version
A well-framed question gets answered faster and teaches you more — and you often diagnose the problem yourself just by writing it out.
Move to Level 3 if:
- Your problem involves data loss, security, or a live system affecting people right now
- You've been stuck more than a day with no progress
- Community responses assume expertise you don't have
Level 3: Bring in a Professional
Some problems are beyond the scope of community support. Signs it's time to hire:
- The system holds sensitive data (client records, financial data, health information) and something is wrong with access controls or backups
- You need a guarantee of resolution — a community volunteer can offer advice, not accountability
- The problem is architectural (something that worked at small scale doesn't scale)
- You're regularly spending more than a few hours a week on maintenance that isn't improving
Hiring a consultant for a half-day to review your setup is often cheaper than weeks of stalled volunteer time. Look for a consultant who works with nonprofits; ask for a scoped discovery call before committing to anything open-ended.
Regardless of which level resolves the problem, one habit makes every future escalation faster:
The Meta-Skill: Documenting as You Go
Whether you solve something at Level 1, 2, or 3, write it down. A one-paragraph note in a shared doc — what broke, what fixed it, why — saves the next person hours of rediscovery. That next person is often future-you.
The goal is not to know everything. It's to build a system where your organization can answer its own questions over time.