> For the complete documentation index, see [llms.txt](https://docs.mulearn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mulearn.org/ig-playbook/common-challenges-and-solutions.md).

# Common Challenges and Solutions

Every IG Lead faces common challenges low attendance, verification delays, inactive members, quality issues, difficulty finding mentors, and burnout. Here are practical solutions for each.

<mark style="color:$primary;">**Low Attendance at Office Hours**</mark>\
→ Promote 1 week in advance, survey members on preferred times, invite guest speakers, make content highly relevant.

<mark style="color:$primary;">**Task Verification Delays**</mark>\
→ Assign dedicated verifiers from your core team, set clear verification criteria, use a shared checklist.

<mark style="color:$primary;">**Inactive Members**</mark>\
→ Reach out personally, understand blockers, offer different task types, create mentoring pairs.

<mark style="color:$primary;">**Quality of Proof-of-Work**</mark>\
→ Provide clearer project briefs, break projects into phases, offer mentorship, share examples from other IGs.

<mark style="color:$primary;">**Difficulty Finding Mentors**</mark>\
→ Ask members for industry connections, reach out to alumni, partner with other campus clubs, contact local tech communities.

<mark style="color:$primary;">**Burnout as an IG Lead**</mark>\
→ Empower co-leads, distribute responsibilities, schedule breaks, communicate with cluster about workloads.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mulearn.org/ig-playbook/common-challenges-and-solutions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.