> 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/measuring-ig-success.md).

# Measuring IG Success

**TLDR:** Success is not measured by activity count. It is measured by outcomes task completion rates, member level progression, quality of proof-of-work, and real-world impact.

Success is NOT measured by activity count. It's measured by outcomes:

* Task completion rates
* Member level progression (how many reached Level 5 & 6)
* Quality of proof-of-work (projects, open-source contributions)
* Impact of projects (portfolios, career placements, social value)
* Cross-IG collaborations initiated
* Bootcamp outcomes and participant satisfaction
* Member retention and engagement trends

### <mark style="color:$primary;">Quick Health Check Questions</mark>

* Are office hours happening consistently?
* Are task verifications happening within 24 hours?
* Are members progressing to higher levels?
* Is proof-of-work being created and showcased?
* Are you collecting feedback from members?
* Is mentorship happening?
* Are new members joining regularly?


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mulearn.org/ig-playbook/measuring-ig-success.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.