> For the complete documentation index, see [llms.txt](https://makeathon.mtflabs.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://makeathon.mtflabs.net/evaluating-a-makeathon/future-development.md).

# Future Development

<figure><img src="/files/XzzpsAELOlPndS24ABV0" alt=""><figcaption></figcaption></figure>

### **Identifying areas for improvement and future development**

Building on your success and working to constantly improve is an important step in ensuring the success of future Makeathons. Here are some ways to specifically identify these areas:

1. **Collect third party feedback**: In addition to the feedback you collect from participants, you can also ask partners, colleagues, sponsors, and other stakeholders about their experience of the Makeathon. Look for common themes and areas of concern that emerge from the feedback.
2. **Analyse your KPIs**: Identify areas where the actual results fell short of the desired outcomes and consider what changes could be made to improve these metrics in the future.
3. **Evaluate the program**: Evaluate the program of the Makeathon, including the activities, workshops, and speakers. Look for areas where improvements could be made, such as incorporating more diverse speakers, offering more hands-on activities, or providing more guidance to participants.
4. **Review the images**: Have a look at the photos and videos that you took. Do people look happy? Engaged? Is it the right environment? Does it need more colour? Would bright t-shirts, coloured lighting or decorations have added creative flair? What would you like to see in the background during the presentations?
5. **Review the budget**: Review the budget of the Makeathon and identify areas where savings could be made or where additional funding could be allocated to improve the event.
6. **Benchmark against other events**: Benchmark the Makeathon against similar events you are aware of. Look for areas where the Makeathon fell short in comparison and consider what changes could be made to improve its competitiveness.

By specifically identifying areas for improvement and future development, you can make targeted changes that will improve the success of future Makeathons.


---

# 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, and the optional `goal` query parameter:

```
GET https://makeathon.mtflabs.net/evaluating-a-makeathon/future-development.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.